1 / 12

Alternative Data Interoperability Solutions

Alternative Data Interoperability Solutions. Abstract.

naron
Télécharger la présentation

Alternative Data Interoperability Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Alternative Data Interoperability Solutions

  2. Abstract Johnson County AIMS serves as a GIS data service provider for 21 cities and 510,000 residents. In addition to providing data, AIMS also receives GIS data from both the private and public sector. AIMS must be able to import and export GIS data to multiple GIS and CAD formats. In looking at various solutions, including ESRI's data interoperability extension, AIMS has incorporated Safe software's FME (feature manipulation extraction) into their everyday business processes. FME is used in generalizing Johnson County's utility data from multiple service providers and allows for easy re-distribution of this data in different formats. This paper will look at why AIMS decided to use FME and how FME is been used on an every day basis within a County government GIS organization.

  3. What was the problem? • DDR (Digital Data Request) • Have to replace an AML based distribution process • Have to output DXF, DGN, shape, and e00 • Want to output DWG • Here is an example

  4. Choices • Write everything in ArcObjects • Possible but would be a lot of work • Requires advanced skills • Data Interoperability Extension • Still a couple of months away at the time • Only works through ArcMap and we need to automate things • FME • Did everything we wanted • A bit Expensive • Somewhat complex, but simple to use • Easy to automate

  5. 29 Input feature classes • 1 Input clip rectangle • 69 Output DWG layers • 32 Transformers

  6. What else do we use it for now? • CUE (Collaborative Utility Exchange) • Collect and process data from many different sources

  7. Data from 8 different sources • Input formats • Shapefile • Personal Geodatabase • Enterprise Geodatabase

  8. I/CAD Support • Push our data into DGN format to support our law enforcement dispatch system

  9. Daily Uses • Adding lat/long to our address file • Producing intersections from our centerline file • Producing a feature class from septic permit data • Producing a line file from annotation for use in our IMS • Producing a point dataset out of our property feature class • Import AutoCAD based utility information into geodatabase

  10. Conclusions • 4000+ (mostly successful) DDR requests run without supervision • 85 separate FME files run on a regular basis • 10 FME files run on a nightly basis • A multitude of nasty problems fixed with drag and drop processes • Cost has been offset by benefits

  11. Keith Shaw Lead Developer 913-715-1567 Keith.Shaw@jocogov.org

More Related