Re: [atoca] Next milestone

Art Botterell <acb@incident.com> Tue, 25 September 2012 18:52 UTC

Return-Path: <artbotterell@gmail.com>
X-Original-To: atoca@ietfa.amsl.com
Delivered-To: atoca@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2213C11E8091 for <atoca@ietfa.amsl.com>; Tue, 25 Sep 2012 11:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.766
X-Spam-Level:
X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_FWDLOOK=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9fhlBWUaMRxJ for <atoca@ietfa.amsl.com>; Tue, 25 Sep 2012 11:52:06 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3635521F8830 for <atoca@ietf.org>; Tue, 25 Sep 2012 11:52:06 -0700 (PDT)
Received: by padfb11 with SMTP id fb11so2426550pad.31 for <atoca@ietf.org>; Tue, 25 Sep 2012 11:52:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Ybmta5fCbCZcGy/1PeU1UQqcjZI1ICsCRJNt3Fnke54=; b=gG+OCpYLw7CYsE53lYmUPPyKc1ftUM9E83mYT2JyEzxxfj4kxiSUQU3GqXrurKwWTN rfNTHbFvYawdhKcozb9pHkFqMx4FnnDGt3p+AED2vQWoCx9SrEzDVYfaUeLIWYs3qPaV 4mKMnRmUs9qp74dY6S9P7DxOuk4uVYi0KRPIQHa1bGzfOamlRNswj/PjNqU255cXOuP2 Uzpo42SbORpDuJr9L1iCHhghIM7MG/h+fm2rekrksGw8lsKxALhW9GUzZXyezI2IDlFR BFyZDi2uMDDKJsvPdy+yfTzu15uVdtj4z93Yilo1HVIVnM/6BjMiihMouhjIHcfew78d fSEQ==
Received: by 10.68.203.195 with SMTP id ks3mr48388280pbc.79.1348599125937; Tue, 25 Sep 2012 11:52:05 -0700 (PDT)
Received: from [192.168.1.69] (99-182-125-96.lightspeed.frokca.sbcglobal.net. [99.182.125.96]) by mx.google.com with ESMTPS id qb2sm715623pbb.15.2012.09.25.11.52.01 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Sep 2012 11:52:02 -0700 (PDT)
Sender: Art Botterell <artbotterell@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Art Botterell <acb@incident.com>
In-Reply-To: <A8BDD10D-479A-4D72-B565-439DD6923F71@brianrosen.net>
Date: Tue, 25 Sep 2012 11:51:59 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <783AAAE3-344E-4C03-B3FB-E402F84D0699@incident.com>
References: <CABkgnnXJQ25CRw4wVGmvk3tBCKUZGNgei4KOVseFBYJfotxb=Q@mail.gmail.com> <1597D6F5-A6A4-418C-AE5C-C4426992A645@brianrosen.net> <67ADBEFC-B056-4064-B18C-02EB9CBC539E@incident.com> <A8BDD10D-479A-4D72-B565-439DD6923F71@brianrosen.net>
To: Brian Rosen <br@brianrosen.net>
X-Mailer: Apple Mail (2.1283)
Cc: atoca@ietf.org
Subject: Re: [atoca] Next milestone
X-BeenThere: atoca@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <atoca.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/atoca>, <mailto:atoca-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/atoca>
List-Post: <mailto:atoca@ietf.org>
List-Help: <mailto:atoca-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/atoca>, <mailto:atoca-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2012 18:52:07 -0000

Funny thing, that... we tried to make the CAP geometries align with GML... even has a representative from OGC (Carl Reed) on the OASIS committee when we were' specifying it... but then GML changed directions and the CAP spec wound up different.  Personally I'd suggest using the CAP syntax, for consistency, as that can be switched into GML, KML or whatever easily and precisely an application requires.

Yes, ultimately any geocode is really just a shorthand for some polygon.  Different jurisdictions around the world will have different geocoding schemes, and it's hard to assume that every receiving device will be familiar with them all... but geometry is universal... or at least planet-wide.

- Art


