SOP_23_Spatial_Data_Submittals_04-10.pdf

SOP NO. 23

Standard Operating Procedure For

SPATIAL DATA SUBMITTALS

Denver Federal Center Site-wide RCRA Facility Investigation

Prepared for:

General Services Administration

Rocky Mountain Region Denver, Colorado

Prepared by:

URS Corporation Denver, Colorado

April 2010

Revision 2.0

Denver Federal Center SOPs Revision No. 2.0

April 2010 Page i of iii

SOP NUMBER 23 SPATIAL DATA SUBMITTALS

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-i

1.0 INTRODUCTION ......................................................................................................... 23-1

2.0 ARCVIEW 8 (ESRI ARCGIS) COMPATIBILITY...................................................... 23-1

3.0 SPATIAL DATA FORMAT ......................................................................................... 23-1

3.1 SHAPEFILE (*.shp, *.shx, *.dbf, *.prj) .................................................................... 23-1

3.2 DEFINING SPATIAL REFERENCE INFORMATION .......................................... 23-2

3.2.1 Defining a Shapefile Projection Using ArcCatalog........................................... 23-2

3.2.2 Defining a Shapefile Projection Using ArcToolbox.......................................... 23-4

3.2.3 Reprojecting a Shapefile from One Spatial Reference System to Another ....... 23-6

3.3 NON-VECTOR DATA ............................................................................................. 23-8

3.4 SAVING A LAYER FILE REPRESENTATION (*.lyr) OF EACH DATA

SOURCE.................................................................................................................... 23-8

4.0 FILE NAMING CONVENTIONS ................................................................................ 23-9

4.1 PREFIX – CATEGORY ............................................................................................ 23-9

4.2 NAME – DESCRIPTION........................................................................................ 23-10

4.3 SUFFIX – SERIES, VERSION, SOURCE ............................................................. 23-10

5.0 DIRECTORY STRUCTURE ...................................................................................... 23-11

5.1 BASEWIDE DATA AND MAP DOCUMENTS.................................................... 23-11

5.1.1 CAD and Image Files....................................................................................... 23-11

5.1.2 Project-specific Data........................................................................................ 23-11

6.0 DATA DICTIONARY................................................................................................. 23-12

7.0 METADATA ............................................................................................................... 23-12

7.1 ARCCATALOG-BASED XML FORMAT ............................................................ 23-12

7.2 SPATIAL REFERENCE INFORMATION MUST BE DEFINED........................ 23-13

7.3 MINIMUM REQUIREMENTS............................................................................... 23-14

8.0 MAP DOCUMENT ..................................................................................................... 23-14

8.1 THE MAP DOCUMENT (*.mxd)........................................................................... 23-14

8.2 USE ONLY APPROVED MAP TEMPLATES (*.mxt) ......................................... 23-15

8.3 USE ONLY APPROVED MAP STYLES (*.style) ................................................ 23-15

9.0 IMPORTING ARCVIEW 3.X PROJECTS INTO ARCVIEW 8................................ 23-16

9.1 METHOD 1. IMPORTING BY LAYOUT ............................................................. 23-17

9.2 METHOD 2. IMPORTING SELECTED VIEWS................................................... 23-17

9.3 CORRECTING IMPORT ERRORS ....................................................................... 23-18

April 2010 Page ii of iii

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-ii

List of Attachments Attachment A Denver Federal Center Basemap CD

Attachment B Data Dictionary

April 2010 Page iii of iii

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-iii

REVISION LOG

Revision Number Description Date

1.1 SOP No. 23 (prepared by Denver Federal

Center)

September 2002

2.0 SOP No. 23 April 2010

April 2010 Page 23-1 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-1

1.0 INTRODUCTION

This manual provides detailed instructions to allow contractors to submit spatial data to GSA in a format that can be used directly in GSA software and filing structure. All contractors will be provided with this document before contract initiation. A CD accompanies this document that includes approved map templates, styles, and DFC installation-wide spatial data adhering to the directory structure and file naming conventions outlined. (See Attachment A for more information about the DFC Basemap CD.) No contractor will be allowed to submit any spatial data developed without adhering to the rules described in this document, unless agreed to before contract initiation.

APPLICATION of SOP 23 This manual applies to all deliverables submitted by a contractor to GSA. This includes but not limited to all Draft Final, Final Reports/Documents, etc. Should the contractor include these costs in the Final Document submittal and the final document submittal is not required or requested, or in a timely manner for the project, the contractor will submit this EDD to GSA in this format. In addition, the contractor must generate the projects in 8.* and not 3.* for submittal to GSA. Should the contactor generate the project in 3.* then all functionality of a 8.* project must be created such that labels, etc. are associated with the layers and not included as graphics.

2.0 ARCVIEW 8 (ESRI ARCGIS) COMPATIBILITY

All data submitted must adhere to the requirements described below to allow it to be viewed and manipulated in ESRI ArcView 8.X GIS. ArcView 8 is a member of the ESRI ArcGIS family of software products that enables GSA to use GIS for field, office, database, and internet-based applications. By providing GSA with data already prepared for use in ArcView 8, the contractor will enable GSA personnel to maximize work efficiency and more easily build new information by comparing and combining data from various submissions and contractors.

ArcView 8 consists of three separate, but integrated, applications: ArcCatalog, ArcMap and ArcToolbox. ArcCatalog is used to manage data in a Microsoft Windows Explorer-like environment. ArcCatalog functions include previewing and searching for data, generating and reviewing metadata, generating new files for data storage, and organizing folders. ArcMap is used to view, edit, analyze and map data. ArcToolbox includes 20+ tools for data conversion and management and permits batch processing.

3.0 SPATIAL DATA FORMAT

3.1 SHAPEFILE (*.shp, *.shx, *.dbf, *.prj)

All vector data sources (points, lines, or polygons) should be provided in ESRI shapefile format.

ArcView 8 includes conversion tools in ArcCatalog and ArcToolbox that allow some other

