Re: [Geopriv] Some comments on draft-thomson-geopriv-uncertainty-08

James Winterbottom <a.james.winterbottom@gmail.com> Fri, 08 November 2013 19:17 UTC

Return-Path: <a.james.winterbottom@gmail.com>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C16421F9CA8 for <geopriv@ietfa.amsl.com>; Fri, 8 Nov 2013 11:17:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.255
X-Spam-Level:
X-Spam-Status: No, score=-1.255 tagged_above=-999 required=5 tests=[AWL=-0.653, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKuVIXOylBEr for <geopriv@ietfa.amsl.com>; Fri, 8 Nov 2013 11:17:47 -0800 (PST)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id C145521E818A for <geopriv@ietf.org>; Fri, 8 Nov 2013 11:15:26 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id fa1so2621341pad.13 for <geopriv@ietf.org>; Fri, 08 Nov 2013 11:15:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=3TgRpOgX2lHwmxbxdML+po4DUK066gIUxU1m+TXHa64=; b=XN1oq8zQgaVu3iNJfzJe77adewjAQfPWcuDULCB+UbN/BymXsaprw55IiFWNtQ8grW nQpnh6kVPMkGl95zZMw7XF/vAXuS3J5L6v7A+nLaiiWQEdgZ5r+jG7Q7Dlj4/EAs88CS 22y1Yo4KuzJdUfsf95AZ4wEYwq5YxPxs5IxKWstieQYIhcG5GTqpKnDe6LTFP0yc3vIF oH26iWkW4VBxKocXOrHCWpB3XIPEcoPlQn126vDrrZFtawIJLU6RiuZ7LQxrcFuOusqW ZKVbyboLv+rHkKKbZlAAVcZ7xoMqfowe+AAFnIfzqk+4lUCMHKIXjWnJ15ebZ1Ftwjsk 4NIw==
X-Received: by 10.68.113.130 with SMTP id iy2mr16792851pbb.2.1383938118837; Fri, 08 Nov 2013 11:15:18 -0800 (PST)
Received: from [192.168.1.14] (124-149-67-181.dyn.iinet.net.au. [124.149.67.181]) by mx.google.com with ESMTPSA id p1sm8088738pbo.12.2013.11.08.11.15.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Nov 2013 11:15:17 -0800 (PST)
References: <CAOPrzE3Phx0anv9J3zrrBozsf4p0TJk+KZYWZz_hA_=9FyZnOA@mail.gmail.com> <B700712C-1899-494C-9E28-02BC62AE81C3@gmail.com> <9549C6C2-3B3E-4153-A46F-EB930B310115@brianrosen.net> <A16D1601-7DB8-4BD3-901E-B7C8364DF358@gmail.com> <89D45E92-85AB-457D-9A1B-67C163BC2558@brianrosen.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <89D45E92-85AB-457D-9A1B-67C163BC2558@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail-5E67BB3F-B571-45FE-989A-247E398065FC"
Content-Transfer-Encoding: 7bit
Message-Id: <7CD224DA-5C3D-40D3-B82F-5188CC586484@gmail.com>
X-Mailer: iPad Mail (10B329)
From: James Winterbottom <a.james.winterbottom@gmail.com>
Date: Sat, 09 Nov 2013 06:15:15 +1100
To: Brian Rosen <br@brianrosen.net>
Cc: GEOPRIV WG <geopriv@ietf.org>
Subject: Re: [Geopriv] Some comments on draft-thomson-geopriv-uncertainty-08
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 19:17:48 -0000

Sure you can.
We have an explicit radius parameter for circle, you may set this to zero.
We also allow,the definition of just a point.
I think that you will find that the constructs between MLP and GeoShape are almost directly interchangeable.

Cheers
James

Sent from my iPad

On 09/11/2013, at 4:33 AM, Brian Rosen <br@brianrosen.net> wrote:

> Not claiming I know more than you, but I think E2 and MLP report position AND they report uncertainty by describing the position as a point, and the uncertainty as the radius of a circle or ellipse.  They don’t just sent a circle.  It’s point plus circular uncertainty, not just a circle.  In PIDF, you can’t tell the difference between a location reported as a circle with no uncertainty specified from a point with circular uncertainty.
> 
> The definition of the reported position is the lat/lon of the position and the radius of uncertainty.  We have no similar way to report uncertainty in PIDF.
> 
> Brian
> 
> On Nov 7, 2013, at 2:00 PM, James Winterbottom <a.james.winterbottom@gmail.com> wrote:
> 
>> Hi Brian,
>> 
>> MLP and E2 are essentially the same as what we use in Geopriv
>> 
>> Sent from my iPad
>> 
>> On 08/11/2013, at 8:49 AM, Brian Rosen <br@brianrosen.net> wrote:
>> 
>>> Sure:
>>> 
>>> When you get a location from a GPS receiver, it typically uses the NMEA interface, which reports a lat/lon and a Dilution of Precision method of specifying uncertainty.
>>> MLP usually reports location as point with circle, ellipse or arc uncertainty
>>> E2 usually reports location as point with uncertainty
>>> 
>>> Brian
>>> 
>>> On Nov 7, 2013, at 1:02 PM, James Winterbottom <a.james.winterbottom@gmail.com> wrote:
>>> 
>>>> Hi Brian,
>>>> 
>>>> Can you give an example of point 2 please?
>>>> I guess all the systems that I am familiar with use the area to express the uncertainty so I am keen to understand how it might be done differently.
>>>> 
>>>> Cheers
>>>> James
>>>> 
>>>> Sent from my iPad
>>>> 
>>>> On 08/11/2013, at 7:48 AM, Brian Rosen <br@brianrosen.net> wrote:
>>>> 
>>>>> I’ve read this draft, and think it is an excellent explanation of the issues we face in geopriv with measurements.  I highly recommend that we adopt the draft and process it as a work group item.  I am particularly happy with the definitions it offers for the various quantities.
>>>>> 
>>>>> 
>>>>> 
>>>>> I find it lacking in two areas:
>>>>> 
>>>>> 
>>>>> 
>>>>> 1. I think the draft needs to discuss the issues of comparing measurements with different confidence.  I think the bottom line on that is: don’t do it, use one agreed upon confidence.
>>>>> 
>>>>> 2. I think we need to stop expressing measurements as just the uncertainty area.  While I understand why doing so is attractive, I think it is not what real systems do.  Real systems express a measurement and explicitly state the uncertainty of the measurement.  I think we need a way to express that.
>>>>> 
>>>>> 
>>>>> 
>>>>> Brian
>>>>> 
>>>>> _______________________________________________
>>>>> Geopriv mailing list
>>>>> Geopriv@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/geopriv
>>> 
>