[CAP] Geocodes

[Art Botterell]

Farrel -

Unfortunately the NOAA implementation got that part wrong.  A strict  
parser should reject it as invalid.  I've had assurances they plan to  
fix that, but no word on when.

Until then you might prefer the California EDIS feed (http://capnorth.oes.ca.gov/index.atom 
) for testing.

- Art


On Nov 3, 2009, at 11/3/09 12:52 AM, Farrel Lifson wrote:

> I noticed that in CAP messages from the NOAA (for instance in this
> message  http://www.nws.noaa.gov/alerts/fl.cap) they use geocodes of
> the form
>
>  <geocode>012009</geocode>
>
> as opposed to the format in the capspec of
>
>  <geocode>
>    <valueName>Name</valueName>
>    <value>012009</value>
>  </geocode>
>
> Is this a common exception that is widely used and should be taken
> into account when parsing or should a CAP 1.1 compliant parser reject
> a message that contains a geocode like this?
>
> Thanks in advance,
> Farrel
> -- 
> Aimred - Ruby Development and Consulting
> http://www.aimred.com
> _______________________________________________
> This list is for public discussion of the Common Alerting Protocol.   
> This list is NOT part of the formal record of the OASIS Emergency  
> Management TC.  Comments for the OASIS record should be posted using  
> the form at http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency
> CAP-list mailing list
> CAP-list at lists.incident.com
> http://lists.incident.com/mailman/listinfo/cap-list
>
> This list is not for announcements, advertising or advocacy of any  
> particular program or product other than the CAP itself.