
                          BaseOps Version History




Version 7.371

    - Airspace profiles can now be exported to / imported from an
      external Microsoft Excel spreadsheet.  This capability is
      similar to the existing functionality for flight profiles.

    - As part of the Check Case functionality, a warning is now
      issued when a military training route (MTR) intersects with
      an avoidance area.  The check is three-dimensional, meaning
      that the MTR floor and avoidance area ceiling are
      considered when checking for a potential intersection.




Version 7.370

    - This version of BaseOps ships with version 3.2 of the MRNMap
      noise model. Changes in this new version of MRNMap:

        - MRNMap now supports military training route segments with
          asymmetrical widths (i.e., segments where the left and
          right widths are not equal).

        - MRNMap now supports military training route segments with
          a linear width variation.

        - Fixed MRNMap bug in the support of the version 3.0 .inx
          input file format which could result in the
          underprediction of calculated noise.

      BaseOps itself has been updated to remove various warnings
      relating to the above issues.

    - New noisefile data for the F-15EX and T-7 is included with
      NMap and MRNMap.

    - A readme file is now included with MRNMap that list certain
      limitations on allowable input files.  See the file
      Noisemap\MRNMap\Documentation\MRNMap_README_ArrayLimits.txt.




Version 7.369

    - All support for standard flight profiles has been removed
      from BaseOps. This was requested by AFCEC due to concerns
      about the quality of the standard profile library.

    - SlippyMap background map layers now support tiles delivered
      in encrypted https format (previously only unencrypted http
      format was supported). This is becoming important as more
      servers have recently begun requiring an https connection
      (in particular, the well-known ESRI SlippyMap servers
      recently made this change).

      If not explicitly specified, NMPlot will now use an https
      connection for SlippyMap. If you need to access a server
      that only supports http, then added "http://" to the start
      of the "Tile Server URL Prefix".

      See the "SlippyMap" section of the "Background Map Formats"
      chapter of the NMPlot User's Guide for more information.

    - Fixed bug that prevented Climb Angle from being shown for
      helicopter flight profiles.




Version 7.368

    - BaseOps is now a 64-bit application. This allows it to use
      more of your computer's memory, allowing the application
      to process larger datasets and display larger background
      maps.

    - BaseOps is now compiled using the Clang optimizing compiler,
      resulting in the application running significantly faster.




Version 7.367

    - In conjunction with AAM 3.1.0 or later, BaseOps now supports
      multi-fidelity grids: grids whose point spacing varies with
      location. The grid point spacing can be varied depending on
      the resolution required in any given region. For example,
      the resolution can be higher near runways and lower far from
      the airfield.

      See the "Setting Grid Properties" section of the "Running
      Cases" chapter in the BaseOps User's Guide for more
      information.

    - AAM noise modeling methodology includes the concept of the
      noise significance boundary, a 10 dB margin around the noise
      grid and all points of interest. It is recommended that all
      AAM arrivals and departures extend beyond this boundary to
      insure accurate noise calculations.

      BaseOps can now display the noise significance boundary on
      maps, and warn of any AAM flight profiles that fail to
      extend beyond it.

      See the "AAM Noise Significance Boundary" section of the
      "Editing Flight Profiles" chapter in the BaseOps User's Guide
      for more information.

    - When run using topography, AAM requires that all flight tracks
      and flight profiles be confined to the elevation grid's extend.
      This causes problems when converting legacy NMap cases to
      AAM, as it is customary for NMap arrivals and departures to be
      modeled with a final straight segment extending several hundred
      thousand feet.

      When creating AAM .ops files, BaseOps will now automatically
      trim arrival and departure tracks and profiles whose final
      straight segment extends beyond the elevation grid's extent.

      In addition, errors are now raised for other tracks and
      profiles that extend beyond the elevation grid. These will
      need to be fixed manually by the user.

    - BaseOps now runs correctly on computer systems with more than
      one screen/monitor.

      There is one restriction: all monitors must have the same
      display resolution (i.e., the same DPI/PPI/pixels per inch).

    - The standard Microsoft Windows color selection dialog box has
      been replaced with a custom version that supports the latest
      advances in color theory. See the "Color Control" section of
      the "Details of Various BaseOps Components" chapter in the
      BaseOps User's Guide for more information.

    - The mouse wheel can now be used to scroll the text pane (the
      text pane is the portion of the BaseOps user interface below
      the map, where the properties of objects such as tracks and
      profiles can be edited in text form).

    - When working with Shapefile, Raster, and DXF map layers, the
      last-used geographic coordinate system is remembered, and will
      be used as the default when new map layers of those types are
      created.




