On Tue, Nov 29, 2011 at 10:35 AM, Mark Hammond <mark.hamm...@bto.org> wrote:
> Thanks for the heads up.
> Have republished the tables using 4326, and while it correctly calculated
> the bounds this time, the results on preview layer were the same - blank
> map for one table, and the divide by zero error with the other.
>
> Both these tables' spatial fields can be previewed OK using the SQL
> Developer Map view.
>
A division by zero is likely to indicate corrupted data on your end. The
SQL Developer Map viewer is
probably more tolerant to it.
I believe Oracle has functions that allow to locate and fix corrupt
gometries.
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
