ArcGIS-generated fields and AASG content model fields order and type
When deploying your service using ArcMap products, two fields are automatically generated. These are the OBJECTID and SHAPE fields. The XML schemas (http://schemas.usgin.org/schemas/) that are associated with each AASG content model have a very specific ordering of the fields from that content model, and included in this specific order are the ArcMap-generated fields.
To acheive validation of your WFS service, and for your service's data to be interoperable and available within the system, the fields must be in the specific spelling, order, and data type that are assigned in the XML schema. These are usual errors we find when checking the WFS validation of hosted services.
Even though every content model has different fields, the ArcMap-generated fields are reliably in the same place in the field order. OBJECTID must come just before all the content model fields, and SHAPE must come directly after all the content model fields. (A "lax" function does allow Shape_length or Shape_Area or other fields to come after SHAPE field.)
If a field (or element) is causing your WFS service to fail validation, and you have checked to see that the field is in the correct order and spelling as assigned by the XML schema, the data type may be incorrect. The assigned data types are given in each Excel content model workbook under the FieldList tab in the DataType column. These are also given in the XML schema itself, just next to each element (or field heading):
<xs:element name="WellName" type="xs:string"/>
<xs:element name="OtherID" type="xs:string" minOccurs="0"/>
<xs:element name="DrillerTotalDepth" type="xs:double"/>
The above shows that the element WellName is a string, which can consist of any alphanumeric character set. The same is true for OtherID, though the minOccurs=0 tells you that this feild is not required; this means that the field heading does not need to have data filled in to validate, whereas all the required fields must have every record in the data filled in. The DrillerTotalDepth element shows a data type of double, meaning that the data in this field must be a number.
If your dataset is missing data for some fields that are required, the FeildList tab of the Excel content model workbook can guide you as to if the field is non-nillable, meaning data must be filled in for that dataset (in that specific content model) to be appropriate for service and useful in the Geothermal Project. If the field is nillable, the terms "Missing" or "Unknown" may be used for 'string' data type fields, and "-999" may be used for 'double' numeric fields.