1 / 16

GIS Overview: National Perspective

GIS Overview: National Perspective. Frank Richards July 19, 2007. NOAA. NOAA GIS Committee ESRI ELA Google ELA PPBES. NWS. OSIP: NWS Enterprise GIS IT Consolidation. RFC GIS. OSIP Background Status Options. “Arc GRASS” a modest proposal.

duncan-shaw
Télécharger la présentation

GIS Overview: National Perspective

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. GIS Overview:National Perspective Frank Richards July 19, 2007

  2. NOAA • NOAA GIS Committee • ESRI ELA • Google ELA • PPBES

  3. NWS • OSIP: NWS Enterprise GIS • IT Consolidation

  4. RFC GIS • OSIP • Background • Status • Options

  5. “Arc GRASS”a modest proposal “Am I not destroying my enemies when I make friends of them? ” - Abraham Lincoln Prof. Scott T. Shipley Department of GeographyGeorge Mason University 19 July 2007

  6. RFC GIS Replacement ProjectStatement of Objectives (SOO) – the situation 1) Identify systems and software that can be integrated into the AWIPS & AWIPS2 baselines - 2.2.6.1 ArcGIS on Desktop - 2.2.6.2 GRASS on Linux - 2.2.6.new ArcGIS Engine on Linux with GRASS interoperability 2) Provide a way to convert ~ 500 k LOC - Avenue™ to ArcObjects - vBasic to JAVA - GRASS in JAVA, define and apply standards 3) Deploy at 13 RFCs & NWSHQ - ArcGIS Engine Developer Kit on Linux (with maintenance) - Runtime licenses (no maintenance) - Interoperable GRASS modules and utilities 4) Long-term vision - Establish relationships with collocated Universities - Attract and develop (or keep) new talent

  7. RFC GIS Replacement ProjectArcGIS Engine - Architecture • Standard GIS Framework for developing stand-alone GIS applications. • ArcGIS Desktop and ArcGIS Server are built from the same set of software objects. • Cost-Effective Deployment • Applications only require ArcGIS Engine Runtime. • Developer Controls • Available in ActiveX, .NET, and Java. http://www.esri.com/software/arcgis/arcgisengine/

  8. RFC GIS Replacement ProjectArcGIS Engine - Architecture • GIS Software Component Library – ArcObjects • Standard Languages and Platforms – • COM, .NET, Java, and C++ on Windows, Linux, and Solaris • ArcGIS Engine Software Developer Kit • PostgreSQL with 9.3 release (beta in OCT-NOV 2007)

  9. RFC GIS Replacement ProjectGRASS / ArcGIS Interoperability - VISION Transparent exchange of data with ArcGIS Apps - compliance with OGC recommendations GRASS functions callable from ArcGIS Engine Apps - parallel or stand alone operations “Give me six hours to chop down a tree and I will spend the first four sharpening the axe.” - Abraham Lincoln

  10. RFC GIS Replacement ProjectArcGIS Engine – Licensing (prelim. info) GRASS is “free” ArcGIS Engine SDK 1st copy: $5k one time + $3k maint. per year 2nd copy: $3k one time + $1.5k maint. per year Runtime GSA per seat $408 (no maint.) Reductions for higher quantities EDN annual subscription comparison Possible NWS enterprise license

  11. RFC GIS Replacement ProjectRFC – University Relationships NWSHQ/Raytheon DC Area GMU1 Alaska-Pacific APRFC Anchorage, AK tbd Arkansas-Red RBRFC Tulsa, OK OU California-Nevada CNRFC Sacramento, CA tbd Colorado Basin CBRFC Salt Lake City, UT tbd Lower Mississippi LMRFC Slidell, LA tbd Middle Atlantic MARFC State College, PA Penn State Missouri Basin MBRFC Pleasant Hill, KS tbd North Central NCRFC Chanhassen, MN tbd Northeast NERFC Taunton, MA Bridgewater Ohio OHRFC Wilmington, OH tbd Southeast SERFC Peachtree City, GA tbd West Gulf WGRFC Fort Worth, TX tbd NorthWest NWRFC Portland, OR tbd DRAFT 1Universities with strong and recognized GIS programs, and in close proximity with RFC

  12. Year 1 (FY08) Year 2 (FY09) Year 3 (FY10) Demo ArcGIS Engine Code Conversion Deployment GRASS Interop Doc & Training Mat’ls Year 2-3 Planning Students at RFCs Partner Coordination Call for proposals (partnerships) RFC GIS Replacement Project“Arc GRASS” Schedule

  13. RFC GIS Replacement ProjectStudent Required Curriculum 1, SwEng principles and practice 2. JAVA/Linux 3. GIS (OGC, ArcObjects & GRASS) 4. Principles of Hydrometeorology

  14. RFC GISProposed Next Steps • OSIP • Finalize Gate 3 Documents(w/in next 3 months) • ConOps • Modify ConOps to identify open source tools within baseline • Map open source tools into list of requirements • Modify ConOps to include need for ESRI tools: development environment outside of baseline • Develop Business Case • AHPS Proposal(w/in next 3-4 months) • Strategic ConOps/Business Case • Shared server resources: data base and computation • Limited Demonstration of ConOps

  15. Current NOAA Effort: PMEL Using ArcGIS Engine on Linux with JAVA as a language and Postgres as a database (Nazila Merati)

  16. AHPS ProposalFeatures/Linkages • CHPS • Enhanced RFC collaboration • Integration of ESRI – Open Source • Pathway to opertions • Involvement by Universities • Enterprise Architecture • Consolidation of systems • Model scalable to WFOs, National Centers • Single source of key reference information • Reduced bandwidth • Component of desktop consolidation?

More Related