On Sep 25, 2012, at 11:25 AM, Brian Rosen wrote:

> I guess that's my point.  Without more spec, we have interoperability issues.  When you have limited CAP deployment, these can be dealt with by prior arrangement.  We probably can't do that.  I would prefer that a polygon be encoded with GML, which is precise, interoperable and an accepted global standard.  That can be wrapped in a PIDF (an IETF standard) or not, but we need something very interoperable.
> 
> Forcing polygons may work in a forward looking sense.   I'm probably convincible that a jurisdictional areas aren't needed, but so many of the alert sources I'm interested in supporting are based on jurisdictions.  I guess just telling them they need to come up with a relatively simple polygon is okay.  Since increasingly, device location is GPS (or equivalent) based, we probably need geo always.
> 
> Brian
> 
> 
> On Sep 25, 2012, at 2:14 PM, Art Botterell <acb@incident.com>; wrote:
> 
>> On Sep 25, 2012, at 10:30 AM, Brian Rosen wrote:
>>> For example, how do you target "Allegheny County, PA, US"?  A text line?  With what syntax?  A polygon?
>> 
>> 
>> In CAP the recommended presentation would be a polygon, a line of text that might well read "Allegheny County, PA, US" and optionally a <geocode> value, which in the US would typically be a FIPS-based code conforming to the old Emergency Alert System standard (in this case, "042003").
>> 
>> There are a few subtleties here.  First, most hazard footprints don't align very well with political boundaries, so it's actually considered best practice NOT to address an alert to everyone in a political jurisdiction if better resolution is available, which increasingly often is the case.  (This is probably the biggest challenges in the transition from the legacy EAS and Weather Radio systems in the States and the newer CAP-based IPAWS framework.)
>> 
>> Second, but related to the first... there is at present no strict limit on the number of vertices in a polygon in CAP.  Generally this hasn't been a problem, as both manual and model-derived (e.g., from a hazardous materials "plume model" software) polygons tend to be relatively simple.  However, if one uses a political jurisdiction as the target area and if, as often is the case, that jurisdiction is defined at least in part by a waterway or water body, then at least part of the "true" polygon will be fractal in nature and the number of vertices used to represent it becomes an implementation decision.  
>> 
>> In such cases conversion from GIS geometries developed for other purposes can, at least in theory, produce very lengthy polygon description strings.  Some degree of polygon simplification, manually or by means of a "convex hull" calculation, may be helpful in such situations; fortunately those can be calculated ahead of time.  A common guideline and a requirement of the IPAWS profile in the U.S. is that a polygon be limited to 100 vertices.  Again, this is largely a theoretical concern, and I'm not aware of any case where this has actually been a problem.
>> 
>> And third, of course, there's quite a bit of variety in how polygons get represented as strings.  Latitude first and then longitude, or the reverse "x,y" order?  Commas between the coordinates and spaces between the pairs, or vice versa, or some other delimiters?  All such representations are ultimately equivalent (at least until we drill down to the level of whether we're using the increasingly common GPS-standard WGS84 datum or some model of the precise shape of the Earth.)  But it's important to be clear which format is being used and to remember of convert as necessary, e.g., between CAP and KML.
>> 
>> The CAP spec deprecates the use of geocodes (arbitrary string designators) without also providing the corresponding geometry (polygon), since to do otherwise is to assume that the receiving device knows every possible geocoding scheme it might ever encounter, which in an open global system is probably infeasible.  Indeed, ideally we might have done without geocodes entirely, but back-compatibility with legacy systems (and the comfort of some non-GIS-savvy programmers who understood string-matching but were uncomfortable with things like point-in-polygon algorithms) dictated their inclusion.
>> 
>> And the text areaDescription field is defined merely as "human readable" so it can be as concise or as extensive as circumstances dictate.  However, where multi-lingual alerting is required it tends to be kept short to facilitate translation.
>> 
>> -  Art
>> _______________________________________________
>> atoca mailing list
>> atoca@ietf.org
>> https://www.ietf.org/mailman/listinfo/atoca
>