[Imports] [Imports-us] New Orleans: importing buildings and addresses
elliott.plack at gmail.com
Thu Oct 23 14:16:00 UTC 2014
Matt: good work on getting this started. It is definitely unfortunate that
the address points are not spatially paired with the buildings. In my
Baltimore County import, address points are placed at the building
centroid unless there are multiple, (then they are placed at the unit
centroid). If the spatial component of the address node is unspecific, e.g.
it is at the parcel center, than I recommended conflating them if they do
fall within the building footprint, as I did .
Since ZIP Codes aren't part of the source data, I would not spend a ton of
time trying to source them. It might actually distort the authoritativeness
of the original data in that you would be combining a verified source and a
derived source. I think you should proceed without them and utilize JOSM
and the select within tool to add them as a separate import project,
thereby keeping the lineage separate.
 = http://www.openstreetmap.org/#map=18/39.37694/-76.60895
On Thu, Oct 23, 2014 at 9:09 AM, Richard Welty <rwelty at averillpark.net>
> On 10/23/14 8:05 AM, Eric Ladner wrote:
> On Wed, Oct 22, 2014 at 7:20 PM, Matt Toups <mtoups at cs.uno.edu> wrote:
>> Unfortunately there are no ZIP codes in the address data set.
> Again, an area where a GIS database rocks. Import a zip code data set
> into another table, at extract time get the zip code for the particular
> address node in question with a ogr2osm filter.
> what zip code data sets exist that are appropriately licensed? ZCTA
> from TIGER is public domain, but it has some limitations (although i'm
> going to be using it anyway, but not for import to OSM.)
> -- rwelty at averillpark.net
> Averill Park Networking - GIS & IT Consulting
> OpenStreetMap - PostgreSQL - Linux
> Java - Web Applications - Search
> Imports-us mailing list
> Imports-us at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Imports