[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 pnorman):

 Pros:
 - Has a central list
 - Easier updating
 - Changes would cover JOSM back to 2011

 Cons:
 - P2 and iD define their blacklists internally, is there a reason JOSM
 can't do the same
 - Would only effect JOSM
 - Adds a new <policy/> element to the API capabilities document, which is
 a wider change then just updating JOSM's list

 From my point of view, yes, preventing the use of layers commonly used for
 infringing purposes is part of the job of editing software.

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