Opened 11 years ago

Closed 11 years ago

#1181 closed defect (fixed)

Style Editor: "is not _NULL_" does not work

Reported by: Colin Marquardt Owned by: Chris Browet
Priority: minor Milestone:
Component: merkaartor Version:
Keywords: Cc:


The newly changed "is not _NULL_" for [addr:housenumber] does not seem to work, I do not get any house numbers to display. What was the problem with "[addr:housenumber] is *" by the way? I did not see the bug report you appear to have gotten.

I changed my style locally to "[addr:housenumber] is [0-9a-Z]*" for now. I initially wanted "[addr:housenumber] is [0-9][0-9a-Z]*" (to force starting with a number) which according to should work, but doesn't.

Change History (6)

comment:1 Changed 11 years ago by cmarqu

(In [10765]) Nicer sizes for house numbers. They do not render right now though, see #1181.

comment:2 Changed 11 years ago by Chris Browet

Could I have a link to a place with house numbers, please.

My second guess (after a plain bug) would be that a style matches before this one (e.g. "building=yes").

As you know, tag selector are supposed to be mutually exclusive. If not, the first match is taken as a whole, ignoring the others.

Re the "is *", it matches really everything, including non-existing tags (which returns "" by default). The result was that everything after that one was ignored, including the hardcoded fallback styles, like a black line for roads without tags. The result was that newly drawn roads were invisible...

comment:3 Changed 11 years ago by Colin Marquardt

Ah, thanks for the explanation. An area with house numbers is here:

comment:4 Changed 11 years ago by Colin Marquardt

I should add that the "_NULL_" doesn't show up in the style editor, I just see it with a text editor in the mas file.

comment:5 Changed 11 years ago by Chris Browet

My mistake...

Proper syntax is: "not [addr:housenumber] is _NULL_"

comment:6 Changed 11 years ago by Chris Browet

Resolution: fixed
Status: newclosed

(In [10790]) FIX : invalid synatx for "not _NULL_" (fixes #1181)

Note: See TracTickets for help on using tickets.