[OSM-dev] ROMA servers down - osmosis large way problem

Stefan de Konink stefan at konink.de
Tue Dec 30 15:38:08 GMT 2008


Robert (Jamie) Munro wrote:
> Stefan de Konink wrote:
>> Shaun McDonald wrote:
>>>  From API 0.6 there is a limit of 2,000 nodes in a way.
>> Btw; Do you impose this also on a relation? If not, then it is pretty 
>> useless to have an infrastructure that is capable of holding an infinite 
>> amount of nodes and one that is not ;)
> 
> IMHO ways should be restricted to more like 256 nodes, and relations
> should be unrestricted. I don't see how relations and ways should be
> similar in this respect.

<osm version="0.5" generator="OpenStreetMap server">
<way id="100" visible="true" timestamp="2008-04-16T16:42:42+01:00" 
user="ck3d">
<nd ref="260904"/>
<nd ref="260897"/>
<nd ref="260898"/>
<nd ref="185986175"/>
<nd ref="260899"/>
<nd ref="260900"/>
<nd ref="260901"/>
<nd ref="260902"/>
<nd ref="260903"/>
<nd ref="260904"/>
<tag k="highway" v="secondary"/>
<tag k="ref" v="St 2069"/>
<tag k="junction" v="roundabout"/>
<tag k="created_by" v="JOSM"/>
</way>
</osm>

vs

<osm version="0.5" generator="OpenStreetMap server">
<relation id="100" visible="true" timestamp="2008-04-16T16:42:42+01:00" 
user="ck3d">
<member type="node" ref="260904" role="1" />
<member type="node" ref="260897" role="2" />
<member type="node" ref="260898" role="3" />
<member type="node" ref="185986175" role="4" />
<member type="node" ref="260899" role="5" />
<member type="node" ref="260900" role="6" />
<member type="node" ref="260901" role="7" />
<member type="node" ref="260902" role="8" />
<member type="node" ref="260903" role="9" />
<member type="node" ref="260904" role="10" />
<tag k="highway" v="secondary"/>
<tag k="ref" v="St 2069"/>
<tag k="junction" v="roundabout"/>
<tag k="created_by" v="JOSM"/>
</way>
</osm>

I do hope you understand now :)


> I can imagine a system that downloaded only part of a relationship, and
> had abstract add/remove object X from relationship Y methods, but with
> ways it seems much more complicated because of ordering.

It is not a problem at all. Because the ordering is explicit as you can 
observe. A bbox request would bbox on the nodes, but not return all the 
nodes for the complete relational-way. The editor should simply say, you 
cannot extend an incomplete way or move the last point. Or in best case, 
offer an option to download it fully.


Stefan




More information about the dev mailing list