Q&A (expected questions)

[slibby]

• How do we prevent users from adding features from a service with a restrictive license (contradictory to OSM and ODbL)?
• How do we balance the ease of importing new features where no features exist with the issues raised by importing large numbers of features into existing areas with conflicts?
• Is this just a tool for enabling "mini-imports" and making it much easier to do so (along with all the controversy and issues around imports)?
• How to we ensure that features do not have an offset or misalignment due to source data being stored in a different projection than existing OSM data?
• What kind of error handling, overlap monitoring, warnings and duplicate checking has been added to help keep users from inadvertently adding duplicate features or overlapping features.

[mapmeld]

Breaking these down into numbered questions:

1. I like the current system of using localStorage to approve the wording of a license, or the URL of a GeoService if that URL is not provided. We could blacklist particular domains or licenses, but as far as I can tell, the copyright field is usually used just to say the source of the data (e.g. City of Springfield) and not the license

2. I like the no-overlap polygon feature which I just added for buildings. This is easier to add for polygons and possible to add for lines if we use the buffer feature. I need to document this more so we can see more uses of it. I have been using Hartford as an example ( http://gis1.hartford.gov/arcgis/rest/services/OpenData_Community/MapServer/41/query?outFields=*&where=1%3D1 ).

3. The tool could have a few different uses, but as we've been investing more in features like individual approval and in-viewport overlap checks, I think it's better to deal with mini-imports in the viewport.

4. We ask the service outSR=4326, but I ought to research how the background service has offsets... I will create a new issue for this