Main · Download · Order · Documentation · FAQ · Tech Support

(August 2nd, 2019)

I. System requirements

• Operating systems: Microsoft Windows XP/Vista/7/8/10 are supported.
  
• RAM: depends on work mode, required size of free memory is about the size of input file in Polish format. So, this may be 30M or even 1 GB or more.
• Video: hardware acceleration and TrueColor support is recommended.
• It is not guaranteed to run correctly under virtual machines like VMware, MS Virtual PC etc.

II. Evaluation

The following features require license 2.x:

• Visualization of Web maps (except Google Maps) for high detail resolution (scales over 240 m).
• Visualization of MrSID and NITF raster maps for high detail resolution (scales over 240 m).
• The context menu items 'Location | Paste Here', 'Location | Paste Template Polygon', 'Location | Browse in'.
• Export to SHP.
• Export to metafile EMF of whole map.
• Opening of trancated (damaged) GPX tracks, the ones with incorrect ending of file.

The following features require license 1.x or higher:

• Visualization of satellite images from Google Maps for high detail resolution (scales over 240 m).
• Visualization of ECW and JPEG 2000 raster maps for high detail resolution (scales over 240 m).
• Automatic saving of map.
• Semi-automatic vectorizer tool.
• Find by address (the menu item 'Tools | Find by Address...').
• Loading of huge raster maps (format OziExplorer MAP) - over 20-30 megapixels.
• Import from MapInfo MIF/MID.
• Export to MapInfo MIF/MID.
• Import POI from external table file with address data, the formats are: CSV, MS Excel XLS, MS Access MDB, dBase DBF, Paradox DB, Visual FoxPro.
• Splitting map to smaller files (the menu item 'Tools | Split Map to Files...').
• Saving to CRD format (ALAN Map 500 and Holux).
• Taking photo from camera.

NOTE: The list may be extended in future updates.

III. Projections, coordinate systems, datums

List of supported projections
List of supported projected coordinate systems
List of supported datums

IV. File formats

1. Polish format (input format for cGPSMapper.exe)

   Open, Save.

   This is input language of the program cGPSmapper.exe used to generate files in Garmin IMG format.
   [Description]

   • Marine maps are not supported.
   • Lanes, multi-node turn restrictions, road signs, city@city are not supported.
   • Map should not intersect E/W 180^o.
   • In polar area, some distorsion is possible.
   • The sections [MAP], [PLT], [WPT], [SHP], [DBX], [DEFINITIONS], [FILE], [DICTIONARY], [BACKGROUND] are not supported (but the source text may be edited).
   • While saving a file, all comments are ignored except ones before sections [RGNx0].
   • The precision of saved coordinates is limited by 5 or 6 digits after point (depending on "Level0=" setting in the header).
   • Datums: W84, custom parameters.
2. OziExplorer MAP

   Open, Export.

   This is raster map for OziExplorer. It consists of calibration data and reference to external image file like JPG.

   • Supported image formats are: OZF2, OZFx3, BMP, GIF, JPG, PNG, TIFF (support of the last two assumes installation of GDI+).
     The formats OZF, ECW and MrSID are not supported.
   • Projections: Latitude/Longitude, Transverse Mercator, UTM, Mercator, Swedish Grid, BNG, Irish Grid, Swiss Grid, Lambert Conformal Conic (large scales only).
   • Datums: the most of ones supported by OziExplorer.
   • Maximum size: in evaluation mode, the raster size is limited to about 20-30 Mpixels (depending on properties of installed videodriver); License Key allows to load up to 270 Mpixels (depending on Windows version).
3. OziExplorer WPT

   Open, Export.

   This is file with waypoints for OziExplorer.

   • Datums: the most of ones supported by OziExplorer.
4. OziExplorer PLT

   Open, Export.

   This is file with tracks for OziExplorer.

   • Datums: the most of ones supported by OziExplorer.
5. OziExplorer RTE

   Open, Export.

   This is file with routes for OziExplorer.

   • Datums: the most of ones supported by OziExplorer.
6. OziExplorer RT2

   Open.

   This is file with routes for OziCE.

   • Datums: the most of ones supported by OziExplorer.
7. Garmin MapSource IMG

   Open, Export.

   This is the binary cartographic format from Garmin, used for uploading maps to GPS recievier via MapSource software.

   • File size must be < 2 GB.
   • Locked maps are not supported.
   • Labels coding scheme N7 is not supported.
   • House numbering is not supported.
   • 4- and more node turn restrictions are not supported.
   • NT format is not supported.
   • BlueChart is not supported.
8. Garmin MapSource MPS and GDB

   Open, Export.

   This is binary file used by Garmin MapSource to store data downloaded from or prepared for uploading to GPS receiver: waypoint, tracks, routes, lists of maps.
   [Samples]

   • MPS: оnly tracks and waypoints are supported; GDB: оnly tracks, waypoints and routes.
   • The MPS files should be saved by MapSource 4.09 or later version.
