[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] Fwd: Re: [CAP] Need advice on FIPS code to Polygon conversion
Interesting - This is definitely a GIS/Geospatial type of discussion. To start the discussion, I would suggest that the geometries be encoded as GML and not SHAPE files. I would also look at a general solution for providing a registry of geometries for any theme (not just FIPS codes). Two reasons for the above statements: 1.) CAP is an International standard and not just US and 2.) the INSPIRE directive in Europe mandates the use of de-jure standards and GML is an ISO standard (Shape files are not). More to follow on the use of Gazetteers as a registry of geometry resources. Carl I would encourage> >>Delivered-To: 108-ejones@warningsystems.com >>Date: Mon, 15 Sep 2008 16:14:19 -0400 >>From: Bob Bunge <Robert.Bunge@noaa.gov> >>To: Art Botterell <ABott@so.cccounty.us> >>User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) >>Cc: cap-list@lists.incident.com >>Subject: Re: [CAP] Need advice on FIPS code to Polygon conversion >>X-BeenThere: cap-list@lists.incident.com >>X-Mailman-Version: 2.1.11 >>List-Id: Common Alerting Protocol Public Discussion >> <cap-list.lists.incident.com> >>List-Unsubscribe: <http://eastpac.incident.com/mailman/options/cap-list>, >> <mailto:cap-list-request@lists.incident.com?subject=unsubscribe> >>List-Archive: <http://eastpac.incident.com/pipermail/cap-list> >>List-Post: <mailto:cap-list@lists.incident.com> >>List-Help: <mailto:cap-list-request@lists.incident.com?subject=help> >>List-Subscribe: <http://eastpac.incident.com/mailman/listinfo/cap-list>, >> <mailto:cap-list-request@lists.incident.com?subject=subscribe> >>Sender: cap-list-bounces@lists.incident.com >>X-pstn-neptune: 1/1/1.00/94 >>X-pstn-levels: (S:99.90000/99.90000 CV:99.9999 R:95.9108 >>P:95.9108 M:97.0282 C:98.6951 ) >>X-pstn-settings: 5 (2.0000:2.0000) s cv gt3 gt2 gt1 r p m c >>X-pstn-addresses: from <Robert.Bunge@noaa.gov> [419/14] >> >> >>Art, >> >>We can certainly consider it. NWS certainly doesn't have the >>resources to do the QC and there would certainly be some benefit for >>it. To make it more interesting, in addition to US counties, NWS >>also needs something of this sort for both the NWS forecast and fire >>weather zones - both are used to define boundaries of various NWS alerts. >> >>Bob >> >>Art Botterell wrote: >>>Particularly since we're going to be dealing with FIPS codes for however >>>long SAME coding remains in use for Weather Radio and EAS, the idea of >>>accumulating and publishing a standard library of simplified polygons >>>for each of them strikes me as making a great deal of sense. >>>Bob, assuming such a collection existed, do you think NWS might be >>>willing to publish it along with the various shapefiles and such on your >>>website? >>>- Art >>> >>>Art Botterell, Manager >>>Community Warning System >>>Contra Costa County Office of the Sheriff >>>50 Glacier Drive >>>Martinez, California 94553 >>>(925) 313-9603 >>>fax (925) 646-1120 >>> >>>>>>Mick Jagger <lists@jpw.biz> 9/14/2008 4:34 PM >>> >>>>What's needed... and I'm sure somebody knows an efficient way to do >>> >>>>this... is a tool to take full-resolution GIS polygons and simplify >>> >>>Here is a link that discusses this process along with a commercial tool >>>and free tool to do it. >>>http://freegeographytools.com/2007/simplifying-line-and-polygon-shapefiles >>> There are a number of other simplification methods also. I've done >>>some simplification of polygons reducing multi-thousand point polygons >>>down to under 100 for CAP alerts. While the simplification cuts down on >>>the amount of work required, I found there was still a lot of manual >>>cleanup that needed to take place. Checking that too much >>>simplification didn't omit a section, making sure adjoining polygon >>>areas match up by the same points, etc. >>>If there was enough interest, a common resource site for warning >>>polygons could be setup with the manual cleanup work broken down into >>>small work units that people could chip in to help cleanup in their >>>"spare" time. >>>_______________________________________________ >>>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@lists.incident.com >>>http://eastpac.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. >>>_______________________________________________ >>>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@lists.incident.com >>>http://eastpac.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. >>_______________________________________________ >>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@lists.incident.com >>http://eastpac.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. > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]