Re: [mkgmap-dev] add-pois-to-areas entrance as option

You should only tagg the hole polygon as restaurant etc. if the hole polygon contains only this restaurant. Else you should tagg each restaurant etc. as a node inside the building-polygon. Henning ___ mkgmap-dev mailing list

[mkgmap-dev] uisng wildcards in names

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:

Re: [mkgmap-dev] uisng wildcards in names

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 ~

Re: [mkgmap-dev] uisng wildcards in names

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

Re: [mkgmap-dev] uisng wildcards in names

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:

Re: [mkgmap-dev] uisng wildcards in names

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 :-)

Re: [mkgmap-dev] uisng wildcards in names

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:

[mkgmap-dev] Routing with the eTrex 30

Hi all, A couple of weeks ago some of you asked me about the routing capabilities of the new eTrex 30 model. First of all, as I said before. My previous model was a Venture HC, so without routing. I had nothing to compare to, when it comes to routing on an eTrex. Today I finally had time to do

Re: [mkgmap-dev] uisng wildcards in names

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;

Re: [mkgmap-dev] uisng wildcards in names

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

Re: [mkgmap-dev] using wildcards in names

Sure, if those are clear tagging or spelling errors, but is surface='sand;gravel' or surface='loose sand' faulty tagging? How about tags like amenity=restaurant;cafe or cafe;bar or cafe-restaurant? Btw you could cover them with amenity ~ '.*(cafe|restaurant|bar|pub).*'

Re: [mkgmap-dev] Routing with the eTrex 30

Thanks Frank, Thats what I already feared. Hofzicht (Cycleway) is a created line by mkgmap with the make-all-cycleways tag (cycleway=opposite) make-all-cycleways If you are using a style file this option is not necessary because it can be created in the line styles with continue statements and