Version 7.366

    - The following changes have been made to the Noisemap
      distribution:

      - Includes a new version of NMap with a fix for noise contour
        ghosting errors that may appear along the runway heading.

      - Includes a new version of Flight01.dat with updates to the
        noise data, including F-16C GE-129 Block 50 noise data.

      - Includes a new version of MRNMap that fixes a problem with
        the onset-rate adjustment.

      - Includes a new version of Flight02.dat with numerous
        updates to the noise data, including estimate reference
        data for the F-16C F110-GE-129 Block 50 noise data.

    - Flight profile segments can now be copied and pasted between
      flight profiles.  When copying, you can select which subset
      of segment(s) and field(s) you wish to copy.  When pasting,
      you can select whether to overwrite existing segments or
      insert new segments.  This functionality is accessed using
      the new Copy Segments and Paste Segments buttons, which can
      be found in the Segments section of the text pane when
      editing a flight profile.  See the "Editing Flight Profiles"
      chapter of the BaseOps User's Guide for more information.

      This new functionality is also available for copying and
      pasting flight track segments, military operating area
      points, military training route segments, airspace profile
      altitude bands, and static profile segments.

    - When importing data from a BaseOps case file, you previously
      had to manually select every object (flight profile, flight
      track, runway, etc.) that you wanted to import.  Now, you can
      choose to automatically import linked objects.  This choice
      is made on the "Linked Objects" page of the"Importing from
      Noise Case File" dialog box.

      As an example, assume that the BaseOps case you are importing
      from contains a flight profile FP1, a flight track FT1, and a
      runway R1. Furthermore, assume that FP1 operates on FT1, and
      FT1 is associated with R1. Now assume that you have selected
      to import FP1. In this case, FT1 and R1 can be imported
      automatically; you don't need to manually select them.

    - When using the mouse to drag a flight profile point to
      another location on the associated flight track, the
      following improvements have been made:

      - In situations (such as an overhead break) where you have
        one section of flight track lying directly over another,
        preference is given to the section of track that is
        closest to the most recent track distance.  This makes
        it easier to keep to flight profile point on the desired
        section of the flight track.

      - When dragging a flight profile point across the boundary
        between two flight track sections (for example, where a
        curved track section joins a straight section), the
        profile point will snap to the join location, making it
        easier to graphically position a profile point exactly at
        the join location.

    - The flight profile segment table can now be automatically
      sorted by increasing flight track distance.  This
      functionality is accessed using the new Sort Segment Table
      button, which can be found in the Segments section of the
      text pane when editing a flight profile.  See the "Editing
      Flight Profiles" chapter of the BaseOps User's Guide for
      more information.

    - When editing a flight track on the map, you could previously
      drag the end of a straight segment preceded by a curved
      segment to change both the straight segment's length and the
      curve's angle. Now, you can modify this behavior.  Hold down
      Shift key while performing the drag to lock the angle and
      change only the length. Hold down the Ctrl key while
      performing the drag to lock the length and change only the
      angle.

    - When editing a flight track, magnetic headings can be
      displayed in the track segment table of the text pane.
      See the "Editing Flight Tracks" chapter of the BaseOps
      User's Guide for more information.

    - Improvements have been made to how BaseOps runs external
      noise models such as NMap.exe and AAM.exe.

      - When running a case, BaseOps displays a dialog box that
        presents status information.  This dialog box contains
        buttons to minimize the BaseOps window and cancel the
        run.  See the "Monitoring the Status of a Run" section of
        the "Running Cases" chapter in the BaseOps User's Guide
        for more information.

      - You can now select the initial state of the windows in
        which external noise models run (normal, minimized, or
        hidden), as well as the process priority (normal or below
        normal) at which they are run.  See the "External
        Noise Model Options" section of the "Running Cases"
        chapter in the BaseOps User's Guide for more information.

    - A new tool is available to apply a standard profile to
      multiple flight profiles.  To run the tool, select the
      target flight profiles in the list pane, then choose
      "Load Standard Profile Tool" in the "Tools" menu.

      For more information, see the "Using the Load Standard
      Profile Tool" section of the "Editing Multiple Objects
      Simultaneously" chapter in the BaseOps User's Guide.

    - A new tool is available to assign the same home view to
      multiple objects.  See the "Using the Home View Tool"
      section of the "Editing Multiple Objects Simultaneously"
      chapter in the BaseOps User's Guide.

    - The use of elevation and ground impedance can now be turned
      on or off in a scenario.  See the "Change Elevation and
      Ground Impedance Usage" section of the "Using Scenarios"
      chapter in the BaseOps User's Guide.

    - BaseOps' now autosaves cases more frequently.  You can
      change the autosave frequency on the "Autosave System" page
      of the "BaseOps Application Options" dialog box, accessed
      via the "Tools" menu.

    - Flight track types are now sorted by canonical order (arrival,
      departure, closed pattern, Interfacility).  If you prefer to
      maintain an alphabetical ordering, you can choose it on the
      "Sorting" page of the "BaseOps Application Options" dialog
      box, accessed via the "Tools" menu.

    - When displaying a CADRG background map, the CADRG map is
      temporarily turned off when the user zooms out to show a
      very large geographic area.  Previously, this would cause
      BaseOps to load such a huge amount of CADRG data that the
      program would crash.

    - Runway labels are now oriented to follow the aviation chart
      standard.

    - BaseOps now supports high-PPI (high pixel per inch, high
      resolution) monitors.




Version 7.365

    - When working with flight profiles, BaseOps can now
      optionally display the climb angle, climb rate, and
      duration of each flight profile segment.  See the
      "Editing Flight Profiles" chapter of the BaseOps
      User's Guide for more information.

    - When running a case, BaseOps creates a shapefile defining
      the noise contours.  Beginning with this version of BaseOps,
      a corresponding .prj file is also created that specifies
      the shapefile's coordinate system.  This should ease the
      import of contours into third-party GIS systems.




Version 7.364

    - BaseOps now supports a new noise model: AGM, the US
      Department of Defense's model of noise from airborne
      weaponry operations.

    - Update to the "INM-to-NMap Aircraft Code Table.txt" which
      corrects a typo in the entry for the VULCAN aircraft.

    - BaseOps can now process bitmap images in GIF format.

    - Fixed bug that caused BaseOps to crash when running an
      MRNMap case with no points of interest.




