Index
Previous
Next

AspEdit manual      General

  • License: AspEdit is freeware.

  • Disclaimer: The user is responsible for verifying the correctness of all data entered into and generated by AspEdit.  The author declines any liability regarding the correctness of the data, or the consequences of their use

  • Contact: info@lbs.be

  • Installing AspEdit: copy the contents of the package in a folder. Don’t use certain Windows system folders which are read-only,  such as Program Files.  AspEdit will attempt to write in this folder, Windows will not allow that, and will block AspEdit.

  • Uninstalling AspEdit: just delete the AspEdit folder and its contents.  Nothing is written in the registry or Windows folders such as AppData.

  • Recovery in the case of problems: all settings are stored in the file AspEdit.ini.
    When this file would get corrupted, it may prevent AspEdit from starting up correctly.
    Close AspEdit, manually delete the ini file, and start AspEdit again.

  • Creating a new file:
    • Upon starting, AspEdit creates a blank document.  You can start editing it immediately, and then use “File – Save as” to store the edits.
    • Otherwise, use the “File - New“ menu command.
    • By importing an existing OpenAir file.

  • Editing airspace: use the controls at the right to add / delete / edit airspace areas.  See the List dialog box for details.

  • Units: the default units for coordinates and distance can be set via the List dialog box. They can be overridden for each airspace block individually.

  • Editing navaids, waypoints, countries: The same List dialog allows the editing of navaids, waypoints and country borders.

  • Importing NOTAMs: AspEdit can import NOTAMs from a text file containing NOTAMs in raw format. It will generate a text file containing only relevant NOTAMs, and an xml file containing all NOTAMs, allowing the same functionality as a standard airspace file (eg. graphical representation, export to OpenAir).

  • Data storage:  airspace file are xml files, using proprietary tags.  Although it is possible to edit the xml file manually or using any xml editor, it is advised not to do so.  If the formatting of the tags is not strictly adhered to, data loss can occur.

  • Generating OpenAir files:  data can be exported into OpenAir format by using the “File – Save as” command.   The properties can be set via the Export dialog box. This dialog box opens automatically every time the export command is used.