1

GIS Needs Assessment for the

City of Missoula

Prepared by Geodata Services, Inc.

June 6, 2016

2

 

 

Table of Contents 

GIS Needs Assessment Methods and Procedures .................................................................... 3 

Executive Summary ................................................................................................................. 3 

Detailed GIS Needs .................................................................................................................. 5 

User Interviews on GIS Data & Workflow Analysis .................................................................. 7 

User Questionnaire .......................................................................................................................... 7 

Department Interviews .................................................................................................................... 9 

Development Services ‐ Planning ...................................................................................................... 11 

Development Services ‐ Transportation ............................................................................................ 12 

Development Services ‐ Engineering ................................................................................................. 13 

Fire Department ................................................................................................................................. 14 

GIS Services (Information Technology) ............................................................................................. 15 

Missoula Redevelopment Agency ..................................................................................................... 18 

Parks and Recreation ......................................................................................................................... 19 

Police Department ............................................................................................................................. 21 

Public Works ....................................................................................................................................... 22 

Other Departments not Interviewed .............................................................................................. 23 

Other Organizations Collaborating with the City ............................................................................ 24 

Interaction with other Asset and Operations Software ................................................................... 24 

GIS Data Layer Inventory ....................................................................................................... 26 

External Data ................................................................................................................................. 28 

Land Base Sources .......................................................................................................................... 28 

Data and Workflows – Current Situation ........................................................................................ 29 

3

GIS Needs Assessment Methods and Procedures This document is a geographic information system (GIS) needs assessment for the City of Missoula. The Executive Summary follows with an overview of the GIS system in the City of Missoula and a summary of the GIS needs. This is followed by survey results from City GIS analyst staff on their best practices, experience and type of data storage. The report follows with details summarizing interviews for each department and a summary of hardware and software needs for enterprise database implementation. The needs assessment concludes with a summary of the data inventory of the map layers maintained by City departments and the current workflow for GIS layers between departments. GIS data was compiled from all identified City departments representing the data status during a two week period from late March to early April, 2016. The only known exception to this data collection was the developed park asset layers maintained by one of the divisions within Missoula Parks and Recreation. The goals of the project were:

● Assess the existing geospatial operations and needs for the City ● Document the spatial data layers currently being maintained by the City ● Assess the analog data and associated workflows that could logically be added to the

GIS ● Inventory and review the existing GIS data and prepare a citywide summary ● Identify a federated workflow to allow greater coordination and data sharing among City

GIS departments

A summary of the City of Missoula GIS hardware and software needs have been prepared by a collaborative partner, ASYNC GIS, Inc., and are available in a separate report.

Executive Summary The City of Missoula has maintained GIS programs in several departments for the last 15 years. Six years ago there were four GIS analysts maintaining the core data sets and maps that analysts handle today to support all departments. A staff half the size as it was moved from Public Works to Information Technology. Today they maintain parcels, easements, storm water and waste water systems, street centerline data, and other projects as assigned. The core GIS layers are currently maintained in a geodatabase using SDE and Microsoft SQL tables; layers are accessed by other departments through thin clients and workstations via virtual department servers. The City of Missoula IT Department is planning to implement a new server configuration, replacing the older SDE servers to direct connections to SQL GIS database and an enterprise

4

GIS database. The City is also planning on implementing Portal for ArcGIS to handle internal and external web services, web maps and GIS web applications. Approximately 14 additional City staff across six of the seven departments currently utilize GIS data and software to help perform their duties. Each staff member typically maintains their own datasets to support their department’s needs using a combination of common GIS file formats including file geodatabases, shapefiles, and CAD drawings. A dozen additional City departments were not specified to be interviewed or examined in detail for GIS needs. In most instances it was because they did not have GIS staff or workflows, and in a few instances, such as the health department, the GIS support is handled by Missoula County staff and departments. Although the City and County maintain separate staffs and operations, there are some overlap areas through various departments on the urban fringes. The City maintains some data officially outside the city boundaries. One issue complicating data sharing and collaboration is that Missoula County uses Novell spreadsheet software and the City of Missoula uses Microsoft Excel. Historically, some web map services were published by the City with ArcGIS Server, and more recently with Esri hosted ArcGIS Online. There are no two way data dependencies currently between departments, and there are no multi-user versioned geodatabases or GIS feature classes. The City of Missoula maintains an enterprise license agreement (ELA) with Esri that is used for core ArcGIS desktop GIS creation and analysis, but no ArcGIS extensions are currently used. Four separate software systems with GIS or mapping relationships and connections are in operation workflows with City departments:

● New World (utilized by the Police and Fire Department and 911) ● Automation (a program created by Accela, used by many departments for permitting,

licensing, code compliance, service requests, and asset management) ● BuildingEye, a web based program for displaying city permits and sewer connection