Version 7.363

    - BaseOps now supports changes to the way static profiles are
      specified in the latest version of AAM, which brings them in
      line with how NMap static profiles are specified.  AAM static
      profiles operation counts are now specified on a per-segment
      basis.  Also, each segment now has a "number of engines"
      parameter.

      Note that these changes necessitated an update to the AAM .ops
      file format.  Therefore, AAM .ops files created by this
      version of BaseOps can only be run using the latest version
      of AAM.

    - Static profiles can now be exported to / imported from an
      external Microsoft Excel spreadsheet.  This capability is
      similar to the existing functionality for flight profiles,
      but more extensive, as full round-trip editing of all
      static profile properties is possible.

    - BaseOps now supports flight dispersion for AAM aircraft.  This
      allows you to model aircraft operations that have a Gaussian
      probability distribution to the left and right of a flight
      track.  See the "Editing Flight Profiles" chapter of the
      BaseOps User's Guide for more information.

    - When editing static profiles, BaseOps now displays the
      associated static pad on the map.  The pad is drawn at the
      heading specified in the static profile.

    - Aircraft substitutions can now be made for aircraft that only
      appear in NMap's Static NOISEFILE.

    - The default impedance value for water has been changed from
      100,000 to 1,000,000 kPa-s/m^2.  Note that this change only
      affects new BaseOps cases.  Existing cases created using the
      old default value of 100,000 will retain that value unless
      manually updated.




Version 7.362

    - BaseOps now fully supports MRNMap version 3.0.  MRNMap is now
      included with the BaseOps distribution, and BaseOps can be used
      to run a complete MRNMap noise analysis case.

    - Training Profiles have been renamed to Airspace Profiles.




Version 7.36

    - BaseOps now supports NMap 7.3.  This new version of NMap is
      included with the BaseOps distribution.

    - BaseOps now supports AAM 1.4.13.  See the "Installing the
      Optional AAM Module" in the "Getting Started" chapter of the
      BaseOps User's Guide for information on using AAM with BaseOps.

      If you have been using previous versions of AAM with BaseOps,
      you should upgrade to the latest versions of both programs.

    - New NMap and/or AAM noise metrics are now supported:

          - PA (probability of awakening)
          - LEQxx (LEQ for a selected number of hours)
          - ALM (Lmax for a selected flight or static profile)
          - SEL (SEL for a selected flight profile)
          - NAxxxALM (number of events above specified ALM level)
          - NAxxxSEL (number of events above specified SEL level)
          - TAxxxALM (time above specified ALM level)

      See the NMap and AAM documentation for more information.

    - BaseOps now supports the entry of noise level reductions
      (for both windows open and windows closed) for each point
      of interest.  These values are used when calculating the
      new Probability of Awakening noise metric.

    - BaseOps now supports the entry of AAM static profiles.

    - BaseOps now supports a new AAM aircraft category: FixedWing.
      It is similar to the FixedWingVectoredThrust category, but
      assumes a thrust vector angle of zero.  For more information,
      see the comments in the file "AAM\Default AAM Aircraft.txt".

    - For AAM and RNM aircraft, BaseOps warns if the roll angle is
      inconsistent with the direction the aircraft is turning.

    - When used with AAM in topography mode, BaseOps now warns about
      inconsistencies in the extent of the noise, elevation, and
      ground impedance grids.

    - A new tool is available that converts NMap flight profiles
      into AAM profiles.  See the "Using the NMap-to-AAM Flight
      Profile Conversion Tool" section of the "Editing Multiple
      Objects Simultaneously" chapter in the BaseOps User's Guide.

    - BaseOps now supports the elevations fields of runways,
      VTOL pads, and static pads.

    - The latest version of NMPlot, included with the BaseOps
      distribution, features an update to the "Grid Computation"
      and "Point of Interest Computation" mouse tools.  These
      tools now work for grids created from combined NMap/AAM
      BaseOps cases.  When using these tools on combined grids,
      NMPlot will run both noise models and combine the resulting
      output files as necessary.

    - BaseOps now has a batch-mode command-line option to create
      all of the noise model input files (i.e., all .ops, .opx,
      .ins, and .inx files) for a BaseOps case.  See the discussion
      of the -makeopx flag in the "Command-Line Options" chapter
      of the BaseOps User's Guide for more information.

    - The NOISEFILE aircraft noise database has been updated.




Version 7.358

    - BaseOps now ships with MRNMap version 3.0.  BaseOps support
      for MRNMap is currently limited.  BaseOps can create MRNMap
      input files, but cannot run MRNMap -- the model must be run
      manually from the command line.  In addition, certain steps
      must be taken to activate MRNMap support in BaseOps, but
      these steps will deactivate support for NMap -- BaseOps can
      be configured to run either NMap or MRNMap, but not both at
      the same time.  See the ReadMe.txt file in the Noisemap\MRNMap
      directory for more information.

      This is a temporary situation.  A future version of BaseOps
      will fully support MRNMap, at which time NMap and MRNMap will
      work together seamlessly.

      If you do not intend to use MRNMap, you can ignore this issue.
      As shipped, BaseOps and NMap will work together as they always
      have.

    - By popular demand, the method of panning a map with the
      mouse has been changed.  The old 'center on click' pan tool
      has been replaced with a 'grabbing hand' pan tool.  This
      bring BaseOps into line with how panning is done in most
      other software.




Version 7.357

    - Previous versions of BaseOps imposed the restriction that the
      first segment of all departure flight profiles must have a
      height of 0 feet above the airfield reference point.  This
      restriction has been lifted to support cases with multiple
      airfields at different elevations.




Version 7.356

    - For RNM and AAM flight profiles, BaseOps now allows multiple
      flight profile points with the same track distance.  This
      is used to model aircraft that are flying vertically (for
      example, a helicopter ascending vertically).

    - When saving flight profiles to the standard profile library,
      you now have the option of savings MSL heights.  Previously,
      any MSL heights in the profile were automatically converted
      to AGL.

    - The default height for points of interest is now 5 feet
      above ground level.




