Presentation on theme: "Temporal and Spatial Resolution Query. Spatial and Temporal Data Resolution Provides users with the capability of refining GCMD database searches by Geospatial."— Presentation transcript:
Temporal and Spatial Resolution Query
Spatial and Temporal Data Resolution Provides users with the capability of refining GCMD database searches by Geospatial and Temporal Resolution. DIF Syntax – (Changes in Bold ) +Group: Data_Resolution Latitude_Resolution: Longitude_Resolution: + Horizontal_Resolution_Range: [choose from the list of geospatial ranges] Vertical_Resolution: + Vertical_Resolution_Range: [choose from the list of vertical resolutions] Temporal_Resolution: + Temporal_Resolution_Range:[choose from the list of temporal resolutions] End_Group
Horizontal Resolution Range DIF authors must select from the set of valid Geospatial (Horizontal) resolution ranges < 1 meter 1 meter - < 30 meters 30 meters - < 100 meters 100 meters - < 250 meters 250 meters – < 500 meters 500 meters – < 1 Km 1 Km - < 10 Km or approximately.01 degree - <.1 degree 10 Km - < 50 Km or approximately.1 degree - <.5 degree 50 km - < 100 km or approximately.5 degree - < 1 degree 100 km - < 250 km or approximately 1 degree - < 2.5 degrees 250 km - < 500 km or approximately 2.5 degrees - < 5.0 degrees 500 km - < 1000 km or approximately 5 degrees - < 10 degrees > 1000 km or > 10 degrees Horizontal Resolution Range
Modifications since May Original 100 meters - < 1 Km 1 Km - < 100 Km or approximately.1 degree - < 1 degree Modified 100 meters - < 250 meters 250 meters - < 500 meters 500 meters - < 1 Km 1 Km - < 10 Km or approximately.01 degree - <.1 degree 10 Km - < 50 Km or approximately.1 degree - <.5 degree 50 km - < 100 km or approximately.5 degree - < 1 degree Added Resolution Range Valids. The original 100 meters to 100 Km ranges were too broad to accurately query data under 100 Km.
Vertical Resolution refers to both Altitude and Depth resolution. < 1 meter 1 meter - < 10 meters 10 meters - < 30 meters 30 meters - < 100 meters 100 meters - < 1 km > 1 km < 1 second 1 second - < 1 minute 1 minute - < 1 hour Hourly - < Daily Daily - < Weekly Weekly - < Monthly Monthly- < Annual Hourly Climatology Daily Climatology Pentad Climatology Weekly Climatology Monthly climatology Annual Annual climatology Decadal Climate Normal (30-year climatology) Vertical Resolution RangeTemporal Resolution Range Vertical & Temporal Resolution Range
Spatial and Temporal Data Resolution Example Group: Data_Resolution Latitude_Resolution: 1 meter Longitude_Resolution: 1 meter Horizontal_Resolution_Range: 1 meter - < 30 meters Vertical_Resolution: 5 meters Vertical_Resolution_Range: 1 meter - < 10 meters Temporal_Resolution: Daily Temporal_Resolution_Range: Hourly - < Daily End_Group
Summary of Proposal Status Spatial and Temporal Data Resolution proposal sent to Interop: September 8, Comments received: September 8 - October 31, Response to comments sent to Interop: October 31, No other comments received until May 2004 Spatial and Temporal Data Resolution proposal adopted February 2004 (now incorporating comments from May 2004) and placed on development schedule. Scheduled as part of MD9 Version 2 Release (March 2005).
Numerical Model Fields Proposed for the DIF Anne Sophie Archambeau from IPSL, France proposed an addition to the DIF to handle numerical output data sets: Group: Numerical_Experiment Model_Name: Model_Version: Model_URL: Model_Configuration: Model_Resolution: Model_Calendar: Group: Model_Integration_Period Start_Date: Stop_Date: End_Group Simulation_Name: Initial_Conditions: Perturbation: Imposed_Boundary_Conditions: End_Group Interop discussions on proposed new fields summarized in the CEOS IDN Interop Newsletter April 2003: April/ html April/ html Renewed interest expressed through GO-ESSP
Global Organization for Earth System Science Portal (GO-ESSP) Conference (formally ESP) Main Goal: Develop a new generation of software infrastructure to provide distributed access to observed and simulated data from the climate and weather communities The group plans to integrate individual software components, building a federation of frameworks that can work together using consensus standards.
GO-ESSP Progress Formed model metadata group and a middleware group with Points of Contact established for each to ensure that discussions were kept active The IDN also began work with other members of the group to begin a dialogue about implementing a Lucene search engine for geospatial data