[Imports] Importing Indianapolis data
emacsen at gmail.com
Thu Apr 9 15:52:48 UTC 2015
Thanks for your interest in getting this data into OSM. That's very exciting!
We have lots of reasons for needing to evaluate the data pre-seeing it
on OSM. Looking at the sample data you provided, I have a few
1. Simple rectangular ways have more nodes than necessary eg
2. I am not sure about the need for a lot of these address tags. I
think a city or county boundary makes a lot more sense.
3. The source tags belong on the changeset, rather than the individual objects
4. "website" is also for individual features, and doesn't belong on
These are all fixable of course.
 Also, please, in the future, don't use osm.org to test this
process on, supplying an .osm file would be much better, both from a
testing, and license perspective, as well as generally following the
On Thu, Apr 9, 2015 at 11:39 AM, EthnicFood IsGreat
<ethnicfoodisgreat at gmail.com> wrote:
> Thanks to everyone who responded with all the suggestions on importing the
> Indianapolis GIS data. I will check out the links that some of you
> What I am talking about are mass uploads. I was initially planning to
> import building footprints. I already manually imported a few to see what
> the results would look like, using JOSM and the OpenData plugin. You can
> see them here: http://www.openstreetmap.org/#map=18/39.78975/-86.09067. As
> far as I can tell, I translated all the address information from the
> shapefile attributes to the appropriate OSM tags. All the buildings I want
> to import from our data have addresses attached (street name, number,
> zipcode, etc.) We have many more buildings mapped that do not have
> addresses on them (e.g. detached garages, sheds, outbuildings) which could
> also be imported (I included four of them in my test import), but I figured
> the addressed buildings are much more important for now.
> I had looked at Paul Norman's ogr2ogr tool, and it sounds great, but I do
> not know Python and have never used it. Neither have I used ArcGIS
> ModelBuilder or QGIS. I was hoping not to have to learn any new software in
> order to do the import, so that's why I was initially interested in shp2osm.
> But it sounds like ogr2ogr is the way to go, so if someone could walk me
> through how to use it, along with the custom translations, that would be
> great. (I already have Python installed.) Years ago I did some coding, but
> not in any of the newer languages.
> Paul, can you expand on getting local support? It seems to me that adding
> buildings in a major city that has almost none is a no-brainer.
> Mark Bradley
> Imports mailing list
> Imports at openstreetmap.org
More information about the Imports