...
- If a shapefile contains multiple pads, roads, pipelines, and other features, it can be batch uploaded as long as it follows these rules:
- Features can be uploaded if they do not already exist in the system but only if this is specified during the upload. Otherwise, the feature name (pad name, road name, etc) must already exist in the system, and the shapefile's use of that name must be identical to the one the system stores
- If the system has a pad named SHB 1-31, the shapefile must name that pad SHB 1-31. Names like "shb1-31", "shb/cor 1-31", and "shb1a-31b" do not match up and will be rejected.
- The Shapefile Data Dictionary (the attributes in the dbf) must conform to the following:
- Name (Character(254)) -- The name of the feature. If this is a Well Pad, this should be the Pad name. If this is a pipeline, this should represent the beginning and end point of the pipeline. This will be unique for an operator.
- FeatType (Character(254)) -- This is the type of feature. Allowed Entries: Well Pad, Road, Pipeline, Other.
- CollDate (Date or Character(254)) -- Date the data was collected; this should represent the date of the observation, not processing. Format = MM/DD/YYYY.
- DistType (Character(20)) -- Allowed Entries: disturbance or reclamation
...
Status Reports
Please see the Data Dictionaries Dictionaries section of the manual which provides the definitions for each field contained within the data forms.
...
- Features can be uploaded if they do not already exist in the system but only if this is specified during the upload. Otherwise, the feature name (pad name, road name, etc) must already exist in the system, and the shapefile's use of that name must be identical to the one the system stores
- If the system has a pad named SHB 1-31, the shapefile must name that pad SHB 1-31. Names like "shb1-31", "shb/cor 1-31", and "shb1a-31b" do not match up and will be rejected
The Shapefile Data Dictionary (the attributes in the dbf) must conform to the following:
...