I have gained valuable experience working on projects in ArcGIS Desktop and Pro, 3GIS and ArcGIS Online, over the last several years. This page features workflow of tasks I have completed in professional and academic settings.

Experience using ArcGIS Online

Geospatial Data I Published Online For The Ledcor Engineering Team

How to Publish a Layer Online

Summary: The workflow begins by preparing the layer in ArcCatalog, then symbolizing the mxd, making the service, then publishing in ArcMap. Then adding the layer to the online platform in ArcGIS Online.
Workflow
In ArcCatalog
  • Import the layer to the SDE with the name it will have in the SDE
  • Set Privileges: Right-Click the Feature Class -> Manage to access the Privileges and Feature Class Settings:



  • Register as Versioned
  • Create Attachments if fielders need the ability to add photographs to the layer.
  • Enable editor tracking if it is in the working database. This adds fields that records who added a record and when.
  • Change alias so it appears with a descriptive name in the mxd and elsewhere

  • Add the layer from the SDE to the mxd.

  • In ArcMap
  • Set the data source to the SDE listed in the Mapping\EGDB_Connections folder.
  • Symbolize the feature types
  • Set the visible scales
  • Save the mxd to Web_Mapping\MXD
  • Make the service.
  • File>Share As>Service brings you to this.


  • The Service name should be the same as the mxd
  • Publish to X_OneFiber for the Chicago market.
  • Publish the service.
  • In Service Editor go into Capabilities, uncheck KML and, only if the layer will be editable, check Feature Access. Otherwise, it will be a map service.
  • Fill in the Item Description fields
  • Click Analyze, then Publish.


  • Go to the Server Manager
  • Click Feature Access if the layer will be editable. This will create a REST url that ends in “FeatureServer”. If it’s not editable, click Mapping.
  • Copy the REST url

  • In ArcGIS Online
  • Go to my ESRI online account
  • Click Add Item and choose From URL.


  • Paste the REST url into the URL field, click outside of it, then login and click Add Item, then OK.
  • Establish sharing for the layer
  • Go to Content in my online ESRI account and choose the groups to share with.
  • Add the layer to the map
  • Go to My Organization, click Maps and search for the map to which the layer should be added.
  • Click Add>Search for Layers and add the layer
  • Click the + to add the layer to the map and Save.

Publishing Task:

    Responsibility
    Add hub locations and boundaries to the Construction Collector webapp and make the Sites layer searchable.

    Workflow
  • Z-Values needed to be disabled in order to enable publishing of the layer. I disabled them, following the steps on this webpage: https://support.esri.com/en/technical-article/000010389
  • Set the data source for each layer in the mxd to each corresponding layer in the SDE Owner database.
  • Set the visible scale ranges and symbolized the two layers in ArcMap.
  • Table of Contents
  • Saved the mxd with the same name and deleted the original service so Arc would let me re-publish.
  • Added the layers to AGOL and added to the online map.

  • published layer - hubs and their boundaries

    The designer wanted sites to be searchable by name.
  • I searched for the WebApp in the My Organization page of my ESRI account and clicked Edit Application to open WebAppBuilder.
  • Construction Collector WebApp
  • Then clicked Widget to bring up the widgets and opened the Search widget.
  • The Panel of Widgets
  • Added the Sites layer to the Search widget.
  • Specified the Name field as the one to use in the search.
  • Editing the Search Widget in WebAppBuilder

Academic Experience

This is a summary of an academic project on which I gained experience with Arc Toolbox tools, including those for Data Management, Analysis, Spatial Analysis and Conversion. Below is an academic example of a project for which I used ArcMap tools.

Coursera MOOC: Geospatial and Environmental Analysis

As a student in the Coursera UC-Davis MOOC, Geospatial and Environmental Analysis, I was tasked with analyzing ozone concentrations in relation to household income and elevation above sea level in California. The project was based on data for those variables from 2010 to 2011.

Tasks, Hypothesis, Workflow, and Conclusion

