Good morning importers, Given some of the things I've been reading here, would perhaps putting a freeze on the NYC import be best so that the process could be re-evaluated and modified to resolve some of the issues you are experiencing? I would be more than happy to help with looking at the current process and offering my observations and suggestions if you were open to that. I admit to not being ready for actually helping with the importing but perhaps this could be my contribution as a way of understanding the complexities surrounding OSM imports.
-Carol ------------------------------------- Carol Kraemer North River Geographic Systems, Inc http://www.northrivergeographic.com 404.431.0125 [email protected] On Mon, Dec 9, 2013 at 10:55 AM, Serge Wroclawski <[email protected]> wrote: > On Mon, Dec 9, 2013 at 10:28 AM, Alex Barth <[email protected]> wrote: > >> >> On Mon, Dec 9, 2013 at 4:51 AM, Serge Wroclawski <[email protected]>wrote: >> >>> MapBox employee edits have been of bad quality, done extremely rapidly >>> with lots of errors, tons of omissions. In nearly every single task I've >>> examined from a MapBox rapid mapper, I've found errors or omissions in the >>> data, and these edits in aggregate account for 88% of the total completed >>> tasks. >> >> >> Those are some tough allegations. As someone from the MapBox team I'd >> love concrete instances of errors and omissions. >> > > The same exact issues we found last time we had a meeting and talked about > this. The issues are: > > 1. Geometry validation errors > 2. Buildings which are obviously missing from the data but appear in the > imagery > 3. Buildings which have incorrect geometry based in the NYC data based on > the imagery > 4. Addresses which look "odd" and need further investigation > > As we discussed just two weeks ago- I can complain about these issues one > by one, but that clearly doesn't address the problem, because the errors > keep happening from the same users. > > We've consistently improved where I got concrete feedback [1]. As just >> discussed on IM, just concrete examples (w/ changeset, link to osm.org) >> of what you're finding so far would be great. Again, I am committed in >> making this a stellar import. >> > > That would only be possible to do if the pace of the validation was in > line with the pace of the import, but if there are users who continue to do > sloppy work, you simply make the burden on the validators even greater. > > Ideally issues you or anyone else finds is posted to Github, where it's >> easiest to track and work off. >> >> https://github.com/osmlab/nycbuildings/issues?page=1&state=open >> > > The problems are systemic, not individual. Asking me to fix address each > and every single of them is simply a way to stall for time, while the > problem continues. > > >> Next, I would love to open the import task on the tasking manager to >> everyone again (I sent a note to Serge, Eric and Liz on this last week). >> This is a blocker for NYC community not engaging the way it could right now. >> > > The damage to NYC has been quite extensive, and you aren't addressing it. > > - Serge > >> > > _______________________________________________ > 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
