# Presentation: 859028

## NOSA: A Spatial Portal to 

- Kelly Stroker, David Froehlich, Anna Milan
- CIRES, University of Colorado
- Ted.Habermann@noaa.govNOAA, National Geophysical Data Center

- NOSA: A Spatial Portal to
- NOAA's Observing Systems

## NOAA Maps

- Over 400 maps have been  captured from NOAA Web pages and described in the NOAA Maps Project.

**Notes:**
The goal of the NOAA Maps project at NGDC is to characterize how NOAA presently does mapping on the Internet and to explore how a selection event might affect that aspect of NOAA Data Management. The project now includes over 200 maps and over 100 capabilities that those maps provide. The NOAA Observing System Architecture (NOSA) map is our prototype for a standards-based internet map. The capabilities of that map will serve as a comparison to other NOAA maps that are developed using more customized tools. 

## http://nosa.noaa.gov

- The NOSA website provides information about the program and its history as well as several access paths to the NOSA database.

## NOSA Website Architecture @ NGDC

- Geospatial
- Database

- Metadata

- WIST

- LAS

- FYP

- Stations,
- QA

- Map

- Spreadsheet,
- E-mail, txt,
- etc.

- Pipeline

## ArcIMS Map with Multiple Data Layers

## ArcIMS Site and Metadata Links

## ArcIMS Site and Data Links

## What just happened?

- Geospatial Database

- Scientists throughout NOAA contributed

- Spatial
- Query

- COTS
- IMS

- Links back to existing WWW resources

## Integrated Satellite and In-Situ Data Access

## Observation Density

## Find Your Place-NOSA in Your Neighborhood

- Geospatial database = very general searches

## Results: NWS-COOP in Idaho

## OGC Web Map Services

**Notes:**
The Open Geospatial Consortium Web Map Service interface provides URLs that lead directly to maps. Many aspects of the maps can be controlled by arguments in the URLs. The NOSA website provides example URLs with various spatial limits and backgrounds.

## Web Image Slide Trays (WIST)

- The WIST provides simplified access to maps of particular layers for pre-determined regions using a Web Map Server (WMS) and a custom tag library for Java Server Pages.

**Notes:**
The Interactive Map Interface has many features and can be difficult to use. Sometime a simple interface that allows comparison of multiple maps can be more effective. The Web Image Slide Tray is an example of such an comparison interface. It is build on top of an Open Geospatial Consortium Web Map Service interface.

## OGC Web Feature Service

**Notes:**
The Open Geospatial Consortium Web Map Service provides images of maps. The Web Feature Service provides actual spatial features and associated data/attributes. This information is provided in Geographic Markup Language (GML). The example above shows the GML representation of values from the database table nosa_ns.nws_boy_41001_tsqp for station_id=41008.

## NOSA and Google Earth

## Technology Cycle

**TIME**

- Technological
- Disruption

- Era of Ferment

- Selection

- Dominant
- Design

- Disruption #2
- (destroys existing
- competence)

**Notes:**
This brings up another possible explanation for the S-curve. The cycle starts with the introduction of a new, disruptive technology. This disruption leads to a period of experimentation and ferment during which many different approaches to applying the new technology are explored. Overall progress is slow because of this experimentation. At some point selection of a dominant design occurs and energy previously spent on exploring different design options is focused on using that dominant design effectively. Then a second disruption occurs, destroying the competence developed earlier and focusing energy once again into experimentation. 

## One Connection

- NOAA Observing
- System Database

- Http Request

- Spatial Query

- KML Response

- LARC

- Nexrad

- CBOY

- CMAN

- Not one for eachObserving System

## NOSA Website Architecture @ NGDC

- Geospatial
- Database

- Metadata

- WIST

- LAS

- FYP

- Stations,
- QA

- Map

- Spreadsheet,
- E-mail, txt,
- etc.

- Pipeline

## The Data Processing Pipeline

- A pipeline executes a sequence of plug-able data processing tasks. The NGDC data processing pipeline provides a set of pipeline utilities designed around work queues that run in parallel to sequentially process data objects. The pipeline is an open source project hosted in the *Jakarta Commons Sandbox*
- (http://jakarta.apache.org/commons/sandbox/index.html).
- Processing steps are specified as a series of stages in an XML configuration file.

**Notes:**
Data processing goes on constantly at NGDC and in other parts of NOAA. It is an element of data management that features many opportunities for re-inventing the wheel simply because we all do so much of it. The Data Processing Pipeline was developed at NGDC to provide an infrastructure for geospatial data processing at NGDC. The pipeline is built around the Open Geospatial Consortium Simple Features Specification which is used as a canonical representation in memory.  Readers are written to read data in particular formats and create spatial objects in memory. Those features can then be operated on and written to the database.

## DMSP Orbit Processing

- Stage 1. Find Matching Files
- Stage 2. Avoid Duplicate Processing
- Stage 3. Read Data / Create Spatial Objects
- Stage 4. Low-Res Thinning
- Stage 5. High-Res Thinning
- Stage 6. Write Spatial Data to Database

**Notes:**
This example shows the steps that we are taking to process Defense Meteorological Satellite Program spatial footprints from orbit files into a spatial database.

## Find Matching Files

- <!-- Get names of files to process from the ingest directory -->
- <stage className="org.apache.commons.pipeline.impl.FileFinderStage“
-    filePattern=".*\.OIS">
-    <stageDriver
-    className="org.apache.commons.pipeline.impl.SingleThreadStageDriver"/>
-    <enqueue>
-       <value>/mnt/stout/raid/lv2/ois/incoming/</value>
-    </enqueue>
- </stage>

**Notes:**
The “Find Matching Files” stage finds files that match the pattern “*.OIS” in a directory called /mnt/stout/raid/lv2/ois/incoming/. As these files are identified, they are added to the processing queue.

## Treasure??

**Treasure??**