On Dec 21, 2009, at 21:54, Marko Mäkelä wrote:
> On Mon, Dec 14, 2009 at 11:41:05PM +0200, Marko Mäkelä wrote:
>> Yet another solution would be to have a special syntax of variable
>> substitution that would bypass the valueTags, say, $(var) instead of ${var}:
>>
>> (type=boundary | type=multipolygon) & boundary=administrative & name=*
>> { apply
>> {
>> set mkgmap:boundary_name='$(mkgmap:boundary_name)/${name}' | '${name}';
>> }
>> }
>
> I implemented this (see the attached patch). It was easier than I thought,
> and the runtime penalty should be low.
Hm... I tried this out, however I couldn't get a name for the following
boundary which runs down the middle of the Rhine:
http://www.openstreetmap.org/?lat=49.23141&lon=8.38788&zoom=16&layers=B000FTF
This I suppose is a rather complicated example, as the line in question is an
administrative boundary without a name, but it has five relations defining
various boundaries. Am I doing something wrong, or does the way this item was
tagged prevent the name from being displayed?
Cheers.
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
