[OSM-dev] Ways with 40k nodes, was: osmosis pgsql schema

Dave Stubbs osm.list at randomjunk.co.uk
Fri Oct 31 11:20:16 GMT 2008

On Fri, Oct 31, 2008 at 11:02 AM, Stefan de Konink <stefan at konink.de> wrote:
> On Fri, 31 Oct 2008, Frederik Ramm wrote:
>> Any comments?
> You are now basically working around the actual problem. Allowing partial
> ways in the editors for the current bbox. I think hacking and breaking
> ways is bad, duplicate information, missing tags upon edit etc. I think
> storing ways with their tags per 'new segment' is bad too; hence the
> reason I proposed to use an ordered relation to represent ways.

With 40k nodes in a way it takes the API about 30 seconds just to
generate and serve the XML for the way, /without/ the nodes.
The .osm file with no node data goes upto about 100kb. (With node data
that's 5-6MB)
To make a modification to the way, ie: add a tag, you have to reupload
that 100kb of XML, and sit back, probably make a cup of coffee to pass
the time.

I don't think having a single object of this size ends up helping
anybody. With relations we can add indirection to handle extremely
large objects, but with small API units. It just makes everything more
flexible than dealing with megalithic monoliths.


More information about the dev mailing list