1 / 21

Applying Geospatial Conventions to NWS Products Using IRIS

By Jason Burks NWS HUN. Applying Geospatial Conventions to NWS Products Using IRIS. Why do we want NWS products in Geospatial conventions. Flexibility Format that is readily usable Easy integration with other GIS datasets and systems. Requirements. Process all products

carol-shannon
Download Presentation

Applying Geospatial Conventions to NWS Products Using IRIS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. By Jason Burks NWS HUN Applying Geospatial Conventions to NWS Products Using IRIS

  2. Why do we want NWS products in Geospatial conventions • Flexibility • Format that is readily usable • Easy integration with other GIS datasets and systems

  3. Requirements • Process all products • Process the products quickly • Push them into a common format • End format has to be available • Needs to support GIS standards

  4. What has been done already • UGC • Added polygon to warning • Adding of VTEC string • Warnings output as shapefile • Limited amount of products • Work on CAP format • None of these are geospatial conventions except shapefile.

  5. Typical NWS products • UGC MTZ012-050-054-055-010445- • VTEC /O.EXT.KHUN.FA.W.0022.000000T0000Z-090927T0030Z/ • Polygon LAT...LON 3753 8667 3742 8663 3740 8663 3732 8674 3735 8691 3748 8694

  6. Take NWS product and provide in common format Polygon Decoder Postgis Db Non-Polygon Segmented Non-segmented

  7. Decoding data problems • Not all products have • Segments • Polygons • VTEC or HVTEC • And they change • So a programmer has to keep on top of product changes, and installed locations need to update.

  8. Fix for problem • Assumptions about products: • Treated as segmented • Don't maintain information about specific products • Checked for VTEC, and HVTEC • Checked for polygon

  9. Storage of data using Hibernate Spatial Decoder DAO Hibernate Spatial Postgis Db

  10. Using Spring • Flexibility using Spring Framework • Support for caching of lookup data • Threaded Task Executor • Easy configuration/re-configuration • Integrates well with Hibernate and Spatial Hibernate

  11. Application of data using Postgis for Spatial Queries • Intersects • Within • ToWKT • toGeoJson

  12. Support for GIS Conventions Polygon Decoder Postgis Db GeoServer Web Clients Non-Polygon Mapserver Segmented GIS Tools Non-segmented

  13. Output in other formats • Data can be exported to other various formats • GML • Shapefile • WKT • GEO Json • WMS • WFS • KML

  14. NWS Products supported • All Warnings • All Watches • LSRs • UGC based products

  15. Examples • Some examples of the database being used • Web • GIS application

  16. Multi-Use • Now that we have the data in a Common format • Can use it in multiple projects with little effort. • On the web • Research • Verification • ? • Already being used in • Ridge II • Central Region GIS system.

  17. Future Work • Push data on to JMS • Decode more data atomically • Stand-up more GIS services

  18. Questions? • Jason.Burks@noaa.gov

More Related