records (accessible to departments and the public) ● Data View (a no-longer functional ArcIMS based application that was used for address

locator functions as well as viewing sanitary sewer connection records and as-built drawings. An online map displays the as-builts.

A versioned enterprise database is needed, with feature level metadata activated to track user edits and date and time stamps will increase efficiency and collaboration city-wide. One example cited was preparation of an oversize trails and city asset map for offset printing for public distribution. The process resulted in a single point in time inter-departmental trail feature class. There are no workflows to continuously maintain modifications. A centralized versioned geodatabase would be required to handle multiple users and edits. Continuing education for all GIS analysts is needed, focusing on editing in versioned enterprise geodatabases, and using file geodatabases for all project work. There is a need to migrate the expanded core GIS data

5

layers that currently remain in shapefile format into the enterprise geodatabase. Additional continuing education for all City GIS staff on the use of domains and subtypes would increase data quality and accuracy and improve workflow efficiencies. There is also a need for geodatabase standards. We recommend the City consider adoption of the Esri local government data model along with evaluation of the National Emergency Number Association (NENA) data models for citywide address model, street centerline and administrative boundaries. Departments, consultants, citizens, students and other agencies have GIS workflows requiring access to active and historic geospatial data sets developed by the City. There are needs for scripted workflows to replicate core enterprise geodatabase content into formats that are maintained on public and internal data portals, deprecating existing FTP sites. We recommend open data provided in the public open data portal be created through scripts and provided in common formats such as file geodatabase, shapefiles, and comma delimited format (for point data). These scripts could be automated for regular updates on desired intervals. Governance rules and federated roles for edits and metadata updates, and exposure through portal tools will be required to accompany the geospatial data. Summary of needs:

Additional GIS analyst support staff Versioned geodatabase of extended core city-wide data layers federated between

departments Automated feature level metadata Easily accessible documentation (GIS Database Dictionary) of authoritative GIS

datasets Improved access to GIS data for City staff, contractors, and the public with an extended

suite of web based tools and dashboards

Continuing education and training Development of mobile data collection apps and workflows Map Control and positional accuracy Adoption of geodatabase standards and data models Regularly updated acquisition of city-wide high resolution aerial imagery and Lidar

Detailed GIS Needs Additional GIS analyst support staff Based on department interviews and workflows the need is high for additional GIS staff at the City of Missoula. This may take the form of additional analysts in a centralized management model or GIS service division. It may also take the form of additional GIS analysts in specific departments or some combination of the above. The departments where there appear to be the most need are Information Technology, Development Services, and Public Works.

6

Versioned geodatabase of extended core city-wide data layers federated between departments All authoritative GIS datasets identified in this needs assessment should be migrated to an expanded versioned enterprise database. This will provide a common authoritative source allowing staff and others to easily access the most current, authoritative GIS datasets. Automated feature level metadata All authoritative GIS datasets should include the following: Metadata, editor tracking with automatic data entry of last update and editor. All records carry sequential persistent unique identifier(s). Persistent unique feature identifiers expanded from storm water, sewer, parcel and easement feature classes to all enterprise City GIS layers, those that are applicable should also be cross referenced with Automation Easily accessible documentation (GIS Database Dictionary) of authoritative GIS datasets This need could be fulfilled by Esri Open data portal and internal City data portal established for internal GIS data. There will also be a need for a governance procedure and process for adding to and maintaining the enterprise data. The portal tools ideally should provide alternative ways to view data in chart and tabular form with limited query and filter capabilities and to obtain the data in multiple standard formats. The authoritative layers would be scripted for extraction from the enterprise geodatabase on a regular update schedule. Improved access to GIS data for City staff, contractors, and the public with an extended suite of web based tools and dashboards An expanded suite of web based mapping tools is needed for public access. If all of the enterprise geodatabases are also maintained as web services it would dramatically increase the usability of the geospatial resources by a much wider community of users through web based and mobile applications. The need includes story maps on key programs and processes and city success stories such as those projects with high rate of return examples. A companion portal controlled by department is needed for some data with privacy restrictions, such as vehicle collisions, crimes, and health at actual scale or resolution.

Continuing education and training There are two primary GIS training needs: 1) Continuing education for all City GIS analysts on versioned editing and transitioning from shapefile to enterprise geodatabase format; and 2) All staff training in light GIS data queries and analysis, web portal queries, using web based and mobile applications, and ArcGIS Maps for Microsoft Office. Development of mobile data collection apps and workflows Including offline mapping and data attribute collection on inexpensive tablets and smartphones. The need also includes what some call the “Internet of Things”, the sensors and automated vehicle systems (AVS) to add location attributes to regular automated operations. This includes

7

a wide range of systems for equipment based city maintenance tasks (equipment up/down, paint nozzle on/off, etc.) water, air quality and energy sensors, and law enforcement. Map Control and positional accuracy A master geodetic control point database, geographically spread through the City is needed. This would allow least squares adjustment of the parcel layer, as-built integration to match master geodetic control point database, and alignment of enterprise data layers. There is a need to explore state Montana Land Information Act grant funding to assist. Adoption of geodatabase standards and data models The two largest needs for standards and data models are exploring use of the NENA (NG911) data models for addressing, street centerline, and emergency response related administrative boundaries, and the Esri local government data model. The highest priority appears to be a standard address model. Coordination with the county and regional or statewide entities on this would be beneficial. The need to migrate data to the Esri local government data model increases efficiency and lowers workloads for GIS analysts as standardized web services and tools are available. Regularly updated acquisition of city-wide high resolution aerial imagery and lidar High resolution leaf-off 6 inch imagery with spatial precision control was last purchased by the City in 2006. Most large Montana cities typically follow a 3-5 year update cycle for image acquisitions. High resolution image acquisition is becoming more affordable and possibilities for cooperative bids with other western and central Montana cities, and Coeur D’Alene and Spokane exist. Lidar is less common in Montana but growing increasingly important and drone acquisition may be more realistic in selected city areas.

User Interviews on GIS Data & Workflow Analysis

User Questionnaire

Geodata Services conducted an initial survey of the City department staff to determine their current use of GIS. Seven staff members with significant GIS duties completed the surveys, representing the following departments: Fire, Development Services, Transportation and Planning, Information Technology, Montana Redevelopment Agency, and Parks and Recreation. These staff had GIS experience ranging from 5 to 25 years, with an average of 18 years. Their experience with specific GIS tools is shown in Figure 1. Most are familiar with the GIS software versions used for the last three years. Less than half the staff has experience with the newer Esri web based mapping tools. There is a need for GIS staff familiar with Python scripting and ModelBuilder for batch processing data and automating common procedures. This service can be obtained through contractors, however the City GIS operations are large enough to sustain an expanded staff capable of some development work to improve the efficiencies for all staff.

8

One staff that recently was hired does have some capability with Python scripting, but is only able to provide it for some specific duties in Development Services.

Figure 1 Survey results on staff experience

We asked staff how many core GIS layers they currently maintain. The answers ranged from 3 to 30. On average each staff maintains approximately 17 layers, but there is significant variance. Three of the staff maintain less than 6 layers. The majority of City staff utilizing GIS access a several core layers that are maintained on the SDE server. Only 14% typically work with these layers on a regular basis. The GIS data format they typically work with includes 43% with file geodatabases, 29% shapefiles, and 14% with Excel files. There is a need for all City staff to get comfortable and regularly work with either direct database sources and file geodatabases and migrate their shapefiles to a geodatabase format. There are many benefits to this including better performance, support for longer field names, attribute domains, and additional storage components to name a few. Other software the City staff regularly interface with their GIS workflows include several versions of CAD software including DWG TrueView 2015, AutoCAD, AutoDesk Map 3D. The Transportation division of Development Services (MPO) relies heavily on TransCAD, which works with ArcGIS for Desktop and data stored in Microsoft Access. The Urban Forester uses

9

