Does the OpenStreetMap API set a limit on the number of nodes in a way? Does the OpenStreetMap API set a limit on the number of members in a relation? asked 20 Jul '10, 20:59 Sven L |
Yes. Currently api set limit 2000 nodes per way. All api limit can be see in http://api.openstreetmap.org/api/0.6/capabilities. Coastline and ofter that object that are over 2000 nodes length are typical divided around 500 node pieces. This make easier edit pieces, because you can add nodes to them. answered 20 Jul '10, 21:29 kallam |
The number of nodes in a way is limited to 2,000. Just like other API limits, this is coded in the application.yml file in the rails port: http://git.openstreetmap.org/?p=rails.git;a=blob;f=config/application.yml;hb=HEAD There is currently no limit to number of elements in a relation, but it is possible that one could be added at a later time. You should certainly avoid ever having more than 2,000 members in a relation even if it is currently possible. Relations that big slow down editing and cause unnecessary waste of bandwidth. For route relations or boundaries, make cascading relations if you're approaching a four-digit number of members. For multipolygon relations, split them in several parts. answered 20 Jul '10, 22:13 Frederik Ramm ♦ Tordanik 2
Cascading relations are a bad idea. They are hard to understand and hard to work with in software. As far as I know, no software currently understands them. This problem should be solved on a different level.
(21 Jul '10, 06:45)
Jochen Topf
JOSM understands cascading relations.
(22 Jul '10, 20:13)
Baloo Uriza
|
Use the following API call to find the limits. http://api.openstreetmap.org/api/0.6/capabilities answered 21 Jul '10, 09:56 Firefishy ♦♦ |