I'm getting the "error 107 can't parse coordinates" error.
GPSMapEdit is producing a .mp file that compiles just fine. However, MapSetToolKit is producing an .mp file for the preview that is nonsense. Structurally it looks OK, but the coordinates are a mess. Some values are apparently correct lat/lon. Others are just garbage. For example, the first line (where cgpsmapper fails) has:
Data0=(-46043.6679687500,-107.0344696045),(-23003.6679687500,22932.9648437500),(36.3323669434,-107.0344696045)
The shapefile that I imported into GPSMapEditor is in UTM 12N, which is between -107 and -108 longitude, and the data happens to be between 36 and 37 degrees north. So, the last coordinate is pretty good, the first has a plausible longitude, and the other values make no sense, not even as UTM values.
Presumably this is indicative of MapSetToolkit creating a bad .pv file that is used to generate the .mp for the preview image, but I don't see how to fix it.
UTM zone 12 is between -114 and -108, UTM zone 13 is between -108 and. -102.
Quote from: maps4gps on April 25, 2013, 01:49:40 PM
UTM zone 12 is between -114 and -108, UTM zone 13 is between -108 and. -102.
Sorry, that was a typo in my original message. But that still doesn't seem to explain my I'm getting the garbage coordinates in the output of cgpsmapper when MapSetToolbox calls it to generate the preview image.
Looks like operator error :-(
On import, GPSMapEdit displays "Transverse Mercator" as the projection. In my first attempt, I accepted this value. I now went back and looked more carefully and realized there is an option to select UTM North, which then opens a window allowing me to select Zone 13. Now it works.
But along the way, I thought I'd try converting the shapefile to WGS84 to eliminate any confusion over projections. I'm pretty sure I made this work before. I convert to WGS84, then import that new shapefile into GPSMapEdit, selecting the same value object type for the lines and the same field for the labels as I did for the UTM data. I select Latitude/Longitude for the coordinate system, and leave WGS84 as the datum.
I set the map properties, save the .mp file, then run cgpsmapper. Runs successfully.
I now open MapSetToolKit and follow the same steps as I did for the .img file that started with the UTM shapefile. I select a different Product Code, then execute. The .pv file is generated, the preview .mp file is generated, but cgpsmapper dies on bad coordinates in the preview .mp file. I'm more confused than ever.
Correct, UTM (Universal Transversal Mercator) is different than Transverse Mercator.
I only use cgpsmapper as a check to see if all the tiles that are supposed to be included in a mapset are included. Hopefully someone who uses cgpsmapper more can help in this.
Quote from: nm_map_user on April 25, 2013, 10:41:24 AM
I'm getting the "error 107 can't parse coordinates" error.
GPSMapEdit is producing a .mp file that compiles just fine. However, MapSetToolKit is producing an .mp file for the preview that is nonsense. Structurally it looks OK, but the coordinates are a mess. Some values are apparently correct lat/lon. Others are just garbage. For example, the first line (where cgpsmapper fails) has:
Data0=(-46043.6679687500,-107.0344696045),(-23003.6679687500,22932.9648437500),(36.3323669434,-107.0344696045)
The shapefile that I imported into GPSMapEditor is in UTM 12N, which is between -107 and -108 longitude, and the data happens to be between 36 and 37 degrees north. So, the last coordinate is pretty good, the first has a plausible longitude, and the other values make no sense, not even as UTM values.
Presumably this is indicative of MapSetToolkit creating a bad .pv file that is used to generate the .mp for the preview image, but I don't see how to fix it.
Hello friend were you able to fix it? I am dealing with similar issue so can you help me out? Waiting for reply thanks in advance:)
Look at my second post in this thread. The problem I was having was that my input was in *Universal* Transverse Mercator, but I was selecting (plain-vanilla) Transverse Mercator in the drop down list because I hadn't scrolled far enough to find the UTM entries.
Perhaps you're having the same problem