[OpenStreetMap] #4501: Include API usage policy technical limitations into Capabilities

[OpenStreetMap]

#4501: Include API usage policy technical limitations into Capabilities
--------------------------------------------------------+-------------------
 Reporter:  don-vip                                     |       Owner:  rails-dev@…                
     Type:  enhancement                                 |      Status:  new                        
 Priority:  minor                                       |   Milestone:                             
Component:  api                                         |     Version:                             
 Keywords:  download threads usage policy capabilities  |  
--------------------------------------------------------+-------------------
 We are currently working on a change in JOSM in order to download data
 with several concurrent threads, up to to the maximum number allowed by
 the OSM API usage policy (currently 2):

 http://wiki.openstreetmap.org/wiki/API_usage_policy#Technical_Usage_Requirements

 http://josm.openstreetmap.de/ticket/7914

 Problem is: the usage policy may be subject to change without anyone
 noticing in our team. Worst, after such a change, all contributors using
 an older version of JOSM could make queries that do not respect the
 updated usage policy.

 For these reasons, I would like to know it it is possible to include the
 maximum number of download threads in the response to GET
 /api/capabilities.

 That would allow all running JOSM instances, old and new, to automatically
 comply to the current usage policy.

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