Internet GIS and Geospatial Web ServicesSession ObjectivesTypes of Internet GIS ApplicationsComputing Platforms: The Road MapComputing Platforms: Layering & Market Share ShiftsComputing Architecture Issues: Internet GIS InterfacesComputing Architecture Issues: Openness to…Computing Architecture Issues: Openness to…Computing Architecture Issues: Openness toComputing Architecture Issues: Types of Geospatial DataComputing Architecture Issues: Standards for Geospatial DataComputing Architecture Issues: Standards for Geospatial DataComputing Architecture Issues: Standards for Geospatial DataComputing Architecture Issues: Standards for GeoData TransferClient/ServerComponents of Client/Server SystemsThe ClientThe ServerThe MiddlewareInternet GIS Applications in Urban PlanningInternet GIS Applications in TransportationLos Angeles – online traffic reporting Observations Los Angeles – online traffic reporting Observations (#2)US EPA: EnviromapperAccessing Data and Geospatial Services Behind the ScenesFirst, a Simple Example – MIT OrthoToolsAccessing MIT OrthoServer from ArcMapNext: add in ArcWeb ServicesUsing ArcWeb ServicesSaved AXL File Using ArcExplorer to access FEMA_Flood web servicesGeneralizing this Web Service IdeaMassGIS – Web Service ExampleBoston Globe Article: Mashup of Election Campaign ContributionsWeb Service Chaining using Open Source Tools and Middleware for CustomizationIntelligent Middleware for Understanding Neighborhood Markets A collaborative effort by the Massachusetts Institute of TechnolExamples from MIT ‘Middleware’ ProjectWorkshop SectionsSection 6Section ObjectivePerformance InteroperabilityInteroperability (II)Cost RecoveryOther IssuesSummary and ConclusionsReferencesMIT 11.188/11.520 Web Service Notes1Internet GIS and Geospatial Web Services Introduction Section 1 -- What is Internet GIS? Section 2 -- Internet GIS: state of practice Section 3 -- Future development of Internet GIS Section 4 -- Function comparisons of current Internet GIS programs Section 5 -- Internet GIS applications Section 6 – Issues in the Development of Internet GISThese Internet GIS lecture slides for the MIT class 11.520/11.188 were originally developed by Prof. Joseph Ferreira (MIT) and Prof. Zhong-Ren Peng (UW-Milwaukee) and used as one part of the URISA Internet GIS Workshop (Vancouver, 2006). They were modified/augmented for Fall 2006-2008 for use at MIT by Professors Mike Flaxman and Joe Ferreira.MIT 11.188/11.520 Web Service Notes2Session Objectives Become familiar with some existing Internet GIS applications in city, county and state governments. Examine Some National & International GIS Services which provide useful “base data” Look critically at services/methods being proposedMIT 11.188/11.520 Web Service Notes3Types of Internet GIS Applications Data Sharing and disseminations; Raw GIS data, requires installed software & expertise to use Geospatial Information Sharing and publishing Often includes cartographic representations Can produce single purpose human-readable images Web Data Services Produce machine-readable geospatial information Distributed Analysis Functions (GIS Anywhere); Interoperable GIS Web Services (GIS Anyone Anywhere).MIT 11.188/11.520 Web Service Notes4Computing Platforms: The Road MapMainframe GISDesktop GISInternet GISMobile GISTimeAccessibilityMIT 11.188/11.520 Web Service Notes5Computing Platforms: Layering & Market Share ShiftsServerGISDesktop GISInternet GISMobile GISTimeAccessibilitySpatial Data InfrastructuresCreation, Analysis &Geospatial Content AuthoringInteractive ExplorationLocation BasedServices(not replacement)MIT 11.188/11.520 Web Service Notes6Computing Architecture Issues: Internet GIS Interfaces Single User Interfaces Isolated User User as Part of Enterprise GIS User as Part of Cybershere Groupware Multiple users, one location Multiple distributed usersMIT 11.188/11.520 Web Service Notes7Computing Architecture Issues: Openness to… Modification of System Use / Repurposing of Data Comment / Markup of Data Data EditingMIT 11.188/11.520 Web Service Notes8Computing Architecture Issues: Openness to… Modification of System Closed / Proprietary Semi-open / Public API Open Source –noncommercial use only Open Source –allowing commercial usesMIT 11.188/11.520 Web Service Notes9Computing Architecture Issues: Openness to Repurposing of Data Flattened image or graphics (picture of a map) GeoreferencedImagery Layer visibility control Layer symbolization control Examples Re-use of Google Earth imagery (only allowed in their context) Map layers with fixed opaque backgroundsMIT 11.188/11.520 Web Service Notes10Computing Architecture Issues:Types of Geospatial Data Vector Features Raster (Gridded) Data Geo-associated Database Records Imagery Metadata Perspective Views Geotagged Photos Streaming Position DataMIT 11.188/11.520 Web Service Notes11Computing Architecture Issues:Standards for Geospatial Data For many years, proprietary data formats most common Two issues Vendor interest in capturing/maintaining users Efficiency in operation Often by having data formats mirror internal structuring Vendors provide “value added” in software, but then need means to “persist” data associated with those featuresMIT 11.188/11.520 Web Service Notes12Computing Architecture Issues:Standards for Geospatial Data Many government standards attempted Some “de facto” such as USGS Digital Elevation Models (DEM), TIGER line files Some more formal – National Spatial Data Transfer Standard Generally ended up being either Too specific Too unweildy Lead to Public/Private Partnership Approach Resulting in Federal Geographic Data Committee  Increased interest in open interoperability standardsMIT 11.188/11.520 Web Service Notes13Computing Architecture Issues:Standards for Geospatial Data Vector Features “Simple Features” specification (2D points, lines, polys) Geographic Markup Language (GML)Raster (Gridded) Data & Imagery GeoTIFF (geographically tagged TIFF images) JPEG2 (includes GML metadata)Geo-associated Database Records SQL + Simple FeaturesMetadata Federal Geographic Data Committee Standards (FGDC)MIT 11.188/11.520 Web Service Notes14Computing Architecture Issues:Standards for GeoData Transfer