1 / 15

Geospatial Information Officer

Geospatial Information Officer. Brenda Smith. Office of Environmental Information Environmental Protection Agency Smith.Brenda@epa.gov. Today’s Topics. Where the GIO fits in at EPA GIO roles Background Experience as core enterprise geospatial issues Will NOT be ALL of them!

blake-may
Download Presentation

Geospatial Information Officer

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. Geospatial Information Officer Brenda Smith Office of Environmental Information Environmental Protection Agency Smith.Brenda@epa.gov

  2. Today’s Topics • Where the GIO fits in at EPA • GIO roles • Background • Experience as core enterprise geospatial issues • Will NOT be ALL of them! • Questions from you

  3. Where the GIO fits in at EPA • Report to the CIO • In Headquarters • Working with individuals throughout OEI (and many other Federal and State communities)

  4. GIO Roles On Geospatial-related issues: • Build partnerships internally and externally • Provide leadership within OEI • Retain sense of how applicable various technologies are • In collaboration with you, work toenhance the GIS capabilities enabling all EPA offices to quickly generate and share necessary geospatial data

  5. Background • Education: • B.A. – Math/Computer Science, 1987 • M.S – Computer Science, 1995 • Employment: • 1987: Defense Intelligence Agency

  6. Background cont’d • 1987 to 1994: Directorate for Info Systems • Database Application Developer • System Administrator/Tech Support • 1990: Discovered GIS!

  7. Background cont’d • 1994 – 2004: Directorate for Analysis, GIS Division • Tech Support for GOTS GIS • Software installation • Help desk/Troubleshooting • End User (analysis) training • Live data feeds • Data Admin (GIS/non-GIS data formats) • Land Classification standards • Data loader specifications • System Admin Training

  8. Background cont’d • 1994 – 2004: Directorate for Analysis, GIS Division • GIS Analysis (GOTS) • Intelligence Preparation of the Battlespace (IPB) • Line Of Site (LOS), Cross Country Movement (CCM), Site Selection modeling, Movement Modeling, etc. • Time Critical Analysis (temporal) • GIS Application Development (GOTS & COTS) • GIS Enterprise Architecture for DoD Intel Community

  9. Experience with GIS Enterprise Architecture • Issues : • WHO • WHAT • WHERE • WHEN

  10. Experience with GIS Enterprise Architecture • WHO are the customers: • Non-GIS savvy professionals • Analysts/Warfighter/Policy • GIS professionals (ERDAS/ESRI) • Application Developers

  11. Experience with GIS Enterprise Architecture • WHAT (Data/Processes/Functions/Tools): • Common data sets (GIS/non-GIS formats) • Reduce Data Loading Redundancy where possible • Geospatial functions influence tools (Analysis <-> Visualization) • GIS Analysis • Interactive Web • Static Display geospatially

  12. Experience with GIS Enterprise Architecture • WHERE (People/Data/Tools): • Data stored • How close to the data are the users • Desktop • Local Server (LAN) • Remote Server (WAN) • Server Side vs Desktop • Applications costs • Functions/Tools needed • Technology COULD be used (GIS/non-GIS)

  13. Experience with GIS Enterprise Architecture • WHEN (temporal data, time to answer): • Performance • Minimum bandwidth • Infrastructure (network/processing power)

  14. Experience with GIS Enterprise Architecture • Lessons Learned: • May have SOME separation of production from dissemination (or at a minimum influence schema) • Accept that different “clients” are required, but they must share data • APIs are important • Starting the ‘Exploitation of Metadata’ • Resourcing/Staffing/Expertise • Hard to do this “on the cheap”

  15. Now, from you Questions?

More Related