RE: [Geopriv] RFC 3825 Updates

From: Dawson, Martin ^lt;Martin.Dawson@andrew.com>
Date: Thu Feb 01 2007 - 21:49:12 EST

There seems little point in providing resolution parameters if all they mean is that subsequent digits should be interpreted as zero (ignoring for a moment that the text actually says they could be either one or zero - meaning the encoding represents a set of points). The sender could just set them to zero in the encoding in the first place - meaning the resolution parameters are superfluous. Cheers, Martin -----Original Message----- From: Andrew Newton [mailto:andy@hxr.us] Sent: Friday, 2 February 2007 1:45 PM To: Dawson, Martin Cc: Carl Reed OGC Account; geopriv@ietf.org; Marc Linsner; Thomson, Martin Subject: Re: [Geopriv] RFC 3825 Updates On Feb 1, 2007, at 9:12 PM, Dawson, Martin wrote: > The salient question then, if all that is intended to be > communicated is > the point, is what would the sender be intending to communicate > with the > resolution parameters - and what is the recipient of that information > supposed to interpret it as meaning? As I said, the information is to aid in conversion of 1's and 0's to ASCII digit strings, such as what you would find in GML. > Certainly - it doesn't have to mean uncertainty; it could be conveying > an extent (an area), as is described in the examples in the A.1 > section > of the RFC. Either way, it's not just a point. Well, there is no doubt about it. That appendix is confusing. It seems to talk about how one would interpret a lower resolution point with higher resolution values, ending up with an area in the higher resolution values -- which it shouldn't do. I think the purpose of the appendix is to demonstrate change in the resolution parameters relative to distances humans more readily understand. > What use, for example, should the OGC make of the resolution > parameters > in coming up with a GML representation of the 3825 encoding? Once they have their lat/long values, none -- they throw the resolution parameters away (i.e. the resolution parameters are not be represented explicitly in GML). -andy ------------------------------------------------------------------------------------------------ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any unauthorized use of this email is prohibited. ------------------------------------------------------------------------------------------------ [mf2]

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv
Received on Thu, 1 Feb 2007 20:49:12 -0600

This archive was generated by hypermail 2.1.8 : Thu Feb 01 2007 - 21:49:00 EST