Services

MODSCAG processing at UCSB

MapServer data search and order tool

UMN MapServer interface for distributing snow products
tiling
- streamline tiling procedure for Sierra tiles defined by Dozier
- prototype will have one tile resolution
check out http://www.dnr.state.mn.us/maps/tomo.html for a possible design
use CartoWeb http://www.cartoweb.org as the MapServer client

Product distribution

Goals
Requirements
- Must support snow and ocean products
  - known users for each of these user groups
  - ocean
    - provide products to OceanREASoN at Goddard
      - what form do they want
        
        ftp prepared by Manuala?
      - aren't required to distribute to anyone else as Goddard distributes them
        
        would be cool to be able to see time series
- who we are required to provide products to:
  - ocean
    - UCSB data to Watson
  - snow
    - required to make available to other people in the project
      - most users want data for specific ROIs
- who it is advantageous to collaborate with:
- who/what can give us good PR:
  - ocean
    - web service based access would be good PR for us
- 3 categories of users
  - EIL
    - need uniform set of interfaces
    - what are the usage/storage metrics?
      - how many granules online per ROI
  - who we are contractually obligated to keep happy
  - small number of users on snow side
- should have tools to summarize our data collections
  - data volume by ROI
  - granule count by ROI
  - these tools exist for ADL but are difficult to use
- tiling
  - useful mostly to machine interfaces
  - for zooming and browsing in a Google Earth type interface
  - do we need to create tiles for our own use
    - How does Metacarta tiling engine help us?
the current MODSCAG workflow should be formalized and made available to our users
- request
  - {x,y,t}
  - projection
- reproject
  - MODIS input
- MODSCAG
  - GeoTIFFs, etc
- where does the tiling fit into the processing?
  - before or after MODSCAG is run?