Version 7.355

    - Second beta version of BaseOps with Advanced Acoustic Model
      (AAM) support.  New features include:

        - Editing flight profiles for AAM helicopter,
          tilt-rotor, and vectored thrust aircraft

        - Support for new noise metrics, such as Time Above

        - Creating AAM .OPS input files

        - Running AAM from within Noisemap

        - Support for cases containing a mix of NMap, RNM,
          and AAM operations, with automatic summing of
          combined grid

        - Opening and importing from legacy AAM .OPS files

        - Aircraft substitutions work with AAM aircraft

        - Reports, symbols, flight profile tables, quick add,
          etc. are updated to support new AAM parameters such
          as thrust vector angle and aircraft configuration

        - Support for AAM's NOTERRCHECK keyword

        - NMPlot's "Grid Computation" and "Point of Interest
          Computation" mouse tools now work with AAM grids

        - Migration of NOISEFILE numeric power settings to
          AAM aircraft in flight profiles.

    - BaseOps can display a graph of distance verses height
      for flight profiles.  Press the "Show Profile Height
      Graph" button at the bottom of the text pane while
      editing a flight profile.

    - Fixed bug that can cause BaseOps to issue a misleading
      error message when long navigational aid names are used.

    - When exporting contours to an ESRI Arc/Info Shapefile,
      the accompanying metadata file previously had the
      extension of ".xml".  This file now has the extension
      ".shp.xml", which tells ArcMap that the xml file is
      associated with that shapefile.




Version 7.354

    - Beta version of BaseOps with AAM support.




Version 7.353

    - Elevation and ground impedance grids created by previous
      versions of BaseOps were incompatible with some versions
      of NMap.  This has been corrected.




Version 7.352

    - BaseOps can now handle National Elevation Data (NED) datasets
      that have internal void areas of missing elevation data.

    - When editing the noise calculation grid properties, the area
      covered by the grid is now shown on the map.

    - The version of NMPlot distributed with BaseOps has been updated
      to fix bug that could occur when combining multiple grids
      created by INM.  If this bug was triggered, NMPlot would
      enter an endless loop and never finish combining the grids.




Version 7.351

    - Updates to BaseOps' elevation and ground impedance support:

        - BaseOps can now calculate ground impedance grids
          based upon an elevation grid.  Locations where the
          elevation is less than a user-supplied threshold
          value are assumed to be covered with water.

        - Fixed bug that could cause a fatal error when creating
          elevation and ground impedance grids.




Version 7.35

    - BaseOps now includes support for creating, editing, and
      viewing the elevation and ground impedance grids used by
      the NMap and RNM noise models when they are run in
      topography mode.  This support includes:

        - Ability to import elevation data from:
            - National Elevation Dataset (NED) files
            - Shuttle Radar Topography Mission (SRTM) files
            - Noisemap .elv files

        - Ability to import ground impedance data from:
            - National Land Cover Data (NLCD) 2001 files
            - USGS Digital Line Graph (DLG) Hydrography files
            - Noisemap .imp files

        - Ability to manually enter and edit elevation and
          ground impedance data.

        - Ability to view and edit a library of ground
          impedance values for common ground covers (for
          example, water, grass, and asphalt).

        - Real-time display of the elevation and ground
          impedance at the map location under the mouse cursor.

      For more information, see the "Editing Elevation and
      Ground Impedance Data" chapter of the BaseOps User's Guide.

    - BaseOps now supports bitmap background maps in the Albers
      Conical Equal Area projection.




Version 7.34

    - For flight profiles where the aircraft conducts a
      pre-flight static runup, the way in which the runup power
      is entered has been changed.

      Recall that the runup power is specified in the first row
      of the flight profile's segment table.  Previously, when
      entering the runup power, BaseOps would display the
      available flyover operation power descriptions (OPCs).  The
      user would select the most appropriate flyover OPC.  Later,
      when running the case, BaseOps would select the static OPC
      that most closely matched the user's choice.

      In some situations, the algorithm used by BaseOps to select
      the matching static OPC yields non-optimal results.

      Therefore, the way in which the runup power is entered has
      been changed.  Now, when entering the runup power, BaseOps
      displays the available static operation power descriptions.
      The user selects the most appropriate OPC from the list of
      available static OPCs.

    - For interfacility flight profiles, pre-flight static
      runups are now performed only if the initial airspeed
      is zero.  This allows interfacility tracks to be used in
      a manner similar to INM's overflight tracks.

    - Fixed bug with XY coordinate transformations when using a
      rotation angle of 90 or 270 degrees.




Version 7.33

    - Fixed bug in BaseOps' filtering capability.




Version 7.32

    - BaseOps now includes a tutorial lesson set.  To view the
      lesson index, choose "Tutorial" from the "Help" menu.

      The tutorial is intended primarily for base planners.
      The lessons cover how to use BaseOps to perform common tasks
      faced by a base planner, such as analyzing a noise complaint
      location.  The lessons assume that an up-to-date BaseOps
      case for the base is available.

      The lessons provide step-by-step instructions.  Each lesson
      includes short video clips that illustrate how to perform
      the steps.




