[OSM-dev] Very long ways have been split (was: Status of Database Server after 0.4 Upgrade: Fragile)

Sebastian Spaeth Sebastian at SSpaeth.de
Mon May 14 08:57:05 BST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jon Burgess wrote:
> How about
> 
> Plan B:
> =======
> - If a way is too large to return, don't return it!
> - Instead perhaps we can add a new tag which says something like:
> 
> <way id=12345 segs_excluded="true" seg_count="5000" >
>  <tag k=... > 
>  [ more tags, but no segments ]
> </way>
I like that approach for a couple of reasons, let me quickly list them:

* Right now, we download potentially large amounts of data for small
bboxes if a long way happens to cross it. This would allow us (ie JOSM)
to lazily load those way segments, when the use can already work on that
bbox.

* right now, we return nodes with the one long way but without all other
(potential) ways on that node. So users can easily and accidently try to
delete nodes which they think are otherwise unused when they are not.
Does the API protect us from fiddling with these nodes?

[snipped Plan C which also sounds good]

Spaetz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGSBZQbtVRNeSDtgERAsyUAJwLnM5nBAseiul3AUM9YByvdjzGzwCglrkP
ZGUTnE5L1zabX1UC08XU3oE=
=kwmF
-----END PGP SIGNATURE-----




More information about the dev mailing list