9. Garmin PCX5

   Open.

   These are files with waypoints, tracks and routes (.wpt, .trk and .rte).

   • Waypoint types are not supported.
   • Datum: WGS 84.
   • Units: latitude/longitude in degrees or degrees and minutes.
10. Navitel NM2

    Export.

    This is binary file used by Pocket PC navigation software Navitel Navigator 3.x.

    • Maps loading is not supported (export only).
11. Navitel NTM

    Open, Export.

    This is binary file used by Pocket PC navigation software Navitel Navigator 2.0 and 3.0.

    • Locked maps are not supported.
12. Magellan MapSend WPT

    Open.

    This is file with waypoints and routes for Magellan MapSend.

13. Magellan MapSend TRK

    Open.

    This is file with tracks for Magellan MapSend.

    • The files should be saved by MapSend 1.00 - 4.10+.
14. Lowrance MapCreate LCM

    Export.

    This is the binary cartographic format from Lowrance Electronics, Inc, used for uploading maps to GPS recievier via MapCreate software.

    • Maps loading is not supported (export only).
    • External lcmBulder DLL from 3rd party authors is used, so all the supported features are limited by the lcmBulder facilities.
15. Lowrance user data file (USR)

    Open.

    This is file with tracks, waypoints and routes in binary format for Lowrance devices.

16. ALAN Map 500 CRD and LST

    Open, Export.

    Binary cartographic format for the GPS-reciever ALAN Map 500.

    • Export of objects with size over 1.82 degrees in latitude or longitude is not supported.
    • Export of polygons with holes is not supported.
17. ALAN Map 600 ARD

    Open, Export.

    Binary cartographic format for the GPS-reciever ALAN Map 600.

    • Export of map covering are over 1.82 degrees in latitude or longitude is not supported.
    • Export of polygons with holes is not supported.
    • Routing is not supported.
18. ALAN Map 500/600 TLG/TRL

    Open, Export.

    This is file with tracks for ALAN Map 500/600.

19. ALAN Map 500/600 WRT/WRP

    Open, Export.

    This is file with waypoints and routes for ALAN Map 500/600.

20. Holux MapShow CRD and LST

    Open, Export.

    Binary cartographic format from Holux Technology Inc.

    • Format version prior to 1.10 is not supported.
    • Export of objects with size over 1.82 degrees in latitude or longitude is not supported.
    • Export of polygons with holes is not supported.
21. Holux MapRoute ARD

    Open, Export.

    Binary cartographic format for the GPS-reciever Holux GM-120.

    • Export of map covering are over 1.82 degrees in latitude or longitude is not supported.
    • Export of polygons with holes is not supported.
    • Routing is not supported.
    • House numbering is not supported.
22. Holux MapShow WPO

    Open, Export.

    This is file with waypoints and routes for Holux GM-100.

23. Holux MapShow TRK

    Open, Export.

    This is file with tracks for Holux GM-100.

24. Holux MapShow305 WPT

    Open, Export.

    This is file with waypoints for and routes foe Holux GM-305.

25. Holux MapShow305 TKL

    Open, Export.

    This is file with tracks for Holux GM-305.

26. ESRI shapefile

    Import, Export.

    Binary files, which are widely used in professional GIS (ArcView, MapInfo etc).
    [Description]

    • File types either .SHP + .DBF or .MDB are supported.
27. MapInfo MIF/MID

    Import, Export.

    Text files for spatial data interchange from GIS MapInfo.

    • Import of TEXT, ROUNDRECT, ELLIPSE and ARC objects is not supported.
    • Robinson projection is not supported.
    • While export, all coordinates are saved in WGS84 degrees.
28. GPS eXchange file (GPX)

    Open, Export.

    This is file with tracks, waypoints and routes in XML-based format.
    [Description]

29. Nav N Go iGO 8 track (TRK)

    Open.

    This is file with track for iGO 8.

30. Nav N Go iGO Primo track (TRK)

    Open, Export.

    This is file with track for iGO Primo.

31. Nokia Landmark Exchange file (LMX)

    Open, Export.

    This is XML file with landmarks (waypoints) for Nokia Maps (Ovi Maps).

    • Binary version of the LMX format is not supported.
    • Address tags, coverage radius and precision information is ignored.
32. Google Earth user data (KML, KMZ)

    Export.

    This is file with user-defined geospatial vector data in XML-based format.
    

    • Vector image of map may be exported as KMZ. 3D data are supported.
    • Waypoints and tracks may be exported as KML or KMZ.
33. Enhanced metafile (EMF)

    Export.

    Vector image of map.

34. Windows bitmap (BMP)

    Export.

    Raster image of map.

35. Enhanced Compressed Wavelets (ECW)

    Open.

    This is raster wavelet map format developed by Earth Resource Mapping, Ltd.

    • File must be georeferenced.