Version 7.31

    - Aircraft substitutions are now supported.  When creating a
      BaseOps case, you may need aircraft that are not present in the
      standard aircraft library.  To handle this situation, BaseOps
      now allows you to define aircraft substitutions that
      associate new aircraft names with equivalent proxy aircraft
      that are in the library.  For more information, see the
      "Defining Aircraft Substitutions" chapter of the BaseOps
      User's Guide.

    - BaseOps now supports Undo/Redo.

    - An Add mouse tool is now available that allows you to add data
      by clicking on the map.  You can add new point-type objects,
      such as static pads and points of interest.  You can also add
      new profile points to flight profiles.  For more information, see
      the "Add Mouse Tool" section in the "Working with the Map Pane"
      chapter of the BaseOps User's Guide.

    - When you select a flight track or flight profile segment on the
      map, the corresponding row in the text pane segment table is
      selected, and vice versa.  The text pane segment table now has
      a triangular icon to indicate the selected segment.

    - BaseOps now supports avoidance areas.  See the "Editing
      Avoidance Areas" chapter in the BaseOps User's Guide.

    - BaseOps now supports waypoints.  You can display waypoints on
      a map, and import them from DAFIF.

    - You can now select the units (seconds, minutes, or hours) used
      to specify time durations (for example, flight profile runup
      times).  See the "Units" page of the "BaseOps Case Options"
      dialog box.

    - BaseOps now gracefully handles BaseOps cases that have
      unrecognized aircraft, engines, noise suppressors, and/or power
      units.

      Consider the following example.  Suppose a user adds a new
      aircraft to the Noisefile database, creates a BaseOps case
      that uses the new aircraft, then e-mails the case to a
      colleague who doesn't have the updated Noisefile database.

      Previously, the colleague would have been unable to open the
      BaseOps case.  If they tried, BaseOps would terminate with an
      error message.

      Now, using the latest version of BaseOps, the colleague would
      be able to open and edit the case.  They would not, however,
      be able to run the case without the missing Noisefile data.

    - The way operation scaling factors are entered has changed.
      Previously, scaling factors were entered as percentages (scale
      number of operations by 30%).  They are now entered as
      multiplicative factors (multiply number of operations by 0.3).
      This new method should be less ambiguous.

    - BaseOps now issues an error message if an RNM case is run with
      a grid size greater than 499 grid points in either the X or Y
      direction.  If a grid larger than this limit is run, the RNM
      noise model will run without producing an error message, but
      will silently truncate the grid to 499x499 grid points, and
      will place the grid in the wrong location.

    - If a BaseOps cases contains RNM aircraft, BaseOps now warns
      about points of interest with heights less than 1 foot.  RNM
      sometimes crashes if points of interest have near-zero heights.

    - Fixed bug whereby BaseOps would crash if a departure flight
      profile's aircraft conducted pre-flight runups, but Noisefile
      did not contain any static data for that aircraft.  BaseOps now
      gives an error message about the missing static data.

    - Windows XP or Vista is now required to run BaseOps.  The Windows
      95, Windows NT, and Windows 2000 operating systems are no longer
      supported.




Version 7.3

    - BaseOps now supports RNM cases that use topography and ground
      impedance.




Version 7.299

    - Fixed bug: BaseOps would crash when computer was connected to a video
      projector.




Version 7.298

    - BaseOps can now read a georeferenced bitmap map layer whose image is
      stored in Windows Bitmap (.BMP) format with a color depth of 1 bit per
      pixel.  Previously, only color depths of 8 and 24 bits per pixel were
      supported.

    - Improved error messages when reading ESRI ARC/INFO world files.




Version 7.297

    - BaseOps can now import a wider range of DXF background map files.




Version 7.296

    - Fixed bug: BaseOps would crash when importing runways from DAFIF (Digital
      Aeronautical Flight Information File).  This was due to DAFIF runways
      whose width exceeded the NMAP-imposed maximum of 999 feet.  BaseOps now
      clips runway widths to a maximum of 999 feet when loading DAFIF runways.

    - Full screen mode is now supported.  In full screen mode, BaseOps's main
      window expands to fill the screen.  Various elements, such as the title
      bar, the main menu, and the Microsoft Windows task bar, are hidden.  Use
      full screen mode to gain the maximum possible working area for editing a
      BaseOps case.

      To enter full screen mode, press Ctrl+F11, or select "Full Screen" from
      the "Edit" menu.  To leave full screen mode, press Ctrl+F11, or press the
      "Exit Full Screen" button on the toolbar.

      Even though the main menu is hidden in full screen mode, you can access it
      using keyboard shortcuts (for example, Alt+F to access the "File" menu).

      Even though the task bar is hidden in full screen mode, you can switch to
      another application using Alt+Tab.




Version 7.295

    - When the user either runs or checks a BaseOps case, a report containing
      the results is displayed in the BaseOps text pane.  If the text pane was
      hidden when the case was run or checked, the report would not be visible,
      which was confusing.  BaseOps now automatically unhides the text pane in
      this situation.




Version 7.294

    - BaseOps can now import .BPS files containing static profiles with no
      power segments.

    - Fixed bug: BaseOps would crash when running a case if an airspeed above
      999 kts was entered.  BaseOps now limits airspeeds to <= 999 kts, so as
      not to overflow the space available for airspeed digits in the OPS file.




Version 7.293

    - Fixed bug: BaseOps sometimes crashes when displaying a "Flight Profile
      Operations Summary" report if there are flight profiles with undefined
      flight tracks.




Version 7.292

    - Fixed bug: map scales were incorrect in reports that were exported as
      HTML web pages.




Version 7.291

    - Fixed bug where BaseOps would confuse the destination and origin runways
      of an interfacility flight track when creating an NMap OPS/OPX file.

    - Two bugs have been discovered in the NMap noise model.  Both of these bugs
      cause NMap to crash with a cryptic error message.  Until these bugs are
      fixed, BaseOps has been configured to warn about conditions that can
      trigger these bugs.  These two conditions are:

        - Flight profiles with segments less than 100 feet in length.

        - Cases that contain only helicopter operations (a case must contain at
          least one fixed-wing aircraft operation).




