When LAS is configured to use a Dapper server as the data source, you must configure an LAS Dapper service that LAS can use to read the data source and create the intermediate netCDF files it needs to make plots and create other products from the data. A simple file is used to tell LAS about the dapper servers it will need to access to read your data.
If you configured your LAS to set up the sample in-situ datasets this file should contain something like this:
<dapper_servers> <dapper name="PFEG Dapper Server" url="http://las.pfeg.noaa.gov/dods/"/> <dapper name="PMEL Dapper Server" url="http://dapper.pmel.noaa.gov/dapper"/> <dapper name="OSCAR Dapper Server" url="http://www.epic.noaa.gov/dapper/oscar/"/> </dapper_servers>
The <dapper_servers> XML element contains a list of individual <dapper>elements that describe how the Dapper service can connect to theappropriate server associated with an LAS dataset.
To add your own Dapper to LAS you must add another <dapper> tag to this file.
The attributes of the <database .../> tag are:
- matches the value of the <db_name> tag in the dataset configuration file (see Creating the dapper configuration file)
- the OPeNDAP base URL of the drds server.