I stand (happily) corrected. Roy
On Thu, Jun 28, 2012 at 12:14 PM, Richard, Joel M <[email protected]> wrote: > Assuming you're asking about storing them in the database, I will differ from > Roy here and suggest saving them into to floating-point-number fields. That's > always seemed to me to be to be the bets way to go (one discrete data element > per field). > > I also feel combining is easier than parsing, but that's just me. :) > > --Joel > > > Joel Richard > Lead Web Developer, Web Services Department > Smithsonian Institution Libraries | http://library.si.edu/ > (202) 633-1706 | [email protected] > > > On Jun 28, 2012, at 3:04 PM, Roy Tennant wrote: > >> Myself, I'd go with LAT,LONG. in decimal notation, with preceding plus >> or minus when appropriate. Easy to parse and Google Maps ready. >> Roy >> >> On Thu, Jun 28, 2012 at 11:57 AM, Mark Jordan <[email protected]> wrote: >>> code4libers: >>> >>> What's the best (i.e., most standardized and flexible) format for storing >>> single-point geocoordinates? Pages like >>> http://www.maptools.com/UsingLatLon/Formats.html offer too many choices. >>> >>> TIA, >>> >>> Mark