April 2010 Page 23-2 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-2 formats to be converted into shapefiles; however, to ensure maximum convertibility, it is best to generate new data directly as shapefiles when possible using ArcMap edit function. A shapefile actually consists of at least three files by the same name in the same directory that have different file extensions:

• <shapefile name>.shp – Map features

• <shapefile name>.shx – Index file to associate map features with attributes

• <shapefile name>.dbf – Tabular, feature attribute information

• <shapefile name>.prj – Spatial reference (projection) information

3.2 DEFINING SPATIAL REFERENCE INFORMATION

All data sources should use the State Plane Coordinate System with the following parameters:

COORDINATE SYSTEM: State Plane

ZONE: Colorado Central (3476), (FIPSZONE : 502)

DATUM: NAD83

SPHEROID: GRS80

UNITS: Feet

Although older versions of ESRI ArcView software do not utilize the *.prj file associated with shapefiles, explicitly defining a shapefile’s spatial reference information is imperative in ArcView 8. Without projection information, a shapefile added to ArcMap produces a warning message and may not work correctly in certain operations. There are two ways to define the projection of a shapefile in ArcView 8: 1) Using ArcCatalog (single shapefile), 2) Using ArcToolbox (multiple files).

3.2.1 Defining a Shapefile Projection Using ArcCatalog

1. Right –click on the shapefile of interest in the ArcCatalog Table of Contents and choose

Properties from the context menu to access the Shapefile Properties dialog.

2. In the Fields tab, choose the record selector left of the Shape name in the list of Field Names.

3. Select the ellipses following the Spatial Reference property in Field Properties to produce the Spatial Reference dialog.

April 2010 Page 23-3 of 23-38

4. If no other spatial data source has yet had its projection defined, it will be necessary to choose the Select…option to select a predefined coordinate system (See 5a). If even one other data source has already had its projection defined that shares the same projection as the new data source to define, choose the Import… option (See 5b).

5a. Browse to the coordinate system definition, usually defined by a coordinate system, datum, units and location parameter (zone) that matches the coordinates the spatial data source is actually using. For DFC data, always make sure that you data is developed to allow it to be correctly defined with the NAD 1983 State Plane Colorado Central GIPS 0502 (Feet).prj.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-3

April 2010 Page 23-4 of 23-38

5b. Browse to the data source that has already had its projection defined to automatically assign the same one to the data source of interest.

3.2.2 Defining a Shapefile Projection Using ArcToolbox

If more that one data source needs to have its spatial reference information defined, it is more efficient to use ArcToolbox to define the shared projection of multiple data sources at one time.

1. Choose the Define Projection Wizard (shapefiles …) option from the ArcToolbox Data Management / Projections tools.

2. Select all the data sources that share the same projection by browsing and holding down the <SHIFT> or <CTRL> keys to select multiple files.

3. Choose Next, then Select Coordinate System to launch the Spatial References Properties dialog.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-4

April 2010 Page 23-5 of 23-38

SOP NUMBER 23 SPATIAL DATA SUBMITTALS

4. As in the previous menu using

ArcCatalog, choose Select … if the same projection has not been defined yet for any other data source, otherwise choose Export to export the projection information from the defined data source to all the other data sources in the projection list.

5. Choose Next to review the batch process information, then choose Finish to complete projection definition for all selected files.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-5

April 2010 Page 23-6 of 23-38

SOP NUMBER 23 SPATIAL DATA SUBMITTALS

3.2.3 Reprojecting a Shapefile from One Spatial Reference System to Another The two previous sections described methods to define the existing projection of a data source. However, in many cases data sources will not already be stored in the State Plane, Colorado Central, NAD83, feet coordinate system used at the Denver Federal Center. In such instances, it will be necessary to change the underlying projection of the data to make it consistent with these standards. To reproject data, use the Project Wizard (shapefiles, geodatabase) found in Data Management Tools in ArcToolbox.

1. Browse to the files that you wish to reproject. (Warning: The spatial reference system of all files to reproject must already have been defined using one of the projection definition methods described previously. A warning will display if any of the data sources you choose still needs to have its projection defined.)

2. Next, choose an output location to store the results. If you choose the same output location as your input location, all original files will be overwritten without a warning.

3. Choose the new coordinate system into which to project all data sources selected. In some instances, you will be asked to select a transformation to use to convert from one datum to another. Then, select all input files that are in the same projection, choose the Set Transform button

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-6

April 2010 Page 23-7 of 23-38 and pick one from the standard list.

4. If the exact extents of your data sources is known, the can be entered in the next frame of the project wizard. A desired precision can also be set at this point.

5. After reviewing a summary of the wizard input, choose Finish to regenerate all input into the new projection you defined.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-7

April 2010 Page 23-8 of 23-38

SOP NUMBER 23 SPATIAL DATA SUBMITTALS

3.3 NON-VECTOR DATA

