Thanks for taking the the time to look things over - we'll definitely use your advice. A few follow up things:
> I was unable to open the xml files. Do you have any osm files we could view? Does this one work? https://github.com/atx-osg/atx-buildings/raw/master/xml/482090108062-buildings.xml It opens on my computer in JOSM (version 8677). > When we did the Seattle building and address import, we tried the JOSM conflation plug it. Because of problems using the plugin, we decided to do the import without. The fall back is training people to look for existing objects when they import. Oh no - what kinds of problems? The plugin is enticing because it handles some of the weirder parts of the import by deferring to human judgement in a natural way. It seems to do okay on the few neighborhoods I've looked at, but we'll ditch it if it will be more trouble than it is worth. Thanks again! -andy On Mon, Sep 28, 2015 at 2:25 PM Clifford Snow <[email protected]> wrote: > > On Mon, Sep 28, 2015 at 8:10 AM, Andy Wilson <[email protected]> > wrote: > >> The City of Austin has recently put much of their GIS data into the >> public domain. A group of volunteers from the Austin Open Source GIS Users >> Group and Open Austin (local Code for America brigade) would like to pull >> this data into OpenStreetMap. >> >> Our focus right now is the set of building footprints and address point >> data. We are trying to follow the Import Guidelines and have posted our >> plan for review on the OSM wiki: >> https://wiki.openstreetmap.org/wiki/Austin,_TX/Buildings_Import >> >> We are still finalizing data processing scripts and logistics / >> coordination details, but I think we've nailed down the main pieces. If >> anyone could spare some time to review our approach, it would be much >> appreciated. Thanks! >> > > I was unable to open the xml files. Do you have any osm files we could > view? > > State and Country address tags are not required. A geospatial lookup can > determine state and country. > > The metadata shows an obectid field. If the id has persistence, I would > suggest including it in the import. You could use it with a script to keep > the address data updated from the cities monthly updates. > > Addresses on vacant lots and parks are useful for routing. I would > recommend importing them. > > When we did the Seattle building and address import, we tried the JOSM > conflation plug it. Because of problems using the plugin, we decided to do > the import without. The fall back is training people to look for existing > objects when they import. > > I also recommend using a JOSM map paint style address tag validator to > help find errors between addresses and streets. There are a few available. > > Good luck, > Clifford > > > > -- > @osm_seattle > osm_seattle.snowandsnow.us > OpenStreetMap: Maps with a human touch >
_______________________________________________ Imports-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports-us
