Cannot add assertMatch/assertNoMatch declarations with inside() selector

[Don-vip]

From IRC it appears this is not possible to write this:

node[amenity=parking][inside("BR")] {
  throwWarning: "foo";
  assertMatch: "node amenity=parking";
  assertNoMatch: "node amenity=restaurant";
}

[17:28:55] <vorpalblade> For the validator.mapcss, does anyone know how to write an assertMatch for specific countries, e.g. [inside("US")]?
[17:40:46] <@don-vip> vorpalblade take a look to Brazilian rules: https://github.com/OSMBrasil/validador-josm/blob/master/Rules_Brazilian-Specific.validator.mapcss
[17:43:55] <vorpalblade> They don't appear to have any assertMatch/assertNoMatch statements.
[18:00:29] <@don-vip> ah sorry I misunderstood. It's not possible, the "inside" keywork is only applicable to selectors
[18:01:07] <@don-vip> why would you want to use this in the assertMatch clause ? 
[18:09:40] <vorpalblade> I want to specify the location of the assertMatch -- I always get errors on assertMatches inside checks which specify countries. If I remove the inside("COUNTRY"), the errors stop.
[18:10:14] <vorpalblade> Example: *[name="TODO"][inside("US")] { throwError: tr("Name is TODO"); assertMatch: "node name=TODO"; }
[19:41:11] <@don-vip> ah, probably we create primitives at (0,0) for assert rules
[19:41:57] <@don-vip> we should create them at the centroid of the first country specified in an inside clause
[20:20:57] <vorpalblade> OK. Thanks. I thought that might be the case, and if it was, I thought there *might* be a way to specify the lat/lon of the primitive.
[22:36:58] <@don-vip> no I simply didn't think to it

This is because fake primitives created for the assertions are always located at (0,0) instead of the correct country.

[Don-vip]

In 14484/josm:

fix #17058 - Cannot add assertMatch/assertNoMatch declarations with inside() selector

[GerdP]

Several unit tests fail because relations now have an unexpected node member at (0,0)

[Don-vip]

In 14486/josm:

see #17058 - fix unit tests

[Don-vip]

It broke Styles/Lane_and_Road_Attributes don't know why yet.

[GerdP]

Maybe it was r14481?

[Don-vip]

Yes, but I don't understand why. My new rule should only catch declarations starting with -.

[GerdP]

Not sure but I think a simple ant dist after an svn update didn't update MapCSSParser.
I've now done ant clean dist and see the modifications in MapCSSParser, but now JOSM refuses to start, see start-error.txt

[Don-vip]

It seems your epsg ant task has not run. Or if you run JOSM from eclipse you may have forgotten to refresh your project (F5).

[GerdP]

Yes, sorry, F5 did the trick. I think you have to tell the parer that MINUS should only match at the beginning of the line.

< EXTIDENT: <MINUS> <IDENT> >

[Don-vip]

Yes r14489 did the trick :)

[GerdP]

Really? On my machine Styles/Lane_and_Road_Attributes looks almost like Wireframe View.

[Don-vip]

Works fine for me, you probably need to recompile the .jj file.

[GerdP]

I tried from Eclipse as well as command line after

• svn up
• ant clean dist
• cd dist
• java -jar josm-custom.jar

See

[GerdP]

With r14508 I've now pressed the Reset button in Map Paint Styles dialog and re-added the Lane and road attributes. After that action the style works again.

[Klumbumbus]

I tried to readd the assert, but the assertMatch statements fail.

territories.mapcss

@@ -10 +10 @@
 *[addr:street =~ /(?i).*Strasse.*/][addr:street !~ /(?i).*Strasser.*/][inside("DE,AT")],
 *[name =~ /(?i).*Strasse.*/][name !~ /(?i).*Strasser.*/][inside("DE,AT")] {
   throwError: tr("street name contains ss");
+  assertMatch: "way name=Hauptstrasse";
+  assertNoMatch: "way name=Hauptstraße";
+  assertNoMatch: "way name=Kapitän-Strasser-Straße";
+  assertNoMatch: "way name=Peter-Strasser-Platz";
+  
 }
 *[addr:street =~ /(?i).*Straße.*/][inside("LI,CH")],
 *[name =~ /(?i).*Straße.*/][inside("LI,CH")] {
   throwError: tr("street name contains ß");
+  assertMatch: "way name=Hauptstraße";
+  assertNoMatch: "way name=Hauptstrasse";
 }

INFO: Source Validatortests has been modified. Reloading it...
Dec 09, 2018 6:02:13 PM org.openstreetmap.josm.data.validation.tests.MapCSSTagChecker addMapCSS
WARNING: Expecting test 'street name contains ss' (i.e., [*[addr:street'REGEX'(?i).*Strasse.*][addr:street'NREGEX'(?i).*Strasser.*][ParameterFunction~inside(class org.openstreetmap.josm.gui.mappaint.Environment,class java.lang.String <DE,AT>)], *[name'REGEX'(?i).*Strasse.*][name'NREGEX'(?i).*Strasser.*][ParameterFunction~inside(class org.openstreetmap.josm.gui.mappaint.Environment,class java.lang.String <DE,AT>)]]) to match way name=Hauptstrasse (i.e., TagMap[name=Hauptstrasse])
Dec 09, 2018 6:02:13 PM org.openstreetmap.josm.data.validation.tests.MapCSSTagChecker addMapCSS
WARNING: Expecting test 'street name contains ß' (i.e., [*[addr:street'REGEX'(?i).*Straße.*][ParameterFunction~inside(class org.openstreetmap.josm.gui.mappaint.Environment,class java.lang.String <LI,CH>)], *[name'REGEX'(?i).*Straße.*][ParameterFunction~inside(class org.openstreetmap.josm.gui.mappaint.Environment,class java.lang.String <LI,CH>)]]) to match way name=Hauptstraße (i.e., TagMap[name=Hauptstraße])

[Don-vip]

In 14540/josm:

fix #17058 - support assertions with several countries

[Klumbumbus]

In 14552/josm:

• see #16301 - make id mandatory
• see #17058 - add asserts to territories.mapcss

[Klumbumbus]

I think this ticket is still not fully fixed. See r15325 I added:

*[aeroway=aerodrome][!icao][faa!~/\d/][inside("US")],
*[aeroway=aerodrome][!iata][faa!~/\d/][inside("US")] {
  throwOther: tr("{0} without {1}", "{0.tag}", "{1.key}");
  group: tr("Airport tagging");
  /* assertNoMatch: "way aeroway=aerodrome faa=OK12"; not properly working due to inside() */
  /* assertMatch: "way aeroway=aerodrome faa=ORD"; */
}

I commented the asserts because one doesn't work and the other fails when [inside("US")] is used. Or did I anything wrong?

[Don-vip]

Replying to Klumbumbus:

did I anything wrong?

No, I did. I created #18097

[Don-vip]

In 15359/josm:

see #17058, fix #18097 - fix MapCSSTagChecker.getLocation