Re: [atoca] Next milestone

[Art Botterell <[e-mail]>]

Dunno, Carl... certainly we were glad to have you there on the TC representing OGC... and yet somehow, despite all our best intentions, the coordinate order wound up reversed in CAP vs GML.  And then, of course, KML came into play, different yet again.  But standards-political history isn't the topic here.  The practical point is that there are a variety of ways out there to say what's ultimately the exact same thing.  

- Art

On Sep 25, 2012, at 12:28 PM, Carl Reed wrote:

> Art
> 
> GML changed directions? Not sure what you mean. There is now an OASIS GML profile for use in OASIS EM standards. Being referenced in HAVE, xAL, and EDXL. Perhaps in the next version of CAP? :-)
> 
> Cheers
> 
> Carl
> 
> 
> -----Original Message----- From: Art Botterell
> Sent: Tuesday, September 25, 2012 12:51 PM
> To: Brian Rosen
> Cc: [e-mail]
> Subject: Re: [atoca] Next milestone
> 
> 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 <[e-mail]> 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
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/atoca
>> 
> 
> _______________________________________________
> atoca mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/atoca