![]() As soon as changes are made in the field, it shows up on the map that everybody sees the next day instead of the next quarter." Hossack said: "I'd say the biggest thing is better data management, better data accuracy, and the timeliness of data. Being able to consolidate the data and serve up real-time views of the data improved workflows drastically. Having a robust ArcGIS Enterprise architecture transformed data management at Maricopa County. Our big thing was just trying to plan for the possibility of what we could be using it for." The county now has different setups for different uses, from single-machine deployments to 12 multimachine deployments to support high availability. ![]() Baker said: "As ArcGIS Enterprise evolved and added more technology and features, we tried to evolve with it and make plans, whether we were using it or not. Rebuilding from scratch allowed Maricopa County to plan, making sure there would be capacity when and if needed. Maricopa County established an enterprise license agreement with Esri to move from physical machines to virtual machines (VMs) using ArcGIS Enterprise. The first step was a complete redesign of the system. Moss, who gained the trust of other GIS groups, credits Maricopa County for combining different GIS resources and the Geographic Information Officer's (GIO) office with energizing the team and giving it the resources needed to succeed. As he worked to untangle the data and server, more and more GIS departments around the county joined his core GIS group, growing from 2 people to 18 in just eight months. Moss managed to track down the right passwords and started implementing changes. That's when Moss knew something had to be done. Moss said: "We didn't know how to get into the server, and we didn't know how to change it." Director Moss learned that an employee in charge of GIS for regulatory agencies had left without sharing passwords or documentation. The pivotal moment came in 2014 when the county almost lost access to its data and servers. Furthermore, we weren’t able to capture spatial data very well back then because data that were collected in the field were recorded on paper." ![]() As a result, there was a lot of manual work involved to get data refreshed. Hossack said: "We did not have integration with other databases that hosted business data in nonspatial SQL Server tables. File-based GIS data were managed as shapefiles in shared folders or Personal Geodatabases in Microsoft Access. At the time, there was no enterprise geodatabase. Steve Hossack, now GIS software architect, was hired as a database administrator six and a half years ago. Figuring out which data source to update was difficult because individuals edited and kept versions on different desktops. You never really knew which was authoritative or the newest at the time."ĭata was also static and only updated quarterly, recalled GIS analyst Christopher Turner. Data was in many geodatabases, in many shapefiles, and in 17 different iterations on everybody's computer across the county. Kacie Baker, GIS software architect, said: "Data was definitely siloed. For years, data was managed by different groups all over the county with little collaboration between them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |