Hi, to save you efforts in persuing your original attempt to modify the sketch handlers, I have created http://trac.openlayers.org/ticket/2787 with a patch.
This does not solve all vector layer and date line issues though. If you play with the spherical-mercator example after applying my patch, you will see that features crossing the date line can turn invisible when zoomed out and the map extent changes. Regards, Andreas. On Aug 16, 2010, at 10:00 , 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. > > Regards, > Andreas. > > > -- > Andreas Hocevar > OpenGeo - http://opengeo.org/ > Expert service straight from the developers. > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers. _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