Image data should be provided in TIF file format (*.tif, *.tfw). A worldfile that provides spatial reference information (*.tfw) should accompany each TIFF file (*.tif). Whenever possible, image data should be registered using the GSA Base Coordinate File that includes the 6 fixed monuments shown here (PP1 is an offsite monument.

ID Northing Easting Elevation Desc

PP1 1689329.077 3099269.576 5790.70 3.5" aluminum cap set in concrete

SC-1 1685740.993 3106831.997 5627.16 3.5" aluminum cap set in concrete

SW-1 1685603.971 3104624.310 5681.31 3.5" aluminum cap set in concrete

NW-1 1688908.395 3105499.661 5638.07 3.5" aluminum cap set in concrete

NE-1 1688983.776 3108932.935 5568.05 3.5" aluminum cap set in concrete

SE-1 1686195.895 3109547.361 5577.90 3.5" aluminum cap set in concrete

Digital elevation models or other grid-based data should be provided in ESRI ArcInfo GRID file format, which is stored in a named directory and always accompanied by an INFO directory at the same level in the directory structure.

3.4 SAVING A LAYER FILE REPRESENTATION (*.lyr) OF EACH DATA SOURCE For every data source that is used as a layer in an ArcView map document, a layer file should be saved in the same location with the data source to preserve symbology, labeling, and other rendering properties. To save a layer file, choose each layer in turn in the Table of Contents in ArcMap, right click to expose the layer context menu, and choose Save as Layer File. Name the layer file the same name as its source if only one layer file will ever be needed (symbology and labeling will not need to be different for different uses). Otherwise call the new layer file the same name as its source file with a descriptor following the name such as roadscl14pt for 14 point labels on the center line roads layer.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-8

April 2010 Page 23-9 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-9

4.0 FILE NAMING CONVENTIONS

File naming conventions need to be consistent to allow GSA staff to easily find related files for comparison, integration, or duplicate elimination. Each data source filename should include a prefix labeling its general content, a more explicit descriptor, and finally a suffix that describes version or series information. Typically, do not include project area information in the filename, since this will be determine by the directory within which the data is stored.

4.1 PREFIX – CATEGORY

Include one of the following categorical prefixes to classify each data source. If a data source fits two categories or falls into a category not yet define, the contractor should work with GSA personnel to create a new or combined class.

ast – above-ground storage tank

BD### – building number to proceed name of environmental samples collected within a building bh – borehole blg – building bnd – boundary ctr – contours ele – electrical system features fnc – fence gs - gas gw – groundwater

IA##O – site identifier (such as IA14N), proceeds environmental sample names ophoto – orthophoto rd – road rec – recreation rr – railroad sdwk – sidewalk sol – soil spot – point elevation str – stream sw – surface water swr – sewer collection system features

April 2010 Page 23-10 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-10 stm – storm water collection system features tel – telecommunication system features ust – underground storage tank utl – utility veg – vegetation wl - well wall – wall wtr – water distribution system features (e.g. domestic water line) zon – zone

4.2 NAME – DESCRIPTION

Include an abbreviation for the name or identifier for data sources representing a single object, such as a stream (strMcGulch.shp). Typically do not include project area designators in the name, since the project directory in which the data source is stored will determine this. The exception is environmental samples, which should include a site or building designator prefix as described above and a date stamp suffix as described below.

4.3 SUFFIX – SERIES, VERSION, SOURCE

For periodically collected environmental sample data, a suffix should be added to distinguish one data source from another. For example for quarterly samples, the year and quarter should be added as YYQ#, or 02Q1 for the first quarterly sample collected in 2002. For sporadically collected samples, a date stamp YYMM should be used, such as 0202 for samples collected in February 2002. For a sample type that will not to be sampled again, no date stamp is needed since it is already a unique data source.

Do not use words like new and old to describe versions. If existing data must be edited, then a dash followed by the edit date should be added to the name to indicate which version it is. Once all previous versions have been discarded, GSA personnel can decide how to reconcile any edits and drop the date suffix from the final version that results.

If it is necessary to distinguish a data source developed by an outside entity for public use from one developed for GSA directly, a suffix can be added to distinguish the source. For example, USGS could be added to a stream filename to indicate it is a US Geological Survey version of the stream. LKWD could be appended to the name of files obtained from the City of Lakewood.

However, if more than one or two files are going to be used from an outside source, it is better to place these data sources in their correct location in the directory structure in a subdirectory labeled with the name of the data provider.

April 2010 Page 23-11 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-11

5.0 DIRECTORY STRUCTURE

5.1 BASEWIDE DATA AND MAP DOCUMENTS

All data sources in shapefile format that cover the entire area of the DFC installation or at least large portions of it or represent a single entity like a stream that traverses the installation should be stored in the Coverages directory. Within the Coverages directory, data sources should be placed in one of the following subdirectories based on their purpose:

• Base – base map layers like roads, buildings, etc

• Locations – environmental sampling data

• IS-CS – environmental site boundaries and area of concern polygons

• Offsite – areas adjacent to DFC but not within the boundaries of the compound

• Utilities –water, storm water, sewer, electrical, etc.

All map documents should be placed in the Projects directory. Since each ArcView 8 map document (*.mxd) file contains a single map, an abbreviation of the map title and page size should be used to describe it. For example, a basewide utilities map could be called wtrswrele36x24.mxd to indicate that it contains just water, sewer and electrical utilities (as opposed to all utilities) on a 36 inch wide by 24 inch tall map. If a map contains only site specific data, the title of the map should be prefixed with the site number (e.g.

IA14N02Q1envchem17x11.mxd).

5.1.1 CAD and Image Files

All data sources stored in Computer-Aided Design (CAD) format should be places in the Cadfiles directory. Orthorectified photos should be placed in the Image/Airphoto directory.

Pictures or photos of buildings should be placed in the Image/Bldg directory. Maps of project areas should be placed in the Image/Maps directory. Company logos and other types of images should be placed in the Image/Other directory. Cadfiles or image files that represent buildings should be named by their building number and an appropriate descriptive prefix (UTL – utility, Mod – modification, BH – borehole, etc.).

5.1.2 Project-specific Data

Project-specific data should be stored in a directory labeled with its IA or other location identifier within the Coverages directory described previously. Within each project directory, subdirectories should be established to organize all spatial data layers (coverages, cadfiles, etc.).

To make it easier to load map documents, even project specific ArcView 8 map documents (*.mxd) should still be stored in the Projects subdirectory at the root level.

April 2010 Page 23-12 of 23-38

SOP NUMBER 23 SPATIAL DATA SUBMITTALS

6.0 DATA DICTIONARY

A simple, but complete data dictionary must be submitted with each spatial data submittal that briefly describes each spatial data source included. The data dictionary should be submitted in an easy-to-read tabular or report format that includes the following headings:

FILENAME – if data files are submitted in more than one directory, include the full path

DESCRIPTION – provide a brief but clear description of content and use

FORMAT – list both the type of data (point, line, polygon, image, grid, drawing, etc.) and the file format along with its characteristic extension (e.g. shapefile - *.shp)

DATE CREATED – include the day, month and year the data was generated

7.0 METADATA

7.1 ARCCATALOG-BASED XML FORMAT

Each spatial data source must be accompanied by an ArcView 8-based XML file that describes its content. This file can be automatically generated in part by choosing the data source name listed in the table of contents in ArcCatalog then selecting the metadata tab. To edit this metadata file to include other required information:

1. click on the metadata tab

2. choose the edit button

3. click on one of the 7 sections of FGDC metadata to begin modifying

4. click on the tab within the section that describes the type of information you wish to update

5. update information in each field (trying particularly hard to fill in all red lettered sections that include the word REQUIRED at the beginning of the text string)

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-12

April 2010 Page 23-13 of 23-38

NOTE: A metadata text file that includes standard sections such as access and use constraints is included on the CD that accompanies this document. This can be imported into the metadata using the Import Metadata button found on the metadata toolbar when the Metadata tab is active. Each contractor can add their contact information and other repetitive data then use the Export Metadata button to create a more complete, general purpose metadata file. Significant time can be saved by importing this descriptive information into the metadata for each data source before conducting further metadata edits. If this method is followed, it is possible that only the file’s purpose and abstract and specific descriptive information about feature attributes associated with the map features will still need to be described.

7.2 SPATIAL REFERENCE INFORMATION MUST BE DEFINED

Once you define the spatial reference information of a data source using the ArcCatalog or ArcToolbox method described in an earlier section, ArcView 8 will automatically include this in the metadata. This is also true of all other information that ArcView 8 can determine from the data itself, such as extent, feature type and number of features, etc. To view all automatically recalculated metadata entries, review the Spatial tab of the ESRI Stylesheet for the data source of interest.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-13

April 2010 Page 23-14 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-14

7.3 MINIMUM REQUIREMENTS

The following descriptive information is required for each spatial data source submitted.

Including additional information is encouraged to enable the metadata to meet Federal Geographic Data Committee (FGDC) standards as well as possible. The three levels of the outline below relate to the ArcView 8 Metadata Editor dialog and indicate the menu, tab or button popup dialog, and finally the actual information field that must be completed shown in bold type.

Identification

Description

Abstract, Purpose

Access and Use Constraints

Contact

Person, Organization, Telephone, E-mail, Address

Citation Information

Title, Originator, Publication Date

Spatial Reference (automatically added once defined)

Entity Attribute

Attribute

Label, definition, units (if applicable) for each user-defined attribute field

Metadata Reference

Contact Information

Person (rest not necessary if it is the same as in the identification section)

8.0 MAP DOCUMENT

8.1 THE MAP DOCUMENT (*.mxd)

An ArcView ArcMap map document (*.mxd) will be generated for each map produced for a project. All map documents should be stored in a Projects directory, either at the root level of the directory structure for basewide projects, or within a subdirectory labeled with its project area (e.g. IA14N). Metadata should be generated for each map, but only needs to include the purpose, abstract, and complete contact information listing the person who actually designed the map rather than the project manager. The metadata should indicate if any symbols or map elements were used that are not found in the DFC map style and if a DFC approved map template did NOT serve as the basis for the map. This will enable GSA personnel to add new

April 2010 Page 23-15 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-15 symbols and map elements to the DFC.style if necessary and review Layout View effectively to check for product consistency.

8.2 USE ONLY APPROVED MAP TEMPLATES (*.mxt)

The CD accompanying this document includes a DFC directory of approved map templates of various sizes. Some even include base map data as part of the template, requiring that the data sources are retained in the correct directory structure as provided on the CD when copied into your working directory. The DFC folder of templates should be saved in C:\arcgis\arcexe81\Bin\Templates so that when choosing to start with a template at startup or later changing to a template using the Change Layout button on the Layout toolbar, the DFC templates will be automatically available in a DFC tab in the Templates dialog.

8.3 USE ONLY APPROVED MAP STYLES (*.style)

A map style file of approved symbols and map elements for use at DFC called DFC.style has been included on the CD that accompanies this document. To make these styles available for use in ArcMap

1. Copy this file to your ..\arcgis\arcexe81\Bin\Styles folder.

2. Choose Styles > Style Manager from the Tools menu to open the Style Manager dialog.

3. Choose Add and browse to the DFC.style file to add it to the list of available map styles.

4. It is recommended that all other styles be turned off in the Tools > Styles > Style References dialog, so that only elements and symbols associated with the approved DFC map style are available.

5. If a desired symbol is not available in the DFC map style, a symbol from another style can be used, but make sure to indicate that you had to use some additional symbols and/or map elements from other styles in the metadata for the map document. This will enable GSA to add it to the DFC style if appears to be a symbol or map element that will be find later use in other projects.

April 2010 Page 23-16 of 23-38

9.0 IMPORTING ARCVIEW 3.X PROJECTS INTO ARCVIEW 8

There are two methods for importing Layout and View documents from an ArcView 3.X project file (*.apr) into ArcView 8 map documents (*.mxd). Each map document is comprised of a single map (layout) containing one or more data frames – a data frame in ArcView 8.X is analogous to a View in ArcView 3.X. An ArcView 3.X project file often contains multiple layouts, so typically one *.apr is imported into several single-map map documents. If only the data and symbology is desired, instead of a final map presentation, the user can import selected Views instead of having Views selected for import automatically based on which Layout is to be imported. ArcView 3.X charts, tables, scripts and dialogs cannot be imported into ArcView 8.

Tabular joins and links are also lost during the conversion. Therefore, any themes based on an Event Theme or relying on joins for symbology or labeling in ArcView 3.X will not appear correctly in ArcView 8. Sometimes it may be easier to open an ArcView 3.X and fix it to eliminate dependencies that ArcView 8 will not recognize before proceeding with the import process. Data source paths in the *.apr file to import should not be relative (start with a ./) or utilize a variable in the pathname, because only full paths to data sources will be read correctly by the Import tool. The first step to importing an ArcView 3.X project is to launch the Import ArcView 3.X Project option from the File menu in ArcMap. Browse to the ArcView 3.X project file (*.apr) file that you wish to import. Views and Layouts found in the project will appear in their respective lists as soon as you choose an ArcView project file.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-16

April 2010 Page 23-17 of 23-38

SOP NUMBER 23 SPATIAL DATA SUBMITTALS

9.1 METHOD 1. IMPORTING BY LAYOUT

Choose a Layout from the list of all the Layouts found in the current ArcView project file to automatically import it and all of its associated Views into an ArcView 8 map document (*.mxd). After choosing a layout, the View Selector window will become grayed out and Views associated with the layout will automatically become check marked for import. Usually no map will be converted perfectly, so review the Correcting Import Errors section below.

9.2 METHOD 2. IMPORTING SELECTED VIEWS

Since the approved ArcView 8 map templates may differ substantially from map layouts used in ArcView 3.2, in many cases it will be preferable to just import Views by selecting the None option for Layouts to import. Then just check mark the Views needed to construct a single map. Use one of the approved DFC map templates provided on the CD that accompanies this document to generate a new map using the Change Layout button on the Layout toolbar. After adding a template, adjust the text and map elements if necessary to match important features in the original ArcView 3.2 layout.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-17

April 2010 Page 23-18 of 23-38

SOP NUMBER 23 SPATIAL DATA SUBMITTALS

9.3 CORRECTING IMPORT ERRORS

After importing ArcView 3.X information in ArcView 8, it will be necessary to reestablish tabular joins and links and recreate event themes. The graphing tool accessed with the Tools>Graphs>Create option can be used to reconstruct any charts that had been present. Click on the Source tab in the Table of Contents and choose the Add Data button to import tabular data that had resided in an ArcView 3.X table document. Not all map elements translate correctly from ArcView 3.2 into ArcView 8. Therefore, it important to examine north arrows, scale bars, legends, etc. and replace them with ArcView 8 elements where conversion has not been effective. Sometimes text formats may need to be adjusted and neatlines reset, too. If the map resulting from an imported project is not consistent with approved DFC ArcView 8 map templates, map deliverables will NOT be accepted. Therefore, if a contractor’s ArcView 3.2 layouts differs more than slightly from DFC ArcView 8 standards, it is better to import Views only and use an approved DFC map template to reconstruct the map.

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-18

April 2010 Page 23-19 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-19

ATTACHMENT A

DENVER FEDERAL CENTER BASEMAP CD

April 2010 Page 23-20 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-20

To assist GSA personnel and contractors to more effectively implement the procedures described herein, a CD containing basemap layers, sample maps, templates, styles, etc. has been created to accompany this document.

A.1 CD Contents – General

• readme.txt - this document

• arcgis/arcexe81/bin/styles - ArcView8 installation location to store templates included here

• arcgis/arcexe81/bin/templates - ArcView8 installation location to store templates included here

• cad - original and new base map data developed in AutoCAD

• coverages/base - DFC base map shapefiles

• coverages/locations - environmental sampling and management layers (prairie dog, wells)

• coverages/offsite/ophoto2002 - shapefiles that cover full study area, not as detailed as base/ ones

• coverages/offsite/Lakewood - floodplain and base map data provided by the City of Lakewood

• coverages/utility - utility shapefiles for water, sewer, electric, etc.

• gridtin - ArcInfo grid (5ft pixel) and TIN versions of elevation model

• image - place to store orthorectified images if you wish to copy them to the server or local drive

• logo - logos for contractors, GSA, DFC, etc.

• metadata - contact and quality information about the basemap products, SOP for ArcView 8, and descriptions of shapefiles produced in Data Dictionary

• projects - ArcView 3.2 (*.apr) and ArcView 8.X(*.mxd) projects to print out maps

A.2 CD Contents – Full Listing without Descriptions (See the Data Dictionary in Attachment B or the individual metadata for each shapefile in ESRI ArcView 8 ArcCatalog for more information about a specific data set.)

|| readme.txt – listing of CD contents in general

+---ARCGIS

| \---ARCEXE81

April 2010 Page 23-21 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-21

| \---BIN

| +---STYLES - ArcView8 styles generated from map documents included on CD | | | DFC.style | \---templates - ArcView8 templates generated from map documents included on CD

| | DFCBASE.MXT

| | dfcenvmgmt17x11.mxt | | dfcutility.mxt +---CAD - original digitized cad files of aerial photo features from which shapefiles were generated | DFC_baseorig.dxf - DFC original base map from older data, used for comparison | DFC_baseorig.dxf.xml | DFC_ophoto2002.dxf - digitized aerial photo information | DFC_ophoto2002.dxf.xml | SurfaceModelEast.dxf - data used to generate contours on the east side of DFC | SurfaceModelWest.dxf - data used to generate contours on the west side of DFC +---coverages - see data dictionary in Attachment B for a description of each shapefile | +---BASE - basemap data

| | BLDG.AVL

| | BLDG.DBF

| | BLDG.LYR

| | bldg.lyr.xml

| | BLDG.PRJ

| | BLDG.SBN

| | BLDG.SBX

| | BLDG.SHP

| | bldg.shp.xml

| | BLDG.SHX

| | bldgold.dbf | | bldgold.shp | | bldgold.shx

| | BRIDGE.AVL

| | BRIDGE.DBF

| | BRIDGE.LYR

| | bridge.lyr.xml

| | BRIDGE.PRJ

| | BRIDGE.SBN

| | BRIDGE.SBX

| | BRIDGE.SHP

| | bridge.shp.xml

| | BRIDGE.SHX

April 2010 Page 23-22 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-22

| | CANOPY.AVL

| | CANOPY.DBF

| | CANOPY.LYR

| | canopy.lyr.xml

| | CANOPY.PRJ

| | CANOPY.SBN

| | CANOPY.SBX

| | CANOPY.SHP

| | canopy.shp.xml

| | CANOPY.SHX

| | CONCPAD.AVL

| | CONCPAD.DBF

| | CONCPAD.LYR

| | concpad.lyr.xml

| | CONCPAD.PRJ

| | CONCPAD.SBN

| | CONCPAD.SBX

| | CONCPAD.SHP

| | concpad.shp.xml

| | CONCPAD.SHX

| | CTR.AVL

| | CTR.DBF

| | CTR.LYR

| | ctr.lyr.xml

| | CTR.PRJ

| | CTR.SBN

| | CTR.SBX

| | CTR.SHP

| | ctr.shp.xml

| | CTR.SHX

| | FCWALL.AVL

| | FCWALL.DBF

| | FCWALL.LYR

| | fcwall.lyr.xml

| | FCWALL.PRJ

| | FCWALL.SBN

| | FCWALL.SBX

| | FCWALL.SHP

| | fcwall.shp.xml

| | FCWALL.SHX

| | GATE.DBF

| | GATE.LYR

| | gate.lyr.xml

April 2010 Page 23-23 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-23

| | GATE.PRJ

| | GATE.SBN

| | GATE.SBX

| | GATE.SHP

| | gate.shp.xml

| | GATE.SHX

| | HYDRO.AVL

| | HYDRO.DBF

| | HYDRO.LYR

| | hydro.lyr.xml

| | HYDRO.PRJ

| | HYDRO.SBN

| | HYDRO.SBX

| | HYDRO.SHP

| | hydro.shp.xml

| | HYDRO.SHX

| | perifence.dbf | | perifence.lyr | | perifence.lyr.xml | | perifence.prj | | perifence.sbn | | perifence.sbx | | perifence.shp | | perifence.shp.xml | | perifence.shx

| | RAILROAD.DBF

| | RAILROAD.LYR

| | railroad.lyr.xml

| | RAILROAD.PRJ

| | RAILROAD.SBN

| | RAILROAD.SBX

| | RAILROAD.SHP

| | railroad.shp.xml

| | RAILROAD.SHX

| | REC.AVL

| | REC.DBF

| | REC.LYR

| | rec.lyr.xml

| | REC.PRJ

| | REC.SBN

| | REC.SBX

| | REC.SHP

| | rec.shp.xml

April 2010 Page 23-24 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-24

| | REC.SHX

| | ROADCL.AVL

| | roadCL.dbf | | roadCL.lyr | | roadCL.lyr.xml | | roadCL.prj | | roadCL.sbn | | roadCL.sbx | | roadCL.shp | | roadCL.shp.xml | | roadCL.shx

| | ROADS.AVL

| | ROADS.DBF

| | ROADS.LYR

| | roads.lyr.xml

| | ROADS.PRJ

| | ROADS.SBN

| | ROADS.SBX

| | ROADS.SHP

| | roads.shp.xml

| | ROADS.SHX

| | sdwkbkpth.avl | | sdwkbkpth.dbf | | sdwkbkpth.lyr | | sdwkbkpth.lyr.xml | | sdwkbkpth.prj | | sdwkbkpth.sbn | | sdwkbkpth.sbx | | sdwkbkpth.shp | | sdwkbkpth.shp.xml | | sdwkbkpth.shx

| | SPOTELEV.AVL

| | SPOTELEV.DBF

| | SPOTELEV.LYR

| | spotelev.lyr.xml

| | SPOTELEV.PRJ

| | SPOTELEV.SBN

| | SPOTELEV.SBX

| | SPOTELEV.SHP

| | spotelev.shp.xml

| | SPOTELEV.SHX

| +---Locations - environmental features

April 2010 Page 23-25 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-25

| | prairiedog.dbf | | prairiedog.prj | | prairiedog.sbn | | prairiedog.sbx | | prairiedog.shp | | prairiedog.shp.xml | | prairiedog.shx | | wellfromophoto.dbf | | wellfromophoto.prj | | wellfromophoto.sbn | | wellfromophoto.sbx | | wellfromophoto.shp | | wellfromophoto.shp.xml | | wellfromophoto.shx | +---OFFSITE - includes areas not inside DFC boundaries | | +---Lkwd - data provided by the city of lakewood

| | | | JCOROADS.DBF

| | | | JCOROADS.PRJ

| | | | JCOROADS.SBN

| | | | JCOROADS.SBX

| | | | JCOROADS.SHP

| | | | JCOROADS.SHX

| | | | lkwdroads.dbf | | | | lkwdroads.sbn | | | | lkwdroads.sbx | | | | lkwdroads.shp | | | | lkwdroads.shx | | | | lkwdroadsmrg.dbf | | | | lkwdroadsmrg.shp | | | | lkwdroadsmrg.shx

| | | | PARKS.DBF

| | | | PARKS.PRJ

| | | | PARKS.SBN

| | | | PARKS.SBX

| | | | PARKS.SHP

| | | | PARKS.SHX

| | | | RAIL.DBF

| | | | RAIL.PRJ

| | | | RAIL.SBN

| | | | RAIL.SBX

| | | | RAIL.SHP

| | | | RAIL.SHX

April 2010 Page 23-26 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-26

| | | | SCHOOLS.DBF

| | | | SCHOOLS.SBN

| | | | SCHOOLS.SBX

| | | | SCHOOLS.SHP

| | | | SCHOOLS.SHX

| | | \---Floodpln

| | | | BASINS.DBF

| | | | BASINS.PRJ

| | | | BASINS.SBN

| | | | BASINS.SBX

| | | | BASINS.SHP

| | | | BASINS.SHX

| | | | CLOCATE.DBF

| | | | CLOCATE.PRJ

| | | | CLOCATE.SBN

| | | | CLOCATE.SBX

| | | | CLOCATE.SHP

| | | | CLOCATE.SHX

| | | | DFIRM.DBF

| | | | DFIRM.PRJ

| | | | DFIRM.SBN

| | | | DFIRM.SBX

| | | | DFIRM.SHP

| | | | DFIRM.SHX

| | | | FLDPLN.DBF

| | | | FLDPLN.PRJ

| | | | FLDPLN.SBN

| | | | FLDPLN.SBX

| | | | FLDPLN.SHP

| | | | FLDPLN.SHX

| | | | floodpark.dbf | | | | floodpark.prj | | | | floodpark.sbn | | | | floodpark.sbx | | | | floodpark.shp | | | | floodpark.shx | | | | greenmtnfp.dbf | | | | greenmtnfp.prj | | | | greenmtnfp.sbn | | | | greenmtnfp.sbx | | | | greenmtnfp.shp | | | | greenmtnfp.shx

April 2010 Page 23-27 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-27

| | | | LAKEWDFP.DBF

| | | | LAKEWDFP.PRJ

| | | | LAKEWDFP.SBN

| | | | LAKEWDFP.SBX

| | | | LAKEWDFP.SHP

| | | | LAKEWDFP.SHX

| | | | mcintyrefp.dbf | | | | mcintyrefp.prj | | | | mcintyrefp.sbn | | | | mcintyrefp.sbx | | | | mcintyrefp.shp | | | | mcintyrefp.shx | | | | slakewdfp.dbf | | | | slakewdfp.prj | | | | slakewdfp.sbn | | | | slakewdfp.sbx | | | | slakewdfp.shp | | | | slakewdfp.shx | | \---ophoto2002 - DFC data that includes aerial photo information of adjacent areas

| | BLDG.AVL

| | BLDG.DBF

| | BLDG.PRJ

| | BLDG.SBN

| | BLDG.SBX

| | BLDG.SHP

| | bldg.shp.xml

| | BLDG.SHX

| | BNDJOB.DBF

| | BNDJOB.PRJ

| | BNDJOB.SBN

| | BNDJOB.SBX

| | BNDJOB.SHP

| | bndjob.shp.xml

| | BNDJOB.SHX

| | BRIDGE.AVL

| | BRIDGE.DBF

| | BRIDGE.PRJ

| | BRIDGE.SBN

| | BRIDGE.SBX

| | BRIDGE.SHP

| | bridge.shp.xml

| | BRIDGE.SHX

April 2010 Page 23-28 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-28

| | CANOPY.AVL

| | CANOPY.DBF

| | CANOPY.PRJ

| | CANOPY.SBN

| | CANOPY.SBX

| | CANOPY.SHP

| | canopy.shp.xml

| | CANOPY.SHX

| | CONCPAD.AVL

| | CONCPAD.DBF

| | CONCPAD.PRJ

| | CONCPAD.SBN

| | CONCPAD.SBX

| | CONCPAD.SHP

| | concpad.shp.xml

| | CONCPAD.SHX

| | CTR.AVL

| | CTR.DBF

| | CTR.PRJ

| | CTR.SBN

| | CTR.SBX

| | CTR.SHP

| | ctr.shp.xml

| | CTR.SHX

| | ctr2ft.dbf | | ctr2ft.sbn | | ctr2ft.sbx | | ctr2ft.shp | | ctr2ft.shx

| | FCWALL.AVL

| | FCWALL.DBF

| | FCWALL.PRJ

| | FCWALL.SBN

| | FCWALL.SBX

| | FCWALL.SHP

| | fcwall.shp.xml

| | FCWALL.SHX

| | FlightLine.dbf | | FlightLine.prj | | FlightLine.sbn | | FlightLine.sbx | | FlightLine.shp | | FlightLine.shp.xml

April 2010 Page 23-29 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-29

| | FlightLine.shx | | FlightLineSpot.dbf | | FlightLineSpot.prj | | FlightLineSpot.sbn | | FlightLineSpot.sbx | | FlightLineSpot.shp | | FlightLineSpot.shp.xml | | FlightLineSpot.shx | | GroundControl.dbf | | GroundControl.prj | | GroundControl.sbn | | GroundControl.sbx | | GroundControl.shp | | GroundControl.shp.xml | | GroundControl.shx

| | HYDRO.AVL

| | HYDRO.DBF

| | HYDRO.PRJ

| | HYDRO.SBN

| | HYDRO.SBX

| | HYDRO.SHP

| | hydro.shp.xml

| | HYDRO.SHX

| | REC.AVL

| | REC.DBF

| | REC.PRJ

| | REC.SBN

| | REC.SBX

| | REC.SHP

| | rec.shp.xml

| | REC.SHX

| | ROADS.AVL

| | ROADS.DBF

| | ROADS.PRJ

| | ROADS.SBN

| | ROADS.SBX

| | ROADS.SHP

| | roads.shp.xml

| | ROADS.SHX

| | sdwkbkpth.avl | | sdwkbkpth.dbf | | sdwkbkpth.prj | | sdwkbkpth.shp

April 2010 Page 23-30 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-30

| | sdwkbkpth.shp.xml | | sdwkbkpth.shx

| | SPOTELEV.AVL

| | SPOTELEV.DBF

| | SPOTELEV.PRJ

| | SPOTELEV.SBN

| | SPOTELEV.SBX

| | SPOTELEV.SHP

| | spotelev.shp.xml

| | SPOTELEV.SHX

| \---UTILITY - digitized utility data. NOT VERY COMPLETE or ACCURATE, since had to pick out from photo.

| ELEBOX.DBF

| ELEBOX.PRJ

| ELEBOX.SBN

| ELEBOX.SBX

| ELEBOX.SHP

| elebox.shp.xml

| ELEBOX.SHX

| ELEPOLE.DBF

| ELEPOLE.PRJ

| ELEPOLE.SBN

| ELEPOLE.SBX

| ELEPOLE.SHP

| elepole.shp.xml

| ELEPOLE.SHX

| MANHOLE.DBF

| MANHOLE.PRJ

| MANHOLE.SBN

| MANHOLE.SBX

| MANHOLE.SHP

| manhole.shp.xml

| MANHOLE.SHX

| PIPELINE.DBF

| PIPELINE.PRJ

| PIPELINE.SBN

| PIPELINE.SBX

| PIPELINE.SHP

| pipeline.shp.xml

| PIPELINE.SHX

| SIGN.DBF

| SIGN.PRJ

April 2010 Page 23-31 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-31

| SIGN.SBN

| SIGN.SBX

| SIGN.SHP

| sign.shp.xml

| SIGN.SHX

| SIGNL.DBF

| SIGNL.PRJ

| SIGNL.SBN

| SIGNL.SBX

| SIGNL.SHP

| signl.shp.xml

| SIGNL.SHX

| TANK.DBF

| TANK.PRJ

| TANK.SBN

| TANK.SBX

| TANK.SHP

| tank.shp.xml

| TANK.SHX

| TELTOWER.DBF

| TELTOWER.PRJ

| TELTOWER.SBN

| TELTOWER.SBX

| TELTOWER.SHP

| teltower.shp.xml

| TELTOWER.SHX

| TRAFLT.DBF

| TRAFLT.PRJ

| TRAFLT.SBN

| TRAFLT.SBX

| TRAFLT.SHP

| traflt.shp.xml

| TRAFLT.SHX

| wtrhydrant.dbf | wtrhydrant.prj | wtrhydrant.sbn | wtrhydrant.sbx | wtrhydrant.shp | wtrhydrant.shp.xml | wtrhydrant.shx +---gridtin - Digital Elevation model of installation in GRID and TIN form - CONTOURS may be more accurate

April 2010 Page 23-32 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-32

| +---dfcdem | | dblbnd.adf | | hdr.adf | | sta.adf | | w001001.adf | | w001001x.adf | +---dfctin | | tdenv.adf | | tedg.adf | | thul.adf | | tmsk.adf | | tmsx.adf | | tnod.adf | | tnxy.adf | | tnz.adf | \---info | arc.dir | arc0000.dat | arc0000.nit | arc0001.dat | arc0001.nit | arc0002.dat | arc0002.nit +---logo - company logos for use in creating layouts

| FEC.BMP

| GSA.BMP

+---metadata - important general information about CD contents | DataDict.doc - data dictionary found in Attachment B | DFC_ALL Layer List.doc - description of CAD layers | DFCSOP4AV8_051202.doc - Standard Operating Procedures manual | FlightLinesSurvey.xls - information collected for flight lines | GroundControl.xls - actual ground control points surveyed for aerial photo | OphotoMetadata.doc - general metadata concerning the orthorectified photos | VectorMappingMetadata.doc - general metadata about the layers digitized from the aerial photos \---projects - sample projects in ArcView 3.2 (*.apr) and ArcView 8 (*.mxd) dfcbase.apr dfcbase17x11.mxd

April 2010 Page 23-33 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-33 dfcenvmgmt17x11.mxd dfcutility17x11.mxd prjarea17x11.mxd prjarea36x24.mxd startup-dfcbase.apr template.def - ArcView 3.2 templates

April 2010 Page 23-34 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-34

ATTACHMENT B

DATA DICTIONARY

April 2010 Page 23-35 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-35

Bldg

• Building – poly-line, used to outline occupied structures, (residential, commercial or government). Building numbers and historic attributes have been added, but building 1, 25, 710A, and USGS Lab have more than one outbuilding given the same name, so BldgID is NOT unique.

• Out –bldg – poly-line, used to outline all unoccupied buildings larger than 12’ X 12’ (garage, storage, unit, shed, etc.)

• Bridge – poly-line, used to outline all bridges including on roadways and on pedestrian ways

• Canopy – poly-line, used to outline structures found over pumps at gas stations, picnic areas etc.

• DFCtin – triangulated irregular network model of study area topography generated from surfacemodel.dxf

• DFCDem – digital elevation model in Arc/Info grid format with 5 foot pixel resolution

• Elebox – point, used to identify all boxes that appear to house electrical utilities

• Elepole – point, used to identify all poles that are either power pole, light pole or combination light/power pole

Hydro

• Catch_basin – point, used to identify grates used as storm drains, usually found along roadways and in parking lots, may also be in open areas in lower elevation spots such as depressions

• Concdrain_– poly-line, used to outline concrete lined drains, will have hydrologic feature running at ground elevation in the center

• Culvert_span_rd – poly-line, hidden drain line running under roadways, usually connected to headwalls on each end

• Ditch –poly-line, used to identify ditches carrying water, these are usually man–made features

• Drain– poly-line, used to identify features carrying water, these are natural features

• Drop_inlet – point, used to identify an curb inlet or storm drain under a curb

• Headwall – poly-line, used to outline culverts or headwalls

• Inter_stream–3d – poly-line, used to identify streams that may or may not carry water, intermittent stream

• Lake_– poly-line, used to outline lake, either man-made or natural

April 2010 Page 23-36 of 23-38

W:\Projects\22240312_GSA_Rev_Mod_Negot\8.0_Working_Files\Revised SOPs\SOP_23_Spatial Data Submittals_04-10.doc 5/4/2010 3:28 PM 23-36

• Pond – line, used to outline bodies of water smaller than lakes

• ConcPad – polygon, concrete pad, patio or pad around manhole

Fcwall

• Fence – poly-line, used to identify major fence lines, usually depicting property lines, but not always

• Guard_rail – poly-line, used to outline guardrails along roadways

• Ret_wall – poly-line, used to outline all major retaining walls, does not include small retaining walls in residential area yards

• Rwall – poly-line, same as Ret_wall

• Wall – poly-line – used…