1 / 22

Web GIS: Programming Techniques for Online Mapping Apps

Seth Peery , Senior GIS Architect Virginia Tech Enterprise GIS 2014-03-05. Web GIS: Programming Techniques for Online Mapping Apps. Objective: Understand how web maps work, what goes on behind the scenes, and how to actually deploy them in production IT environments

ishi
Télécharger la présentation

Web GIS: Programming Techniques for Online Mapping Apps

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. Seth Peery, Senior GIS Architect Virginia Tech Enterprise GIS 2014-03-05 Web GIS: Programming Techniques for Online Mapping Apps

  2. Objective: Understand how web maps work, what goes on behind the scenes, and how to actually deploy them in production IT environments • Common architectural features of web mapping applications • Web Mapping Workflows • Examples from on-premises and cloud mapping platforms

  3. Web Mapping vs. Supporting GIS components Web Mapping You are here. Cartography Data Management

  4. All these components exist (somewhere) whether your app is local or in the “cloud.” Software Architecture • This layer consists of web content that’s not the web application – look and feel, formatting, etc. • This layer addresses the functionality of your application – e.g., what happens when the user clicks? • This layer concerns the transport of data from its source format, with the appropriate presentation., to the web application. • This layer concerns map symbology. It is more of a workflow item than a subsystem – it may be handled in the source data or the map svc. Everything from here down is data

  5. Functional Components ofAll Web Mapping Applications • Source data • Data accessible to the web app • Basemap (increasingly coming from third party services) • Thematic layers (your data) • Representation/symbology of the data • Web service to return thematic data • Web map object and application logic • Web application container/interface for the map (presentation)

  6. Cloud The “cloud” over Web Mapping • Objectives • Author Maps • Publish Services/Apps • Use the above • Approaches • Public cloud SaaS • Public cloud PaaS • Internal cloud provider(Enterprise GIS) • All on your own machine Increasing Control Increasing Abstraction VT Enterprise GIS Ground

  7. On-premises and cloud workflows (ESRI)

  8. ArcGIS Server Deployment Scenarios • Cloud (AGOL) workflow: • Identify source data • Make an MXD in ArcGIS for Desktop • Publish a Map Service based on the MXD to AGOL, set capabilities • In “My Map”, add layers and save to My Content • Create a web application from the map • Host from AGOL or copy app to your own server On-premises workflow: • Identify source data • Move source data to a location visible to the GIS server (e.g., ArcSDE, file GDB on server) • Make an MXD with data source references to “production” copy of data • Publish a Map Service based on the MXD, set capabilities • Create a web application that consumes the service • Configurable web viewer (e.g. Application Builder) • Custom code (e.g., JS API)

  9. Examples • Publishing data to ArcGIS for Server • ArcGIS Viewer for Flex (Configurable web mapping application) • ESRI JavaScript API • ArcGIS Online

  10. Initial Setup • Assemble data, make a map and make sure the server can access it

  11. Publish to ArcGIS Server

  12. REST Services Directory • The map we created in ArcMap is now available as a REST endpoint and can be accessed via the REST services directory by a web mapping application. http://training.gis.vt.edu/arcgis/rest/services

  13. Web Service representations of the map REST SOAP

  14. REST preview • Web Services have no UI – they’re meant to be used by computer programs • The REST services directory provides a minimal preview web application for human viewers • We’re not done yet – this is not a “real” web application. http://training.gis.vt.edu/arcgis/rest/services/samples/BlacksburgRCL/MapServer

  15. ArcGIS Viewer for Flex • SFV is a configurable web mapping application from http://resources.arcgis.com • The app is a Flash-based viewer that can be modified (to an extent) via a set of XML files http://resources.arcgis.com/en/communities/flex-viewer/

  16. Flex Viewer Example http://training.gis.vt.edu/geog5984/sampleflex/

  17. FlexViewer Source http://training.gis.vt.edu/geog5984/sampleflex/config.xml

  18. ArcGIS Server JavaScript Viewer Example: Blacksburg RCL over ESRI terrain http://training.gis.vt.edu/geog5984/samplejs/example2.htm

  19. “My Map” in AGOL

  20. From “My Map” to Web Map

  21. ESRI Developer Resources • Main ArcGIS Server Resource Center:http://resources.arcgis.com/en/help/main/10.2/index.html#//0154000002np000000 • ArcGIS Viewer for Flex http://resources.arcgis.com/en/help/flex-viewer/concepts/ • ArcGIS Server JavaScript API Reference:http://help.arcgis.com/en/webapi/flex/apiref/index.html

  22. Contact Information Seth Peery Senior GIS Architect, Enterprise GIS Virginia Tech Geospatial Information Sciences 2060 Torgersen Hall (0197) Blacksburg, VA 24061 (540) 231-2178 sspeery@vt.edu http://gis.vt.edu

More Related