Talk:Addresses/Archive 1
Better documentation needed
Better documentation, with examples, is needed to make entry and editing of address information easier. For several years, one of the big complaints about OpenStreetMap.org databases being exported to smartphones and handheld GPS units is that entry of a specific street address might get one to the geometric midpoint of a street or road, but that may be many miles or kilometres from one's intended destination. From comments I've read on the Web, I gather this is a particularly severe problem outside of Europe. As the article currently stands, it lacks concrete examples of how address information can be added to a street such that not every house number is added, but by inserting the house numbers at the ends of city blocks or at road intersections, the software can calculate approximate locations and get one closer to the actual location sought. I've read the article as it now stands and am unable to make any sense of it. It would be better to define it in a "how-to" section than to leave it up to volunteer editors to try to experiment with data entry and produce a big mess that would need to be cleaned up later. — User8192T @ 20:53, 5 January 2015 (UTC)
- Well, the information is there: Addresses#Using_interpolation. In short, the known addresses (f.e. the corner addresses) are mapped as nodes, with addr:housenumber=*, addr:street=* and all other tags you'd expect there. Then, there's a way drawn that connects the know addresses from low to high (note that intermediate points may also be addresses, or they may be non-tagged nodes just to define the form of the interpolation line). Then the interpolation line is tagged with addr:interpolation=even/odd/all to define the type of interpolation. In Mapnik, the housenumbers are rendered like normal, but interpolation lines show a thin black line. --Sanderd17 (talk) 15:30, 8 January 2015 (UTC)
Resolved: Seems to require no action Mateusz Konieczny (talk) 11:27, 25 September 2020 (UTC)
Buildings with multiple postcodes
How to tag buildings which have more than one postcode ? -- pmailkeey 2016:6:30
- Exactly the same way you can have buildings with multiple house numbers in streets ! Create as many address nodes as needed, don't tag the buildings themselves with addresses ! — Verdy_p (talk) 05:15, 11 March 2017 (UTC)
- Resolved: Seems to require no action, it is documented on the page Mateusz Konieczny (talk) 11:27, 25 September 2020 (UTC)
2 companys/places one address?????
Tried to drag the two comp./places on the address, but it combined all the tags so it was inpossible to relate different tags to eachother eg. name and type of place. Tried to use relations, but idk the role the companies/places should use in the relation or what i should tag the relation. (sorry for bad eng.) --unsigned comment by: Sssandum, 10 March 2017, 17:47 (UTC)
- Usually the simplest solution is to place two nodes at very close locations on the same building, so that you can tag each POI separately (also separately from the address node which would contain only the housenumber/housename; and the street name if there's no associatedStreet where that address node would be a member with role "house"). You don't need to repeat the address on the 2 POIs for companies.
- Using relations seems overkill, but it's possible:
- You'll need one separate relation per company/POI, containing the same address node or building way as its single member.
- Don't tag the address node for describing any one of the 2 companies/POIs, the address node will only have addr:housenumber/name (and "addr:street=*" if not part of an associatedStreet relation, plus posibly "addr:city=*" if this is ambiguous for the same street name split between or separating two cities).
- But tag the two separate relations to give their company names, or contact name/phone, opening hours, or type of activity, but don't tag its location address (which is already indicated by their member node or way containing "addr:*=*" tags).
- Note that some POIs won't be recognized in some renderers if they are tagged as relations (the same renderers have also problems sometimes with addresses using closed ways or multipolygon-relations for buildings instead of single nodes, but we should not be limited here by tagging for specific renderers, including non-graphical renderers such as plain text search tools like Nominatim). — Verdy_p (talk) 04:52, 11 March 2017 (UTC)
- Adding the same address properties to several features is not a problem. You'd rather have to do it in some places, where addresses cannot be expressed well with polygons. E.g. in Italy you usually get a housenumber for every possible entrance (even if it is not used currently). This leads to many shops being accessible via several address nodes (but often they do not use all of them as a range, but specify the one that is their main entrance). On the other hand, and this is applying to your question, doctors tend to be in the upper floors, i.e. mostly accessible via the stairs and the same entrance, so they have the same address even if they are different businesses in different apartments/offices, different floors, etc. The easiest solution to the problem is repeating the address property on every feature and interpret the address as a property of the feature (and not as a feature of it's own as it is also often done)--Dieterdreist (talk) 16:40, 15 May 2017 (UTC)
- Resolved: Seems to require no action, it is documented on the page Mateusz Konieczny (talk) 11:28, 25 September 2020 (UTC)