napsg 2010 fire/ems conference - data sharing basics
TRANSCRIPT
Data Sharing Basics & Regional Efforts
Peter Di Turi, Lead GIS Analyst
Seattle Fire Department
Topics
• Simple Data Concepts• GIS Data Formats• GIS Web Services• Fire/EMS Data Standards• GIS Data Repositories• Fire/EMS GIS Data Repositories
Simple Data Concepts
• What’s The Difference Between Information and Data?– Information:• The communication or reception of knowledge
– Data:• Information that can be digitally transmitted and
processed
– Metadata: Data about the data.
Simple Data Concepts
• What’s The Difference Between a Data Repository and a Data Format?– Data Repository:• A physical or logical container for data
– Data Format:• The structure of a data repository
– Proprietary - Industry-Standard– User-Defined
Simple Data Concepts
• Examples Of A…– Data Repository:• Physical: USB drive, PC, server, warehouse, cloud• Logical: File, spreadsheet, database, shapefile, geodatabase
– Data Format:• Text: fixed or delimited, ASCII or binary• Proprietary: ArcGIS Server, Access, Excel, Oracle, SQL Server• Industry-Standard: Shapefile, GeoRSS, GML, KML• User-Defined: business attributes (it’s “almost” all up to you!)
Simple Data Concepts• What Data Repositories work for:– A single-user? • ANY OF THEM.
– More than one user at the same time?• Physical: server, warehouse, cloud• Logical: geodatabase (SDE), database (Oracle/SQL Server)
• Data Formats can have issues related to:– Compatibility, performance, unreliable metadata
Topics
• Simple Data Concepts
• GIS Data Formats• GIS Web Services• Fire/EMS Data Standards• GIS Data Repositories• Fire/EMS GIS Data Repositories
GIS Data Formats
• Traditional GIS Data Format:– Text Files (Fixed Width and Delimited)– DBase (DBF)– Arc/Info Coverages and INFO tables (ESRI)– Personal Spreadsheets and Databases– Other vendors (Autodesk, Intergraph, MapInfo, etc.)– Shapefiles (ESRI -> open standard)– Personal Geodatabases (Microsoft/ESRI)– RDBMS Links (Informix, Sybase, Oracle, SQL Server)
GIS Data Formats
• Newer GIS Data Formats:– SDE (ESRI –working with MANY RDBMSs)– File Geodatabases (ESRI)– SDO (Oracle Spatial)– SQL Server 2008 Spatial (Microsoft)– KML (Google Earth) – Bing Maps– Open Geospatial Consortium• GeoRSS, WKT, WKB, GML (XML variant)
GIS Data Formats• GeoRSS (Geographic Really Simple Syndication)
<?xml version="1.0"?> <?xml-stylesheet href="/eqcenter/catalogs/rssxsl.php?feed=eqs7day-M5.xml" type="text/xsl" media="screen"?> <rss version="2.0" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel> <title>USGS M5+ Earthquakes</title> <description>Real-time, worldwide earthquake list for the past 7 days</description> <link>http://earthquake.usgs.gov/eqcenter/</link> <dc:publisher>U.S. Geological Survey</dc:publisher> <pubDate>Thu, 27 Dec 2007 23:56:15 PST</pubDate> <item> <pubDate>Fri, 28 Dec 2007 05:24:17 GMT</pubDate> <title>M 5.3, northern Sumatra, Indonesia</title> <description>December 28, 2007 05:24:17 GMT</description> <link>http://earthquake.usgs.gov/eqcenter/recenteqsww/Quakes/us2007llai.php</link> <geo:lat>5.5319</geo:lat> <geo:long>95.8972</geo:long> </item> </channel> </rss>
GIS Data Formats
• WKT (Well-Known Text)
-- Creating a geography Point from WKTDECLARE @Edinburgh geography SET @Edinburgh = geography::STPointFromText('POINT(-3.19 55.95)', 4326)
- Creating a LineString from WKTDECLARE @SydneyHarbourBridge geographySET @SydneyHarbourBridge = geography::STLineFromText( 'LINESTRING(151.209 -33.855, 151.212 -33.850)',4326)
GIS Data Sources• WKB (Well-Known Binary)
--Creating a Geometry Collection from WKB
SELECT geometry::STGeomCollFromWKB(
0x00000000070000000200000000014044333333333333C002888A47ECFE9B0102000000020000009BFEEC478A8802C033333333333344406666666666F65340B81E85EB51B81B40, 0)
-- Creating a Point from WKBDECLARE @ByteOrder bitDECLARE @GeometryType intDECLARE @longitude floatDECLARE @latitude floatSET @ByteOrder = 0SET @GeometryType = 1SET @longitude = 21.01SET @latitude = 52.23DECLARE @WKB varbinary(max)SET @WKB = CAST(@ByteOrder AS binary(1)) + CAST(@GeometryType AS binary(4)) + CAST(@longitude AS binary(8)) + CAST(@latitude AS binary(8))DECLARE @Point geographySET @Point = geography::STPointFromWKB(@WKB, 4326)
GIS Data Sources
• GML (Geography Markup Language)-- Creating a MultiPolygon from GMLDECLARE @MultiPolygon geometrySET @MultiPolygon = geometry::GeomFromGml('<MultiSurface xmlns="http://www.opengis.net/gml"> <surfaceMembers> <Polygon> <exterior> <LinearRing> <posList>2 3 5 3 6 8 2 7 2 3</posList> </LinearRing> </exterior> </Polygon> <Polygon> <exterior> <LinearRing> <posList>10 20 20 20 20 30 10 30 10 20</posList> </LinearRing> </exterior> </Polygon> </surfaceMembers></MultiSurface>', 0)
-- Creating a Geometry Collection from GMLDECLARE @GeometryCollection geometrySET @GeometryCollection = geometry::GeomFromGml('<MultiGeometry xmlns="http://www.opengis.net/gml"> <geometryMembers> <Point> <pos>15 10</pos> </Point> <LineString> <posList>4 10 2 3</posList> </LineString> </geometryMembers></MultiGeometry>', 0)
Topics
• Simple Data Concepts• GIS Data Formats
• GIS Web Services• Fire/EMS Data Format Standards• GIS Data Repositories• Fire/EMS GIS Data Repositories
GIS Web Services
• What is a Web Service?– Standardized way to receive and transmit data
over the Web between computer applications– A Web Service requires these components:• Identifying, or tagging data (XML)• Protocol to transfer/receive data messages (SOAP)• Describing the services/metadata (WSDL)• Listing/publishing of services (UDDI)
GIS Web Services
• You can get, or consume data from GIS Web Services with:– A client application (Web browser, ArcGIS
Explorer, your .NET/Java/Flex, etc. code)
• You can host data from GIS Web Services with:– A server application (ArcGIS Server authoring
tools, your .NET/Java/Flex, etc. code)
GIS Web Services
• Creating a Web Service SHOULD CONSIDER:– what data is REALLY needed– security– performance (particularly for GIS Web Services)– metadata – documenting your data WELL (WSDL)
• The goal: a uniform way to safely dole out your best data on-demand and quickly
Topics
• Simple Data Concepts• GIS Data Formats• GIS Web Services
• Fire/EMS Data Format Standards• GIS Data Repositories• Fire/EMS GIS Data Repositories
Fire/EMS Data Format Standards
HUH?
Are YOU kidding??
Fire/EMS Data Formats/Standards
• NAPSG/ESRI Fire Data Model– Advantages:• Supports emergency management, hazards,
infrastructure specifically for Fire service• Indifferent to base maps, so it’s flexible• Has ArcGIS Geodatabase export of data model• Has detailed data dictionary
Fire/EMS Data Formats/Standards
• NAPSG/ESRI Fire Data Model– Disadvantages:• Doesn’t cater to every department’s detailed data
needs -> need to write data extensions to the model• Flexibility in base data may lead to lost opportunities in
mutual-aid data sharing (utilities, roads, etc.)• No XML-based messaging standards• Doesn’t deal with EMS
Fire/EMS Data Formats/Standards
• EDXL (Emergency Data Exchange Language)– Advantages:• Facilitates emergency information sharing using XML• Promotes real-time message exchanges• Developed from DHS Disaster Mgt. E-Gov Initiative• XML Data Standards for Message Distribution,
Resource Messaging, Hospital Availability, Situation Reporting, Tracking of Emergency Patients• Data Standards Implement GeoOASIS Where (GML)
Fire/EMS Data Formats/Standards
• EDXL (Emergency Data Exchange Language)– Disadvantages:• Not specific to Fire Service or EMS • Not low-level data• Not meant for routine data exchange• Requires application for sending/consuming messages
One Wish…
Topics
• Simple Data Concepts• GIS Data Formats• GIS Web Services• Fire/EMS Data Format Standards
• GIS Data Repositories• Fire/EMS GIS Data Repositories
GIS Data Repositories• Internal GIS Data Server Solutions– ORACLE or SQL Server Spatial• Native database spatial data, Web services
– ArcGIS Server• database spatial data, Web services
– Simple file (shapefile, spreadsheet, personal GeoDB)• Well-Organized: SharePoint• Less Organized: drives/directories/files/readme.txt
GIS Data Repositories• External GIS Data Server Solutions– SkyDrive, Office Live– Somebody Else’s Server (ArcGIS, Spatial DBs, Files)– SOCRATA (data.seattle.gov)– ArcGIS Mapping for SharePoint– ArcGIS Server Geoportal Extension (NOAA NCDC)– ArcGIS Server Cloud• Amazon EC2 OR ESRI-hosted OR ESRI-managed
– ArcGIS Online
Topics
• Simple Data Concepts• GIS Data Formats• GIS Web Services• Fire/EMS Data Format Standards• GIS Data Repositories
• Fire/EMS GIS Data Repositories
Fire/EMS GIS Data Repositories• Public Government:– LA County eGIS: Station Fire Perimeters– NYC DataMine: Companies, Battalions, Districts
• Local:– King County Zone 3 NEW SharePoint Site• Developed to support ValleyCom CAD implementation• Provides unified mutual-aid fire mapping needs
– Future PrePlan Respository (SeaTac FD Grant Application)
Additional References• GIS In The Cloud: The ESRI Example– David Chapell, Chappell & Associates, Sept. 2010
• Geodata.gov and Oregon Geospatial portals• WA State Geospatial Clearinghouse– Learn About Metadata and Contribute Metadata
• Open Geospatial Consortium– Standards: CityGML, GML, KML, WFS, WMS
• ESRI– ArcGIS Server Web Mapping…for Local Government
The Bottom Line• Data comes from many places and in many
different forms for GIS’s to have to swallow• GIS Web services make data sharing easier but
there’s a learning curve to develop/use them• The ESRI Fire Data Model is more useful with a
set of Web data format messaging standards• I don’t care where my data is – I want it now!• Well-documented metadata is always JOB #1!
Questions/Comments?
Peter Di Turi
GIS Analyst
Seattle Fire Department
301 2nd Avenue South
Seattle, WA 98104-5031
Work: 206.386.1542
E-mail: [email protected]