Version 7.29

    - Changes to exporting/importing profile operations to/from spreadsheets.
      See the "Editing Flight Operations With a Spreadsheet" chapter in the
      BaseOps User's Guide.

        - Exported spreadsheet rows are now grouped by aircraft and flight track
          type.

        - Additional columns are exported.  The new columns contain spreadsheet
          functions that calculate the total number of operations, Day/Evening/
          Night percentage splits, subtotals, and total operation percentage
          splits for the profiles within each aircraft/track-type group.

        - The file format used to export and import spreadsheets has changed.

          Previously, a tab-delimited text file format was used.  However, using
          this format, it is not possible to export spreadsheets that include
          functions.  Also, this format does not allow cells to be marked as
          containing text, so Microsoft Excel interprets some names (such as
          35E2) as exponential notation numbers.

          Therefore, the XML Spreadsheet file format is now used to export and
          import spreadsheets.  This format is supported by recent versions of
          Microsoft Excel.

    - BaseOps now maintains a history of the major events that occur while
      editing a case.  BaseOps can be configured to automatically record major
      events as they occur.  Alternatively, you can maintain the case history by
      manually adding and editing case history events.  See the "Using Case
      History" chapter in the BaseOps User's Guide.

    - The .baseops case file format has changed.  Data in the new file format
      is compressed, so case files are much smaller.  They also take much less
      time to read and write.

      Existing BaseOps cases will be automatically converted to the new format.

    - BaseOps now checks for flight profiles with too many distinct power
      settings.  The NMap noise model currently limits the number of Omega10
      records associated with a flight profile to 9.




Version 7.284

    - Corrected bug: when opening a case on some Windows 95/98/Me systems,
      BaseOps would crash with the error message "Function CreateFile Failed,
      The parameter is incorrect".




Version 7.283

    - BaseOps can now create a flight profile operations summary report that
      shows, among other information, the breakdown of flight operations by time
      period (day, evening, night) and runway.

      To view the new report, choose "Reports" from the dropdown item type
      selector in the upper-left corner of the BaseOps window.  Then print or
      print preview the "Flight Profile Operations Summary" report.

    - Reports can now be exported to either HTML or text files.  These files can
      then be imported into third-party applications such as word processors.

      To export a report, choose "Export Report to File" from the "File" menu.
      See the "Creating Reports" chapter in the BaseOps User's Guide for more
      information.

    - Reports can now be viewed on the screen (in a format more suited for
      on-screen reading than print preview).  Select the report, then press the
      "View Report" button.

    - For reports that contain maps, you can now control whether the map legends
      include a graphical map scale and a north arrow.  See the "Map Options"
      section of the "Creating Reports" chapter in the BaseOps User's Guide.

    - Changes to exporting/importing profile operations to/from spreadsheets.
      See the "Editing Flight Operations With a Spreadsheet" chapter in the
      BaseOps User's Guide.

        - When importing operations from a spreadsheet, columns are now
          specified using letters ('A', 'B', 'C'...) to match the way
          spreadsheets such as Microsoft Excel label columns.

        - When importing operations, you can optionally choose to import flight
          tracks.  A spreadsheet column containing flight track names is
          specified, and the flight profiles in the BaseOps case are updated to
          use these tracks.

        - When importing flight operations from a spreadsheet, BaseOps ignores
          any rows that have a blank flight profile name. This allows you to
          have rows in your spreadsheet (that contain, for example, operations
          count subtotals) that are ignored when importing.

        - Can now include profile long names when exporting to the spreadsheet.

    - When BaseOps opens a case, it now locks it to prevent it from being opened
      a second time.

    - BaseOps now queries you for your contact information the first time it is
      run.  You can also edit the contact information by selecting "Application
      Options" from the "Tools" menu, then going to the "Contact Information"
      page.

      Currently, this contact information is used for only one purpose: to
      identify the person who currently has opened a BaseOps case, so that if a
      second person tries to open the case on a network drive and finds it
      locked, they can identify who has it open.

      In the future, other uses are planned for this contact information,
      including:

        - initializing case contact information when a new case is created.

        - supporting case history (a record of who, when, and how a case was
          modified.

    - Miscellaneous small changes

        - Can now sort and filter profiles by engine and noise suppressor.

        - When selecting aircraft of interest while setting filter options,
          only those aircraft in the case are displayed.  Previously, all
          aircraft were displayed.

        - On the flight profile page, the length of the selected flight track is
          now shown.

        - Exponential notation is no longer used for displaying/setting the
          number of flight and static operations.

        - The "Rename" command on the "File" menu has been changed to "Save As".

    - Corrected bug that would cause BaseOps to crash with a "Not enough memory"
      error after using print preview for a long time.

    - Partially fixed bug where a bitmap background map layer disappears if you
      zoom in too far.  This bug has been fixed for Windows XP, 2000, and NT
      systems.

      For Windows 95, 98 and Me systems, this bug would be quite expensive to
      fix.  Therefore, at this time, there are no plans to correct it on these
      systems.




Version 7.282

    - When importing objects from BaseOps cases, you can now add a prefix and/or
      suffix to the short name of every imported object.

      Previously, you could add a prefix and suffix to the long name, but not
      the short name.

    - Corrected bug: Error message when running case if "Compute points of
      interest" is checked but no points of interest are defined.




Version 7.281

    - The method used to specify NMap aircraft power settings has been changed.

      In the previous version of BaseOps, the Noisefile interpolation curve was
      selected by choosing either "Clean" or "Dirty".  However, for some cases,
      this method was found to produce unintuitive results.  Therefore, the
      interpolation curve is now selected using operation power descriptions
      such as "Arrival" and "Cruise".

      The "Clean" and "Dirty" settings have been retained as "Variable" and
      "Parallel", respectively.  Therefore, expert users can still directly
      select the noise interpolation curve.  However, most users should instead
      use the operation power descriptions.

      Existing cases that were created using "Clean/Dirty" will now appear as
      "Variable/Parallel".  It is recommended that you update these cases to use
      operation power descriptions.

      See the "Editing Flight Profiles" and "Editing Static Profile" chapters
      of the BaseOps User's Guide.

    - When .BPS files are imported, the power settings of flight and static
      profiles are now imported using operation power descriptions.  Previously,
      there were imported using "Clean/Dirty".

    - When editing flight and static profiles, information about the applicable
      Noisefile records is displayed.

    - Every flight and static profile segment now has a "Notes" field associated
      with it.  You can use these notes to, for example, record the gear and
      flap settings for each flight profile segment.

    - Flight profile point labels can now contain the following symbolic fields:

        - the numeric portion of the power setting (for example, "95")
        - the power units (for example, "%RPM")
        - the operation power description portion of the power setting (for
          example, "Arrival")
        - the full power description with units (for example, "95 %RPM Arrival")
        - the full power description without units (for example, "95 Arrival")
        - the notes associated with the profile point

      Previously, only the full power description with units symbol field was
      available.




Version 7.28

    - You can now delete, duplicate, print, and print preview more than one
      object at a time.  See the "Selecting Multiple Objects" section of the
      "Working with the List Pane" chapter in the BaseOps User's Guide.

    - You can now copy and paste objects (runways, flight tracks, etc.) between
      BaseOps cases.  In the source case, select one or more objects in the list
      pane, then choose "Copy" or "Cut" from the "Edit" menu.  Then go to the
      destination case and choose "Paste" from the "Edit" menu.

    - You can now import information from other BaseOps cases (i.e., from
      .baseops, .bps, .ops, and .opx files).  You can choose exactly what subset
      of a case's information you wish to import (for example, just import
      closed pattern F-16 flight profiles).  See the "Importing Information from
      BaseOps Cases" chapter in the BaseOps User's Guide.

    - Several tools are now available for editing objects en masse.  For
      example, you can change the flight track of multiple flight profiles in a
      single operation.  See the "Editing Multiple Objects Simultaneously"
      chapter in the BaseOps User's Guide.

      The available tools allow you to:

        - Set linked object fields: for example, set the flight track field of
          flight profiles, or set the static pad field of static profiles.

        - Set applicable groups: for example, set the A/C Category field of
          flight profiles.

        - Set the level-flight pattern altitude of closed pattern flight
          profiles.

    - BaseOps now uses an improved method for mapping grid XY coordinates to
      geographic locations.  The new method is more accurate, especially at
      higher latitudes.

    - BaseOps now supports bitmap background maps in the following projections:
        - Lambert Azimuthal Equal Area
        - Stereographic




