On Tue, 11 Sep 2001, Kenji Takahashi wrote:
> I believe so. For example, 3GPP is working on 23.032 series and also Mari
> wrote an ID,
> http://search.ietf.org/internet-drafts/draft-korkea-aho-spatial-dataset-01.t
> xt. They have not been finalized yet but look soon to be.
I have so say I don't like the suggested position format
[N|S]degree.minute.second.f, N60.08.00.235556
degree range [0-90], decimal fraction f in arbitrary length
It doesn't seem to match anything in common use afaik - nautical,
recreational, or GIS - and incurs processing overhead converting
it for use in calculation.
After a couple of years of arguing this issue in Dublin Core, etc. I much
prefer signed decimal degrees, which is unambiguous (well, apart from axis
ordering), simple to understand and parse, and compatible with GIS data.
(Common nautical use seems to be to give position e.g.
49°04'43"N 140°17'32"E or 49°04.71N 140°17.53N, but the degree symbol is
not an ASCII character)
-- Andrew Daviel Vancouver WebpagesReceived on Sat Sep 29 22:22:20 2001
This archive was generated by hypermail 2.1.8 : Thu Jan 22 2004 - 12:32:22 EST