Most geocoded databases usually store Latitude and longitude as decimal 
degrees (a long decimal, to 6 decimal places). e.g. in Australia a 
latitude would look like -35.384213 and a longitude 149.07664519. The 
GIS systems I've come across also use latitude and longitude in this 
format, as do Google and Bing maps when you send them geocode 
co-ordinates to display a street map. Is there any reason you want to 
store co-ordinates as 3 separate base 60 fields? Seems an unnecessary 
complication with all the conversion that will need to be done.

feargal wrote on 22/08/2019 8:12 PM:
> Hi
> 
> I'm trying to figure out the field picture for degrees, minutes and 
> seconds in degrees mins secs data entry?
> 
> This is for entering Latitudes and longitudes
> 
> These will be stored in a SQL Server as a Decimal field, so these data 
> entry fields are unbound
> 
> So for Latitude Degrees it will be an short integer datatype, between 0 
> and 89 (90 is a special case where the min/sec fields MUST be zero)
> 
> Longitude degrees will be between 0 and 179 (180 is a similar special case)
> 
> Minutes for both will be a short integer datatype between 0 and 59
> 
> Seconds will be a decimal datatype ##.##
> 
> How much of that can I specify in a field picture?
> And how much needs to be done pre-depart?
> 


-- 
Tom Krieg
Contact me via the contact page at:
https://sdassociates.com.au