Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#9667 closed enhancement (fixed)

[Patch] Verify interpolation range/values (via MapCSS?)

Reported by: naoliv Owned by: team
Priority: normal Milestone: 14.03
Component: Core validator Version:
Keywords: mapcss Cc:


Could JOSM verify the range/values of address housenumber interpolations?
Using the attached example, it's clear to see that 300 is way out of the range.
Maybe verify if the values in the range are sorted? (and if not give a warning)

Attachments (2)

interpolation.osm (1.3 KB ) - added by naoliv 10 years ago.
9667.patch (7.5 KB ) - added by simon04 10 years ago.

Download all attachments as: .zip

Change History (13)

by naoliv, 10 years ago

Attachment: interpolation.osm added

comment:1 by naoliv, 10 years ago

Could also test for the node values. If the interpolation is even, the numbers should be even (it doesn't make sense to have an odd number in an even range, for example).

comment:2 by Don-vip, 10 years ago

Milestone: 14.02

comment:3 by simon04, 10 years ago

Keywords: mapcss added
Summary: Verify interpolation range/values[Patch] Verify interpolation range/values (via MapCSS?)

The attached patch adds a child selector node_{i} + node_{i+1} in a way, similar to the + of CSS. Then

*[tag("addr:housenumber") > child_tag("addr:housenumber")][regexp_test("even|odd", parent_tag("addr:interpolation"))] + *[addr:housenumber]

matches nodes with a decrease of addr:housenumber within addr:interpolation=even/odd. Short and simple, isn't it? ;-)

Last edited 10 years ago by simon04 (previous) (diff)

by simon04, 10 years ago

Attachment: 9667.patch added

comment:4 by naoliv, 10 years ago

And what about addr:interpolation=all and addr:interpolation=alphabetic? Will it be possible to warn about a addr:interpolation=all with nodes having the values 1 2 4 3 5, for example? (note that we have a wrong sequency of numbers in 3 and 4)

comment:5 by simon04, 10 years ago

Letters in house numbers do not work with this method. addr:interpolation=all has just to be enabled. I do not fully grasp the example 1 2 4 3 5 – how does that conceptually differ from attachment:interpolation.osm?

comment:6 by naoliv, 10 years ago

1 2 4 3 5 is just an example of an all interpolation with numbers in wrong order, but nothing different from before.
My doubt was that I saw an even|odd and thought if all could also be verified.

comment:7 by Don-vip, 10 years ago

Milestone: 14.0214.03

comment:8 by Don-vip, 10 years ago

Resolution: fixed
Status: newclosed

In 6927/josm:

fix #9667 - Verify addresses interpolation range/values via MapCSS (patch by simon04)

comment:10 by Don-vip, 10 years ago

In 6949/josm:

see #9667 - fix unit test

comment:11 by Klumbumbus, 8 years ago

In 10084/josm:

fix #10232, see #9667 - remove wrong "Decreasing house numbers in addresses interpolation" warning; add "Even housenumber in odd address interpolation." warning and vice versa; add addr:interpolation info

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.