[Talk-GB] Beta release: Address mapping tool

[Adrian]

I would like to suggest some refinements to the address mapping tool, mainly for addresses that are already at least partially tagged.

The tool is not picking up street names from associatedStreet relations (and street relations presumably). It is flagging addr:street as missing. In GB (from taginfo) addr:street has 120,000 different values and there are 12,000 associatedStreet and street relations. So a significant number of street addresses that have been mapped, are being missed. Example: all the addresses tagged on Broadmead https://pietervdvn.github.io/mc/develop/uk_addresses.html?test=true&z=19&lat=51.49323&lon=-0.21279&language=en

It is not displaying flat numbers that have been tagged with addr:flats and a range. Instead it is soliciting a single flat or unit number. It needs to display the value of addr:flats with an explanation in words: "all flat numbers from {start} to {end} inclusive". (This is the rule, because address interpolation does not apply to addr:flats.) It needs to give the contributor the possibility to correct the value of addr:flats. The displayed envelope needs to show one example of the address with a flat number (and say this is one example), or possibly allow the user to click through all the flat numbers in sequence. Example: all the flat numbers tagged on the six entrances to Broadmead, URL as above. The tool gives the impression that those six nodes are all duplicates of each other. Question: should the user be given the opportunity to add a range of flat numbers if there isn't an addr:flats tag?

Where it has been tagged, address interpolation/interval needs to be interpreted and spelled out. In other words
"all house numbers from {start} to {end} inclusive"; or
"odd numbers from {start} to {end}"; or
"even numbers from {start} to {end}"; or
"a single address with this value".
If addr:housenumber consists of two numbers separated by a dash, and the interpolation has not been tagged, the user needs to be asked to choose from among the appropriate ones of the above four options (odd numbers would only be offered if start and end are odd, similarly for even numbers). This question would also be asked if the user enters two numbers separated by a dash. In the case of multiple house numbers, the displayed envelope needs to show one example of the address with a house number, or possibly allow the user to click through all the numbers in sequence. Examples:
40-70 Munden Street (interpolation tagged as all)
1-7 Fitz-George Avenue (interpolation not tagged, it should be odd)
41-49 Edith Road (interpolation tagged as none, note this is a combination case where there is also addr:flats. So an example address would be Flat 5, 41-49 Edith Road.)
These are all near the above URL, they should be reasonably easy to find. The addressing in this area is a bit of a mess; this is at least in part because iD hides some of the tagging from the user.

Semicolon notation (separating items in a list) needs to be interpreted, so that users don't see semicolons. For instance, "numbers {a}, {b} and {c}". Example: flats 1A and 1-12 Auriol Mansions, near the above URL. This is a combination case of addr:flats and semicolon notation: addr:flats=1A;1-12.
Example: 31;10 on Southcombe Street and Vernon Street https://pietervdvn.github.io/mc/develop/uk_addresses.html?test=true&z=19&lat=51.49436&lon=-0.21143&language=en (This is a case where iD may have played a part in creating a mess, because it hid from the user, the address tags that were specified in associatedStreet relations. The user moved the address tags he could see, onto a new multipolygon.)
Example: 12;26 Trevanion Road https://pietervdvn.github.io/mc/develop/uk_addresses.html?test=true&z=19&lat=51.49066&lon=-0.20988&language=en

Please don't fix up any of the "mess". This is to allow other users to see the same things that I have seen.