Tree Works, a 3rd party software package that is integrated with ArcGIS Desktop and stores data in file geodatabase format. One of the goals of the City IT staff is to support a federated data model stored on a versioned enterprise geodatabase. An expanded set of core layers that each department maintains will be accessible to other departments for workflows that do not currently exist. We recommend that this enterprise geodatabase be structured for versioning and where appropriate simultaneous edits by users. Access and structure for this will likely be controlled by the federated end user, but other models for governance should be explored in future stages of GIS development following this needs assessment. Current workflows have been developed to avoid simultaneous editing by dividing responsibilities. Approximately 17% of respondents indicated they have needs for simultaneous editing and versioned geodatabases, 83% said they do not. There will likely be increased need for this to achieve greater efficiencies, and as more sharing and workflows develop when more data sharing becomes available between departments. We asked respondents if they maintained their own custom base map for their operations and 43% said they did, 57% said they did not or simply used the Esri base maps. In follow up interviews and data reviews, GIS users in the Parks and Recreation department indicated a need for a reinstall and configuration and performance check to enable access to Esri base map data.

Department Interviews As part of the needs assessment Geodata Services also conducted interviews with the following six departments as identified by the City IT Director. The interviews ranged from one to two hours. We have summarized the key workflows and data needs for each of the six departments we interviewed Departments that do not currently use GIS or expect future GIS data or workflows were not interviewed during this needs assessment. GIS web services and new tools targeted at non-traditional users are starting to be deployed by the City of Missoula GIS staff in IT. There is a large need for more web services and portal content, and recommendations on these needs were addressed in the executive summary, and detailed needs assessment sections and in individual department interview summaries. There is significant potential for additional City staff to make use of light GIS capability through Esri portal and web services, ArcGIS Maps for Office, and published maps and apps. This is true of all departments using GIS presently and many who are not. There is also significant potential for administrators to increase their efficiency in planning and administrative tasks with access to the geospatial web based tools.

10

Table 1 Participating Staff in GIS Interviews

NAME DEPARTMENT POSITION GIS USAGE AUTOMATION

Don Verrue Development Services Assistant Director of Development Services Viewer

Doug Harby Development Services Construction Projects Manager Viewer

Jessica Morriss Development Services Transportation Planning Manager Viewer

Kevin Slovarp Development Services City Engineer Viewer

Laval Means Development Services Planning Services Manager Viewer

Mike Haynes Development Services Director of Development Services Viewer

Garin Wally Development Services - Planning GIS Analyst/Planner Analyst

Aaron Wilson

Development Services - Transportation Planning Planner II Analyst

David Gray

Development Services - Transportation Planning Planner III Analyst

Jason Diehl Fire Department Fire Chief Viewer

Ken Wickman Police Department IT and GIS Analyst

John Pilsworth Fire Department Volunteer? Analyst

Christy Weigand GIS Services - IT GIS Coordinator Analyst

Eric Andersen GIS Services - IT Senior GIS Analyst Analyst

Cage Urquhart GIS Services - IT Senior Network Systems Administrator

Network Administrator

Carl Horton Information Technologies IT Director Viewer

Tod Gass

Missoula Redevelopment Agency

GIS Analyst/ Redevelopment Project Coordinator Analyst

David Selvage Parks and Recreation - Administration

Parks Services and Systems Manager Analyst

Only for public requests

Morgan Valliant

Parks and Recreation - Conservation Lands Management Conservation Lands Manager Analyst

Chris Carlson Parks and Recreation Trails & Conservation

Recreation specialist and GIS Analyst Analyst

11

Development Services - Planning

The Planning Division of Development Services currently has one planner with GIS analyst skills who spends approximately 80% of their total time doing GIS analysis functions. These include Python and modeling capabilities, but those are limited to a portion of Development Services overall tasks. Authoritative GIS datasets are maintained in two functional areas, planning and land use. They all utilize the GIS department ownership and easement layer stored in SDE enabled geodatabases and combine that with a variety of layers they maintain for project work. They commonly work with shapefiles and many stand alone project data sets. There is a need for and expressed desire for more centralized enterprise data sets and more efficient workflows to avoid some of the duplication. They also overlap and have shapefile duplication with the trails and conservation lands maintained by the Parks and Recreation staff. Master files are accessed through ArcGIS MXD files, and when virtual servers and mapped drive letter designations change it breaks the data links in the mxd files, causing inefficient workflows to recreate data links. The Planning Division of Development Services maintains the zoning and land use maps and other data sets associated with planning and development such as FEMA floodplain mapping program maps. They also conduct annual GIS projects dealing with growth in the Missoula area. This includes the Urban Fringe Development Area (UFDA) maps and planning looking at growth areas on the urban fringe. They also do an annual inventory and analysis of “entitled lots”, parcels with higher potential future growth rates and lots that have been platted but haven’t been built or undeveloped planned areas, old subdivisions that were improved or developed really slowly over multiple years and phases. Some are more than 20 years old, with thousands of subdivisions that were approved in the 1990s and 2000s. Current growth policy encourages development in the core and the urban fringe that are experiencing development

Chris Boza Parks and Recreation - Urban Forestry Urban Forester

Analyst & Tree Works

Amy Dennis Public Works

Admin. Services Manager/Project Coordination Viewer Data Entry

Ashley Strayer Public Works Administrative Secretary Viewer Data Entry

Brian Hensel Public Works Superintendent, Streets Viewer

Carla Krause Public Works Public Works Advisor Viewer

John Wilson Public Works Public Works Director Viewer

Lori Hart Public Works Administrative Assistant - Public Works Viewer Data Entry

Pat Brook Public Works Collections Supervisor Viewer

Wayne Gravatt Public Works Traffic Services Coordinator Viewer

12

pressures. Where entitled lots are turning into actual development and for potential annexation areas, planners and GIS analysts are monitoring building permits to track the entitlement lots. GIS analyst identified three to five additional staff that may benefit from training in ArcGIS Pro and web based light GIS analysis tools.

Development Services - Transportation

