Do you mean geography and geometry of MSSQL? Or what geo types?
IMHO: in general no (but I'm no specialist).
Only the most basic geo types have a simple character, like latitude/longitude.
And then there exist variants which allow for WGS 84, ITRS, rijksdriehoekcoordianten (Dutch) with quite complex casts between them because earth is "living" too and things change over time; positions move over time.
The more complex geo types with interesting data share the problems of blob/clob.
I think it is better to have geo specialists solve it in their function-specific apps for the moment and maybe over time they can standardize things further. I think there is too little common ground for a standard such as ODBC to provide standard support.
Do you mean geography and geometry of MSSQL? Or what geo types?
IMHO: in general no (but I'm no specialist).
Only the most basic geo types have a simple character, like latitude/longitude.
And then there exist variants which allow for WGS 84, ITRS, rijksdriehoekcoordianten (Dutch) with quite complex casts between them because earth is "living" too and things change over time; positions move over time.
The more complex geo types with interesting data share the problems of blob/clob.
I think it is better to have geo specialists solve it in their function-specific apps for the moment and maybe over time they can standardize things further. I think there is too little common ground for a standard such as ODBC to provide standard support.