On Dec 19, 2007 4:49 PM, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:
> On Dec 19, 2007 10:14 AM, 80n <[EMAIL PROTECTED]> wrote: > > Since osmxapi doesn't have this limitation I'm wondering if it would be > > feasible to download some selected ways (landuse=forest, etc) from > osmxapi > > [1] for a much larger area. These could then be merged with the z12 > data > > from the main api. > > I was thinking if osmxapi could note while loading if an area exceeds > the size of a zoom-12 tile, then a special search for > [osmxapi:oversize=1] would return only those objects. This should be > fairly quick. > This should be feasible. I'm thinking something like: /api/0.5/way[bbox=w,x,y,z]/oversize would return all ways that are not in the bbox but have an extent that *includes* the bbox. > > Really, it's a bug in the API that such polygons arn't returned since > they intersect the requested area. > > Most of the suggestions here seem to suffer from the problem that > they're specific to zoom-12 rendering. If the data ever gets detailed > enough that we switch to zoom13 or 14, we have ot go add lots more > such nodes... > Yes, we shouldn't add any more z12 assumptions. > > Have a nice day, > -- > Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ >
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
