Web Service and Layer Naming Conventions
The AASG State Geothermal Data project provides OGC (Open Geospatial Consortium, opengeospatial.org/standards) compliant WMS and WFS services per the specifications outlined by the USGIN (see the USGIN site for more detials). AASG adopted the requirements and recommendations of USGIN for networking, data sharing, and enhanced interoperability. Such recommondations include naming conventions; the following outlines AASG-adopted naming conventions which require a specific format for naming Web Services and the Layers that contain the data within that service.
The ArcMap project (.mxd) used for your AASG Web Feature and Web Map Services will have a title for the data frame (the first element in ArcMap layer tree which displays a layer or collection of layers) and a title for the layer. The data frame title shows as "Map Name" on an ArcMap service rest page. Of particular importance is the layer name, which is used as a building block in the WFS Get Feature request. Without proper layer name, the service will fail to validate (see group post on Validating Web Services).
Data Frame Naming Conventions
The data frame title must be a concatenation of the abbreviation of the state represented by the data as well as the service type. The service type will be the same as the name of the AASG content model used to prepare the data (see http://www.stategeothermaldata.org/data_delivery). These concatenated names may not contain spaces or other characters and must be plural. Also be aware of capitolization. Data Frame naming examples include:
Layer Naming Conventions
Layers are generally identical to the name of the content model used for the data. Here, the name is NOT pluralized and does NOT specify the state. Layer name examples include:
For Chemistry (aqSpringChemistry and aqWellChemistry) content models and services, more than one layer may be used. Those layer names are as follows: