Wednesday, September 23, 2015

Lab 2: Geospatial Web Services

Goals

In this lab we were able to learn the skills to both author and create geospatial web services. Throughout this lab exercise we were introduced to the process of authoring geospatial data to create as well as host geospatial web services on ArcGIS Online for Organizations and also through the ArcGIS server and the server hosted by UWEC's department of Geography and Anthropology. During this lab we learned the techniques of how to publish geospatial web services to various formats such as ArcMap, through the ArcGIS server, shapefiles and Excel CSV files. We were introduced to the creation of a feature access service which allows for end-user editing.

Methods

Part 1: Publishing Feature Hosted Services through ArcGIS Online

In this first portion of the lab we needed zip a large feature dataset in order to upload the data directly to the ESRI cloud. To do this we first zipped the data and after logging in to ArcGIS Online added the file to our individual contents and publish the file as a feature service. Once the zip file was uploaded to ArcGIS Online and the file was published as a feature service it could then be added to a map. The layers within this zip file then became editable features within the web-based map. 


(Fig. 1) This is the window which appears after the data from the zip file we created was published on ArcGIS. As can be seen in this image the data is now in the form of a feature service.
Another dataset which can be added to ArcGIS Online is a feature hosted service using a CSV file. While the process of publishing an Microsoft Excel CSV file is the same as adding a group of shapefiles in the form of a zip file as explained earlier it was a new way in which we learned how data could be incorporated into the ArcGIS Online interface. The CSV file used in this portion of the lab was based on Wisconsin Fire Occurrence data. Once it was published to ArcGIS Online we needed to assign the X and Y data from within the CSV file to longitude and latitude respectively in order to locate the features. We were also able to configure pop-ups. Pop-ups allow web maps to be much more interactive and help to display relative data when an end user selects a feature. For instance, in this case when the viewer of the map of Wisconsin Fire Occurrences selects a point which represents a fire they are able to see information about the date of the fire (Fig. 2).


(Fig. 2) By utilizing pop-ups through ArcGIS Online's mapping service we can give more detail about individual data points in a given feature class. As seen in this image for instance we can enable pop-ups so the end user is able to select each data point and gain more information about that particular point.
Yet another way which we learned how to publish feature services was directly through ArcMap. By using this method, every dataset within the map document is published in a single instance. To do this we first loaded two data sets, lakes as well as rivers and streams, and selected to share as a service. The next step was to edit the feature service in order to control what types of edits the users can make. Feature services can be configured so that end users can create or add, delete query and update features or data within the feature service. Next, we had the option to share the service and within the service editor we clicked the "analyze" option in order for the program to examine the map you are about to publish and make sure there are no errors. As long as no errors are found (or the errors are fixed) the service can be published and viewed on ArcGIS Online. 

Part 2: Publishing a Tiled Map Service Using ArcGIS Online

Similarly to part 1, the second part of this lab exercised focused on publishing feature services and other data types to ArcGIS Online, however in this portion we published these services using the ArcGIS Server. The first step in this process was to add a database connection using ArcCatalog. To do this we selected the SQL Server as our database platform and authenticated the database using our individual username and password. Next we added a raster data file to the new database we connected to. After cleaning up the dataset by changing the symbology a bit, we were ready to share the data as a service (similar to how we did in part 1 of the lab). However, one big difference in the procedure was connecting to the UWEC Geography and Anthropology Department ArcGIS Server in this portion. To do this we needed to add an ArcGIS Server by again entering in information such as the server URL and more authentication information (Fig. 3). 


(Fig. 3) In order to share a service to ArcGIS Online using the ArcGIS Server we needed to connect to the server itself before our feature service was able to be published.
Once this was complete we then got the list of options available to us through the service editor window which, as discussed in part 1, allowed us to set the different parameters for our image. One particular option we looked at in part 2 of this lab exercise was caching. We adjusted the caching for this service so that when users go to access this feature service it will be draw using tiles from a cache. This option minimizes the stress put on the server. We also set the minimum caching scale to 10 and the maximum to 17 and changed the tile format to mixed rather than PNG. As we did in part 1 we again selected the "analyze" option within the service editor to check for errors and when none were found (or they were all resolved) we were able to publish the service. 

(Fig. 4) Within the Service Editor in ArcMap the developer has the option to adjust a wide variety of settings which will impact the end user's experience when viewing the final published service. In this image the cache settings are being adjusted.

Part 3: Author a Map Document, Create a Feature Service & Add to a Web Map

In the final part of the lab we authored a map, created a feature service and a reference for the service in a web map. The first step in this process was to import two sets of data: earthquakes and hurricanes. Next, we changed the symbology of both layers in order to make it easier for the viewer to understand which events were more severe than others by using a graduated color ramp for hurricanes and graduated symbols for earthquakes. Then we enabled time as a layer for both of the two sets of data. To do this we selected the "time" tab within the layer properties and used the dates of the events in the time field. Once this was applied in ArcMap we were able to enable the time on the map and view the progression of the events based on the dates each natural disaster occurred. When we later went to share the service and publish the features to ArcGIS Online we needed to enable this content in the "capabilities" portion of the service editor so that the end-users would be able to see this time progression in the final product as well. 


(Fig. 5) Within the layer properties of both the earthquake and hurricane layers we were able to enable time. This then displays the individual events over time rather than just a set of stagnant points.
(Fig. 6) Once both layers have time enabled we are able to use the time slider tool in ArcMap to display the events and make sure everything is working correctly.
To produce the final map we enabled pop-ups for both the earthquake data points and the hurricane lines to include information about each of the events including date they occurred, name and other pertinent data. In addition we were also able to apply the time settings in order to display the progression of events.

Results

As a result of this lab exercise we learned how to publish and share feature services from a wide variety of platforms including CSV files, zipped files, as well as directly using ArcMap and ArcGIS Server. The maps which I published can be seen using the links below. 

Part 1 Maps:



Part 3 Map: 


Sources

Data sources for this lab are listed below in the order they were used: 
  • Mastering ArcGIS Geodatabase by Maribeth Price, 2014
  • Wisconsin DNR, 2013
  • Cyril Wilson, 2012 (unpublished Lakes dataset)
  • Advanced Remote Sensing Class at UW-Eau Claire, Fall 2012
  • Fu, Pinde, 2015
  • \\EsriPress\GTKWebGIS\Chapter3\Data.gdb\Earthquakes, courtesy of USGS National Atlas
  • \\EsriPress\GTKWebGIS\Chapter3\Data.gdb\Hurricanes, courtesy of NOAA National Climatic Data Center


No comments:

Post a Comment