Roadway History - gis-t.transportation.org

Roadway HistoryAutomating Quick Workflows for Simple Tracking

Florida Department of Transportation

⮚Kyle Purvis (Presenter)▪ Statistics Administrator for District One of the FDOT

• [email protected]

⮚Jozette Calvert (GIS Coordinator)▪ GIS Coordinator for District One of the FDOT


⮚Dylan Kanhai (Application Developer)▪ GIS Intern for District One of the FDOT


Introductions

mailto:[email protected]




◼ Simple and quick◼ Works well with smaller/job specific datasets◼ Removes GIS intimidation factor for non-technical users◼ Allows “Old School” spreadsheet/paper file users to get involved ◼ Establishes Official repository◼ Gives Employees new to the position access to the “Institution

Knowledge”◼ Users can visualize there data geographically and with other datasets

Overview


Roadway History Problem


The Solution


SharePoint Access FGDB

How did we get there?

• Quick workflow to stand up basic tracking of job specific data to be integrated into GIS

• Less than one hour if spread sheet is already implemented by user

• Allows users to edit records in form view

• Users do not need any type of GIS software or GIS experience to edit records

• Drag and drop file functionality for adding documents

• Record specific documents can be accessed from the map

• Entire process can be automated to reflect user changes

*or any spatially enable database


1. Create a SharePoint List to store records2. Create SharePoint Library to store documents

❖Important:▪ SharePoint list must contain a field to relate records to library documents (if you wish to

link records to documents)o Two basic options:

1. Establish file naming convention that relates documents to records2. User inputs unique file or folder name per record entered

SharePoint


1. Link Access to SharePoint list2. Create Table to Table query to export table to .mdb

• Note: Empty personal geodatabase (.mdb) should be created beforehand through ArcGIS desktop or catalog so you will a place to export the table to

▪ Advantage that can be leveraged during this export queryo Reformat data to meet GIS expectations✔String to Double or vice versa✔Rename fields✔ Join data from other Sharepoint Lists or databases✔Add calculated columns

◼ Advanced concepts using autoexec querieso Use Update Query to update SharePoint table with geoprocessing resultso Use calculated columns to update document library attributes

Note: Process can be automated by autoexec macro and powershell to keep .mdb table updated with new SharePoint entries and edits

Access


1. Basic GIS model or python script

FGDB

Note : Process can be automated through basic python script in scheduler


◼ Use the FGDB to create service and/or application of your choosing

Application

*Example uses basic web app builder in local portal


Built In link to Specific Document


Built in Link to All Documents by Year


◼ Hire a new intern

◼ Upload the rest of our County’s records within the District

◼ Consolidate “domain” categories for better queries

◼ Incorporate official memos that document historical changes made to LRS basemap

Looking to the Future History App


◼ User Permissions◼ “Domain” changes on the fly◼ Data backup◼ Data Validation◼ Attribute file folders and documents◼ Users can set email alerts of changes made◼ Automatic user tracking field for who made changes last◼ Automatic date fields for created and modified dates◼ Set up workflows for approvals, acknowledgments

Leverage Built-in SharePoint Features


Drainage Report Link Example


Drainage Links Straight to Report


Drainage Link to SharePoint for Editing


◼ Maintenance Agreements• Lighting, Mowing, Litter, Weed Control, Sweeping, etc. . . .

▪ Public Maintenance Requests▪ Environmental Permits▪ Drainage Reports▪ Traffic Operation Studies

• Speed Studies, Intersection Studies, Corridor Studies, TMC, etc. . . .

▪ Signals/Signal Systems▪ Material Facilities

• Aggregate Mines, Asphalt/Concrete Plants, Precast Prestress, and Testing Labs

Other Applications Utilizing this Workflow


Questions?