Transportation planning in the Metropolitan Planning Area (MPO) includes two planners with GIS analyst skills who spend approximately 40% of their time doing GIS analysis functions. The primary planning technology tool they use and maintain is TransCAD, which utilizes CAD and GIS Shapefiles and includes many Microsoft Access tables for attributes. They run the TransCAD regional model, which provides air quality, C02, and other outputs for the MPO. There is also a TransCAD micro model which provides similar outputs for a smaller geographic area that is not implemented. Units of analysis are Traffic Analysis Zones, which are built from census block layers. The MPO is responsible for running the TransCAD model following every long range growth plan update (every five years) and for incremental runs for specific projects, such as a bridge reconstruction. The transportation staff with GIS experience have the second highest magnitude of interaction with other departments, next only to the core GIS IT staff. There is a need for interdepartmental collaboration on the street centerline and transportation asset geodatabase model and feature design. The transportation planners have just completed a local functional classification system with implications on future GIS data collected by Public Works and Engineering such as sanding, plowing, sidewalk installs, etc. All of these assets are important to Transportation and the models they support. Transportation GIS analysts said that collaborative agreements and standardized data models fitting multiple agency needs would be beneficial. There are extensive data inputs and outputs of the TransCAD model: Component inputs include: a level of service assessment, American Community Survey census data, urban fringe data analysis data, historical growth rates, transit network metrics including accident statistics and peak hours, number of lanes and speed limits, bike and pedestrian counts, road condition, land use classes, employment, peak hour metrics, and crash data (can’t release at original detailed location). The Summary File Outputs from the TransCAD model include traffic counts, transit metrics and congested vehicle hours. Transportation GIS staff utilize most of the core GIS layers maintained by the GIS IT analysts, and spend considerable time processing data from others into a format that they can utilize directly. For example 911 response times are not always realistic for transportation modeling. They are limited by the lack of some data layers that are not currently being collected or are only partially mapped, such as sidewalk data, signage, bike lane designation, on-street parking marking, pavement inventory, road and sidewalk condition, etc.

13

TransCAD will not run directly off an ESRI enterprise geodatabase. It is a stand alone program specialized for transportation planning. The GIS staff will benefit from an enterprise geodatabase for their extensive sourcing needs, but the actual TransCAD runs will remain separate. All model runs out of the NAS storage physically housed in the transportation office, and backups are to a disc attached to the NAS with intermittent backups. They expressed a need for a better back up system. The scratch geodatabase for a given run is 10 gb and sometimes they conduct four runs at the same time. Longer term storage is needed for all of the long range planning runs, McLay’s bridge, Higgins and Madison reconstruction runs (e.g. 2010 and 2040 run, 2010 & 2040 partial closure, 2010 & 2040 full closure). These all have to be archived for the record. They average 30 runs during a year. Further discussion and performance testing will be required and more detailed discussion of how the TransCAD runs are run and stored.

Development Services - Engineering

We interviewed the City Engineer along with other Development Services and Public Works staff. They enter data in Automation but do not maintain any GIS data at present. There is a need to provide additional GIS support for the engineering department and begin additional field collection efforts on assets. The core layers and assets and their associated attributes were defined many years ago, and are included in the data matrix. There has not been any GIS staff in engineering since the reorganization several years ago, and no maintenance and development of the assets are currently done by the engineering department. They provide updates to GIS IT on marked up maps or work orders. The department expressed a priority interest in developing an asphalt assessment map GIS application. They need it to be on a real time schedule, sometimes the data attributes are out of date and incorrect when the GIS Coordinator does not receive the data in a timely manner. It costs $20/square foot to replace typical street pavement, so a 100 foot trench can be costly if mistakes are made. High resolution imagery is also a priority. For streets and most public works, having six inch, high resolution imagery is important, and saves a lot of time in field mapping. Leaf off imagery is essential, in order to be able to see through the tree canopy of mature deciduous trees. The 2014 imagery was not good enough. The 2006 data was sharper. Some staff mentioned that the data was subsampled (possibly Mr Sid compression) which may have created some use issues. Purchasing citywide 6 inch imagery on a regular schedule is a preferred need. The staff mentioned a three year interval preferred, ten year cycle may be expected. There was significant need mentioned for bringing of transportation infrastructure and other assets including paint lines, striping, overlays, chip seals, pavement management and other operations to track assets and report to council and document the need for more funding when needed. The service vehicles such as snowplows are GPS enabled, but are not equipped with

14

automated vehicle collection and other AVL software and sensors, e.g. sensors to track blade, brush or plow up/blade/brush or plow down, or paint on/paint off by location. There is much potential for inter departmental access between engineering and other departments with data flowing in both directions. For example the transportation pavement painting, no parking areas, etc. are used by transportation in their planning. The larger urban forest shade trees can extend the replacement and repair time for asphalt by eight years. The current street centerline road layer has not been networked, so routing, tracking and other related functions are not available. This did not appear to be of concern to Engineering or other departments, since the primary interest is in tracking and analyzing GIS data rather than doing hydrologic modeling, outage tracking, etc. There is a reverse 911 ability available for public notices for public health or safety, and it does not rely on the transportation network.

Fire Department

The Fire Department GIS work was being maintained by an experienced retired GIS Analyst working as a volunteer, volunteering three to four hours per day for the last eight years. The department started with AutoCAD and New World software. The geospatial data are currently maintained in ArcGIS as shapefiles. The analyst regularly coordinates with the County 911 GIS analyst. The Fire Department does not do very much GIS analysis, they mostly use the software for collecting and displaying data. New World is the program that is used by the 911 center and by the police and fire departments. It is run on an independent server and runs GIS and SDE, built and maintained by the New World consultants. In the spring, 2016 the City/County brought up a new server in testing and development mode, and plan to move it into production in the fall, 2016. There is a need to coordinate further on this so that the City geodatabase design takes the 911 and NG 911 requirements into account. The Fire Department geospatial data layers that are maintained include street names, hydrants, 311 response area administrative boundaries, evacuation zone maps, road access, and city base map including building type (condo, apartment, etc.) and map grid. Street Names - These are local labeling and minor modifications to the City master road centerline data. The analyst prints Esri map books for the fire response vehicles and wants the most accurate information available. A need was expressed for additional customized data entered by firemen in an editable web map be collected to improve the information on the map book base map. Hydrants - There are approximately 1,200 hydrants maintained by Mountain Water Company, and another 400 from other sources such as Upper Grant Creek, the University facilities and student housing, El Mar Estates, and the Ranch Club. Mountain Water has provided regular data updates, but currently it is unclear if that will continue with ownership changes of the company. Mountain Water provides flow rates with the shapefiles they provide.

15

CityBase- This includes condos, apartment buildings, community anchor institutions and a basemap built on the City IT GIS basemap. 311 Polygon – Response area within the City to guide rural fire departments on where to respond in the City. There is a companion file that does the opposite for the City fire to respond in the county. Evacuation zones- Firemen on light duty have been preparing these. The Rattlesnake has been completed and Grant Creek was being worked on when we conducted the interview. These include drop points. Road access - The Fire Department analyst reports master file edits that are required to the IT GIS staff to do the master update. The Fire Department analyst also does custom labeling on the map books that he prepares. There is a need to provide additional training in ArcGIS annotation, Maplex label adjustment and file geodatabase features for the fire dept analyst to make the base map labeling more efficient and enable persistent updates that are independent of the mxd file. This would also allow incorporation into base maps prepared by other departments such as police and other first responders beyond the Fire Department. There is also potential to incorporate some of the pre-plan documents that are carried in the fire engines with additional response scenarios. This needs further discussion in the next phases to detail the possible inclusions.

