10 Terra/MODIS Images for Aug. 14, 2005 Alaska North Slope Oil Industrial Area Landsat 5: June 15, 2005 NSSI Data System Tom Heinrichs UAF - Geographic Information Network of Alaska NSSI OG: 14-Nov-2006

Workshop Objective Establish consensus on the NSSI data system’s functional and content requirements

Objectives of This Presentation Present an overview of GINA’s design suggestions for the NSSI data system, based on: –Experience with other data systems and projects –Input from multiple previous data workshops and Oversight and Staff presentations and feedback Introduce some of the questions to be answered to meet the workshop objective

System Objectives Why does NSSI need this system? What differentiates it from other existing systems?

GINA Background and Projects Four examples: –Alaska Fire Service imagery and hot spots –Arctic Geobotanical Atlas –Landsat 5 reception for Alaska –Statewide mapping image and elevation data clearinghouse

“MODIS was great in detecting fires in remote locations. Almost this entire summer we were out of resources used for detection flights, MODIS filled the gap for us.” --Corey Doolin, Zone Coordinator Upper Yukon Zone BLM Alaska Fire Service

Arctic Geobotanical Atlas

Landsat 5: 2004 vs Alaska acquisitions 2004: 25 scenes FCDAS/GINA/EROS impact: 2005: 3889 scenes 2006: 4780 scenes

Current: MMS Sea Ice MMS Goodnews Bay offshore placers MMS Beaufort weather models USGS AmericaView NSF Sea Ice NSF Botanical Mapping Alaska Ocean Observing System Statewide Mapping: Imagery and DEMs Proposed MMS-CMI gridded data offshore NSF IPY data management

Data Systems: Role within NSSI Data systems serve every goal in the NSSI Oversight Group’s charter –Determination of information needs –Coordination –Public access These goals extend statewide

Fundamental Components Project tracking Literature database Local and traditional knowledge Data store Data discovery (metadata)

Fundamental Service Support decision making –By providing easier access to available information, leading to better informed decisions –By serving data easily ingestible by Decision Support Systems

Project Tracking

Literature Database Tied to geospatial location Literature and reports Copyright and proprietary issues

Local and Traditional Knowledge Important for local buy-in Integration with quantitative data not straightforward STG subcommittee

Base Layers Elevation Hydrography Geodetic control Cadastral Transportation Governmental Units Landcover Bathymetry Digital Orthoimagery

Suggested NSSI Layers … Developed with stakeholders

Gridded products Hajo Eicken:

Geospatial Databases and Interoperability Interoperating using Open Geospatial Consortium protocols

Open Geospatial Consortium Interoperability Client Application ArcGIS, Google Earth, Internet Map Server, etc DNR Land Records USGS DOQQs DOT Roads CPAI/BP Pipelines BLM Native Allotments NSB Fish Habitat

System Objectives Why does NSSI need this system? What differentiates it from other existing systems?

Why does NSSI need this system? To realize the goals: –Determination of information needs –Coordination –Public access To make better decisions using –Better (more complete) information –New techniques (GIS models) To realize savings of time and money

What differentiates this system? Designed to meet NSSI goals –“Agenda-less” source of data –Audit trail (litigation) –Owned by and serving the objectives of NSSI, which are broader than any one agency’s goals –Will lead to the service of larger, statewide goals

Topics for This Group Review of the proposed data layers (content); Discussion and comment on suggested standardized grids and projections; Review of the recommended system functionality; and Generation of a list of suggested topics/issues that could be addressed through DSS functionality. from: North Slope Science Initiative, Science Technical Group; Remote Sensing & GIS Subcommittee Meeting; November 13, 2006 Workshop Summary