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

OpenStreetMap trac at noreply.openstreetmap.org
Wed Nov 20 00:43:29 UTC 2013


#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 woodpeck):

 @pnorman, your reasoning only holds if you assume that the OpenStreetMap
 API with its current license is the only API against which the editing
 software will be used. If someone were to use any of the programs to
 connect to a system that uses the OSM API but is licensed differently,
 then image sources that are not allowed for OSM might become available or
 vice versa. So, which imagery is allowed depends not on the editor but on
 the API (and project) the editor connects to. This might be less of an
 issue for iD or P2 which would likely have to be embedded into that new
 system anyway, but JOSM - or any other standalone editor for that matter -
 doesn't require a code change to be used with different servers.

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



More information about the rails-dev mailing list