It seems that the Microsoft SQL Server Geography data type is better suited for lat/lon because Geography "stores ellipsoidal (round-earth) data, such as GPS latitude and longitude coordinates."

While the Geometry data type "represents data in a Euclidean (flat) coordinate system."

I have data stored in SQL Server Geometry data type column, and it is lat/lon coordinates - the SRID is EPSG:4326.

The reason being, is the data is used by Geoserver, and Geoserver only recognizes Geometry data types for SQL Server. But the data is 4326.

Is there anything wrong with doing this? Will there be accuracy or performance issue? Should/could the data be converted?

  • what do you do with the data? is it a global coverage or regional?
    – Ian Turton
    Jul 6 '18 at 17:30
  • Also I believe GeoServer can read the Geography column from an SQLServer DB at least from a quick look at the code base.
    – Ian Turton
    Jul 6 '18 at 17:32
  • @IanTurton - mostly regional
    – user210757
    Jul 6 '18 at 17:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.