I need two maps and two graphs. I will need to join layers and tables to make the graphs and maps. The results can be used for both. Data provided: elevation, ozone, and household income data.

Tasks
Form a hypothesis about the variables. Consider the relationship between lower atmospheric ozone concentrations and elevation is and the relationship between ozone concentration and household income is. Are there any relationships at all? This is my investigation.

Hypothesis
I would think the relationship between income and ozone concentrations would be inverse (lower income, higher concentrations) and the ozone to elevation relationship would be direct.

Workflow
  • In order to create a graph of ozone and elevation, I attached ozone means and the DEM 30 raster to the air quality stations point layer.

  • Join using Extract Multi Values to Points tool
  • Join the ozone_average table to attribute table of air_quality_locations point feature layer, by right clicking the layer > Joins and Relates > Join (check "keep only matching records" to exclude null values)
  • Right click on air_quality_locations
  • Join with ozone_averages, using Site from the layer and Site_id from the table as the fields
  • This adds the field avg_ozone_2010_2011 to the layer
  • Since this is just a temporary join, make it permanent by exporting it as a shapefile (named air_quality_locations_ozone.shp). The permanent shapefile is necessary to prevent the error "Could not open workspace %1."
  • Attach elevation field from DEM raster to the attribute table of the air_quality_locations_ozone layer
  • If the two layers were both vector, I could do a spatial join. But since one is a raster, I need the Extract Multi Values to Points tool.
  • Using the Extract Multi Values tool produces an error saying, "Cannot open workspace %1." Therefore, Extract Multi Values to Points is the necessary tool
  • Input feature class: air_quality_locations_ozone input raster: dem_30_ca (don't select the option to interpolate values)
  • With this layer, create a TIN and raster for ozone concentrations to compare ozone data vs. household income
  • The TIN is essential because it provides elevation data with each air quality station
  • 3D Analyst > Data Management > TIN > Create TIN
  • Input feature class: air_quality_locations_ozone
  • height field: avg_ozone_ which was named avg_ozone_2010_2011 in the ozone_averages table (coordinate NAD_1983_California_Teale_Albers); Output TIN: AirQualityTIN
  • Convert AirQualityTIN to raster:
  • Convert TIN to raster: 3D Analyst > Conversion > TIN > TIN to Raster
  • Input TIN: Airquality_Ozone_to_TIN; Output Raster: AQ_TIN2Raster (file name must be <=13 characters) (Float, Linear, Sampling Distance = CELLSIZE 30)
  • Create a graph of ozone and household income
  • Use Zonal statistics as table tool to create a table of mean ozone values using census tracts as your zones
  • I can use this new layer's ozone values to make the graph comparing those to household income.
  • Spatial Analyst tools > Zonal statistics as Table tool
  • Input raster or feature zone data: census_tracts_with_income; zone field: GEOID
  • Input value raster: AQ_TIN2Raster
  • Statistic type: Mean
  • Output table: census_tracts_with_income_ozone
  • Joined this table with census_tracts_with_income using GEOID field where join was based and exported it as permanent data layer census_tracts_with_income_ozone
  • Created graph of household_income (Y axis) vs ozone concentration (X axis) with trend line using attribute table from census_tracts_with_income_ozone
  • Created graph of ozone concentration (Y axis) vs elevation (X axis) from attribute table of air_quality_locations_ozone
  • Dissolve census_tract_with_income_ozone to county level
  • Data management > Dissolve tool
  • Input feature: census_tract_with_income
  • Output feature class: census_tracts_with income_ozone_dissolved
  • Dissolve field: block_id , which gives me county boundaries
  • Field: MEAN (statistics type – MEAN) If I do not specify a statistic type, it will complain the "statistic field is empty."

  • Conclusion
    According to my two graphs, I was right because the income trendline goes down to the right and the elevation trendline goes up to the right. I think the dataset and results could be improved by adding air quality monitoring stations in the less populated eastern half of the state.
    Final Results
    final results

      Arc Desktop, Pro and 3GIS Experience

      Tasks I have completed in a professional setting

      ArcGIS Pro Experience

      My current responsibilities include updating parcel data along transmission and fiber lines in counties within the footprint of the power company.

      Task
      Populating name, mailing address, location addres, municipality and county that are on the deed from parcel to parcel.

      Workflow
    • I set up parcel verification projects like this by adding the owner's name, mailling address and site address, municipality, county name, impacted alignment, impacted corrider, impacted vegetation, adjacent, line list, and line list number fields from the Impacted layer, which contains the existing parcels.
    • The county's parcel data viewer provides a map of the area and the PID number, owner's name, mailing address and site address (sans town, state and zip code).
    • Verifying Parcels
    • Once the attributes are populated I run the Select by Location tool (below) to find all parcels intersecting the red alignments line, and use the Sequential Numbering tool to generate a numerical list that represents each parcel. I run the Select by Location analysis against the yellow easement buffer and green vegetation buffer, as well, for transmission power lines. But there is no need to analyze those intersections for this line because it is underground fiber.
    • Verifying Parcels

      ArcMap Experience

      Terrain Analysis
      I worked with the transmission team my first 3 years at Burns & McDonnell, adding missing structures, updating installation years and mapping distribution along circuit lines, applying terrain analysis in GeoDigital and Google Earth.

      Task
    • Identify distribution wires from pole to pole, analyzing imagery to indicate whether to confirm the existence of distribution wires.
    • Google Earth was used where street view was available. GeoDigital was used to inspect poles that were not shown in Google Earth's Street View.
    • Inspecting Poles for Distribution
    • The pole in the above picture contains transmission, distribution, communication wires and a guy wire. The view direction is north
    • The three wires on top, extending east are transmission (Tx), which are always near the top of a transmission pole. The thin wire just below the Tx is a guy, connected to a stub pole to the west. Distribution wires (Dx) start at the crossarms below the guy wire, evidenced by the insulators, two of which are visible. Another guy wire is seen below the Dx, extending south. Below that the clamped wires are Dx, and the others in that area are for the light and traffic. The next light wire is a nuetral, which runs east and west. Communications wires, which are always below a neutral if the pole has a neutral, are next. Cable wires are usually dark and thick, as seen on this pole, accompanied by a black box, which is seen to the left. This is standard arrangement on a pole, with Tx, Dx, Communication, top to bottom.
    • For this pole I would enter "Y" in the Dx attribute and "Y" under joint use, since the poles contains both Dx and communications wires.

    • Engineering Drawing Interpretation
      Inspecting Poles for Distribution
    • The above plan shows part of a circuit with new (black circle), proposed (half filled circle), and existing structures. I manually added these as points into the geodatabase if the structures were missing and entered their installation year if existing.
    • Below are more examples of experience from professional projects. The work for all of these was done in ArcMap.

      Spatial Analysis
      Task

      Add new features from layers that contain features already in the SDE without adding the duplicate features.

      Workflow
    • Select by Location
    • Copy the SDE layers and load the copies into ArcMap.
    • Load the new layers into ArcMap.
    • Open Select By Location and choose the new features as the target layers. Only point features are selected so as to match the feature type of the source data.
    • Choose "intersect the source layer feature".
    • Select by Location
    • Click OK and only the duplicate features in the target layers will be selected.
    • Delete the selected features from each layer, then load the remaining features into the SDE.
    • Task
      Find fiber optic segments within 1000 feet of WOW cables.
      Workflow
    • Since we had no license for Spatial Analysis tools, I used the Near Tool, which required use of ArcMap Advanced. If Near was inaccessible, I could have established a buffer around each WOW line, then run a Spatial Join of fiber optic lines with the buffer.
    • Near Tool
    • Transmedia as Input features and WOW as Near features.
    • Provided the output in a spreadsheet with OLT Name, fiber segment and distance to the WOW cables, sorted by OLT Name

    • Data Management
      Task
      Edit the domain of a certain attribute in the SDE in order to provide options for values for users to enter.

      Workflow
    • Run the Add Coded Value To Domain tool once each for each value choice
    • Add Coded Value to Domain
    • Enter the value in the Code Description field so that it will show up in the drop down menu in the attribute table's field. Code Value and Code Description get the same text because the options the user sees should exactly match what they want to enter into the field.
    • Run the Assign Domain to Field tool

    • Task
      Format new utilities points and lines data to conform to utilities layers on the SDE to enable proper display on the online platform
      Workflow
    • Attribute values for specific fields in the each layer must be entered exactly as shown in this example for point features:
    • Utilities Points Required Formatting
    • Select data in the new data layer by municipality since all the new data was added for the same village
    • Add Utility Type to the new layer
    • Select By Attributes all features of specific utility type with this SQL statement: SELECT FROM (LAYER NAME) WHERE DESCRIPTION/ALIAS LIKE '%Storm%'
    • With all the Storm features selected, the value of "Storm sewer" can be Field Calculated into the Utility_Type field for the appropriate features
    • field calc appropriate values
    • Load the new features into the SDE: Right click the SDE layer in ArcCatalog, select Load, add the newly formatted layer, click Next x3, Finish
    • The new points and lines appear on the online platform
    • Online Platform displaying new features

      SQL Query
      Task
      Search the points layer in the SDE for all nonStreetlight utility point features in Yorkville that were uploaded by two employees
      Workflow
    • Open Select by Attributes from the attribute table of the Points SDE layer
    • Enter: MUNICIPALITY = 'Yorkville' AND FEATURE_TYPE <> 'Streetlight' AND (UPLOADER = 'Jane Doe' OR UPLOADER = 'John Doe')
    • Hit OK
    • 3GIS Experience

      Task
      Assign fiber segments to individual permits

      Workflow
    • Zoom in so 3GIS can display the features
    • Select Fiber Cable for Layer Type
    • Add Coded Value to Domain
    • In the search window, select Fiber Cable, FQNID, Equals, and enter the FQNID, which is the segment name
    • Select Fiber Cable in the dropdown so 3GIS knows what to search for
    • Click the Selection Polygon icon and draw a polygon around the features
    • Select the appropriate FQNID in the list that appears and click Associate
    • Task
      To design outside plant fiber optic cable sites with features, including the fiber cable and handholes, that will deliver 5G technology to businesses.

      Workflow
    • I begin by logging into 3GIS, then opening the construction product development map for the market I am working in, using my ArcGIS Online login credentials.
    • I then open the list of workorders that are open to me and activate the work order that is due the soonest.
    • Work begins by creating the following essential layers (circled): structures (e.g., handholes), fiber cable, span (the cable's conduit), fiber equipment, poles (if the site is aerial), slack loop, and splice closure.

    • Creating Features

      Fiber cable is selected in the image and its attributes are shown.

    • The endgame of creating an as-built site is to run a signal trace to track the fiber from the site back to its hub.
    • To start the signal trace, the splice closure must be the selected feature in the signal trace tab. Select the MPT fiber equipment (beginning point of the signal) in the dropdown fibercable menu on the left. Select the fiber it should be connected to. Enter 1-6 for the fiber range for the MPT in the left fiber range column and the range that is specified in the splicing redline document for this site in the right column. If the fiber range is not included in the list of ranges in that column, there is no connection and one must be created.

      To create a connection go to the Connection Manager tab. Enter the ranges and click the blue and red connection button in the lower left corner of the connection manager window.

      Signal Trace

      Run the signal trace to see if the connection now goes to the hub, or if it does not, where it stops. Do this by clicking the tower icon in the Signal Trace window (below). If it stops short of the hub, run connection manager again from where the signal stops. Do this until the signal is traced to the hub (see image below). Click on the Excel icon to download the signal trace report and upload it as part of the final report for the site.

      Signal Trace Complete

    Website Designed with HTML5, CSS and Bootstrap 4, originally in Notepad++, but most recently in Visual Studio by Doug Wolfinger. © 2025 Doug Wolfinger