backwards compatability: mapfeatures
Hallo, I am using mkgmap for building a topo-map with a lot of selfmade icons. Since it is working ok (and in my opinion a little easier to keep the overview), I am still using the mapfeatures option. The problem is now, that everything works ok with the ancient mkgmap version r659, but if I use a more recent version, only some of the icons are created, some are missing and some get a wrong symbol. Can anybody please check, what's wrong with my data or with the usage of the mapfeatures option in more recent versions of mkgmap? Here is my osm-example-file, with all items placed at N53 E09 http://demuur.gmxhome.de/mapfeatures_example_v003.zip And here is my mapfeatures and my typ file. http://demuur.gmxhome.de/osm-map-features_v003.cvs http://demuur.gmxhome.de/osm_v003.typ The correct display of the icons created with mkgmap r659 can be seen at http://wiki.openstreetmap.org/wiki/Image:Garmin_Maps_Feature_Example_De_Muur... Thanks, Torsten
Hi On Sun, Feb 22, 2009 at 06:01:06PM +0100, Torsten Leistikow wrote:
I am using mkgmap for building a topo-map with a lot of selfmade icons. Since it is working ok (and in my opinion a little easier to keep the overview), I am still using the mapfeatures option.
Thats no problem, it should be perfectly backward compatible as the mapfeatures file is just converted inside mkgmap to the new form.
version r659, but if I use a more recent version, only some of the icons are created, some are missing and some get a wrong symbol.
I've tracked down the version where it went wrong and it appears to be 856. This deals with points that are cities. We treat every point with a garmin code between 0x0100 and 0x1100 as a city although this was a temporary arangement, and its clearly not going to work for your map. Does that fact match the problems you see? We probably need a command in the style files to say that a point is a city. Mark: what do you think? ..Steve
Steve Ratcliffe schrieb:
We treat every point with a garmin code between 0x0100 and 0x1100 as a city although this was a temporary arangement, and its clearly not going to work for your map.
Does that fact match the problems you see?
In my example all icons with code numbers 0x01?? are not display when the map is build with the actual mkgmap. So this is explained. But some other icons are also missing. Interestingly one icon (0x400c) is twice displayed correctly for a bus-stop and a bus-station, but the same icon (0x400c) is not displayed for a tram-stop. Maybe this is just a side effect of the 0x01?? codes, the garmin products are often behaving very strangly, when you play around with the code numbers. But still, if I modify my mapfeatures-file and leave out all 0x01?? codes (but I leave them in the typ-file), it is not working 100% like the old version. The problem with the tram stop for example stays. The problem must also be older than version 856. I tried the modified mapfeatures-file with version 821, and the result is the same as with the actual version. So somewhere between 659 and 821 there must have been a change, where some of my icons get lost. Gruss Torsten
On Sun, Feb 22, 2009 at 08:25:15PM +0100, Torsten Leistikow wrote:
But some other icons are also missing. Interestingly one icon (0x400c) is twice displayed correctly for a bus-stop and a bus-station, but the same icon (0x400c) is not displayed for a tram-stop. Maybe this is just a side effect of the 0x01?? codes, the garmin products are often behaving very strangly, when you play around with the code numbers.
I've found the problem with the tram_stop. It is because the input .osm file has duplicate node id's. If you fix the node id on the tram stop to be unique then it does get displayed. The change that causes it to stop working is 738 (merge from style branch, Osm5XmlHandler). It is to deal with relations and is essential so can't be changed back to how it worked before. Regards, ..Steve
Steve Ratcliffe schrieb:
I've found the problem with the tram_stop. It is because the input .osm file has duplicate node id's. If you fix the node id on the tram stop to be unique then it does get displayed.
Autsch. I fixed the node-ids and moved all my point numbers from 0x10?? to 0x60??. Now everything works ok with the latest mkgmap version. Thanks for your help and many thanks for your work on mkgmap. Gruss Torsten
participants (2)
-
Steve Ratcliffe -
Torsten Leistikow