[mkgmap-dev] Why are all the un-named peaks called '6140565'?
From Mark Burton markb at ordern.com on Sun Mar 14 22:29:38 GMT 2010
Hi Someoneelse, > Is "6140565" the last name in the .osm file being processed at that > time? I've seen a similar effect with all unnamed natural=peak being > named "YHA Ravenstor" (which happened to be the last name in the file > that I was processing at the time). As to how to fix it; haven't a clue... That's interesting to learn. In this case, 6140565 does appear as a tag value: <node id='27424899' lat='55.8449129' lon='-4.4298279'> <tag k='highway' v='bus_stop'/> <tag k='nat_ref' v='6140565'/> </node> Hey, that's a really great bug, it causes anonymous peaks to be named in honour of a bus stop! Mark
- Previous message: [mkgmap-dev] Why are all the un-named peaks called '6140565'?
- Next message: [mkgmap-dev] Why are all the un-named peaks called '6140565'?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list