[OpenStreetMap] #5024: Provide imagery blacklist in API capabilities

[OpenStreetMap]

#5024: Provide imagery blacklist in API capabilities
--------------------------+--------------------------------------------
  Reporter:  don-vip      |      Owner:  rails-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:
 Component:  api          |    Version:
Resolution:               |   Keywords:  capabilities imagery blacklist
--------------------------+--------------------------------------------

Comment (by don-vip):

 [https://docs.google.com/document/d/1uemhXWKwbu3RNjAWcG0R-
 nEFaN1FHjZl1McFwjXkNSc/pub some LWG activity from Feb 25th] stating:

 >''Getting JOSM’s blacklist update is important for the DWG, be it by
 modifying the API to return a blacklist or not. The question is, should
 this be delivered by the OpenStreetMap API? The positive is that it
 actively helps prevent well meaning map data and editor software
 contributors from contaminating the OSM database with data from non-
 allowed sources. The potential negative to this is that it may imply that
 other source not on the blacklist are OK. After discussion, it was felt
 that the right balance could be struck by additionally adding a whitelist,
 which may also be of use in its own right. Therefore:''

 >''LWG recommends and supports an API-delivered blacklist AND whitelist.
 We urge that it be made clear in supporting documentation that if a source
 is not on the blacklist, that does not imply that it OK and research
 should be done before adding it.''

 >''Potential whitelist https://github.com/osmlab/editor-imagery-index''

 The next meeting was scheduled on March 25th but I can't find the minutes?

-- 
Ticket URL: <https://trac.openstreetmap.org/ticket/5024#comment:4>
OpenStreetMap <http://www.openstreetmap.org/>
OpenStreetMap is a free editable map of the whole world