Geoserver uses geometry, not geography

Question

When using a SQL database as the store, Geoserver requires that the spatial data are stored in a geometry, not geography column. Naturally, as we are dealing with geospatial features and not just Euclidean planar geometry, one would expect the opposite to be true.

Is there any reason for this? Am I missing something important about these two datatypes?

Answer 1

It is not clear as to what backend database you are using? Also need to know the version of GeoServer as well to give a definitive answer. For PostGIS geography is supported in recent versions of geoserver 2.1. If you are referring to SQL server then I do not believe geography support is implemented.

Answer 2

You may want to ask this on the geoserver mailing list - http://geoserver.org/display/GEOS/Mailing+Lists

At least with PostGIS, a geography type is distinct from a geometry type. There's a little information here but basically (as you probably already know):

• geography is for spherical
• geometry is for cartesian

In the case of web-mapping in general, the defacto coordinate system has become Mercator/Web-mercator which is cartesian and therefore should be stored in geometry.