applying geospatial conventions to nws products using iris
DESCRIPTION
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 - PowerPoint PPT PresentationTRANSCRIPT
Applying Geospatial Conventions to NWS Products Using IRIS
By Jason Burks NWS HUN
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 Process the products quickly Push them into a common format End format has to be available Needs to support GIS standards
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.
Typical NWS products
UGCMTZ012-050-054-055-010445-
VTEC/O.EXT.KHUN.FA.W.0022.000000T0000Z-090927T0030Z/
PolygonLAT...LON 3753 8667 3742 8663 3740 8663 3732 8674
3735 8691 3748 8694
Take NWS product and provide in common format
Polygon
Segmented
Non-segmented
Non-Polygon
Decoder PostgisDb
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.
Fix for problem
Assumptions about products: Treated as segmented Don't maintain information about specific
products Checked for VTEC, and HVTEC Checked for polygon
Storage of data using Hibernate Spatial
Decoder PostgisDbDAO Hibernate
Spatial
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
Application of data using Postgis for Spatial Queries
Intersects Within ToWKT toGeoJson
Support for GIS Conventions
Polygon
Segmented
Non-segmented
Non-Polygon
Decoder PostgisDb
GeoServer
Mapserver
GIS Tools
Web Clients
Output in other formats
Data can be exported to other various formats GML Shapefile WKT GEO Json WMS WFS KML
NWS Products supported
All Warnings All Watches LSRs UGC based products
Examples
Some examples of the database being used Web GIS application
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.
Future Work
Push data on to JMS Decode more data atomically Stand-up more GIS services
Questions?