I agree that having some sort of "shadow database" or annotation layer, with private information attached to OSM would be a good idea. You also have to consider why it hasn't been created already. I've run a similar building-centric system on http://MajuroJS.org for a couple of years.
I suspect that if you used it in the field, this kind of database would struggle with (a) admins not knowing whether to create and update buildings on OSM or on the internal side, (b) not knowing how to cope with an OSM feature being deleted and redrawn, (c) convincing people to support many private data-layers when a free one is still accessible. On Wed, Feb 18, 2015 at 6:06 PM, Bryce Nesbitt <[email protected]> wrote: > There are a lot of offending tags: chicken count is high on my list. > > And the toilets: private toilets don't belong, unless the owners of the > hut really intend to invite hikers in. > This seems to be a common theme among developing country / HOT mappers to > catalog and map > the contents of non-public buildings. > > > -- > This appears to be hand collected data, uploaded for storage on OSM in > multiple changesets. > > Now an excellent open source project would be a *shadow database* for > things like this. Let the organization (e.g. the Red Cross chapter) collect > data using OSM tools, and reference that data to OSM primary keys, but keep > the private data separate and private. > > _______________________________________________ > Imports mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/imports > >
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