GIS Services (Information Technology)

The City GIS Information Technology (IT) staff includes two full time GIS analysts with many years’ experience. They formerly worked in Public Works. In reorganization several years ago they were assigned to IT. They each have distinct and separate primary duties, with one handling the annexation, ownership and easement GIS data and the other handling public works data for storm and waste water and associated assets. They both are familiar with each other’s workflows and procedures and have administrative privileges to each other’s tasks when necessary. They also maintain key layers derived from or related to their primary responsibilities. These are identified by staff position in Table 1. The GIS Coordinator maintains and develops the waste water and storm water systems. These are high liability assets, and include maintenance components and several types of asset characteristic and features such as sewer lines and STEP tanks. The sources for this data are as built engineering drawings stored as pdf documents on the City FTP system. More detail on these layers is provided in the Public Works section. Street centerline data are maintained by the senior GIS analyst. Updates to the transportation layer and road centerlines resulting from ownership and easement modifications are coordinated between staff. Neither the street centerline nor storm or waste water line feature class layers are networked for routing or outage tracking. There is a need for interdepartmental

16

collaboration on the street centerline and transportation asset geodatabase model and feature design. This is also covered in the Development Services-Transportation section. The implications for this go beyond the City of Missoula. The Next Generation 911 (NG911) will be implemented nationally within two years. It is heavily dependent on GIS and will require GIS workflow changes. We conducted a short interview with the Missoula County GIS Coordinator and the 911 GIS Analyst. They indicated they were prepared for the transition but national standards are still being developed and there will likely be modifications in data structures and workflows as the process evolves. There is a need for the City and County to have further in-depth discussions on this topic, particularly on adoption of the National Emergency Number Association (NENA) National address model and the common street centerline geodatabase and feature data set. It is likely that an additional GIS Analyst will be required focusing primarily on the address model and street centerline maintenance. The senior GIS analyst also updates the administrative boundaries such as Neighborhood and Ward boundaries and city limits and annexation areas derived from council actions and typically built from the parcel framework. The senior GIS analyst also maintains geographic features for all documents that do not convey property rights. They also handle one-off requests from various City departments. Other special projects are handled by the GIS coordinator, for example a current project looked at community anchor institutions and major retail zones and calculated square footage combined with Montana Department of Revenue parcel based data for fire and safety concerns to come up with fire safety zones. The GIS coordinator also has duties relating to Automation. Both core IT GIS staff provide limited GIS support for other departments on a request basis but do not have formal maintenance responsibilities. The parcel layer, maintained by the GIS Analyst, originated from the statewide Montana Department of Revenue cadastral parcel layer and has been maintained by the City ever since. The parcel layer has varying degrees of geographic location accuracy within different parts of the City. Staff indicated that in some parts of town, the parcel data is mismatched by factors exceeding the width or length of an entire parcel. No City staff mentioned a master geodetic control point layer maintained by the City. There is a need to develop this layer and use it to maintain the parcel ownership fabric, and to assist in leveraging as built CAD drawing and digital submissions. Further research and metadata process searches are recommended to determine and preserve the source of geodetic control used in the 2006 and 2014 high resolution image acquisition and georeferencing. These control points, combined with other geodetic control could be used to spatially adjust the parcels and provide a framework and foundation for utilizing the parcel fabric tools provided in the Esri local government data model. This would be a labor intensive task. Given the workload of existing staff it is unlikely it would be accomplished without additional new staff hires.

17

We also recommend coordination with the Montana state stewards for geodetic control at the Montana State Library and the CATSPAW, which provides control for NAIP imagery updates and provides the geodetic control for the Montana Department of Revenue statewide parcel layer for property taxation. Even though City agencies do not prefer this version of the parcel layer, there would be value in matching parcel boundaries for GIS overlays and regular updates via geoenrichment of selected DOR attributes into the City parcel data and assets. Measurements from as-builts and contractor submissions, primarily in CAD formats and CAD based drawings are used by the GIS Coordinator for the sewer and waste water infrastructure mapping, and by the senior GIS analyst for modifications to the parcel layer. There are periodic submittals of the data to the Missoula County GIS staff that process the City updates and incorporate those with the county parcel updates and provide those to the Assessor’s office and the Montana Department of Revenue. The typical workflow when there are annexations or new developments includes the following steps:

1. CAD input is received from the developers, consultants and other contractors. 2. The GIS analyst initially enters the records from the CAD submittals via address

geocode and georeferencing from information on the drawing that references known locations from other GIS layers parcels, street centerline, easement, PLSS, etc.

3. The CAD submittals are viewed through Trueview CAD viewing software and saved as PDF and DWG file formats.

4. After the initial review in a subsequent step, the analyst updates the parcel or easement layer in the GIS using the actual survey and engineering measurements from the drawing.

When City utility inspectors do on-site inspections they typically prepare sketches which the analyst digitizes in the GIS and posts results to the City FTP site for the inspectors to check. There are four additional steps on the Automation data entry side in addition to the GIS workflow. There is a need in the strategic and implementation phase to look at more efficient workflows to improve the efficiency of this process. The administrative boundaries and easements are maintained by the GIS analyst. Boundaries require Council action. The workflow involves using the parcel source to represent the legal boundaries, typically for MRA projects, neighborhoods and wards and also Missoula County recorded resolutions affecting the City. The analyst follows the initial data entry with a quality control/quality assurance check and confirmation. Easements are also handled by the GIS Analyst. They are created by type, e.g. sewer main. Approximately 300 to 400 of a total 4,600 maintained by the City Clerk are currently with geographic features, going back to 1982. Title companies are the typical source for source documents relating to easements that list the City or County by name. Missoula County currently does not maintain easements in GIS format.

18

