1. The errors should be fixed by the user (at least those that were caused by the import). I have yet to look at any of the areas I didn't conflate, so I don't know how they look. For me, the biggest source of validation errors that I've had to fix come from people having imported building footprints in the past in certain areas, as these ended up overlapping slightly with the current import due to the import's simplification steps (and may very well have had validation errors to begin with); another source has been alleys being slightly off and overlapping with buildings. Hopefully any validation errors that slipped past in the initial conflation will be caught during validation. As for POIs, I've been merging them in when I see them, although I'm sure I've missed some.
2. We used neighborhood outlines, which seemed like a reasonable way to divide the data. I don't think time is much of an issue, since someone can always choose one of the smaller areas if he or she wants. In my opinion, the biggest issue with the larger areas is lost work from JOSM crashing. Since we automated the upload of much of the data while you are uploading everything via JOSM, I think it makes sense for you to have used smaller areas. 3. We don't have a contributor guide, although we probably should make one. Elliott might be able to expand on some of the above points. -Matthew Petroff On Tue, Apr 7, 2015 at 1:24 PM, Michael Schnuerle < [email protected]> wrote: > Great work and I've got a few questions that may help with our Louisville > import and upcoming imports. > > http://www.civicdataalliance.org/gis-open-data-american-printing-house-open-street-map/ > > 1) I looked at some of your areas already conflated. There seems to be > lots of Crossing Buildings, Ways, Buildings/Ways errors. Shouldn't these > be fixed by the user? We are also merging POIs into buildings/addresses, > is that required too? > > 2) Your areas are so much larger than ours, with 281 for all of Baltimore > vs 575 for the smaller Louisville. Isn't that hard for users to import? > Even at our sizes it can take someone 30+ minutes to complete an area. But > maybe we are missing something and should have created larger areas. > > 3) Do you have a step-by-step Contributor Guide like other imports have? > We'd like to add some of your tips to ours. > > 4) Does anyone know if the tasks.openstreetmap.us site can get updated > from version 1 to version 2.9+? The current version is buggy and lacks > some usability features (invalidated tasks differently, bigger map, > highlighting who did what) the new version has. Example: > http://tasks.hotosm.org/project/923 > > Thanks! > > *Michael Schnuerle* | Code for America Louisville Brigade Captain > @CivicDataAlly <http://www.twitter.com/CivicDataAlly> | > CivicDataAlliance.org <http://www.civicdataalliance.org/> | Open Data > Portal <http://data.civicdataalliance.org> > > On 4/7/15 8:00 AM, [email protected] wrote: > > The initial, automated phase of the import has now been completed using > scripts from the OSM Import Toolkit [1] and my imports account [2]. A task > has now been set up on the openstreetmap.us tasking manager for the manual > conflation and verification phase [3]. > > -Matthew Petroff > > [1] https://github.com/jremillard/osm-import-toolkit > [2] https://www.openstreetmap.org/user/mpetroff-imports/history > [3] http://tasks.openstreetmap.us/job/59 > > On Wed, Mar 25, 2015 at 7:02 PM, Elliott Plack <elliott.plack at gmail.com > <https://lists.openstreetmap.org/listinfo/imports-us>> > wrote: > > >* Dear Imports and Imports-US communities, > *>>* Today a dedicated team of Baltimore area OpenStreetMap supporters and > *>* mappers are proposing an import of Baltimore buildings and addresses. The > *>* import background and procedures are documented on the OSM wiki: > *>* https://wiki.openstreetmap.org/wiki/Baltimore_Buildings_Import_2.0 > <https://wiki.openstreetmap.org/wiki/Baltimore_Buildings_Import_2.0> > *>>* The code is available on GitHub: > https://github.com/osmlab/bmorebuildings > <https://github.com/osmlab/bmorebuildings> > *>>* Additionally, the import has been added to the import catalog: > *>* https://wiki.openstreetmap.org/wiki/Import/Catalogue#Community_Imports > <https://wiki.openstreetmap.org/wiki/Import/Catalogue#Community_Imports> > *>>* The import team includes users ElliottPlack and mpetroff. The data > *>* provider and owner is Jim Garcia with Baltimore City MOIT. > *>>* Briefly, the data comes directly from MOIT free of any license, will full > *>* permission for import. The data is simplified, conflated where possible, > *>* and prepped for automated import. Data that conflicts with existing data > is > *>* set aside for manual review. It is the intention of the authors of this > *>* import to utilize the OSM Tasking Server to divide up manual review tasks. > *>>* Thanks for considerations, > *>>* ElliottPlack > *>>* mpetroff* > > > _______________________________________________ > Imports-us mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/imports-us > >
_______________________________________________ Imports-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports-us
