WAsP Map Editor 12 - Release Notes

This document describes the new features and other changes made.

WAsP Map Editor version

Roughness/Landcover consistency-check-error, leaving a so-called LFR-error unnoticed, has been fixed.

A GWA (Global-Wind-Atlas)-map-import error, occurring in connection with some GlobCover map-data, has been fixed.

An error occurring, when saving a map in Lat-Lon coordinates in GML-format, has been fixed.

An error prevented *.asc grid maps to be read. This error has been fixed.

Some errors occurring when editing landcover/roghness-change lines have been fixed.

An error sometimes occurring when anchoring landcover/roughness-change lines to a node has been fixed.

An error sometimes occurring when joining two landcover/roughness-change lines to a node has been fixed.


Map Editor version

Fixed problems with downloading grids from GWA data services.

Map Editor version

The landcover concept is fully introduced, allowing advanced description of terrain surfaces, like roughness + displacement height, in addition to the simple roughness length. Thus, maps with advanced land cover features may be opened or imported (see below), or you may add advanced landcover features to an existing map by editing in much the same way as you would add a simple roughness feature.

The new GML-file format is fully introduced. It has two variants, "ORO" for elevation or height contours: extension .oro.gml, and one for land cover, "LCV", including simple roughness: extension .lcv.gml. The latest WAsP version supports the two GML variants. Please notice that in order to save advanced landcover features in a map you must use the landcover-GML map-file format.

Elevation- and landcover maps can be imported from the Global Wind Atlas (GWA) database. The landcover maps may be imported as roughness-maps, i.e. the landcover categories are converted to roughness lengths during the import, using a built-in lookup-table. When not using this roughness-option, the land cover description will just contain the landcover category-index of the appropriate database, e.g. CORINE(5) when using the Corine-database.

The AutoCAD DXF file format in no longer supported in this Map Editor version.

Importing elevation, landcover or roughness maps for the Global Wind Atlas database from completely homogeneous areas (e.g. sea surface) may cause an error during the import operation. For the time being, one should instead create a map containing only a surrounding height or contour or landcover-change line to define the elevation or landcover, resp., for the map area.

This version supports two Lambert conical projections: "Lambert 93 (France)" and "Cape Verde National". However, these projections are not supported by WAsP itself. So, in order to use maps with those projections in WAsP you must transform them to a projection and datum supported by WAsP, e.g. UTM WGS84 (with the proper zone).


Map Editor version

Bug fixes:

  • Maps with projections with WGS84 would write “WGS-8” and not (as expected) “WGS-84” in the datum description in the description line of the map file. This could create problems in WAsP. Now WGS84 datum is always described as “WGS-84”.


  • When saving a map in one of the binary .map formats (BIN16 or BIN32) the projection description would be lost in the file. Now the projection description is saved in the description line of the binary file, exactly as in ASCII .map map-files.


  • When creating a digital map from scratch, by loading a background map without previously having specified the map domain in the “Create an empty map” menu option, the map editor would crash just after you have calibrated (geo-referenced) the background map by means of 3 or more fix-points.  This has now been fixed.


Map Editor version

New features:

• WAsP Map Editor can create, edit and save map files in new GML format (note that separate orography and roughness map files are needed for the new GML map file format)
GML application schema

Bug fixes:

• An irritating bug regarding the internet-address (URL) for the Global Wind Atlas Warehouse database has been fixed (the bug prevented the correct URL to be used for map-import from the Global Wind Atlas Warehouse database)


Map Editor version release notes

A bug regarding SRTM-map import has been fixed.
Import of SRTM-maps would crash if one or more of the involved 1x1 degree map tiles had no water boundary lines.
This bug has now been fixed.


Map Editor Release notes

1. Implementation of map import from Global Wind Atlas(GWA) warehouse Map Server.

a. Elevation maps: From a combination of SRTM and Viewfinder databases.
b. Roughness maps: From GlobCover database and in the European area, from the Corine database.

2. Fixing some bugs regarding LFR-errors at the boundary, and regarding plyline-editing.


Map Editor Release notes

1. A bug prevented maps, exported from WAsP, from being opened by the Map Editor, if these maps contained very long polylines.
  This bug has been fixed.

2. The projection system has until now operated with UTM, UTM-N and UTM-S projections, although UTM and UTM-N were functionally identical. With a new GeoProjectionDatabase (no. 17) the "plain" UTM has now been removed from the projection system, but when opening old maps, "plain" UTM is automatically converted to UTM-N.
The above also applies to projection handling in WAsP and in the projection transformer utility.

WAsP Map Editor Version

1. The manual editing algorithms had some bugs, e.g. one that lead to an error when joining two polylines.
These bugs have been fixed.

2. The "File Add and replace" algorithm had a bug, leading to an error situation. This bug has been fixed.

3. The SRTM-import had some bugs that lead to error situations when tiles - completely or partly covered by the
 specified domain - were not available in the SRTM-database. These bugs have been fixed.

WAsP Map Editor Version

Two bugs in the SRTM import could cause the import procedure to break down or result in faulty maps. The bugs were about 1) the treatment of voids in the imported grid-map tiles (points where the elevation is unknown); and 2) the joining of neighboring tiles when the specified covered more than one SRTM map-tile.

We have fixed these bugs so that SRTM import should work smoothly.


WAsP Map Editor

  • Import of gridded elevation (orographic) maps as well as roughness-length maps are now supported
  • Faster, more efficient check of roughness consistency and LFR-errors.
  • Coherent roughness areas can now be treated as a whole. The roughness value of an entire roughness-area may be edited using a new area editing option.


MapEditor - Release C

- functionally equivalent to 11.3 Release C Build 360

MapEditor 11-3-ReleaseC-Build360.msi:
- fixes a few bugs regarding the SRTM-importer
- implements import of Google Earth KML- and KMZ files

MapEditor 11-3-ReleaseB-Build357.msi:
- fixes a bug regarding the add-and-replace operation.

MapEditor 11-3-ReleaseA-Build354.msi:
- SRTM Map importer implemented
- Projection database reading (Asian Windows versions) error fixed
- Shape file reading errors fixed
- Shape-file elevation from associated dBase file now supported
- DXF-map reading bug re. files with unspecified DXF-format version now fixed

MapEditor11-1-Build338.msi :
- GIS-type coordinate meta-files for scaling/calibration of background maps are now supported.
- BLN-map files to be immported
- Shape files to be impported
- Faster, more efficient check of LFR-errors

MapEditor10-1-Build320.msi :
- includesGeoProjection Database 11, to which the "Israel Transversal Mercator" Projection has been added
- the licence check has been removed for use with WasP Engineering 3.

Version 10. installation package "C":
- includesGeoProjection Database 11, to which the Argentinian projection has been added
- solves an installation problem with non-English Windows systems.

Version 10.0:
Please notice that the exe-file and the help-file (*.chm) are now named WAsPMapEditor10.

Afew bugs have been corrected since build 290 (MapEditor9):
1) artifact LFR-errors in special cases; fixed.

2) LFR-error calculation break-down in special cases; fixed.

3) Dead-ends not updated when line-type is changed: fixed.

Some (2) new features have been implemented since build 290 (MapEditor9):

1) Import of Golden Software BLN-maps.

2) Import of Shape-file maps (*.shp). Roughness information from the associated database file (*.dbf) is so far disregarded.

Please consult the "What's New?" topic in the on-line Help for more details.