The City has an administrative rule (Administrative Rule number 646) in place requiring “Released for Construction” submittals by all project coordinators for subdivision and sanitary and storm sewer extension projects. There is a need to discuss minor modifications of this administrative rule: to replace the term “geocoding” to “georeferencing”; to add other submission formats such as shapefiles or file geodatabases (though CAD are still the most common systems for engineering firms); to require that the submittals be in a global datum rather than local and in the Montana State Plane NAD83 projected coordinate system with a World file attached to the CAD file; to submit their control points with latitude, longitude coordinates with floating point entries with at least 6 levels of precision. This would replace the option to submit a drawing with local coordinates and “enough adequate information in the vicinity of the project to accurately locate it”. Both staff process sidewalk data and an incomplete data set of signage and traffic signals. There are four to five different sidewalk data sources, since some are private and others are installed by the City. MRA handles these inside their jurisdictional areas. There is no standardized workflow to deal with these assets. There is significant need for publishing web services with the core GIS layers maintained by the City IT GIS staff. This, accompanied by continuing education for all City staff that require map data on the light GIS tools would decrease the request queue for the City GIS staff and serve the users’ needs with increased capability. The GIS coordinator recommended some Finance Department staff could benefit from using the ArcGIS Maps for Office tools in Excel spreadsheets, for instance. They could also use the Geoforms and reporting tools for infrastructure reporting.

Missoula Redevelopment Agency

The Missoula Redevelopment Agency (MRA) has one GIS analyst with many year’s experience. Their primary software has included AutoCAD and Esri ArcGIS, and the Esri software has been used increasingly in recent years. The primary authoritative GIS dataset MRA currently maintains is the Urban Renewal District (URD) boundaries. These are based on the City GIS ownership layers and parcels and right of way is preferred as a boundary when it is available. The boundaries of the URDs do not split parcels whenever possible. In addition to parcels, the boundaries are also formed from roads, right of ways, rivers and railroad tracks. GIS files that MRA works with are usually shapefiles. MRA prepares blight studies. These take three to six months to complete and are very thorough. They are based on state statutes. Topics of blight studies include public safety, police and fire, public health, status of buildings, tax base, and zoning inconsistencies. MRA coordinates regularly with the Montana Department of Revenue on tax increment districts and look up geocodes to make sure taxes are paid and the status of taxation. They receive a large data file from the county to look up geocodes. There might be a more efficient way to accomplish this through a published web service. Historic data is available since 1997.

19

MRA also does custom base maps and occasionally uses older DWG files from Autocad for cartographic effects and preferable fonts, and for street names. Like the Fire Department, there may be some value in training for Maplex and other smart labeling techniques now available in ArcGIS. The GIS analyst exports data to KMZ (Google format) for the MRA administrative staff to view on Google Earth. The opportunity to supplement this with the richer content and maps and apps in ArcGIS Online will enhance this current workflow.

Parks and Recreation

The Parks and Recreation Department has four staff that work with GIS and desktop ArcGIS. The Urban Forester uses Tree Works with ArcGIS integrated into the core software and does not appear to use the GIS extensively outside this program. The Developed Parks staff director maintains assets in the GIS. Two staff in Conservation Lands and Trails use the GIS regularly. One of them has more in depth experience with GIS, and is one of the few staff using file geodatabase structures. The Parks office is physically separated from the City Hall and has some issues running the GIS, requiring an examination of the latest GIS install. They work on thin clients and workstation clients. Connections issues and intermittent connections occur and result in some GIS data being developed and maintained locally. The ArcGIS desktop maps are authored with MXD files with pointers to the data sources. A common problem in Parks that also was mentioned in most other departmental interviews was broken links when remote drives changed names or letters. This problem can be mitigated by using relative links functions with ArcGIS, and storing data in standard file geodatabase formats or enterprise databases with consistent structure. Imagery base maps are of particular interest to Parks staff. Several staff mentioned the usefulness of Bing image maps that had been deprecated last year (actually the licensing agreement between Esri and Microsoft was modified and the Bing imagery became available only through an additional fee). The Esri image base map is high resolution anywhere in North America and exceeds the resolution of NAIP imagery obtained by the state for multiple years. There is a need for additional training so staff can access supplemental image web services. This department has one of the busiest call-in public comments traffic in the City. These are the only items that are entered in Automation. Previous attempts to adopt Automation in the past did not appear to meet the needs of the Parks staff so they maintain their asset attributes locally in shapefiles, spreadsheets and other local databases. We were unable to obtain GIS data for developed parks, but did get a list of layers that are tracked. The developed park layers include major features, such as ball fields, sport courts, etc.

20

They do not maintain attribute data on park assets such as play equipment. There is a potential acquisition of 150 acres from Five Valleys Land Trust at the Marshall Mountain Ski Area which would serve as a regional park used for fee based events. There is no GIS mapping of the site or facilities at present. GPS units are in all snow removal and mowing equipment and other vehicle assets. There is no AVL software running with these to provide additional details of operation, such as when the snowplow blade is in operating position. Customer Service Requests (CSR) are entered in Automation by the Park Operations staff in the administrative building. We reviewed the conservation lands, trails and urban forest GIS data. The trail network, park lands, open space and related lands are comprehensively mapped and attributed by type and several other characteristics. Parks and Recreation has the lead in creating new trail features, but other departments have projects relating to trails administrative boundaries, and also contribute GIS data, particularly the Development Services GIS staff in planning and transportation. Having a centralized enterprise database of these features should benefit the overall workflow and minimize duplication and non-intentional conflicting version updates, or duplication of efforts. There have been web services published in the last few years with the ArcGIS Server, but not in a comprehensive and systematic way. They were primarily done as proof of concept and pilot projects. The primary method of providing the public with city recreation assets is the publication of a wall map with lands, administrative boundaries, trails, parks and many other features on a wall map (D size). Types of use, amenities, and services are shown in a matrix in the sidebar of the map. This inventory and attribution was not derived from the GIS data, it was created in a spreadsheet table format and designed with graphic software for the wall map. Converting this to a GIS database and enabled through pop-ups would be desirable, and relatively easy to complete. There is significant need for web services of these layers to supplement the static printed map source. Web accessible maps and mobile data collection tools for Parks administrative and customer service staff should benefit maintenance of the core layers that they maintain. The department has a limited number of dedicated GPS field collection devices, one resource grade collector and a couple of recreation grade collectors. Keeping those in sequence with the ArcGIS updates has been problematic, and examples were given where standard workflows for field collection were interrupted. There is a significant need in this department (as in Public Works) for training and implementation of the Esri mobile collection tools Collector, Survey 123, etc. using common smartphone and tablet devices to extend the capabilities for field collection. This department has converted more asset data to GIS than many other departments. These include lighting, signage and overall management activities which vary from year to year and include weed sprayed areas, forest thinning, and irrigation systems. Among other uses, they leverage these data for presentations to City Council. There was desired interest in geocoding park access permits. Neighborhood commons areas are mapped if they connect with public land. There was also interest in mapping the new regional park facilities in more detail, there

