USGIN recommendataion is to encode WMS layer names and WFS feature types in a 'parameter' object using JSON syntax (see USGIN_ISO_Metadata.docx, p 73, lines 758-777). The parameters value is a list of key:value pairs enclosed in curly brackets ('{key:"value", key1:"value1"…}'). The keys should be the exact string that is required for the data access request parameter. For example, a dataset distributed through a particular layer in a multi-layer WMS:
<gmd:description>
<gco:CharacterString>
Whatever descriptive text you want.
parameters:{layers:"gtp_datagap_well_data_collection"}
</gco:CharacterString>
</gmd:description>
In the case of a dataset distributed through a particular feature type in a multi-feature WFS:
<gmd:description>
<gco:CharacterString>
Whatever descriptive text you want.
parameters:{ typeName:"BoreholeLithInterval2.0"}
</gco:CharacterString>
</gmd:description>
we need to update the metadata records to include these parameters
USGIN recommendataion is to encode WMS layer names and WFS feature types in a 'parameter' object using JSON syntax (see USGIN_ISO_Metadata.docx, p 73, lines 758-777). The parameters value is a list of key:value pairs enclosed in curly brackets ('{key:"value", key1:"value1"…}'). The keys should be the exact string that is required for the data access request parameter. For example, a dataset distributed through a particular layer in a multi-layer WMS:
In the case of a dataset distributed through a particular feature type in a multi-feature WFS:
we need to update the metadata records to include these parameters