[Talk-us] importing zip codes

Steven Johnson sejohnson8 at gmail.com
Mon Feb 17 20:00:39 UTC 2014


Formally, the Census product is called ZCTAs - Zip Code Tabulation Areas,
and they are polygons. They are useful in a variety of operations internal
to Census Bureau, and externally as part of the transportation planning
program but, as others have pointed out, they are NOT official Zip codes.
The Zip codes maintained by the USPS are point features; attributes of the
postal address. They are often grouped in the Delivery Sequence File, and
in that sense, represent linear features.

I commend Charles for wanting to improve the Zip code data within
OpenStreetMap, but given the second-hand provenance, it's dubious currency,
and structure of the data, I would recommend against importing it. Like
others, I'd recommend contacting the Imports group and take up the issue
with them.

Best,
SEJ

-- SEJ
-- twitter: @geomantic
-- skype: sejohnson8

There are two types of people in the world. Those that can extrapolate from
incomplete data.


On Mon, Feb 17, 2014 at 2:52 PM, Toby Murray <toby.murray at gmail.com> wrote:

> What exactly is the census data representing? Zip codes are not polygons
> (they are routes) so I'm curious what exactly they are modeling.
>
> But beyond that, I'm not sure zip code boundaries are all that useful in
> OSM. I think Nominatim already figures out zip code basics from
> addr:postcode values in the data although I'm not overly familiar with its
> internal workings.
>
> Toby
>
>
>
> On Mon, Feb 17, 2014 at 1:11 PM, <osm at charles.derkarl.org> wrote:
>
>>
>> Hi,
>>
>> I have a shape file from census.gov which contains the boundaries for
>> all zip
>> codes in the US. This data should not need licensing in that it comes
>> from the
>> us federal census.
>>
>> I would also like the community to answer this technical question: Each
>> boundary obviously shares a border with another zip code. Should those
>> shared
>> boundaries have the same way, and then each zip code becomes a relation?
>>
>> Failing any negative replies, I will cook up an implementation and provide
>> some .osm files for review before importing.
>>
>> Charles
>> Boulder Creek, CA, USA
>>
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
>>
>
>
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20140217/1b06b64e/attachment-0001.html>


More information about the Talk-us mailing list