From frank.hu...@gmail.com on September 18, 2012 13:15:40

I tried to see wheather I have the same issues with AdvancedMapViewer, but I can not load the render theme as I did it inside Locus. The render theme can not find the symbol file as within Locus at /sdcard/Locus/mapsVector/_themes.

I guess I need to adjust all file path settings before I can try to reproduce it without Locus.

From frank.hu...@gmail.com on September 19, 2012 12:26:04

AdvancedMapViewer.apk also shows the wrong symbols: a track tagged with mtb:scale=0 and mtb:scale:uphill=4 show up with symbols for mtb:scale=4 and mtb:scale:uphill=4

From menion.asamm on January 08, 2013 00:00:12

Hi,
problem found in PositiveMatcher and also NegativeMatcher object

point is, that library iterate over all keys and values separately. So when found key from one tag that match and value from different tag that match, it's result is true

solution is something like this

@Override
boolean matchesWay(List<Tag> tags, byte zoomLevel, Closed closed) {
    // basic checks
    if (this.zoomMin > zoomLevel || 
            this.zoomMax < zoomLevel ||
            !this.elementMatcher.matches(Element.WAY) || 
            !this.closedMatcher.matches(closed)) {
        return false;
    }

    // check key/values
    for (Tag tag : tags) {
        if (keyMatcher.matches(tag) && valueMatcher.matches(tag)) {
            return true;
        }
    }
    return false;
}

this do, that I check all tags separately if they match to key & value pair. For this need to be rewrote all matchers objects!

From LudwigBr...@gmail.com on January 13, 2013 19:40:51

I am currently looking into this. To make my life a bit easier, could you add some screenshots, a minimal mapfile with the mtb file in it and a theme?

I think I understand the issue and it should not be too difficult to fix.

Status: Accepted

From devemu...@gmail.com on March 19, 2013 07:28:02

Thilo

Is this issue corrected at the rewrite branch?

It also happens to me (using the master branch) at one of my custom maps and for now I use prefixes as described also at https://groups.google.com/forum/?fromgroups=#!topic/mapsforge-dev/l1sS1PC8qfM Thanks.

From openandr...@gmail.com on July 14, 2013 11:44:11

Question: is this solved in the rewrite?
It affects all yes/no pairs too.

Example: http://www.openstreetmap.org/?lat=47.276&lon=15.1144&zoom=13&layers=M The Gleinalmtunnel at the A9 in Austria, tagged as

• tunnel=yes
• oneway=no
  so the tunnel is rendered as "no", that means as ordinary road.
  With stripped oneway=no the tunnel renders correct.

In the meantime I clear all yes/no's that are not really necessary, however this is no solution. Assigning unique values to tags such as I do with the MTB:SCALE (like tunnel=t_yes/t_no) is no solution cause it leads to incompatible maps depending who is redering them.

From LudwigBr...@gmail.com on August 29, 2014 10:07:57

I just had another quick look at it and unfortunately this is not solved as easily as comment #3 suggests: the problem is basically that the connection between tag keys and tag values has been lost in the optimization process (that I do not really understand), so at that point we do not know what tag the "yes" (one of the more frequent value clashes) applies to.

Fixed in #1366.