Version 7.27

    - When BaseOps runs a case, it now creates a final noise grid for each
      scenario.  The final noise grid contains additional metadata beyond
      what the NMap and RNM noise models produce, such as more detailed
      information about the parent BaseOps case, and more detailed attribute
      information for the flight tracks, points of interest, etc.

      In addition, if the BaseOps case contains both NMap and RNM aircraft,
      the final noise grid will contain the sum of the NMap and RNM noise
      grids.  The user no longer has to manually create the summed grid.

    - When BaseOps runs a case, it now automatically exports noise level
      contours to a file in ARC/INFO Shapefile format.  This capability is
      provided as a convenience to those users whose contouring needs are
      relatively straight-forward.  User with more demanding needs can still
      use NMPlot to create contour shapefiles.

      To set contour options, choose "Contours" from the dropdown item type
      selector in the upper-left corner of the BaseOps window.

    - When BaseOps creates a noise contour shapefile, it also creates a
      metadata file containing information about the shapefile.  This metadata
      file conforms to the Federal Geographic Data Committee's Content Standard
      for Digital Geospatial Metadata (FGDC-STD-001-1998).

      To view and edit the metadata, choose "Contours" from the dropdown item
      type selector in the upper-left corner of the BaseOps window.

    - Contact information (name, organization, address, etc.), an abstract (a
      narrative summary of a BaseOps case), and a purpose (a brief description
      of the reason that a case was created) can now be entered into a BaseOps
      case.  Choose "Case" from the dropdown item type selector in the upper-
      left corner of the BaseOps window.




Version 7.26

    - The maximum duration of a static profile segment was decreased to 99999
      seconds.  This is due to a limitation of the .OPS/.OPX file format, which
      only allows 5 digits for this value.

    - When editing a flight profile, the profile's flight track is now drawn in
      the editing color.  This makes the flight profile's track stand out from
      other tracks that may be shown in the background.




Version 7.25

    - When importing cases created by previous BaseOps versions (ie, .BPS, .OPS,
      and .OPX files), the long name of flight tracks, flight profiles, and
      static profiles is set equal to the first comment line.




Version 7.24

    - When checking a case, BaseOps warns about NMap flight profiles with
      flight tracks anchored by VTOL pads.  Since NMap does not currently
      support VTOL pads, any flight tracks used by NMap aircraft must be
      anchored by runways.

    - When running a case, BaseOps now checks for scenarios that perform an
      inconsistent set of changes to a case.  An example would be a scenario
      that deletes a flight track but not the flight profiles that use it.

    - BaseOps now contains a workaround to a limitation of NMap.  NMap does not
      handle runways with names containing lower-case letters.  To work around
      this limitation, BaseOps now converts runway names to all-upper-case when
      creating NMap OPS/OPX files.




