Editing Process for Treatments

 

Files created: abyss\\sts\mm01\project\treatments\trt_mm01.shp and ..\trt_mm01_<datestamp>.shp; this second file is zipped up into viner\sts\decisionmodel\shapefiles\ trt_mm01_<datestamp>.zip
  1. Files sent in from agencies: In the best of all possible worlds, agencies will ftp or email in treatment shapefiles made with Digimatic, in Albers 8. These will have standardized field definitions.
    2.

    Alias

    Type

    Precision

    Width

    Indexed

    Shape

    FIELD_SHAPEPOLY

    0

    8

    true

    Idgis

    FIELD_CHAR

    0

    9

    false

    Blockname

    FIELD_CHAR

    0

    32

    false

    Priority

    FIELD_DECIMAL

    2

    5

    false

    Ppa_id

    FIELD_DECIMAL

    0

    4

    false

    Trttype

    FIELD_CHAR

    0

    32

    false

    Agency

    FIELD_CHAR

    0

    10

    false

    Acres

    FIELD_DECIMAL

    3

    16

    false

    Notes

    FIELD_CHAR

    0

    128

    false

    County

    FIELD_CHAR

    0

    32

    false

    State

    FIELD_CHAR

    0

    25

    false

    Quad

    FIELD_CHAR

    0

    41

    false

    Apps

    FIELD_DECIMAL

    0

    1

    false

    Dosage

    FIELD_CHAR

    0

    10

    false

    Sourcethm

    FIELD_CHAR

    0

    64

    false

  2. Initial scans: Look for spelling errors, if any, and make corrections.
  3. Checking treatment shapefiles that have been changed to Delimiting grids: On occasion (such as with Indiana), treatment shapefiles have been re-classified as delimiting grids. Solution proposed has been to keep one ArcView project for both, and then cut-and-paste entries from shapefile to the other.
  4. Checks finished, we now merge these new shapefiles with master shapefile: Using Xtools Merge Shapefiles, a new shapefile is created. Old records for compared against new for inconsistencies, and then old records are deleted.
  5. Overlay routine is run: Pertinent GIS information (presently, state, county, and quad) are captured from baselayer data and placed in pertinent fields of master file.
  6. Unique ID checked or created: This year’s unique ID is in the form of <state fips no>/<county fips no.>/<unique two digit number for each polygon within county>. E.g.: the first recorded treatment polygon in Henry County, Virginia is 51/089/01. The fifth record polygon in Pitt County, Virginia is 51/143/05.
    7.

 

Vertical Updating: Procedure for partial updating of master shapefile by state.

  1. Existing shapefile is queried by state name (e.g., "Wisconsin" above) and those records are deleted.
  2. New data is merged with old in using an Xtools type of operation to make a new shapefile. For purposes of documentation, an additional field is added, "Sourcethm", that contains the name of the source shapefile for each record.

Horizontal Updating: Procedure for attribute updating from Oracle Web DB.

  1. The datbase administrator provides a text file format of all data read from Oracle Web DB interface.
  2. This text file is added as a table to ArcView project, and a script reads all field names and places them in a list.
  3. Same script deletes all fields from a copy of the master shapefile with same names as those in text file table list, with the exception of the unique ID.
  4. Same script joins text file table to the copy of the master shapefile by unique ID and fixes the joined fields permanently, then removes the joined table.

Potential problems: What would be done when records are added?