36. MrSID (.SID)

    Open.

    This is raster wavelet map format developed by LizardTech, Inc.

    • File must be georeferenced.
    • Georeference may be World file or in the header.
    • The coordinate system is read from PRJ file, if any, then from GeoTiff tags, then from "IMAGE::WKT" tag.
    • Non-lidar files are supported.
    • The supported color schemes are RGB(A) and Grayscale(A), without real using alpha-channel.
    • Multi-band files are not supported.
    • Just 1-byte samples are allowed.
37. National Imagery Transmission Format (NTF)

    Открытие.

    This is raster wavelet map format developed by U.S. Department of Defense.

    • File must be georeferenced.
    • Georeference may be World file or in the header.
    • The coordinate system is read from PRJ file, if any.
    • The supported color schemes are RGB(A) and Grayscale(A), without real using alpha-channel.
    • Multi-band files are not supported.
    • Just 1-byte samples are allowed.
38. JPEG 2000 (JP2)

    Open.

    This is raster wavelet map format standardized by ISO/IEC 15444-1:2004

    • File must be georeferenced.
    • Georeference may be World file, GML, ERS.
39. JPEG/Exif (JPG)

    Open as bookmark.

    Geo-tagged JPG images.

    • GPS location of snapshot exposure must be presented at Exif header.
    • Datum: WGS-84.
40. Comma-separated values (CSV)

    Export bookmarks.

    Textual tables with commas as field separators, used to export bookmarks.
    [Description]

    • For each type/subtype of bookmarks presented in current map, separate file is created, with the name consisting of identifiers of type and subtype delimited by dash.
    • The first line of each file defines identifiers of the attributes per columns.
    • The time of bookmark, if any, is exported in the format "YYYY.MM.DD,hh:mm:ss" in GMT.
41. Custom POIs for Garmin POI Loader (CSV)

    Import, Export as bookmarks.

    Textual format of custom POIs for Garmin POI Loader.
    [Description]

    • Each .csv file is imported to separate dynamic subtype of the bookmark type "Custom POI" or, for speedcam tables, of type "Speed camera".
    • On exporting, separate .csv file is created per each subtype of the types "Custom POI", "Speed camera", "Navitel safety alerts".
    • Speed units: km/h.
    • Datum: WGS-84.
42. Custom POIs for TomTom (OV2)

    Import, Export as bookmarks.

    Binary format for navigation software and devices from TomTom company to store custom POIs.

    • Each .ov2 file is imported to separate dynamic subtype of the bookmark type "Custom POI".
    • On exporting, separate .ov2 file is created per each subtype of the types "Custom POI".
43. Safety alerts for iGO (TXT)

    Import, Export as bookmarks.

    Textual table of speed cameras and other safety alerts used by Nav N Go iGO 8 and iGO Primo.

    • Import to bookmarks with type "Speed camera" and "iGO safety alerts".
    • Export from bookmarks with types "Speed camera", "iGO safety alerts", "Navitel safety alerts", "CityGuide speed cameras" and "CityGuide traffic signs".
44. Safety alerts for Navitel Navigator (TXT)

    Import, Export as bookmarks.

    Textual table of speed cameras and other safety alerts used by Navitel Navigator ver.3.2 and higher.

    • Import to bookmarks with type "Navitel safety alerts".
    • Export from bookmarks with types "Speed camera", "Navitel safety alerts", "iGO safety alerts", "CityGuide speed cameras" and "CityGuide traffic signs".
45. Speedcams and traffic signs for CityGuide (BKM)

    Import, Export as bookmarks.

    Textual table of speed cameras and traffic signs used by CityGuide ver.7.x and higher.

    • Import to bookmarks with type "CityGuide speed cameras" and "CityGuide traffic signs".
    • Export from bookmarks with types "CityGuide speed cameras", "CityGuide traffic signs", "Speed camera", "iGO safety alerts" and "Navitel safety alerts".

V. Protocols of GPS recievers

The protocols are used to determine current position, velocity, altitude etc.

1. NMEA-0183 over COMM port

   The following sentencies are supported: $GPRMC/$GNRMC, $GPGGA/$GNGGA, $GPGLL/$GNGLL, $PGRMZ, $PGRME, $HCHDG.

2. Garmin protocol over COMM port

   A800 protocol is supported.

3. Garmin protocol over USB

   A800 protocol is supported.

VI. Graphics limitations

Magnification of raster maps over 14х is not supported. (Note this is the limitation namely of OS but not GPSMapEdit itself). Higher stretching will lead the program to output a gray rectangle instead.

VII. Taking photo limitations

These limitations are applied to the function "Take Photo" of the window "Camera View":

• 1. The camera must support Microsoft DirectShow.
• 2. Image is captured in the resolution of current video stream (high-definition photo resolution, if any, is not supported).
• 3. The photo taking is not available under Windows 2000.

On taking photo as bookmark attribute (e.g. type "File Link/Photo"), it is possible to use a camera compatible with Windows Image Acquisition.

This website uses cookies.
Using this website means you accept Privacy Policy
and agree to the use of cookies.