21

are currently no maps of the development and they did not mention any as built drawings or CAD files submitted by contractors. The Developed Facilities staff had difficulty using the IT GIS core layers in some portions of the City where the survey control is problematic and the parcel lines, street centerline and right of ways don’t line up with the imagery and other referenced features. This is less important for the conservation and trails data but particularly affects the park assets that fall within thin strip areas such as medians and other narrow right of ways. This will persist after a conversion to a central enterprise database for the core layers such as ownership and easements and right of ways. There is a need for additional adjustments in the parcel fabric, geographic coordinate database system (GCDB) adjustments of the public land survey to additional survey control, to address these issues, followed by best fit adjustments to the map features that rely upon them. This would be a major task and would require considerable time and expense to complete. As a result there is a need for developing persistent unique identifiers for park assets. In other sections of this report we have recommended crosswalk unique identifiers between systems, in this case between the GIS features and Automation. Overcoming reluctance for developed park asset managers to use Automation and addressing the underlying reasons for this when possible will be necessary for successfully implementing this procedure.

Police Department

The Police Department has one staff with GIS experience who primarily works with the 911 data coordinator. They work with the core layers maintained by the City GIS staff, but do not develop authoritative GIS layers of their own. They work with New World software which is also used by the Fire Department and the 911 operations run by the County. Previous releases of this software did not include links to ArcGIS. This may change in the future with a development server set up in the spring allowing version 11 of New World to be installed, with an embedded version of ArcGIS. The deployment in an operational setting is scheduled for the fall, 2016. New World is also the program that 911 uses for routing. Accident data is recorded to the nearest intersection, but crime data is not mapped systematically. This may change with the addition of GIS to New World. Intersection representation of data such as crime or accidents is useful for delivery to the public with some level of generalization for privacy protection. For internal analysis, address level collection, or utilizing the GPS in the police cars would be more accurate and useful for geospatial analysis. The police are interested in acquiring an accurate position for all public and private surveillance cameras downtown and in other areas of town with higher user activity. They are also interested in attributing this data with field of view and developing applications to analyze surveillance footage after a crime.

22

Next Gen 911 is very dependent on GIS capabilities. There will be significant interaction required between law enforcement and GIS analysts as this moves forward, particularly relating to address data model applications, street centerlines and administrative boundaries.

Public Works

Public Works does not currently maintain any core authoritative GIS layers and relies on IT GIS staff for operational mapping. The GIS Coordinator maintains storm water and sewer and the street centerline file and the Senior GIS analyst maintains ownership and easements. The main source for infrastructure data updates are “as built” drawings of new construction or reconstruction projects performed by private citizens and developers. A program called Data View was created by a former staff software developer approximately 14 years ago and was used to link the parcel ownership data to the waste water system. It has recently been disabled and its two major functions replaced by Building Eye and an online Sanitary and Storm Map. Staff desire an application where both functions are located in one place, and ArcGIS online and Portal provide the opportunity to modernize the functionality provided in the past by Data View. Further assessment, use case development and design discussions could determine whether existing applications would suffice, or whether some customization might be desired. Public Works has a new director and has retained a long term employee that is retired but consulting part time for the department. This is a critical position as the department is reconstituted and provisioned. She will also provide invaluable assistance in the strategic and operational phases of deploying an enterprise GIS system with significant institutional knowledge. Although Public Works staff do not directly enter data into the GIS, they do provide data to the GIS Coordinator related to asset attributes. This data is entered into the GIS and then synced to Automation. In addition, public works staff maintain work orders in Automation that serve as a record of maintenance to the City’s infrastructure. A strong need was identified, particularly with storm water, for staff in the field to be able to view the maps and edit and make notation while on site. Public Works, like almost all other staff, indicated that they only use the City parcel data rather than the Montana Department of Revenue version of the parcels. Updates are more timely in the City version. As mentioned previously, the data is periodically provided to the County and then subsequently to the state, but further exploration is needed to see how the County processes the data, how it compares and resolves differences and what other workflows they apply. This is not just a one way issue. The DOR maintains many more fields and related tables than the City does in their Orion database. There are use cases and needs to process this more extensive data tied to parcels for planning and other functions. If the parcels are out of sequence it can cause problems for City staff as well.

23

Sanitary sewer infrastructure was typically created from as-built drawings and records and entered in coordination with the City parcel layer. Sewer infrastructure is often field-verified. They are also looking at equipping all the maintenance vehicles with GPS receivers. There is a need in this instance for resource grade GPS (sub-meter or better). There is one vehicle that is dedicated to video sewer inspections. Existing videos are stored on DVD until the next follow up inspection. There is a regular need for service operations, such as jetting a sewer line to be logged by line segment in the asset inventory. The storm water assets were typically created on the high resolution 6 inch 2006 image base. The storm water features are not field verified as often as the sanitary sewer infrastructure. The parcel layer has varying degrees of geographic location accuracy within different parts of the City. In some parts of town, the parcel data is mismatched by factors exceeding the width or length of an entire parcel. There is currently an impervious area study underway, an essential prerequisite for creating a storm water utility for rate setting. The street asset operations have little or no GIS inputs presently but there is great potential in the future. For example, potholes are not entered into Automation. There is text based reporting mechanism on the City web page. The report a pothole from an outside source is routed to public works administrative staff. They don’t have the capability to report back when the pothole is fixed. This could all be automated with an out of the box crowdsourcing application from Esri to report potholes, with AVL and GPS devices on the vehicles to automatically log the fix, and provide public notification of the fix. It would allow more proactive planning and budgeting and link with other pavement management operations. The same holds true for snow plowing and painting linear striping, miles striped, gallons used, etc. We conducted an interview with the City of Bozeman Public Works Department who implemented this technology. A field trip to visit with them and view their operations and equipment would be very beneficial. The sign assets are another opportunity. These are not as conducive to automated AVL technology, but the Esri mobile collection tools paired with smartphones and tablets could provide a workflow that would be successful in maintaining the inventory. Several other assets were also mentioned as a need for better geographic tracking to complement Automation. These include sidewalk assets, handicapped parking, and traffic calming facilities.

Other Departments not Interviewed

The Parking Commission and other City Departments would benefit from a comprehensive parking inventory maintained as a series of GIS layers (lease areas, parking structures, and public parking spaces).

