Integrating LAS, OPeNDAP, GIS

1
Integrating LAS, OPeNDAP, GIS THREDDS

• Steve Hankin, Jonathan Callahan, Roland
  Schweitzer, Kevin OBrien, Ansley Manke, Xiaoping
  Wang

2
Current LAS GIS Connections

• LAS can output GIS ASCII raster product
• LAS UI can connect to a GIS back end
• LAS offers OPeNDAP URLs for all data(some GIS
  applications read OPeNDAP)

3
(No Transcript)
4
Future LAS GIS Connectivity

• LAS will become an OGC compliant Web Map Server
• LAS will become an OGC compliant Web Coverage
  Server
• LAS will be able to send incoming requests to
  other web services

5
Current LAS
6
New LAS
7
LAS Rewrite

• Rewrite LAS Product Server in java
• Complete separation of data server and back end
  services
• More robust
• More flexible
• Using newly available java libraries

8
More Connections

• Some GIS applications read OPeNDAP(LAS/FDS
  outputs OPeNDAP)
• WCS-THREDDS Gateway Serverconverts NetCDF to GIS
  (LAS outputs THREDDS catalogs)

9
HPCC Proposal

• Implement WMS/WCS capabilities as part of the LAS
  Product Server rewrite
• Another step toward integration of GIS/scientific
  data
• Benefits from installed base of LAS servers
• To provide greater access to real-time and
  historical information to users in a more
  complete, more usable form.