From: <gj...@al...> - 2007-09-10 18:03:50
|
Justin Richer wrote: > I propose that we incorporate suggestions of several easily-parsable, > mutually-disambiguatable syntactical formats for this field. While a > user of the language COULD use a coordinate format different from =20 > this, > they SHOULD use one of these given formats to ensure interoperability. > So this becomes a strong suggestion of use, with solid guidelines and > examples. > > 42=B0N 71=B0W > 42.358 -71.060 > 42.358=B0 -71.060=B0 > 42.358=B0N 71.060=B0W > 42.358N 71.060W > 42:35.8N 71:6.13W > 42:35:8N 71:6:7W > 42:35:8.453 -71:6:4.343 Looks good to me. This scheme doesn't match any standards I've seen, =20= but it seems like your purpose here is just to define something =20 that's unambiguous and parsable. I've never seen colons used to =20 separate D:M:S, but I like it, it's entirely analogous to time notation. Degree symbols (=B0) are superfluous since coordinates are already =20 defined in terms of degrees. -Greg |