I understand! The counties are fine for splitting up the data. These zip codes are very interesting anyway, but it looks like some real work will be needed to process them. After looking on the net, I think there will be a big market for such data and I am facinated by the idea of being able to make money from this.... need to think about it some more.
mike On Sun, Dec 20, 2009 at 9:15 PM, Katie Filbert <[email protected]> wrote: > On Sun, Dec 20, 2009 at 2:54 PM, [email protected] > <[email protected]> wrote: >> >> This is even more detailed, >> I have uploaded the osm files : >> >> http://ia341327.us.archive.org/0/items/OpenstreetmapZipcodes/tl_2009_34_zcta5.osm >> and >> >> http://ia341327.us.archive.org/0/items/OpenstreetmapZipcodes/tl_2009_34_zcta3.osm >> > > Using cartographic license, the Census Bureau came up with boundaries that > do not overlap. These are not the same as official USPS zip codes, used for > mail delivery. > > Also, the Census Bureau zip code files are way out of date. (although it's > 2009 TIGER data, the zip codes are dated 2002 and 2000) > > Please try some other unit of geography, such as Census tracts, for dividing > up OSM data in chunks to work on. For importing, zip code boundaries are > not appropriate for OSM. > > -Katie > > PS. - Do note that using and not understanding zip code polygons is a common > mistake seen in academic literature, such as using them to normalized date. > It happens even in some scholarly geography journal articles. > > _______________________________________________ > Talk-us mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/talk-us > > _______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-us
