All,
Not sure if this is a postgis or geoerver problem, but I am continuing to have an issue with polys that straddle the date line. I have some polygon data originally digitized on Google Earth with longitude values 0 - 360. I insert these into a geometry-based table in postgis, and they display correctly in Geoserver. A few of these polys return false for IsValid due to self-intersection, so I use MakeValid on them, test for validity, and they still look good in geoserver. Now I try to put these data into a new postgis geography table. everything the same except casting the geom to geog (the_geom::geography). I get a warning on a few of them: "NOTICE: Coordinate values were coerced into range [-180 -90, 180 90] for GEOGRAPHY". Then when displaying the new table in geoserver the polys now longer straddle the date line, turn inside-out, etc.
Any ideas are greatly appreciated.
Thanks,
Steve
What Geoserver version are you using? dateline handling has been gradually improved. It is seems possible however that Postgis coercion wrecked the topology. Any particular problem with just storing them as geometry? We do this a lot.
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.
Geoserver 2.5.3. Postgis 2.1.
The data are all over the world, and I also want to calculate the area of the polygons, and some intersections.
On 12/11/2014 3:21 PM, Phil Scadden wrote:
What Geoserver version are you using? dateline handling has been
gradually improved. It is seems possible however that Postgis coercion
wrecked the topology. Any particular problem with just storing them as
geometry? We do this a lot.
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Geoserver 2.5.3. Postgis 2.1.
Should handle it. Can you try creating the objects with -180:180 longs on input? I dont do enough with Postgis to know it's ins and out but in past have had less dateline hassles with postgis than with arcSDE. Be extremely cautious doing area calculations. A proper geodetic calculation is one thing (and tough), doing it over the date line or a pole is something else again.
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.