1 / 24

Tom Heinzer Manager, MPGIS Service Center, USBR SA, Agency GIS Tech. Team

Tom Heinzer Manager, MPGIS Service Center, USBR SA, Agency GIS Tech. Team Chemical Engineer, GISP. Diane Williams Principal Engineer GIS/RS/Modeling Agency GIS Tech. Team. MPGIS Service Center. The un-learning. 5 years ago a small technical team at USBR

elroy
Download Presentation

Tom Heinzer Manager, MPGIS Service Center, USBR SA, Agency GIS Tech. Team

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. Tom Heinzer Manager, MPGIS Service Center, USBR SA, Agency GIS Tech. Team Chemical Engineer, GISP Diane Williams Principal Engineer GIS/RS/Modeling Agency GIS Tech. Team MPGIS Service Center

  2. The un-learning 5 years ago a small technical team at USBR started a theoretical research project to come up with new comprehensive ways to look at data management This included access, organization, and dissemination

  3. As it turned out we didn’t need new ideas on how to manage data. We needed to UN-LEARN one key notion: That the physical organization of data is somehow fundamental to organizing data

  4. Put another way: How we ‘organize data’ should have nothing to do with how we arrange/store it on disk or in SDE or in Web Services

  5. We then drove this interesting premise to its conclusion. So, whatever we use to organize the data, it can’t be the data itself. If we can’t use the data, then we had to use some ‘object’ to represent the data. The constraints we imposed were: The object must know everything about the data The object must integrate into ArcGIS The object must be ‘re-arrangable’ inside of some framework The theory was that these ‘data objects’ could then be ‘organized’ in some type of ‘Virtual Presentation Tier’

  6. Properties Name Layer File Source Metadata Data Icon Methods File GDB SDE Web Service Behavior Transportable XML Serializable

  7. Virtual Presentation Tier Physical Data Tier File GDB 1 Feature Class 1 Feature Class 2 Raster 1 File GDB 2 Feature Class3 Raster 2 Feature Class 4

  8. We wanted to make organizing GIS data more intuitive using • this virtualized environment • The easiest way to do this, was to leverage something • the user already knew how to do: • Navigate TreeViews in Windows • So, the final step was to design these data objects to be • tree nodes in Windows TreeView controls, embedded in ArcGIS.

  9. Virtual Presentation Tier Physical Data Tier Roads100kCalifornia RdsKernCounty24k US_Roads_All Folsom_Lake_Roads SacCountyRoads24k Caltrans24kHWays

  10. Virtual Presentation Tier Physical Data Tier Roads100kCalifornia RdsKernCounty24k US_Roads_All Folsom_Lake_Roads SacCountyRoads24k Caltrans24kHWays

  11. So, how is this used in an enterprise system?

  12. Data Served From Agency Data Served From Region Data Served From Local Office Bureau Tier Region Tier Office Tier Reclamation GIS Library

  13. Bureau Tier Regional Tier Office Tier Personal Tier USBR Spatial Library

  14. Enterprise Data Manager: Remote Data Management

  15. Few last thoughts… Same data management tools are given to everyone Virtualization and tiering solved many of our data management problems Consultations with ESRI Scott Morehouse on software design Time spent on data management Fun Try it

  16. Tom Heinzer (916) 978-5273 theinzer@usbr.gov

More Related