Talk:Key:object
Just a stopgap?
For something like a fire hydrant in front of a house or a memorial within a park, it seems to me that object=* would be a less-than-ideal way to tag the address. In a jurisdiction where a parcel of land has an address (not just the building on it), a landuse area like landuse=residential or leisure=park could be tagged with addr=* as usual, and data consumers could infer the siren or hydrant's address from the containing landuse area. That said, if the address is coming from an import of fire hydrants, object=* could be a temporary place to store the address until it could be moved to an addr=* on a more appropriate feature. – Minh Nguyễn 💬 20:55, 23 January 2020 (UTC)
- See my latest change, I incorporated your annotations to the specification. Sry for replying so late, there is much work to do --Valor Naram (talk) 19:09, 29 January 2020 (UTC)
- @Valor Naram, what was the reasoning behind the definition of this key? All objects in the OSM database are uniquely described by the georeferencing and can therefore be easily assigned to the correct postcode/street/house number via border relations. A large part of the data seems to have been created by an import: https://taghistory.raifer.tech/#***/object:postcode/ Has the import been documented and approved somewhere, as the rules require? --geow (talk) 21:28, 16 March 2020 (UTC)
- For developers or database specialists finding out the said information is easy, you're right. I am not the author of the key. I just translated its documentation to English (more or less accurate because I do not understood everything). I do not like it when a Key/Tag has no documentation in English. The author of the key is BlackBike --Valor Naram (talk) 18:52, 19 March 2020 (UTC)
- According to the originator of the tag (BlackBike?), it was actually added by a mechanic edit / automated edit of existing objects, not officially an import, though the same concerns may apply. It may have been discussed in Germany only? --Jeisenbe (talk) 02:01, 20 March 2020 (UTC)
- @Valor Naram, what was the reasoning behind the definition of this key? All objects in the OSM database are uniquely described by the georeferencing and can therefore be easily assigned to the correct postcode/street/house number via border relations. A large part of the data seems to have been created by an import: https://taghistory.raifer.tech/#***/object:postcode/ Has the import been documented and approved somewhere, as the rules require? --geow (talk) 21:28, 16 March 2020 (UTC)
- Is the postal address or no physical address requirement even explicit or formal? It seems to be from proposals or drafts. There was at least Talk:Addresses#Which_address_are_we_mapping:_postal_or_physical_.3F directly asking, suggesting contact:*=*. post=* is suggested on Tag:amenity=letter_box. On the postal aspect, there are quite numerous discussions on different postal address, and PO boxes. -- Kovposch (talk) 06:34, 17 March 2020 (UTC)
Why not is_in=*?
object=* doesn't really mean anything. The prefix itself should be clear on its own. This would also avoid you needing to decide "It is not used in combination with the Key:addr:* tags." in a new key -- Kovposch (talk) 06:44, 17 March 2020 (UTC)
- I just translated the key from its original German page to English. This way I hoped this key gets more attention and can be more ratified (maybe lead to a proposal that covers cases the key describes). Please contact BlackBike, he's the author of the key. I also personally think you should document new Keys/Tags in English first. --Valor Naram (talk) 18:52, 19 March 2020 (UTC)