sent from a phone
> On 22. Dec 2017, at 22:27, Rainer wrote:
>
> So it would be contact:addr:postcode_major_recipient
nice, maybe we could add the issuer as well, e.g.
contact:addr:deutsche_post_aktiengesellschaft:postcode_major_recipient
;-)
seriously, something more
Thinking about contact:addr:*, that sounds like a good idea.
So it would be contact:addr:postcode_major_recipient
Advantage is that it describes the purpose to be used for contacting the
company, authority, hospital or whatever POI, but not e.g. for
navigation, because it doesn't have a
I think one mapping practice with contact:* could help .
1- addr:* tag space is for generic addresses, used by all consumers
2- if there is ambiguity between adresses (postal, physical, ...) then
use several namespaces
2a - addr:* tag space for physical address (used by geocoding, routing, ...)
Hi,
The British terminology for this is a 'non-geographic postcode'. I suggest
that this terminology might make a more appropriate general tag because
a) The purpose of the tag to indicate the non-geographic nature of the
postcode, not the volume of post the address recieves
and
b) Special
Am 17.12.2017 um 21:22 schrieb Warin:
> As they are not related to a physical address then why use the address
> space?
The addr tag space is for postal addresses, that are not guaranteed to
be physical at all (for example addr:city is the postal city, which
might be completely un-surveyable).
Hello,
In stead of creating an additional tag and thus an additional country
specific rule,
why not using addr:full (or in the contact namespace if some prefer) to
put this special addr that doesn't follow the standard country rule ?
Regards,
Marc
Le 17. 12. 17 à 22:25, Rainer a écrit :
>
sent from a phone
> On 17. Dec 2017, at 21:26, José G Moya Y. wrote:
>
> Obviously, phone numbers and email addresses are not "on the ground", so they
> are just as out of scope of OSM as PO boxes/special zips are.
I believe this is a very limiting view of both, the
They are used together with addr:city. The combination aoff
addr:postcode_major_recipient and addr:city acts as an alias for
addr:postcode & addr:city & addr:street & addr:housenumber.
Am 17.12.2017 21:22, schrieb Warin:
As they are not related to a physical address then why use the address
El 17/12/2017 21:17, "Tom Pfeifer" escribió:
On 17.12.2017 14:36, José G Moya Y. wrote:
>
> National-wide phone numbers treated (such as +1-800-x in USA, cellphones,
> "vocal nomad" numbers (+34-51-xx in Spain, if I remember well) are
> unlinked to physical addresses
As they are not related to a physical address then why use the address
space?
Possibly the contact space? contact:mail:postcode=*
-
I believe 1800 numbers cannot be used internationally, so I don't use
the ISD codes, that OSM requests, with these.
On 18-Dec-17 12:36 AM,
On 17.12.2017 14:36, José G Moya Y. wrote:
Do you mean PO box? In some cities, massive PO boxes have a special Zip code/ postal code. It could
be a property of the PObox address.
It is kind of a postbox, but the mail might actually still be delivered by the carrier (and not
picked from a
Do you mean PO box? In some cities, massive PO boxes have a special Zip
code/ postal code. It could be a property of the PObox address.
Maybe an attribute at the POI is right, as POI use to list email addresses
and web addresses, which are independent from actual physical address (as
PO boxes
As these postcodes are kind of a virtual address that is not tied to a particular pysical location,
my opinion would be _not to add them to OSM_, which is a geo database and not primarily a post code
reference database.
Typically for those companies in DE, there is an additional physical
Hi all,
recently I came across postal codes in POI addresses, which aren't the
classic scheme addr:postcode & addr:city & addr:street &
addr:housenumber. However it is a special postcode that is assigned to
recipients that receive a big amount of post every day, typically big
companies or
14 matches
Mail list logo