Is it possible to use wildcards in names as part of a style sheet so only one
type is needed?
ie
amenity=fuel operator=Sainsb* [0x6000 resolution 19 continue ]
this would also allow for misspellings?
--
View this message in context:
On Sun, Oct 16, n Willink wrote:
Is it possible to use wildcards in names as part of a style sheet so only one
type is needed?
ie
amenity=fuel operator=Sainsb* [0x6000 resolution 19 continue ]
this would also allow for misspellings?
You can use:
amenity=fuel operator ~
I understand this can be done with regular expression, but I'm not familiar
with this.
Just found out that surface ~ '.*gravel.*' covers tags like surface=gravel;sand
:-)
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Thanks ,both of you ; will have a go
Good point also about case sensitivity
I'm trying to get icons for various petrol stations / hotels / supermarkets
so they show up on my nuvi
without having to create individual exceptions
--
View this message in context:
name ~ '[Ss]parda.*'
will find sparda and Sparda
Am 16.10.2011 18:03, schrieb Minko:
I understand this can be done with regular expression, but I'm not familiar
with this.
Just found out that surface ~ '.*gravel.*' covers tags like surface=gravel;sand
:-)
Yes, it finally worked , providing you select the correct type! I had
initially set my type too high.
amenity=fuel operator ~ 'Tesc.*' [0x6201 resolution 20 resume next ]
This gave me all the Tesco (+ Extra) fuel pumps in the area.
Thanks again
--
View this message in context:
I have tried now to flag unpaved roads with the following string:
highway=* surface ~
'.*(cob|compact|dirt|earth|gr|loam|mud|peb|sand|unpaved).*' { add
mkgmap:unpaved=1 }
This will include things like:
misspellings (surface=coblestone)
variations like cobblestones and cobblestone;
I'm not sure if this is always a good thing. If these faults wont cause
a different look in the map, no one will fix these faults. I think it
will be better to repair osm-data e.g. with taginfo.
Henning
___
mkgmap-dev mailing list
