Re: [talk-ph] several variations of postcodes in osm-ph

2009-09-15 Thread ian lopez
ng sambale wrote: From: maning sambale Subject: Re: [talk-ph] several variations of postcodes in osm-ph To: "Eugene Alvin Villar" Cc: "osm-ph" Date: Tuesday, September 15, 2009, 11:49 AM On Tue, Sep 15, 2009 at 11:40 AM, Eugene Alvin Villar wrote: > I suggest using addr:po

Re: [talk-ph] several variations of postcodes in osm-ph

2009-09-14 Thread maning sambale
On Tue, Sep 15, 2009 at 11:40 AM, Eugene Alvin Villar wrote: > I suggest using addr:postcode exclusively. > > Zip codes in the Philippines is really meant to facilitate addressing and > addr:postcode does that nicely. +1 here > Redundancy issue: > The issue above (of which key to use to store zi

Re: [talk-ph] several variations of postcodes in osm-ph

2009-09-14 Thread Eugene Alvin Villar
I suggest using addr:postcode exclusively. Zip codes in the Philippines is really meant to facilitate addressing and addr:postcode does that nicely. Also, I don't think tagging streets with postal_code is that useful and may even be harmful. We'd be splitting streets whenever they cross a boundar

Re: [talk-ph] several variations of postcodes in osm-ph

2009-09-14 Thread maning sambale
Follow-up. the is_in:zip may came from data imports. OSM map features actually recommends two: addr:postcode - normally attached to an address node/way of a POI postal_code - same as above, but can be applied to streets as well On Tue, Sep 15, 2009 at 10:22 AM, maning sambale wrote: > Hi, > > T

[talk-ph] several variations of postcodes in osm-ph

2009-09-14 Thread maning sambale
Hi, There are several key tag for philippine postcodes in the Philippines. addr:postcode postal_code is_in:zip Often, these postcodes is attached to a POI. Can we "standardize"? Any ideas? -- cheers, maning -- "Freedom is still the most rad