We have a slight issue come up with an application being written for a foreign market.
We currently store longitude and latitude data as float (due to some restrictions concerning our EF application, it cannot handle the geospatial data types that we would normally use).
We have copies of the database in another country and the application has been built multi-lingual. The issue that has arisen is that in that other country the commas and periods we use in the use and interchanged so that a US number of 12,345.67 would be converted to 12.345,67, which is all well and good for currency, but it's not so good for geo data.
Thus, when we view the geospatial data via SSMS in the US, we see 38.8951, but the operators in the other country see 38,8951.
My question is: Is this due to the way the data is stored or simply the SSMS app used to view the data?
My first reaction (and answer given) was that all numerical data is stored collation-free, using a single decimal point for float and decimal data types, and therefore its the application displaying the data, but I am unable to find anything to support that opinion.
Thanks,