diff --git a/Dockerfile b/Dockerfile
index aaac206..104ba63 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -4,7 +4,7 @@ LABEL maintainer="Kyle Wilcox <kyle@axiomdatascience.com>"
 ENV ERDDAP_VERSION 2.14
 ENV ERDDAP_CONTENT_URL https://github.com/BobSimons/erddap/releases/download/v$ERDDAP_VERSION/erddapContent.zip
 ENV ERDDAP_WAR_URL https://github.com/BobSimons/erddap/releases/download/v$ERDDAP_VERSION/erddap.war
-ENV ERDDAP_DATA /erddapData
+ENV ERDDAP_bigParentDirectory /erddapData
 
 RUN \
     curl -fSL "${ERDDAP_CONTENT_URL}" -o /erddapContent.zip && \
@@ -15,13 +15,33 @@ RUN \
     rm /erddap.war && \
     sed -i 's#</Context>#<Resources cachingAllowed="true" cacheMaxSize="100000" />\n&#' ${CATALINA_HOME}/conf/context.xml && \
     rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* && \
-    mkdir -p ${ERDDAP_DATA}
+    mkdir -p ${ERDDAP_bigParentDirectory}
 
 # Java options
 COPY files/setenv.sh ${CATALINA_HOME}/bin/setenv.sh
 
-# ERDDAP setup.xml
-COPY files/setup.xml ${CATALINA_HOME}/content/erddap/setup.xml
+# Default configuration
+ENV ERDDAP_baseHttpsUrl="https://localhost:8443" \
+    ERDDAP_flagKeyKey="73976bb0-9cd4-11e3-a5e2-0800200c9a66" \
+    ERDDAP_emailEverythingTo="nobody@example.com" \
+    ERDDAP_emailDailyReportsTo="nobody@example.com" \
+    ERDDAP_emailFromAddress="nothing@example.com" \
+    ERDDAP_emailUserName="" \
+    ERDDAP_emailPassword="" \
+    ERDDAP_emailProperties="" \
+    ERDDAP_emailSmtpHost="" \
+    ERDDAP_emailSmtpPort="" \
+    ERDDAP_adminInstitution="Axiom Docker Install" \
+    ERDDAP_adminInstitutionUrl="https://github.com/axiom-data-science/docker-erddap" \
+    ERDDAP_adminIndividualName="Axiom Docker Install" \
+    ERDDAP_adminPosition="Software Engineer" \
+    ERDDAP_adminPhone="555-555-5555" \
+    ERDDAP_adminAddress="123 Irrelevant St." \
+    ERDDAP_adminCity="Nowhere" \
+    ERDDAP_adminStateOrProvince="AK" \
+    ERDDAP_adminPostalCode="99504" \
+    ERDDAP_adminCountry="USA" \
+    ERDDAP_adminEmail="nobody@example.com"
 
 COPY entrypoint.sh /
 ENTRYPOINT ["/entrypoint.sh"]
