On Monday, August 16, 2010, <christopher.schm...@nokia.com> wrote: > > On Aug 16, 2010, at 4:00 AM, ext Andreas Hocevar wrote: > >> Hi, >> >> I stand corrected, at least in part: >> >> On Aug 16, 2010, at 09:37 , Andreas Hocevar wrote: >> >>>> I am still not sure that >>>> doing this in the renderer rather than in path.js, polyon.js is the >>>> right thing. >>> >>> I am. Fixing this in the handlers won't help for features that cross the >>> date line that come e.g. from a WFS, because there you will likely have >>> coordinates that don't exceed the world extent. >> >> I just asked Andrea Aime from GeoServer how GeoServer handles features that >> cross the date line. So if you store a feature with coordinates like -181 0, >> -179 0, GeoServer will accept that by default (but not in cite testing >> mode). And it will also return coordinates like this as stored, i.e. not as >> 179 0, -179 0. >> >> I do not know how other WFS implementations, or MapFish, or FeatureSever >> handle this. > > FeatureServer returns exactly what you give it; it doesn't know > what a world is.
Catching up on this thread... Same for MapFish. -- Eric Lemoine Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Tel : 00 33 4 79 44 44 96 Mail : eric.lemo...@camptocamp.com http://www.camptocamp.com _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
