[Main] [Download] [Order] [Documentation] [FAQ] [Tech support] [About author]
(March 5th, 2014)
GPSMapEdit is designed to help users of Garmin, Lowrance, CityGuide, ALAN, Holux and Navitel Navigator navigation systems to create custom maps. The software provides quick loading and viewing vector maps in so-called "Polish format", comparing them with various geodetic data like Google Maps, raster maps, GPS tracks and waypoints.
Some of navigation systems, such as iGO, TomTom, Garmin, Nokia Maps, Navitel provide users function to import simple custom data consisting of POIs only, as well as speed cameras alerts. GPSMapEdit may be used to visualize and edit such data.
In addition, the software may be used for converting GPS-tracks, waypoints and routes among various formats.
All navigation systems support only closed undocumented map formats (for instance, Garmin IMG). However since early 2000, the utility cgpsmapper.exe is available, allowing to convert geodetic data presented in text files (with .TXT or .MP extension) in open and well documented format into binary Garmin IMG files. Its input language is called "Polish format" or MP format.
At this moment, maps in Polish format may be converted (using GPSMapEdit or by other applications) also to Lowrance, Magellan, ALAN, Holux, Navitel and other similar formats.
For instance, great number of maps may be found at the server mapcenter.cgpsmapper.com.
Yes. There are 3rd party convertors from other open formats to MP, e.g. from Open Street Map. The example of converting Polish map into Magellan one is described here. In addition, there are applications to pre-process MP files like mp2mp.
And, of course, you may write you own software based on Polish format! In this case, GPSMapEdit may be used as your covertor's output verification tool and also as source of ready code of the parser.
The maps accepted by OziExplorer are raster ones being scanned images of paper maps. Automatic recognition of such images necessary to transform the data to vector presentation is rather complex task (like OCR and even more). Some so-called vectorizer tools are available in market, but most of them have very high prices while still require large amount of manual labour.
However, you may use raster maps in GPSMapEdit as base both for manual drawing of vector ones over them, and to fix existing vector maps.
Please see details here.
GPSMapEdit is shareware. Please see the License Agreement for details.
Some of features are to be unlocked by License Key. The information about License Key ordering is here.
You may leave message in the guest book or contact me via Email. Bug reports, feature requests etc are welcome!
The answer is here.
GPSMapEdit does not require installer and ready to run from any folder. Just download the latest version without installer, unzip it into any suitable folder.
However the installer is also available.
There are 3 ways:
This may be result of incorrect map converting from other formats.
In general, map contains a few zoom levels for different scales. In Polish format, the levels are defined in the header of map (section [IMG ID]) through parameters "LevelX=", "ZoomX=". If all objects belong to one of level (e.g., to 0-th one), the window will be empty for all other scales.
You may delete the empty levels to solve the problem. (NOTE: less detailed level should be always empty, according to cGPSMapper' documentation; so minimal number of levels is two).
This show active zoom level of the map, corresponding to the selected scale. The mark ">" means overzooming and "<" - underzooming. Symbol "*" reminds that automatic level selection is turned off: the given level is visualised for any scale (see menu item 'View | Levels').
"Ready*" status message appearing after map loading indicates that some warning messages was generated. You may see the log using menu command 'File | Message Log'.
Note that some kinds of Garmin receviers never visualize some types of objects at all. For instance, city blocks are not shown in eTrex Vista.
Moreover, some important kinds of objects have no corresponding object type in Garmin's GPS-navigators (in the "basic" type set). Examples are railway/subway stations, squares etc.
This is limitation of POI presentation: they are described as point without direction.
Yes. Just please set 'File | Map properties | Header | Coding schema' and 'Code page' properly.
This is feature of Polish format used to declare upper case, highway marks and other issues affecting on labels visualization.
Garmin maps store all coordinates with maximum precision equal to 360î/224=2.1*10-5 (about 2.4 meters). So there is no reason to store data in Polish format with higher accuracy.
In Polish format, it is possible to define an object as set of elements distributed over zoom levels ('DataX=' and 'OriginX=') rather than define several single-element objects, one per each level. This approach allows to treat an object as 'whole': user may move, rename, change type, delete etc the object in all zoom levels simultaneously.
In contrast, MP files imported from IMG always contain single-element objects. (The intrinsic reason is in IMG format details.) This provides some source of 'traps and pitfalls' for users while editing.
So, the 'Join per-level Objects' function combines similar objects from different levels to the joined objects. The 'Split Objects by Levels' one breaks the objects to per-level parts back.
This is term from linear algebra refering to any combination of linear coordinates transformations.
In particular these are shift, shear, turn, stretching, compressing and so on.
Sometimes even vector maps may have such distorsions. Applying affine transformation to these maps may significantly improve their precision.
In general, affine transformation may be specified by three pairs of points; each pair consists of source point and destination one. In particular, both points of a pair may be equal meaning no shift at the place. If points are equal two by two in each three pairs, the transformation changes nothing.
To apply an affine transformation to a map, you should have some high-precision geodetic data for the calibration. These may be a raster map (OziExplorer) which is calibrated as well or tracks and waypoints obtained using GPS-navigator. It is important to make sure that all coordinates are presented in the same datum or be able to convert to WGS84.
Follow the directions:
If something is wrong you may 'Undo' transformation and try again with other pairs.
You may freely change tools temporarily during preparing to affine transformation - to 'Drag Map' tool or to 'Select Objects' etc - and go back to pairs defining.
It is recommended to define pairs as distant as possible from each other and from center of the map. This may provide higher accuracy.
Datum is like frame of reference. Each point at earth surface is defined as combination of latitude, longitude and elevation. But all the three values depend on origing of coordinates, direction of axes, and accuracy of measured Earth radius and polar flattening. Different datums are used in different countries. As a result, coordinates of the same point may differ in two datums.
For instance, Russian maps are based on "Pulkovo-1942" datum. The one used in GPS is WGS84. In Moscow region, they are shifted approximately in 150 m. To avoid loss of GPS precision (wich is about 15 m) you should always make sure that all coordinates are defined in or converted to the same datum.
Note the list below does not correspond to the order of implementation.