A search indicates that OSM tags are case sensitive and are expected to all be lowercase except for names, example given: highway=Unclassified needs to be highway=unclassified for it to work properly. http://wiki.openstreetmap.org/wiki/Beginners_Guide_1.4.1 So I believe being case sensitive for OSM tag matching is the proper behavior. Bill On 03/17/2014 10:29 AM, GerdP wrote:
Hi Michal,
I think the idea is : "garbage in, garbage out" If the OSM renderer treats highway=Primary in the same way as highway=primary, we should also do that, but I doubt that this is true.
Gerd
Michał Rogala wrote
thanks for information :). But don't you think that such matching should be case insensitive? If by mistake some OSM user creates highway=Primary or trail with colour=Red such object won't appear in mkgmap compilation.
best regards
Michal Rogala
2014-03-17 15:37 GMT+01:00 GerdP < gpetermann_muenchen@ >:
Hi Michal,
the tag is evaluated with the java method String.equals(), so yes, it is case sensitive.
Gerd
Michał Rogala wrote
Hi!
I've always thought that matching tag values is case insensitive. But today I found a situation where
colour='#00ff00'
rule doesn't match when tag value is '#00FF00'.
creating a rule (colour='#00ff00' | colour='#00FF00') solved my problem. Is it a bug in mkgmap or this kind of matching should by design be case sensitive? Maybe the hash sign causes trouble somewhere.
best regards
Michal Rogala
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- View this message in context: http://gis.19327.n5.nabble.com/is-tag-matching-case-sensitive-tp5800033p5800... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list