logo separator

[mkgmap-dev] [PATCH] RoadMerger reverses roads

From Andrzej Popowski popej at poczta.onet.pl on Sun Jan 12 14:32:42 GMT 2014


 > Maybe we need a tag like mkgmap:reversible=no

Isn't a bigger problem there?

The situation is that single OSM way creates multiple Garmin ways. This 
could be done by copying OSM way or by referencing OSM way for new 
Garmin object. Both variants can cause problems.

If there is a copy, then it could be processed differently, for example 
when simplifying. And I think routable roads are processed different 
than non-routable. This would lead to misalignment for Garmin objects.

If a new object uses a reference, then there will be problems like with 
reversing. And any other processing of OSM way can lead to some problems 

Multiplying of Garmin objects is done by "continue" statement in object 
definition. I'm not sure, how this is processed internally in mkgmap, 
probably it is using a reference. Maybe would be helpful if we could 
select if there should be copy or reference for Garmin object? For 
example there could be a statement like "continue_with_copy".

Best regards,

More information about the mkgmap-dev mailing list