[OSM-dev] dropping segments

[Tom Hughes]

In message <320075ff0707280325o5c6869b8h7e2859cd4d70aabf at mail.gmail.com>
          "Nigel Magnay" <nigel.magnay at gmail.com> wrote:

> > There is a problem with very large areas/ways. These cause major
> > issues with the API/clients (editors). There was recently a large
> > number of ways that were split due to them being to large. I can't
> > remember the threshold for the number of segments per way that should
> > be the maximum. There are some lakes that are multiple ways for example.
> 
> Isn't that only a problem because the current API only fetches a window onto
> some data, rather than (say) "the entire way of all ways intersecting with
> this bbox".

The API hasn't had that problem since the rails port went live.

Well actually there is still a problem in that any way that goes
straight through the box without any nodes in it will be missing, but
you will get all the nodes and segments for the ways you do get - you
won't only get the nodes and segments that are in the box.

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/