Page :« 1 2 3 4 ALL»

References Cited

COAHP (Colorado Office of Archeology and Historic Preservation)

• 1994 Cultural Resource Programs Compilation of programs of Rocky Mountain and Great Plains States Colorado Historical Society, Office of Archeology and Historic Preservation

Ebert and Associates, Inc.

• 1994 Generally Applicable Methods and Techniques for Conversion of Existing State Cultural Resource Archives to Geographic Information Systems Databases Proposal submitted to National Science Foundation

National Park Service

• nd How to Apply National Register Criteria for Evaluation, National Register Bulletin 15

• nd How to Evaluate and Nominate Designed Historic Landscapes, National Register Bulletin 18.

• nd Guidelines for Evaluating and Documenting Rural Historic Landscapes, National Register Bulletin 30.

• nd Guidelines for Evaluating and Documenting Traditional Cultural Properties, National Register Bulletin 38.

Wood, Noriko

• 1990 Computer Use in State Historic Preservation Offices Interagency Resources Division, Natiopnal Park Service, Washington, DC.

Appendix 1: FGDC Press Release

The United States Geological Survey Federal Geographic Data Committee (FGDC) has awarded $32,150 to the Wyoming State Historic Preservation Office to develop a metadata standard for cultural resources in the western United States. Cultural resources consist of archeological and historical sites, buildings, and historic districts. The Earth Data Analysis Center (EDAC) and the New Mexico SHPO are principal participants and co-sponsors of this project.

Metadata are “data about data.” Metadata describes the content, quality, condition, and characteristics of digital data sets. Metadata are used by potential data users, often through spatial data clearinghouses accessed over the Internet, to determine whether or not the information is appropriate for their application, and how to obtain the dataset. Metadata helps to protect an agency’s investment in digital data.

The project will be conducted in conjunction with historic preservation agencies in eight other western states’ the New Mexico State Historic Preservation Office, the Colorado State Historic Preservation Office, the University of Montana Department of Anthropology, the Montana State Historic Preservation Office, the Archaeology Division of the Arizona State Museum, University of Arizona, the Nevada State Museum, the Idaho State Historic Preservation Office, the Utah State Historic Preservation Office, and the California Office of Historic Preservation.

The project will establish a draft metadata standard to be reviewed by the FGDC Standards working group and will coordinate the development with the FGDC’s Cultural And Demographic Subcommittee. The project will build upon the current FGDC metadata standard and the supplement for geospatially referenced cultural and demographic data metadata.
A training session involving cultural resource managers and archivists will be conducted for the project participants, followed by work on pertinent data elements to include in a cultural resources metadata file. A draft standard document will be prepared for FGDC and public review.

The training session will be conducted by EDAC at the University of New Mexico. EDAC has extensive experience in facilitating and providing training in this area.

This effort is an open collaborative project sponsored by the western States. We encourage those who are interested in participating in the grant work to contact Mary Hopkins (WYSHPO) at 307-766-5324, hopkins@uwyo.edu or Tim Seaman (NMSHPO) 505-827-6347 ext. 531, seaman@arms.state.nm.us.

Appendix 2: FGDC Preliminary Report

http.//colby.uwyo.edu

Appendix 3: SDE Design Details Layer Documentation

ARCH_SURVEY_SMALL (small survey locations)
ARCH_SURVEY_LINE (linear survey locations)
ARCH_SURVEY_POLY(survey boundary polygons)
Attribute Fields:

• ACTIVITY_NUM (key)
• ARMS_ACTIVITY_NUMBER (external key)

Metadata:

• ARCH_SURVEY.USGS_75_TOPO_SGRAPHIC_FLG
• ARCH_SURVEY.GPS_SGRAPHIC_FLG
• ARCH_SURVEY.OTHER_TOPO_SGRAPHIC_DESC
• ARCH_SURVEY.RECT_AERIAL_SGRAPHIC_DESC
• ARCH_SURVEY.UNRECT_AERIAL_SGRAPHIC_DESC
• ARCH_SURVEY.SKETCH_MAP_SGRAPHIC_DESC
• ARCH_SURVEY.OTHER_SGRAPHIC_DESC

Shape Masks:
ARCH_SURVEY_SMALL: polygons only multiple (unioned) polygons OK
ARCH_SURVEY_LINE: lines only multiple (unioned) lines OK
ARCH_SURVEY_POLY polygons only– multiple (unioned) polygons OK
Index Grid Size: 25,000 meters
Coordinate System: UTM Zone 13: NAD27

