logo separator

[mkgmap-dev] [PATCH v1] - clone ways that contain some tag pairs

From Thilo Hannemann thannema at gmx.de on Sun Jul 5 20:30:19 BST 2009

Hi Mark,

I think it would be advantageous to generalize this kind of behaviour.  
What about a "continue" flag in the Garmin type definition in the  
style files? This continue flag would indicate that a match with that  
rule generates a copy of the way, but that the processing continues  
with the next match. For example:

boundary=administrative [0x1e resolution 12 continue]
highway=primary [0x06 level 12]

This would have the same effect as your new command in that with the  
boundary=... line one copy of the way is generated, but the processing  
for that way is continued with the highway=... line and another way is  
generated. The advantage of this is that it is also very useful for  
POIs, where the tags on one node might indicated the generation of  
different POI entries for the same node. It would also make the not- 
very-well-documented and buggy overlays style file obsolete. And it  
gives a good start to deal with the encoding of different values for  
the same key with the ;-syntax, which is currently ignored by mkgmap.

What do you think about it?


Am 05.07.2009 um 21:05 schrieb Mark Burton:

> Further to my earlier email about the problem of ways that have both
> highway and boundary tags defined, here's a patch that possibly
> provides a workaround.
> It lets you specify pairs of tags. If a way has both of the tags
> defined, it is cloned and one of the clones has one of the tags and
> the other clone has the other tag. So for the example in question, you
> could specify the option:
> --clone-ways-with-these-tags=highway/boundary
> Another possible tag pair could be waterway/boundary
> All feedback is welcome.
> Cheers,
> Mark
> <mb-clone-ways- 
> v1.patch>_______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

More information about the mkgmap-dev mailing list