24

● Animal Control ● Cemetery ● City Attorney ● City Clerk ● Grants ● Finance ● Health Department ● Historic Places Commission ● Human Resources ● Mayor ● Municipal Court ● Parking Commission

Other Organizations Collaborating with the City

Missoula Downtown Association Mountain Line Montana Community Foundation Missoula Public Library

Interaction with other Asset and Operations Software

Automation

The City recently completed a conversion of Automation from a system hosted and run by the State of Montana (STISD) to be hosted and run locally by the City. They also upgraded to version 8.0. Before Automation was adopted, the response to requests for building permits was 30 days or more, now it is down to 2-3 days.. Automation has a component that allows the mapping of database fields between GIS and Automation. Once these associations are mapped the software is able to sync data from GIS to Automation. Unique identifiers are used as primary database fields linking the two systems, with the identifier primary key shared between the GIS and Automation. The format is a 2 digit year, a hyphen, a variable length alphanumeric function identifier code, followed by a sequential integer. Project numbers are based on the as-built documents and project number. Data is entered in GIS and synced to Automation where it is available for users to create work orders, preventive maintenance schedules, service requests, condition assessments, etc. Public Works - Waste Water Division The treatment plant maintains more maintenance data than what is entered into Automation. Typically, the information that gets entered into Automation are mainline work orders resulting

25

from preventative maintenance schedules or service request calls from customers. Preventative maintenance schedules generate work orders and staff completes copies of the paper work orders in the field. Paper copies are brought back to the office for office staff to enter. Staff use paper maps to find assets. STEP Tank work orders resulting from customer service request calls are also entered. These are entered after the work has been done. In this case, a work order is just a record of the work that was done and does not serve to direct staff. The treatment plant also enters work orders that pertain to storm water. Storm water work orders are generated by issues. The storm system is currently not maintained on a preventative basis, but on an as-needed basis. BuildingEye This is a permit system end user solution with point data records on an interactive map for engineering, building and planning permits. It provides the ability for City staff and citizens to do limited filter queries by keyword, date ranges and project type in 13 categories. There is no ability to do smart mapping with the tool, all points are displayed at the same size for point symbols. Limited searching by location drawing simple polygon shapes is available. The base map for the application is provided by Mapquest and multiple base maps are not included (e.g. high resolution imagery). There is additional capability for registered users, such as setting alerts. The system is simple and effective for its purpose. There is a need to explore the input/output capabilities of the proprietary application. From previous experience, we believe the input mechanism is an Esri shapefile. Further exploration of the export/import potential and how to complement this application with City built ArcGIS Online web services is needed. New World This software is utilized by the Police and Fire Department and the 911 operations center. We did not review the software interface nor workflows in any detail during this needs assessment, since the operations are entirely handled by Missoula County. A server for the latest version of New World is planned for installation in the same server room as the server running the City wide enterprise geodatabase. The New World consultants configure the Esri GIS system integrated in their software.

26

GIS Data Layer Inventory Table 2. GIS Layers

LAYER NOTES STATUS M-

Maintained I-Incomplete

OWNER

Address Points M GIS Services

Aerial Photography current and historical GIS Services

All_Condos GIS Services

Alleys M GIS Services

BID Zone Boundaries M GIS Services

City Limits M GIS Services

County_Sewer_Billing Data for annexation map; currently being developed. GIS Services

Difficult_Addresses GIS Services

Easements I GIS Services

FEMA Floodplain ?

Lanes street centerlines M GIS Services

LanesBlockAnno_18000 M GIS Services

LanesNameAnno_18000 M GIS Services

Lighting Districts M GIS Services

Medians M GIS Services

Neighborhood Council Boundaries M GIS Services

Parcels M GIS Services

Proposed_Roads M GIS Services

Resolutions i.e., annexed, unannexed M GIS Services

Right of Way i.e., acquisitions, vacations I GIS Services

Sewer Network M GIS Services

Sidewalks I GIS Services

Storm Water Network M GIS Services

Street Lights I GIS Services

Subdivisions GIS Services

Traffic Sign I GIS Services

Traffic Signals GIS Services

Ward Boundaries M GIS Services

27

WWSA Boundary M GIS Services

311 Response Areas Fire

Evacuation Zones Fire

Fire Response Area Boundaries Fire

Hydrants these are non-Mountain Water hydrants Fire

Mountain Water Hydrants

These are provided by Mtn Water and value added by John Pilsworth Fire

Pre-Plans PDF Format? Fire

URD Boundary Currently maintained as individual shapefiles MRA

Entitled Lots Dev Srvc - Planning

Land Use Dev Srvc - Planning

UFDA multiple layers? Dev Srvc - Planning

Zoning Dev Srvc - Planning

MPO Planning Area Dev Srvc - Transportation

MPO Urbanized Area Dev Srvc - Transportation

Athletic fields Park & Rec

Baseball diamonds Park & Rec

Bear Buffer Park & Rec

Bridges Park & Rec

Buildings Park & Rec

City Commuter Trails Park & Rec

City Maintained Landscaped ROWs Park & Rec

City Managed Parklands Park & Rec

Conservation Lands Park & Rec

Fence & Trail Work Park & Rec

Fencing Park & Rec

Future Zones Park & Rec

Golf Courses Park & Rec

Green median strips Park & Rec

Open Space Plan Boundary Park & Rec

Park Asset Management Layers

various park features e.g., surface types/uses, buildings, bridges, well locations Park & Rec

Playgrounds Park & Rec

28

Safe Routes to School? Is this maintained by Parks? Unclear from notes Park & Rec

Sport courts Park & Rec

Stump Removals Park & Rec

Trails (government, internal, public)

includes trails outside of the City Park & Rec

Tree Points Park & Rec

Tree Removals Park & Rec

Vegetation Management Park & Rec

Vegetation Treatments Park & Rec

Wildland Urban Planting Interface extends outside of the City Park & Rec

External Data The following GIS datasets were identified as commonly used and acquired form external sources:

2010 Census Geography (blocks, block groups, tracts) Railroads Rivers Streams Lakes PLSS

Land Base Sources

Orthoimagery Digital Elevation Models Lidar

29

Data and Workflows – Current Situation

The detail in this figure is less important than the workflow lines, all colors show outgoing dependencies, color coded by department. With many of the GIS needs addresses there will be more two-way workflows and greater feedback (more diversity of colored lines on the diagram) Figure 2. Data Workflow Diagram

30