James Gallagher OPeNDAP 1/10/14

Slides:



Advertisements
Similar presentations
Pierre-Johan CHARTRE Java EE - JAX-RS - Pierre-Johan CHARTRE
Advertisements

1 NASA CEOP Status & Demo CEOS WGISS-25 Sanya, China February 27, 2008 Yonsook Enloe.
XPointer and HTTP Range A possible design for a scalable and extensible RDF Data Access protocol. Bryan Thompson draft Presented to the RDF.
Introduction to the BinX Library eDIKT project team Ted Wen Robert Carroll
OASIS OData Technical Committee. AGENDA Introduction OASIS OData Technical Committee OData Overview Work of the Technical Committee Q&A.
Proposed update of Technical Guidance for INSPIRE Download services based on SOS Matthes Rieke, Dr. Albert Remke (m.rieke, 52°North.
Unidata Seminar Series - 30 January 2004 OPeNDAP and THREDDS: Access and Discovery of Distributed Scientific Data Yuan Ho Ethan Davis UCAR Unidata.
Aggregation and Subsetting in ERDDAP (a middleman data server) Bob Simons NOAA NMFS SWFSC ERD.
OPeNDAP in the Cloud Optimizing the Use of Storage Systems Provided by Cloud Computing Environments OPeNDAP James Gallagher, Nathan Potter and NOAA/NODC.
OPeNDAP in the Cloud OPeNDAP James Gallagher, Nathan Potter and NOAA/NODC Deirdre Byrne, Jefferson Ogata, John Relph 26 June 2013.
A Common Data Model In the Middle Tier Enabling Data Access in Workflows … HDF/HDF-EOS Workshop XIV September 29, 2010 Doug Lindholm Laboratory for Atmospheric.
Streaming NetCDF John Caron July What does NetCDF do for you? Data Storage: machine-, OS-, compiler-independent Standard API (Application Programming.
® OGC Web Services Initiative, Phase 9 (OWS-9): Innovations Thread - OPeNDAP James Gallagher and Nathan Potter, OPeNDAP © 2012 Open Geospatial Consortium.
15-Jul-15 JSON. JSON example “JSON” stands for “JavaScript Object Notation” Despite the name, JSON is a (mostly) language-independent way of specifying.
CHAPTER 3&4 ZHONGWEI LI TouchDevelop Book. What are we covering Review of Chapter 1-2 TouchDevelop as a scripting language: actions, events, table and.
CGI Programming: Part 1. What is CGI? CGI = Common Gateway Interface Provides a standardized way for web browsers to: –Call programs on a server. –Pass.
Service-Oriented Programming
Web to Database Connectivity Tools Frank Cervone Assistant Director for Systems DePaul University Libraries Access ‘98 October 3, 1998.
THREDDS Data Server, OGC WCS, CRS, and CF Ethan Davis UCAR Unidata 2008 GO-ESSP, Seattle.
Chapter 9 Using Perl for CGI Programming. Computation is required to support sophisticated web applications Computation can be done by the server or the.
2003 April 151 Data Centres: Connecting to the Real World Clive Page.
OPeNDAP and the Data Access Protocol (DAP) Original version by Dave Fulker.
Chapter 33 CGI Technology for Dynamic Web Documents There are two alternative forms of retrieving web documents. Instead of retrieving static HTML documents,
Concept demo System dashboard. Overview Dashboard use case General implementation ideas Use of MULE integration platform Collection Aggregation/Factorization.
M i SMob i S Mob i Store - Mobile i nternet File Storage Platform Chetna Kaur.
Unidata’s TDS Workshop TDS Overview – Part II October 2012.
NERC DataGrid Vocabulary Server Access Vocabulary Workshop, RAL, February 25, 2009.
A Metadata Based Approach For Supporting Subsetting Queries Over Parallel HDF5 Datasets Vignesh Santhanagopalan Graduate Student Department Of CSE.
Web Services for Earth Science Data Edward Armstrong, Thomas Huang, Charles Thompson, Nga Quach, Richard Kim, Zhangfan Xing Winter ESIP 2014 Washington.
USING PERL FOR CGI PROGRAMMING
Coverages and the DAP2 Data Model James Gallagher.
CHRIS NELSON METADATA TECHNOLOGY WORK SESSION ON STATISTICAL METADATA GENEVA 6-8 MAY 2013 Designing a Metadata Repository Metadata Technology Ltd.
Open Data Protocol * Han Wang 11/30/2012 *
Integrating netCDF and OPeNDAP (The DrNO Project) Dr. Dennis Heimbigner Unidata Go-ESSP Workshop Seattle, WA, Sept
DAP4 James Gallagher & Ethan Davis OPeNDAP and Unidata.
Accessing Remote Datasets using the DAP protocol through the netCDF interface. Dr. Dennis Heimbigner Unidata netCDF Workshop August 3-4, 2009.
CS1001 Lecture 9. Overview Security Security HTML HTML.
The CERA2 Data Base Data input – Data output Hans Luthardt Model & Data/MPI-M, Hamburg Services and Facilities of DKRZ and Model & Data Hamburg,
A Data Access Framework for ESMF Model Outputs Roland Schweitzer Steve Hankin Jonathan Callahan Kevin O’Brien Ansley Manke.
1 WWW. 2 World Wide Web Major application protocol used on the Internet Simple interface Two concepts –Point –Click.
JAVA BEANS JSP - Standard Tag Library (JSTL) JAVA Enterprise Edition.
DAP4, SOAP and THREDDS James Gallagher OPeNDAP Presented by Steve Hankin.
Data Interoperability at the IRI: translating between data cultures Benno Blumenthal International Research Institute for Climate Prediction Columbia University.
OPeNDAP Developer’s Workshop Feb Server-side Functions for Geo-spatial Selection James Gallagher 22 Feb 2007.
AJAX and REST. Slide 2 What is AJAX? It’s an acronym for Asynchronous JavaScript and XML Although requests need not be asynchronous It’s not really a.
OVERVIEW AND PARSING JSON. What is JSON JavaScript Object Notation Used to format data Commonly used in Web as a vehicle to describe data being sent between.
OGC Web Services with complex data Stephen Pascoe How OGC Web Services relate to GML Application Schema.
The ECOST Web-based platform for data providers and for data users.
9/21/04 James Gallagher Server-Side: The Basics This part of the workshop contains an overview of the two servers which OPeNDAP has developed. One uses.
Search Engine and Optimization 1. Introduction to Web Search Engines 2.
TSDS (HPDE DAP). Objectives (1) develop a standard API for time series-like data, (2) develop a software package, TSDS (Time Series Data Server), that.
DAP+NETCDF Using the netCDF-4 Data Model
Checking the Server.
Hadoop.
Avraham Leff James T. Rayfield IBM T.J. Watson Research Center
AJAX and REST.
Unit – 5 JAVA Web Services
Tools to Build Clients.
Checking the Server.
YQL Kevin Murphy CMPS 183.
WEB API.
Remote Data Access Update
Accessing Remote Datasets through the netCDF interface.
API DOCUMENTATION Swetha Mohandas Microsoft Connect 2016
Client-Server Model: Requesting a Web Page
OPeNDAP/Hyrax Interfaces
QoS Metadata Status 106th OGC Technical Committee Orléans, France
Adapting an existing web server to S3
Intro to Web Services Consuming the Web.
Presentation transcript:

James Gallagher OPeNDAP 1/10/14 DAP4 Introduction James Gallagher OPeNDAP 1/10/14

Agenda Input on a Developer’s meeting All about DAP4 The CDM, too Comparison and discussion of DAP4 and CDM

DAP3 DAP4 DAP2: DDS, DAS, Data DAP4: DSR plus DMR, Data This looks like the ‘name game’ but it’s a real difference! While DAP2 was a data model only, DAP4 includes specification of the web services

DAP4 Data Model Coverages: Replace Grids with a more general model: Arrays, shared dimensions and maps ‘Coverage’ is slang for ‘discrete coverage’ as defined by OGC’s abstract coverages specification Maps define the Domain of a discrete function The Array defines the Range Shared dimensions provide the connection between Domain and Range Tabular data: Sequences (a nest-able table) Projection: subsetting based on data types Filters: subsetting based on values

The Services Response (DSR) DSR: Dataset Services Response DSR: Dataset Services Response is the ‘service endpoint’ This contains links to all of the other responses available from the server for a specific dataset A key point for/of REST In DAP2 the ‘base URL’ was undefined; in DAP4 the base URL for a dataset is the DSR

DSR and Content Negotiation DSR provides links to all of the other responses However, a server must implement Content Negotiation. i.e., a browser asking for the DMR winds up displaying a (HTML) web interface while a smart client parses XML

REST We have adopted a strict view of REST Not all of DAP4 fits; DAP4 is not REST The DAP4 web services are REST The DAP4 data/constraint model is not

Dataset Metadata (DMR) This response holds all of the variables and Attributes This defines the environment in which the Constraint will be evaluated

Data and Constraints As with DAP2, Data is returned in a two-part response Can request one or more variables Can ‘slice’ the dimensions of array variables Can filter both Tabular and Array data (because a client must understand the data model and that cannot be expressed by links, this part of the ‘web API’ is not REST).

Examples… The current draft specification has lots of examples: http://docs.opendap.org/index.php/DAP4:_Specification_Volume_1 The ‘test’ servers for DAP4: http://54.204.231.163:8080/opendap/data/reader/dap4/

JSON Simple responses for single atoms - Data Metadata (DMR) encoding

Summary DAP (DAP2 and DAP4) is based on datasets built of variables that share the characteristics of programming languages Constraints are used to subset data on the server DAP4 is a REST API DAP4 specifies ‘modern’ web services