Version 7.23

    - When checking a case, BaseOps warns about flight profiles that extend
      significantly (i.e., more that a few feet) beyond the end of their flight
      tracks.

    - When creating NMap and RNM OPX files, BaseOps automatically fixes flight
      profiles that extend slightly (i.e., less than a few feet) beyond the end
      of their flight tracks.

    - Better error handling if the NMap or RNM noise models crash.

    - Fixed the following BaseOps bugs:

        - Fatal error when using mouse to pan or zoom a map.

        - Fatal error when changing a flight profile's aircraft.

        - Fatal error when importing an Integrated Noise Model (INM) 6.1 case.

        - Check boxes used to select table fields in a report were not visible.

        - Error when displaying Open File dialog box under Windows NT 4.0.




Version 7.22

    - A missing file, "INM10SEL.dat", is now included in the NMap directory.
      This file's absence would cause Omega10 to fail when processing certain
      Integrated Noise Model (INM) aircraft.




Version 7.21

    - BaseOps now creates RUN files in the case directory when NMap and RNM are
      run.  However, since BaseOps supports long file names and the RUN file
      format only supports DOS-style 8.3 file names, the file names in the RUN
      file refer to temporary files with short names.  If you wish to use a
      BaseOps-generated RUN file to run NMap and/or RNM independently of
      BaseOps, you will need to manage these temporary files manually.  See the
      "Running Cases" chapter of the BaseOps User's Guide for more information.

    - NMPlot's "Point Of Interest Computation" and "Grid Computation" tools have
      been modified to work with grids generated by Noisemap/BaseOps 7.21.  Due
      to 8.3 file name limitation of the RUN file format, these tools were
      broken by the release of BaseOps 7.2.  They have now been fixed.

    - Fixed a bug that occurred when running a case in which points of interest
      were computed but the grid was not computed.




Version 7.2

    - A user's guide is now available.  Choose "Contents" from the "Help" menu.




Version 7.1 Beta 1

    - Graphical viewing and editing of data now supported.




Version 7.0 Beta 6

    - Can now export and import flight profile operation counts to/from a third-
      party spreadsheet (such as Microsoft Excel) or database (such as Microsoft
      Access).  Choose "Export Flight Operations to Spreadsheet" or "Import
      Flight Operations from Spreadsheet" from the "File" menu.

    - Can now import the following types of data from DAFIF (Digital
      Aeronautical Flight Information File):

        - Airfield information
        - Navigational Aids
        - Runways
        - VTOL Pads

      Choose "Import from DAFIF" from the "File" menu.

    - Can now import data from Integrated Noise Model (INM) cases.  Choose
      "Import INM Case" from the "File" menu.

    - Standard flight profiles supported.  Use the "Load Standard Profile"
      button at the bottom of the Flight Profile editing page to load a standard
      profile.  Use the "Save as Standard Profile" button to save the current
      profile as a standard profile.  A library of standard profiles for a large
      number of aircraft is included with BaseOps.

      Standard profiles are stored in two BaseOps case files: "Standard Flight
      Profile Library - BaseOps" and "Standard Flight Profile Library - User".
      You can load and edit these two files like any other BaseOps case.

    - Previously, the item list, on the left side of the BaseOps window, only
      displayed the names of items.  The list now also displays the first line
      of each item's notes.

    - New standard group for specifying the type (VOR, TACAN, DME, etc.) of a
      navigational aid.




Version 7.0 Beta 5

    - Can now import BaseOps cases created by previous versions of BaseOps.
      Specifically, .OPS, .OPX, and .BPS files can be imported.  Simply choose
      Open from the File menu, then select the file you wish to import.

    - The item list (the list on the left side of the BaseOps window that shows
      the available flight tracks, flight profiles, etc. ) can be sorted and/or
      filtered.  Use the sort and filter buttons located just above the list.

      Note that the filter button turns bright red and yellow when a filter is
      set.  This is to remind you that the list is being filtered, and that some
      items may be hidden.

    - Groups are now supported.  Choose Groups from the dropdown item type
      selector in the upper-left corner of the BaseOps window.

      You can define arbitrary groups that can be used to classify flight
      tracks, flight profile, etc.  For example, you can make a group called
      "Wing", give it possible values such as "4th Fighter Wing" and "916th Air
      Refueling Wing", and make it applicable to flight profiles.  When editing
      flight profiles, you would see a dropdown control labeled Wing: you could
      specify that this profile represents a 4th Fighter Wing operation, while
      that profile represents a 916th Air Refueling Wing operation.

      Currently, you can use groups when sorting and filtering the item list.

      In the future, there are other planned uses for groups, such as:

          Scaling operations - For example, double the number of operations
          assigned to the 4th Fighter Wing.

          Printing - For example, only print the flight profiles assigned to
          the 916th Air Refueling Wing

    - You can now set the initial case options for new BaseOps cases.  If the
      case file "Noisemap\BaseOps\New Case Model.baseops" exists, BaseOps
      creates a new case by copying it.




Version 7.0 Beta 4

    - Static profiles can be entered.

    - Minor changes were made to the quick-add commands for specifying flight
      profile power settings.




Version 7.0 Beta 3

    - Flight profiles (for both NMap and RNM) can be entered.

    - Reverse button for runways.  To easily enter a reverse-direction runway,
      first duplicate an existing runway, then press the Reverse button,
      located at the bottom of the Runway Edit pane.

    - Locations can now be specified using feet or meters east/north of the
      site reference point.  See the Coordinate System page of the Case Options
      dialog box.

    - Directory structure changed.  BaseOps is now installed to the BaseOps
      subdirectory of the Noisemap directory.




Version 7.0 Beta 2

    - Flight tracks and VTOL tracks can be entered.

    - Back button added.  This works like the Back button in a web browser.
      For example, if you are editing a flight track, then go to the track's
      runway, you can press the Back button to easily return to the flight
      track.




Version 7.0 Beta 1

    - Initial beta release.  This version has limited capabilities: ability to
      create a case, enter some data (runways, points of interest, etc.), and
      save/load case to/from a file.