ARCH_SITE_CENTROID (Site Centroids)
Attribute Fields:

• ARCH_SITE_CENTROID.ARCH_SITE_NUM (internal key)
• ARCH_SITE_CENTROID ARMS_ARCH_SITE_NUMBER (external key)

Metadata:

• ARCH_SITE_LOCATION.USGS_75_TOPO_SGRAPHIC_FLG
• ARCH_SITE_LOCATION GPS_SGRAPHIC_FLG
• ARCH_SITE_LOCATION.OTHER_TOPO_SGRAPHIC_DESC
• ARCH_SITE_LOCATIONLRECT_AERIAL_SGRAPHIC_DESC
• ARCH_SITE_LOCATION UNRECT_AERIAL_SGRAPHIC_DESC
• ARCH_SITE_LOCATION.OTHER_SGRAPHIC_DESC

Shape Mask: single points Only
Index Grid Size: 100,000 meters
Coordinate System: UTM Zone 13 NAD27
Required update functions and dependencies:
1-to-1 relationship with ARCH_SITE_LOCATION (mandatory relation for all rows with valid UTM coordinates)

with ARCH_SITE_LOCATION (Registration Application must add new record; changes in ARCH_SITE_CENTROID will require update of ARCH_SITE_LOCATION).

• ARCH_SITE_LOCATION.UTM_ZONE (reprojection required for Zone 12)
• ARCH_SITE_LOCATION. UTM_EASTING (reprojection required for Zone 12)
• ARCH_SITE_LOCATION.UTM_NORTHING

ARCH_SITE_BOUNDARY (Site Boundaries)
Attribute Fields:

• ARCH_SITE_BOUNDARY ARCH_SITE_NUM (internal key)
• ARCH_SITE_BOUNDARY ARMS_ARCH_SITE_NUMBER (external key)
• ARCH_SITE_BOUNDARY ACTIVITY_NUM (foreign key ACTIVITY; nullable for legacy data.]

Metadata:

• ARCH_SITE_BOUNDARY.BOUNDARY_TYPE (see illustration):
  NULL– null shape (no length available boundaries undefined)
  LEGACY buffered centroid (length=buffer radius)
  SMALL buffered centroid (length
• ARCH_SITE_BOUNDARY BOUNDARY_SOURCE:
  7 5’_TOPO 1:24,000 scale USGS topographic map
  GPS_POOR –positional accuracy (std dev.) >100 meters
  GPS_GOOD –positional accuracy (std dev) 10- 100 meters
  GPS_EXCELLENT positional accuracy (std dev.) 1 – 10 meters GPS_SUBMETER positional accuracy (std dev) < 1 meter
  SKETCH_MAP specify scale in BOUNDARY_SOURCE_NOTES OTHER_SOURCE identify source and scale in BOUNDARY_SOURCE_NOTES
• ARCH_SITE_BOUNDARY.BOUNDARY_SOURCE_NOTES (text field)
• ARCH_SITE_PHY_DESC.SITE_BOUNDARY_COMPLETE_FLG
• ARCH_SITE_PHY_DESC.SITE_BOUNDARY_INCOMPLETE_FL
• ARCH_SITE_PHY_DESC.INCOMPLETE_SITE_BOUNDARY_DESC

Shape Mask: polygons only multiple (unioned) polygons OK
Index Grid Size: Undetermined
Coordinate System: UTM Zone 13: NAD27
Required update functions and dependencies:
Changes in ARCH_SITE_BOUNDARY will require changes in ARCH_SITE_PHY_DESC when BOUNDARY_SOURCE= GPS_G00D (or better) or SKETCH_MAP:

• ARCH_SITE_PHY_DESC.MAXIMUM_SITE_LENGTH
• ARCH_SITE_PHY_DESC MAXIMUM_SITE_WIDTH
• ARC_SITE_PHY_DESC.SITE_AREA
• ARCH_SITE_PHY_DESC.SITE_DIMENSIONS_MEASURED_FLG (not null)
• ARCH_SITE_PHY_DESC SITE_AREA_MEASURED_FLG (not null)

Changes in ARCH_SITE_BOUNDARY will require recomputation of ARCH_SITE_CENTROID coordinates

NMCRIS Site Boundary Types

Appendix 4: SDE Design Details — ArcView Data Entry Application

Buttons retaining original function:
Save
Help
Zoom to active theme Zoom out
Zoom in
Clear selection

Buttons with customized functions:

Connect

:Fires off the master AVENUE script and connects to SDE

Zoom to Active DRG

: Zooms view to the extent of active DRG(s)

Edit

: Clones the active SDE theme into a theme named “Checked Out Features”

Union

: Unions all features based on a common external Id number

Verify

: Invokes an interactive process the get user input if the external ID number then performs a SQL query to return a verification report

Save $

: Commits the changes to the database

Undo Edit

: Removes any changes made to the “Checked Out Features” theme and deletes the theme from the view.

Clear View

: Clears the view of all themes

Erase

: Combines the Undo Edit and the Clear View buttons

Tools retaining original functions:
Identify Select
Vertex edit
Zoom In
Zoom Out
Pan
Drawing tools

• Point
• Line
• Split line
• Polygon
• Split polygon
• Append polygon

Tools with new or modified functions:
Select by rectangle:Modified to keep the selection rectangle graphic showing in the view
Select by polygon:Modified to keep the selection polygon graphic showing in the view
Drawing tools Diamond:Creates a diamond shape for representing surveys under 2.5 acres.

SDE Editing Schema

1. User selects USGS quad(s) from pick list

2. If not previously copied locally, user is prompted to load appropriate CDROM and the quad is copied locally.
3. User logs in to SDE

4. User selects the SDE layer(s) to be edited

5. Application spatially selects features from the SDE layer(s) based on the merged extent polygon of the selected USGS quad(s)
6. User selects the SDE layer to checkout for editing

7. Application creates a spatial lock to prevent editing conflict, clones the recordset for editing, and loads the cloned theme into the view.

8. User zooms to the area of interest.

9. User performs the edit

1. Add new feature
   1. Digitizes new feature with the appropriate drawing tool
   2. Attribute and verify the record
      User enters the external ID number
      Application returns a report of the record for verification
      If verification is correct, application attributes the internal ID number
   3. If necessary, user unions multiple shapes into one record
2. Modify existing shape Same as adding shape
3. Deleting shape
   User selects and deletes exiting shape

10. User saves edits and application commits transaction to database

1. Application checks and verifies record and if ok commits
2. If not ok then record is written to error shapefile

11. User either ends session and disconnects from SDE or selects next SDE layer to edit by looping back to step 6

Appendix 5: SDE Design Details — “C” API Query Application

NMCRIS Spatial Database Access Program Testing Notes

ASSUMPTIONS:

1. The owner of all layers is sde, the owner of all non-sde tables is ops$nmcris
2. All users will have $SDEHOME/Iib added to their LD_LIBRARY_PATH environment variable
3. All testers will have SELECT,UPDATE,INSERT,DELETE access to the following sde layers:
   INPUT_POINTS, INPUT_LINES, INPUT_POLYGONS, INPUT_POINTS 12, INPUT_LINES 12, INPUT_POLYGONS 12, BUFFERED_POLYGONS, BUFFERED_POLYGONS 12, CLIPPED_POLYGONS, QUERY_POLYGONS, REPROJECTED_POLYGONS
4. All users and testers will have SELECT access to the following tables and layers:
   SURVEY_SMALL, SURVEY_LINE, SURVEY_POLY, SITE_POINT, ARCH_SITE_LINK, QUAD_INDEX,
   ARC_SURVEY_QUAD.
5. The users unix account name is the same as their database user name.

TESTING INSTRUCTIONS

1. To create an executable, cd to the source code directory and type
   • % make: which runs the Makefile.

   Type

   • % make clean: to erase all .0 files and the executable and rebuild the executable
2. Alter Makefile for testing or operations
   • To set up for testing mode: CFLAGS = -Dunix ${INCLUDE} -DTESTING
   • for normal mode remove –DTESTING CFLAGS = -Dunix ${INCLUDE}
3. Start the program by typing
   • % spatial: for interactive data input
   • % spatial: for data input from an input file
4. If you are doing interactive input, the program will save user input into a file called inputData.txt. The
   program will check if the inputData txt file already exists If the file exists, the user will be asked if they want
   to overwrite the file. It will exit if they type anything but a word starting with ‘or a carriage return
5. The program check for the following:

Main Menu

• Valid Letter Typed (1-6)
• Letter Typed

• Zone
  1. Valid zone typed “12″ or “13″

Page :« 1 2 3 4 ALL»

pages: 1 2 3 4