diff --git a/README.md b/README.md
index f4e5dbb..2adbfd2 100644
--- a/README.md
+++ b/README.md
@@ -50,10 +50,13 @@ See [these instructions for configuring Tomcat](https://github.com/unidata/tomca
 
 ### ERDDAP
 
+Any number of these options can be taken to configure your ERDDAP container instance to your liking.
+
 1.  Mount your own `content/erddap` directory:
 
     ```bash
     $ docker run \
+        -p 8080:8080 \
         -v /path/to/your/erddap/directory:/usr/local/tomcat/content/erddap \
         ... \
         axiom/docker-erddap
@@ -65,19 +68,106 @@ See [these instructions for configuring Tomcat](https://github.com/unidata/tomca
 
     ```bash
     $ docker run \
+        -p 8080:8080 \
         -v /path/to/your/setup.xml:/usr/local/tomcat/content/erddap/setup.xml \
         -v /path/to/your/datasets.xml:/usr/local/tomcat/content/erddap/datasets.xml \
         ... \
         axiom/docker-erddap
     ```
 
-    **Any custom setup.xml needs to specify `<bigParentDirectory>/erddapData/</bigParentDirectory>`**
+    **If you mount setup.xml file make sure to set `<bigParentDirectory>/erddapData/</bigParentDirectory>`**
+
+2. Configure using environmental variables
+
+    You can set environmental variables to configure ERDDAP's `setup.xml` since version 2.14. See the [ERDDAP documentation](https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#setupEnvironmentVariables) for details. This can be very useful so you don't need to mount a custom `setup.xml` file into your container. If taking this approach you should look into setting the following ERDDAP config options:
+
+    * `ERDDAP_baseURL`
+    * `ERDDAP_baseHttpsUrl`
+    * `ERDDAP_flagKeyKey`
+    * `ERDDAP_emailEverythingTo`
+    * `ERDDAP_emailFromAddress`
+    * `ERDDAP_emailUserName`
+    * `ERDDAP_emailPassword`
+    * `ERDDAP_emailSmtpHost`
+    * `ERDDAP_emailSmtpPort`
+    * `ERDDAP_adminInstitution`
+    * `ERDDAP_adminInstitutionUrl`
+    * `ERDDAP_adminIndividualName`
+    * `ERDDAP_adminPosition`
+    * `ERDDAP_adminPhone`
+    * `ERDDAP_adminAddress`
+    * `ERDDAP_adminCity`
+    * `ERDDAP_adminStateOrProvince`
+    * `ERDDAP_adminPostalCode`
+    * `ERDDAP_adminCountry`
+    * `ERDDAP_adminEmail`
+
+    For example:
+
+    ```bash
+    docker run \
+        -p 8080:8080 \
+        -e ERDDAP_baseURL="http://localhost:8080" \
+        -e ERDDAP_adminEmail="set_via_container_env@example.com" \
+        axiom/docker-erddap
+    ```
+
+    **Depending on your container environment, it may pass in it's own environment variables relating to your resources. Potentially there could be a collision with the `ERDDAP_*` config variables if any of your resources start with ERDDAP.**
 
+3. Configure using a shell script
 
-2.  Mount your own `bigParentDirectory`:
+    You can mount a file called `config.sh` to `${CATALINA_HOME}/bin/config.sh` that sets any ERDDAP configuration environmental variables you want to use. This is sourced in the container-provided `setenv.sh` file and and all variables will be exported to be used by ERDDAP for configuration. These will take precedence over environmental variable specified when running the container (see above).
 
     ```bash
     $ docker run \
+        -p 8080:8080 \
+        -e ERDDAP_adminEmail="overridden_by_config_file@example.com" \
+        -v /path/to/your/config.sh:/usr/local/tomcat/bin/config.sh \
+        ... \
+        axiom/docker-erddap
+    ```
+
+    where `config.sh` contains any of the ERDDAP environmental configuration variables:
+
+    ```sh
+    ERDDAP_adminEmail="this_is_used@example.com"
+    ```
+
+    You can set any number of configuration variables in the config.sh.
+
+    ```bash
+    ERDDAP_bigParentDirectory="/erddapData/"
+    ERDDAP_baseUrl="http://localhost:8080"
+    ERDDAP_baseHttpsUrl="https://localhost:8443"
+    ERDDAP_flagKeyKey="73976bb0-9cd4-11e3-a5e2-0800200c9a66"
+
+    ERDDAP_emailEverythingTo="nobody@example.com"
+    ERDDAP_emailDailyReportsTo="nobody@example.com"
+    ERDDAP_emailFromAddress="nothing@example.com"
+    ERDDAP_emailUserName=""
+    ERDDAP_emailPassword=""
+    ERDDAP_emailProperties=""
+    ERDDAP_emailSmtpHost=""
+    ERDDAP_emailSmtpPort=""
+
+    ERDDAP_adminInstitution="Axiom Docker Install"
+    ERDDAP_adminInstitutionUrl="https://github.com/axiom-data-science/docker-erddap"
+    ERDDAP_adminIndividualName="Axiom Docker Install"
+    ERDDAP_adminPosition="Software Engineer"
+    ERDDAP_adminPhone="555-555-5555"
+    ERDDAP_adminAddress="123 Irrelevant St."
+    ERDDAP_adminCity="Nowhere"
+    ERDDAP_adminStateOrProvince="AK"
+    ERDDAP_adminPostalCode="99504"
+    ERDDAP_adminCountry="USA"
+    ERDDAP_adminEmail="nobody@example.com"
+    ```
+
+4.  Mount your own `bigParentDirectory`:
+
+    ```bash
+    $ docker run \
+        -p 8080:8080 \
         -v /path/to/your/erddap/bigParentDirectory:/erddapData \
         ... \
         axiom/docker-erddap
@@ -86,11 +176,11 @@ See [these instructions for configuring Tomcat](https://github.com/unidata/tomca
     This is **highly** recommended, or nothing will persist across container restarts (logs/cache/etc.)
 
 
-3.  Specify the amount of memory to be allocated:
+5.  Specify the amount of memory to be allocated:
 
    ``` bash
-
     $ docker run \
+        -p 8080:8080 \
         --env ERDDAP_MIN_MEMORY=4G --env ERDDAP_MAX_MEMORY=8G
         ... \
         axiom/docker-erddap
diff --git a/files/setenv.sh b/files/setenv.sh
index a740bfa..fd7da26 100755
--- a/files/setenv.sh
+++ b/files/setenv.sh
@@ -1,5 +1,17 @@
 #!/bin/sh
 
+if [ -f "${CATALINA_HOME}/bin/config.sh" ];
+then
+    set -o allexport
+    source "${CATALINA_HOME}/bin/config.sh"
+    set +o allexport
+fi
+
+ERDDAP_CONFIG=$(env | grep --regexp "^ERDDAP_.*$" | sort)
+if [ -n "$ERDDAP_CONFIG" ]; then
+    echo "ERDDAP configured with: $ERDDAP_CONFIG"
+fi
+
 # JAVA_OPTS
 MEMORY="${ERDDAP_MEMORY:-4G}"
 NORMAL="-server -d64 -Xms${ERDDAP_MIN_MEMORY:-${MEMORY}} -Xmx${ERDDAP_MAX_MEMORY:-${MEMORY}}"
diff --git a/files/setup.xml b/files/setup.xml
deleted file mode 100644
index 04d5a97..0000000
--- a/files/setup.xml
+++ /dev/null
@@ -1,490 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1" ?>
-<!-- setup.xml contains setup information for ERDDAP.
-When you install ERDDAP on your server, many of the settings can be left as is.
-Settings that you must change when you install ERDDAP on your server are marked "MUST CHANGE".
--->
-<erddapSetup>
-
-<!-- 'logLevel' determines how many diagnostic messages are sent to the log.txt file.
-It can be set to "warning" (the fewest messages), "info" (the default), or "all" (the most messages).
-Diagnostic messages are displayed on some HTML pages if displayDiagnosticInfo (above) is 'true'.
-Diagnostic messages are always written to the [bigParentDirectory]log.txt file (see below).
-At ERD, we set this to 'all' for development and 'info' for releases.
--->
-<logLevel>info</logLevel>
-
-<!-- warName becomes part of the public url, after baseUrl/.
-This should always be 'erddap'.
-If you want to install a second ERDDAP for testing/development,
-see http://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#secondErddap
--->
-<warName>erddap</warName>
-
-<!-- bigParentDirectory is the absolute path on the server (with slash at the end)
-to a directory on a drive with lots of space.
-Create a new directory, outside of the tomcat directory, for this purpose.
-The user that runs Tomcat must have read/write privileges for this directory.
-Subdirectories that will be created by ERDDAP are:
-* datasetInfo (which some datasets use to cache information about the dataset
-   to speed up reloading the dataset in the future),
-* flag (where you can put a file with a datasetID's name to force reloading of
-   that dataset) and
-* cache (which ERDDAP uses to hold cached data files - ERDDAP periodically
-   removes files older than cacheMinutes (see below)).
-The ERDDAP log file (log.txt) will be put in this directory.
-You MUST CHANGE this when you install ERDDAP on your server.
-At ERD, we use '/u00/cwatch/erddap/' for releases.
--->
-<bigParentDirectory>/erddapData/</bigParentDirectory>
-
-<!-- Daily status reports and all error messages are emailed to emailEverythingTo.
-Daily status reports are emailed to emailDailyReportsTo.
-Either of these can be not specified, blank (specified but with no value),
-  a single email address ((e.g., john.doe@noaa.gov),
-  or a comma-separated list of email addresses.
-The first emailEverythingTo email address is more important than the others,
-  e.g., it is used for subscriptions to EDDXxxxFromErddap datasets.
-See the email account settings below.
-You MUST CHANGE these to the appropriate browser administrator for your site.
-
-Whether or not you set up the email system, all potential email messages
-are logged to an emailLogYEAR-MONTH.txt file in the bigParentDirectory.
--->
-<emailEverythingTo>nobody@example.com</emailEverythingTo>
-<emailDailyReportsTo>nobody@example.com</emailDailyReportsTo>
-
-<!-- This lets you specify a regular expression which determines which datasetIDs
-in the datasets.xml file should be loaded.
-The default is ".*", which loads all datasets.
-During development or for other reasons, you might want to use a subset, e.g.,
-"(etopo.*|erdQSu101day|erdMHchla8day|erdGlobecBottle|erdBAssta5day|pmelTaoDySst)",
-so that ERDDAP quickly loads a dataset that you are interested in.
--->
-<datasetsRegex>.*</datasetsRegex>
-
-<!-- If true, when you start up ERDDAP, some types of datasets (e.g.,
-EDDGridFromDap) will used cached information (.dds, .das, etc.) to reload
-very quickly, without contacting the remote server.  The dataset's age
-will be based on when the dataset was reloaded last.  Normally this
-should be true (the default), but set it to false if you want to bypass
-the cached information. -->
-<quickRestart>true</quickRestart>
-
-<!-- If you want to restrict access to some datasets, you need to specify
-the method used for logging on (authentication).
-See the info at http://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#security
-Currently, the options are: "" (logins not supported, the default), "custom", "openid".
-Note that openid login doesn't work when testing with localhost (https://127.0.0.1:8443).
--->
-<authentication></authentication>
-
-<!-- If authentication=google, you must supply your Google Client ID.
-See
-https://developers.google.com/identity/sign-in/web/devconsole-project
-When setting this up, for Authorized JavaScript origins,
-for testing on your computer, use the domain "localhost"
-(e.g., origin=https://localhost:8443),
-not "127.0.0.1" (because Google Sign-In doesn't work with anything
-at that domain).
-This will be a string of about 75 characters, probably starting with
-several digits and ending with .apps.googleusercontent.com .
--->
-<googleClientID></googleClientID>
-
-<!-- If authentication=orcid or oauth2, you must supply your ORCID APP Client ID
-  (which will start with "APP-") and ORCID Client Secret (a hex number with hyphens).
-  Get these by logging into Orcid at https://orcid.org/signin.
-  Then click on "Developer Tools" (under "For Researchers" at the top).
-  Then click on "Register for the free ORCID public API".
-    Name: ERDDAP at [your organization]
-    Website: [your ERDDAP's domain]
-    Description: ERDDAP is a scientific data server. Users need to authenticate with Google or Orcid to access non-public datasets.
-    Redirect URIs: [your ERDDAP's domain]/erddap/loginOrcid.html
-  Then click on the Save icon (looks like a 3.5" disk!).
-    -->
-<orcidClientID></orcidClientID>
-<orcidClientSecret></orcidClientSecret>
-
-<!-- This specifies how you have stored passwords in the roles tags in datasets.xml.
-If you aren't storing any passwords this is irrelevant.
-The options (in order of increasing security) are:
-"plaintext", "MD5", or "UEPMD5" (MD5(UserName:ERDDAP:Password) which is the default).
-You should only use "plaintext" or "MD5" if you need to match values stored
-that way in an external password database.
-See the info at http://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#security
--->
-<passwordEncoding>UEPMD5</passwordEncoding>
-
-<!-- This determines whether datasets that the user doesn't currently have access to
-(because he isn't logged in or because his roles don't allow access)
-should be shown on lists of data sets
-(e.g., from full text search, categorize, view all datasets, ...).
-The options are: "true", or "false" (the default).
-If false, no information about the dataset (even its existence) is shown
-  to users who don't have access to it.
-If true, some information about the dataset (title, summary, etc) is shown
-  to users who don't have access to it.
-  If the user clicks on a link to a dataset he doesn't have access to,
-  he will get an error message and be prompted to log in.
--->
-<listPrivateDatasets>false</listPrivateDatasets>
-
-<!-- baseUrl is the start of the public url, to which "/[warName]" is appended.
-You MUST CHANGE this when you install ERDDAP on your server. For example,
-<baseUrl>http://127.0.0.1:8080</baseUrl>              used for running/testing on your personal computer
-<baseUrl>http://coastwatch.pfeg.noaa.gov</baseUrl>    used for ERD releases (erddap and erddap2)
--->
-<baseUrl>http://localhost:8080</baseUrl>
-
-<!-- This is a variant of <baseUrl> which is used when authentication is active and the user is logged in.
-  In general, you take the <baseUrl>, change "http" to "https", and change/add ":8443".
-  This must begin with "https://".
-  If you make a proxy so that ":8443" isn't needed, you don't need to add it here.
-  This is irrelevant if <authentication> is "".
-  See the instructions at http://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#security
-  For example,
-<baseHttpsUrl>https://127.0.0.1:8443</baseHttpsUrl>                 used for running/testing on your personal computer
-<baseHttpsUrl>https://coastwatch.pfeg.noaa.gov:8443</baseHttpsUrl>  used at ERD for releases (erddap and erddap2)
--->
-<baseHttpsUrl>https://localhost:8443</baseHttpsUrl>
-
-
-<!-- **************************************************************************** -->
-
-<!-- Set 'displayDiagnosticInfo' to true if you want the diagnostic info displayed
-on almost all html pages that ERDDAP generates.
-The info is the same info that is written to the [bigParentDirectory]logs/log.txt file.
-It is best to always leave this as 'false'.
--->
-<displayDiagnosticInfo>false</displayDiagnosticInfo>
-
-<!-- ERDDAP lets you choose between two search engines for full text searches:
-* original (the default) - is the best choice if your ERDDAP has fewer
-  than about 10,000 datasets.  It is very robust and trouble free.
-* lucene - is the best choice for more than about 10,000 datasets.
-  The advantages are that with any number of datasets it works fast
-  and uses very little memory.
-  But there are many things that might go wrong with individual
-  queries and with the whole system.
-  And although its behaviour (the datasets it finds and the order that
-  it ranks them) is almost identical to the original search engine,
-  it has a few quirky, subtle, small differences.
--->
-<searchEngine>original</searchEngine>
-
-<!-- Email account information is used for sending emails to the 'emailEverythingTo'
-and 'emailDailyReportsTo' email addresses above.
-You MUST CHANGE this information when you install ERDDAP on your server since you can't use Bob's account.
-If you don't actually want to send emails, change the emailSmtpHost tag contents to be nothing.
-
-emailPassword is optional; if absent, emails can't be sent to non-local addresses.
-
-emailProperties is a list of additional properties in the form
-  prop1|value1|prop2|value2
-For example, gmail accounts need
-  mail.smtp.starttls.enable|true
-The default is nothing.
-(And for gmail, use emailSmtpPort 587.)
-
-Whether or not you set up the email system, all potential email messages
-are logged to an emailLogYEAR-MONTH.txt file in the bigParentDirectory.
-
-If you can't get ERDDAP to send emails (error = "Connection refused")
-and you are using anti-virus software (e.g., McAfee) make sure McAfee
-"Virus Scan Console : Access Protection Properties :
-Anti Virus Standard Protections :
-Prevent mass mailing worms from sending mail" is un-checked.
--->
-<emailFromAddress>nothing@example.com</emailFromAddress>
-<emailUserName></emailUserName>
-<emailPassword></emailPassword>
-<emailProperties></emailProperties>
-<emailSmtpHost></emailSmtpHost>
-<emailSmtpPort></emailSmtpPort>
-
-
-<!-- Information about the ERDDAP administrator is used for the SOS and WMS servers.
-You MUST CHANGE these to describe your installation.
--->
-<adminInstitution>Axiom Docker Install</adminInstitution>
-<adminInstitutionUrl>https://github.com/axiom-data-science/docker-erddap</adminInstitutionUrl>
-<adminIndividualName>Axiom Docker Install</adminIndividualName>
-<adminPosition>Software Engineer</adminPosition>
-<adminPhone>555-555-5555</adminPhone>
-<adminAddress>123 Irrelevant St.</adminAddress>
-<adminCity>Nowhere</adminCity>
-<adminStateOrProvince>AK</adminStateOrProvince>
-<adminPostalCode>99504</adminPostalCode>
-<adminCountry>USA</adminCountry>
-<adminEmail>nobody@example.com</adminEmail>
-
-<!-- Normally, if you have a EDDGridFromErddap or EDDTableFromErddap
-dataset in your datasets.xml, it will try to subscribe to the remote
-ERDDAP dataset so that the local dataset is kept perfectly up-to-date.
-If this ERDDAP is not publicly accessible (http://localhost), or its
-IP address will change soon, or you have some other reason,
-you can tell this ERDDAP to not try to subscribe to the remote
-ERDDAP datasets by setting this to false. (default=true)
-This is the overall setting for this ERDDAP. It can be overridden by
-the same tag (with a different value) in the datasets.xml chunk for
-a given EDD...FromErddap dataset.
-For each fromErddap dataset that doesn't subscribe to the remote
-ERDDAP dataset, you should set <reloadEveryNMinutes> to a smaller
-number so that the local dataset stays reasonably up-to-date. -->
-<subscribeToRemoteErddapDataset>true</subscribeToRemoteErddapDataset>
-
-<!--
-These default accessConstraints, fees, and keywords are used by
-  ERDDAP's SOS, WCS, and WMS services.
-accessConstraints and fees are the defaults for dataset's without an
-  "accessibleTo" tag.
-accessRequiresAuthorization is the default "accessConstraints" for dataset's
-  with an "accessibleTo" tag.
-keywords should describe this ERDDAP's data in a general way and be comma-separated.
-"accessConstraints", "fees", "keywords" can be overwritten by same-named
-  attributes in a dataset's global attributes in datasets.xml.
--->
-<accessConstraints>NONE</accessConstraints>
-<accessRequiresAuthorization>only accessible to authorized users</accessRequiresAuthorization>
-<fees>NONE</fees>
-<keywords>earth science, atmosphere, ocean, biosphere, biology, environment</keywords>
-
-<!-- This appears on the erddap/legal.html web page after the General Disclaimer.
-You can replace any of the [standardParts] with your own HTML.
-[standardContact] references the adminEmail specified above. -->
-<legal><![CDATA[
-[standardDisclaimerOfEndorsement]
-[standardDisclaimerOfExternalLinks]
-[standardPrivacyPolicy]
-[standardDataLicenses]
-[standardContact]
-]]></legal>
-
-<!-- Specify the default units standard (e.g., "UDUNITS" (the default) or "UCUM")
-  that you (the ERDDAP admin) are using to specify units.
-  The value is case-sensitive.
-  This is used by ERDDAP's SOS server to determine if the units need to be
-  converted to UCUM units for WMS and SOS GetCapabilities responses.
--->
-<units_standard>UDUNITS</units_standard>
-
-<!-- ERDDAP automatically generates FGDC and ISO19115 metadata
-for all relevant datasets, using information from the dataset's metadata.
-By default these services are on (true). -->
-<fgdcActive>true</fgdcActive>
-<iso19115Active>true</iso19115Active>
-
-<!-- The default for filesActive is "true". -->
-<filesActive>true</filesActive>
-<!-- This sets the default <accessibleViaFiles> for all of the datasets.
-     Before ERDDAP v.2.10, this tag didn't exist and the hard-coded setting was 'false'. -->
-<defaultAccessibleViaFiles>true</defaultAccessibleViaFiles>
-
-<!-- The default for dataProviderFormActive is "true". -->
-<dataProviderFormActive>true</dataProviderFormActive>
-
-<!-- For the wms examples, pick one of your grid datasets that has longitude and latitude axes.
-The sample variable must be a variable in the sample grid dataset.
-The bounding box values are minx,miny,maxx,maxy.
-The default for wmsActive is "true".
--->
-<wmsActive>true</wmsActive>
-<wmsSampleDatasetID>erdBAssta5day</wmsSampleDatasetID>
-<wmsSampleVariable>sst</wmsSampleVariable>
-<!-- The bounding box values are minLongitude,minLatitude,maxLongitude,maxLatitude.
-   Longitude values within -180 to 180, or 0 to 360, are now okay. -->
-<wmsSampleBBox>0,-75,360,75</wmsSampleBBox>
-
-<!-- ERDDAP has a service that lets remote users set a flag
-to notify ERDDAP to try to reload a dataset.
-These requests use a key which is generated based
-on baseUrl/warName, a datasetID, and flagKeyKey.
-*** CHANGE THIS ONCE, to any text (a favorite quote? random text? It doesn't matter).
-Normally, you won't ever change this again.
-But if you you think someone is abusing the flag system,
-change this text again, restart ERDDAP, and send
-all of the users of the flag system the relevant new flagKeys
-(see the list in the Daily Report). -->
-<flagKeyKey>73976bb0-9cd4-11e3-a5e2-0800200c9a66</flagKeyKey>
-
-<!-- ERDDAP has an email/URL subscription system which sends a user an email
-or pings a url whenever an interesting dataset changes.
-(This is different from the RSS system, which is always active.)
-The system relies on the server being able to send out
-emails to people to validate their subscription requests.
-The emails appear to come from the emailFromAddress below.
-So if your server can't send out emails, don't make this system active.
-You may choose (for whatever reason) to make this system active or not,
-so valid values below are "true" (the default) and "false".
-Note that if you change this and restart ERDDAP, the list of subscriptions
-(in [bigParentDirectory]/subscriptionsV1.txt) isn't affected.
-See also the subscriptionEmailBlacklist in datasets.xml.
--->
-<subscriptionSystemActive>true</subscriptionSystemActive>
-
-<!-- ERDDAP has converters for time, keywords, units, FIPS codes, etc.
-([domain]/erddap/convert/index.html).
-You may make this system active ("true", the strongly-encouraged default value)
-or not ("false").
--->
-<convertersActive>true</convertersActive>
-
-<!-- ERDDAP has a slide sorter ([domain]/erddap/slidesorter.html).
-You may make this system active ("true", the default value) or not ("false").
--->
-<slideSorterActive>true</slideSorterActive>
-
-
-
-<!-- Every loadDatasetsNMinutes (see below), files in [bigParentDirectory]cache and
-the public directory which are more than cacheMinutes old will be deleted.
-At ERD, we use '60'.
-Note that when a dataset is reloaded, all files in the [bigParentDirectory]cache/[datasetID]
-directory are deleted.
-In general, only image files are cached, because the same images are often requested repeatedly.
-Removing files in the cache based on age (not Least-Recently-Used)
-ensures that files won't stay in the cache very long.
-Although it might seem like a given request should always return the same response,
-that isn't true.
-For example, a tabledap request which includes time>someTime will change
-if new data arrives for the dataset.
-And a griddap request which includes [last] for the time dimension will change
-if new data arrives for the dataset.
--->
-<cacheMinutes>60</cacheMinutes>
-
-<!-- This specifies the fewest minutes between checks if the datasets
-need to be reloaded.
-If a given run of loadDatasets takes less than this time,
-the loader just looks at the flag directory and/or sleeps
-until the remaining time has passed.
-The default is 15 minutes, which should be fine for almost everyone.
-No matter what, each dataset won't be reloaded more often than its
-reloadEveryNMinutes value as specified in datasets.xml.
-
-The only disadvantage to setting this to a smaller number is that
-it will increase the frequency that ERDDAP retries datasets that aren't
-loading. If there are lots of such datasets and they are retested frequently,
-the data source might consider it pestering/aggressive behaviour.
--->
-<loadDatasetsMinMinutes>15</loadDatasetsMinMinutes>
-
-<!-- This specifies the most minutes that reloading datasets is allowed to take
-(before the loadDatasets thread treated as "stalled" and is interrupted).
-In general, this should be set to at least twice as long as you reasonably
-think that reloading all of the datasets (cumulatively) should take
-(since computers and networks sometimes are slower than expected)
-This should always be much longer than loadDatasetsMinMinutes.
-The default is 60 minutes.  Some people will set this to longer.
--->
-<loadDatasetsMaxMinutes>240</loadDatasetsMaxMinutes>
-
-<!-- If the number of requests between two runs of LoadDatasets exceeds
-unusualActivity, an email is sent to emailEverythingTo.
-The default is 10000.
--->
-<unusualActivity>10000</unusualActivity>
-
-<!-- The title for the map's legend (or nothing if you don't want a legend title).
-At ERD, we don't use these.  To use these, uncomment them.
-<legendTitle1>NOAA ERD's</legendTitle1>
-<legendTitle2>ERDDAP</legendTitle2>
--->
-
-<!-- The highRes and lowResImagefiles are used for map and graph legends
-(if legendTitle1 and legendTitle2 aren't "") and
-are scaled to the desired size (highRes->80 or 40 pixels square, lowRes->20 pixels square).
-The googleEarthLogoFile is displayed at its original size in the lower left
-corner of the Google Earth map if the user selects the .kml image file type.
-The highRes, lowRes and GoogleEarth images are also used by OpenSearch.
-The questionMarkImage identifies the places on HTML pages where a user can
-mouseOver to get more information.
-These files must be in [tomcat]/content/erddap/images/ directory.
-All files in this directory (and subdirectories)
-will be copied to [tomcat]/webapps/erddap/images (and subdirectories)
-and thus made available for direct downloading by any client.
-(Any text files must be stored as plain ASCII (7 bit) or with UTF-8 encoding.)
-For SGT graphics, currently, the Files designated below must be png, gif, jpg, or bmp.
-If you want to substitute other image files, it is best to make them
-a similar number of pixels wide and high.
--->
-<highResLogoImageFile>noaa_simple.gif</highResLogoImageFile>
-<lowResLogoImageFile>noaa20.gif</lowResLogoImageFile>
-<googleEarthLogoFile>nlogo.gif</googleEarthLogoFile>
-<questionMarkImageFile>QuestionMark.jpg</questionMarkImageFile>
-
-<!-- The font family to be used for all of the text in images.
-"SansSerif" (the default) is always a valid and reasonable option.
-A list of valid font families is printed to the log by the SGT constructor.
-SansSerif is fine on Windows.  I think it translates to Arial.
-I didn't like any of the fonts initially available on Linux. "SansSerif" is almost ok.
-At ERD, we use "Bitstream Vera Sans"
-  (open source fonts from http://www.gnome.org/fonts/ ).
-  I think they are distinctly better than the standard Linux fonts.
-  To use them on your computer, download
-  http://coastwatch.pfeg.noaa.gov/erddap/download/BitstreamVeraSans.zip
-  and unzip the files into [javaHome]/jre/lib/fonts so Java sees them.
--->
-  <fontFamily>DejaVu Sans</fontFamily>
-
-<!-- When possible (and it isn't always possible), ERDDAP breaks source data requests
-into chunks to conserve memory. See the description of these tags in messages.xml.
-You can override the default chunk sizes here with
-  For grids:  <partialRequestMaxBytes>100000000</partialRequestMaxBytes>
-  For tables: <partialRequestMaxCells>100000</partialRequestMaxCells>
--->
-
-<!-- If variablesRequireIoosCategory is true, all variables for all datasets must
-have an "ioos_category" attribute defined (in sourceAttributes or addAttributes)
-with a value from EDV.IOOS_CATEGORIES.
-If you are affiliated with NOAA, you should set this to "true"
-because the NOAA IOOS office wants to be able to categorize variables and
-datasets in this way.
-For non-NOAA ERDDAP installations, there is no downside to setting this to "false".
--->
-<variablesMustHaveIoosCategory>true</variablesMustHaveIoosCategory>
-
-<!-- This is the comma-separated list (recommended: in alphabetical order)
-of the global attribute and variable attribute names which will be
-used to categorize the datasets and shown to clients at urls like .../erddap/categorize/ioos_category/index.html
-(ioos_category is unusual, but is used at ERD).
-If an attribute is a global attribute, identify it by prefixing it with "global:".
-"variableName" is a special case: it categorizes the dataVariable destinationNames.
--->
-<categoryAttributes>global:cdm_data_type, global:institution, ioos_category, global:keywords, long_name, standard_name, variableName</categoryAttributes>
-
-<!-- drawLandMask specifies the default Make A Graph setting for whether the
-landmask should be drawn "over" or "under" surface data on maps.
-"over" is recommended for primarily oceanographic data
-(so that grid data over land is obscured by the landmask).
-"under" is recommended for all other data.
-(This used to be called 'drawLandMask' (still supported).)
--->
-<drawLandMask>under</drawLandMask>
-
-<!-- This is the short description of ERDDAP, which is used on the middle of the
-left side of ERDDAP's home page.
-This can refer to &erddapUrl;, &requestFormatExamplesHtml; &resultsFormatExamplesHtml; and
-[standardShortDescriptionHtml] (from messages.xml).
-If your ERDDAP allows users to log in, all referenced image files, etc.
-  must be in [tomcat]/content/erddap/images or a subdirectory
-  and must be referenced here with &erddapUrl;/images/[fileName].
-If you don't use [standardShortDescriptionHtml], at least include a link like:
-(<a href="&erddapUrl;/information.html">More detailed information about ERDDAP</a>)
-All of the information in [standardShortDescriptionHtml] is also contained in
-<theLongDescriptionHtml> in messages.xml.
--->
-<theShortDescriptionHtml><![CDATA[
-<h1>ERDDAP</h1>
-ERDDAP (the Environmental Research Division's Data Access Program)
-is a data server that gives you a simple, consistent way to download
-subsets of scientific datasets in common file formats and make graphs and maps.
-This particular ERDDAP installation has oceanographic data
-(for example, data from satellites and buoys).
-
-[standardShortDescriptionHtml]
-
-]]></theShortDescriptionHtml>
-
-
-</erddapSetup>