05 FA489725B0006 GIS Data.pdf

Revised 8 June 2023

Design & Construction Plans, Surveys & Studies, and Contract Services

Geographic Information System (GIS) Deliverables

The following requirements ensure 366 CES/CENME receive products that will seamlessly integrate with GeoBase.

I. AS-BUILT RECORD DRAWINGS

A. The final as-built record drawings on computer disc, or digital delivery through the Air Force “DOD SAFE” system shall be completed and returned together with the approved preliminary as-built field data to the Contracting Officer within 21 calendar days of the Contract Closeout Completion Date. The Contracting Officer will submit the electronic as-built record drawings to CE and GeoBase for review of all final as-built record drawings for accuracy, conformance to the A/E/C standards and other requirements contained in this section. The drawings shall be returned to the Contractor if corrections are necessary. The Contractor shall make all corrections and shall return the drawings to the Contracting Officer within seven calendar days of receipt.

II. AS-BUILT FIELD DATA

A. The As-Built Field Data shall be submitted to the Contracting Officer for review and/or approval a minimum of 20 calendar days prior to the date of final inspection. If review of the preliminary as-built drawings reveals errors and/or omissions, the drawings will be returned to the Contractor for correction. The Contractor shall make all corrections and return the drawings to the Contracting Officer within 10 calendar days of receipt. Final As-Built Field Data shall be received and approved by the Contracting Officer by the Contract Closeout Completion Date.

B. The Contractor shall prepare, process, and deliver all site, design, construction, and location related work as geospatial or geographically-referenced data in an electronic format to the Government according the following criteria and guidance. For projects involving A-E design requirements, the A-E Contractor shall draft a new master specification section that addresses the requirements for construction Contractors and/or Sub-Contractors to collect geospatial or geographically-referenced data during and at the completion of construction phase(s).

1. Geospatial data deliverable requirements shall apply for all surveyed, mapped, collected, extracted, derived, designed, or proposed natural and built features supporting project requirements herein.

2. Final site utility layout and computer aided-design (CAD) data deliverables shall be converted to a GIS format (as required) or delivered as a geographically-referenced and survey grade CAD data. As-Builts and other A-E data shall be delivered electronically in formats in accordance with (IAW) Paragraph K.

3. All data deliverables shall be submitted to the Government on a CD/DVD-ROM or digital delivery through the Air Force “DOD SAFE” system

C. THE CONTRACTOR SHALL PROVIDE DELIVERABLES IN THE FOLLOWING

FORMAT

1. Required Format: The Contractor shall submit geospatial or geographically-referenced data in ESRI ArcGIS file geodatabase (FGDB) format. FGDBs shall be ArcGIS Desktop version 10.6 or later version and contain all geospatial (vector), attribute (tabular), and metadata (XML) data. Surveyed data shall be delivered in either an .xls, .csv, or .dbf file including Latitude, Longitude, Elevation, along with feature code/description. No additional files, tables, diagrams or documents should be required to complete required geospatial data deliverables.

2. Other Formats: Geospatial data may also be delivered in other formats (such as an export form Oracle or SQL, or a direct ArcSDE (load) provided the Contractor has obtained written approval from the Contracting Officer (CO). The Contractor can contact the Installation Geobase Office, at (208) 828-6529 for additional details and guidance.

3. File-Based Formats: Individual (non-database or “flat”) geospatial or geographically referenced data files, if required, shall be accompanied with the appropriate external spatial reference files that specify the parameters of the projection, coordinate system, units of measure, and datum. EXAMPLES: ArcGIS Shapefiles Projection Files (*.prj), and auxiliary files (*.aux).

4. AutoCAD data should be delivered in CADD (AUTOCAD 2021 or later).

a) Note: If delivering in GIS increases the cost over a certain dollar amount, it is acceptable to deliver georeferenced CADD format (DWG, DGN, or DXF), AutoCAD 2017 or higher. Prior written approval must be issued by the Project Manager and the GeoBase office before this is acceptable.

D. DATA MODEL

1. Geodatabase deliverables shall be formatted according to the latest official data model version, the Air Force Adaptation (AFA) of the Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE). SDSFIE is the single Department of Defense (DoD) spatial data standard that supports common implementation and maximized interoperability for Installation, Environment, and Civil Works Missions. SDSFIE is registered in the DoD IT Standards Registry and is recognized as the enterprise standard for geospatial data across the entire DoD business mission area. SDSFIE standards are determined and managed by the Defense Installation Spatial Data Infrastructure Group (DISDI) Group, a formal governance body that reports to the Department of Defense’s Installation & Environment Investment Review Board. Refer to the SDSFIE website for additional information : https://www.sdsfieonline.org.

2. Spatial Reference: All locational base map data (point, line and polygon features) collected shall be delivered in ESRI ArcGIS 10.6 or later digital format along with the original source files. All topologically correct geospatial data shall overlay on the installations latest orthorectified imagery provided by the government, using the same coordinate and projection system of the imagery (Transverse Mercator Projection: WGS 1984 UTM Zone 11N, Units: Meters; Vertical Datum: EGM96

Geoid). All accuracy errors shall be reported to the contract program manager and to the GeoBase office.

E. GEOSPATIAL DATA DELIVERABLE GEOMETRY REQUIREMENTS

1. Geometry – The Contractor shall create planimetric and topographic data using methods that support the feature geometry required. Acceptable geometry inclues Point, Line, and Polygon features. To ensure compliance with current spatial database parameters, no “polygonZ”, “polylineZ”, or “pointZ” geometry shall be used, as well as no data with “M” values.

a) Point Features: Shall be created as point and placed in the geometric center of the physical feature they represent. Symbol fonts will not be used to create point features (i.e., no graticules, symbols, or icons).

b) Line Features: Shall be used to represent linear features, including topographic contours.

(1) No lines with only one vertex or lines without positive length values.

(2) Lines will have no erroneous overshoots, undershoots, dangles, or intersections.

(3) Lines will be continuous within their own feature class to ensure spatial query compatibility

(4) Line features shall not be broken into small segments (e.g., use a dashed line symbology on a continuous line instead of dashed lines created with small line segments) or broken for text.

(5) Linear features may be broken at intersections with other line features or nodes IAW AF linear segmentation policy and guidance to ensure proper topological connectivity.

(6) Features must snap together where appropriate, such as two vector segments making up one line.

(7) Line strings must not cross back on themselves.

c) Polygon Features: Shall be used to represent area features.

(1) No Polygons with two or less vertices or without positive area values.

(2) Polygons must completely close and have a single, unique centroid, e.g. no ”C” shaped areas.

(3) No Polygons with invalid properties such as inverted polygons, or invalid polygon vertices caused by software conversion methods.

(4) Polygons representing building must depict the building outline (footprint), not the digitized roofline as seen from above, unless specifically supporting roof studies, designs, or construction. Roof features shall reside in a separate core SDSFIE data layer created by the Contractor IAW Paragraph D.

(5) The contractor shall provide a quality control (QC) report that must state whether all inconsistencies in the data generated were corrected, or it must detail the remaining errors by case. The contractor shall utilize a system and clean routine to assure that data meets these requirements. The quality report must identify the software (name and version) and satisfy the above conditions.

F. FEATURE ATTRIBUTES

1. Attribute data is the tabular (non-vector), non-geometric) data about a geospatial feature. The Contractor shall create and provide the minimum attribution for geospatial data IAW the AF Data Layer Specification applicable for each geographic layer delivered. The AF Adaptation of the SDSFIE data model requires minimal mandatory attribution for every geographic data feature. Please reference SDSFIE Vector Specification Document (SDSFIE-V 4.0, DISR Mandated) which outlines the standards and required attributes. The contractor shall identify all available attribution supplied below. Any null, blank, or TBD (To Be Determined) values in the fields will be accompanied by a written reason the fields were not completed.

Any other required attribution for a given feature class shall be delivered in an external (ancillary) table linked back to the data layer through the use of the Primary Key attribute field.

a) Minimum Attribution: Due to the completeness and/or availability of some government furnished information (GFI), there may be some exceptions to this rule:

(1) Real Property Unique Identifier (RPUID): There may be some features where the RPUID numeric values, designated by the official Air Force Real Property system (ACES RP/TRIRIGA) are not available or do not apply.

Missing RPUID numbers for all applicable features shall be verified as acceptable for those features with the Government before providing final deliverables.

(2) InstallationID and SiteID. There may be some features that are located outside the boundaries of DoD property holdings, therefore no applicable values for these field may exist. Missing InstallationID and SiteID, for all applicable features shall be verified as acceptable for those features with the Government before providing final deliverables.

(1) Feature Name shall be populated with the common name of the feature (e.g., “Base Exchange,” “Water Main”), and FeatureDescription shall be populated with a detailed description of the feature.

(3) Narrative shall contain conditions affecting the quality of the data (e.g., “location derived from as-builts and has not yet been field verified”).

(4) The Primary Key Identifier (IDPK) field shall be populated sequentially according to following the schema: Installation ID_SiteIDxxxxxxx. This is the ACES-RP/TRIRIGA assigned 4 letter installation identified, underscore, the ACES-RP assigned 4 letter and 4 digit site identifier, then a 7 digit sequential (1 to x) number. Example for Saylor Creek Range:

QYZH_VAPM00010000001

(5) Date Edited and Editor Shall be filled out for every feature updated, or added.

(6) Data Collection (Method of collection) Shall be added for every feature edited, and Data Source field shall include the equipment or system utilized to update that data i.e “Trimble R12 Rover survey performed on January 7, 2023. Or georeferenced with imagery collected on Jun 15, 2019.”

2. The contractor shall not develop new libraries without prior written approval from the Project Manager or the GeoBase office.

G. METADATA

1. The contractor shall provide metadata files for all locational data produced under this contract. The metadata file shall conform to the Federal Geographic Data Committee’s “Content Standard for Digital Geospatial Metadata, Version 3.0” (or latest version) found at https://www.fgdc.gov/metadata/csdgm/. Further information on metadata requirements and tools can be found at https://www.sdsfieonline.org/Standards/Metadata The output from the ESRI ArcCatalog metadata generator software (or compatible software) shall be the standard format for all metadata files created under this contract. In addition, the metadata data shall be provided in ASCII text format. The digital metadata files shall be provided to the Government along with each final product deliverable, unless otherwise approved in writing by the Project Manager or the GeoBase office.

H. SURVEY DATA

1. The contractor shall use conventional surveying and other methods, such as a total station or Global Positioning Systems (GPS) for field data collection at an accuracy level in accordance with “Geospatial Positioning Accuracy Standards, Part 3:

National Standard for Spatial Data Accuracy,” published by the Federal Geographic Data Committee (FGDC), dated July 1998. This standards document can be found at https://www.fgdc.gov/standards/projects/accuracy/part3/chapter3 .

2. All Survey data collected shall be provided to the Government in a digital format with an attached Survey Report identifying survey method, equipment list, calibration documentation, survey layout, description of control points, control diagrams and field survey data. In addition, survey field notes.

3. A Survey Control Database (consisting of a survey marker database and a survey traverse database) will be produced for all survey control points established under this contract and delivered in a .dbf or ASCII comma-delimited, or file geodatabase format.

4. If GPS is used, the contractor shall use survey grade GPS, at an accuracy level of ± 2cm, unless otherwise specified by the Geobase office. Survey grade Bench marks are available on the base property and details are available from the GeoBase office.

5. Survey Points shall be delivered in one of the following file types: “.csv”, “.xlsx”, or “.dbf”. These points will include the following attribution in addition to the mandatory attributes listed above:

a) Potable Water

(1) Label, Coordinates (Northing, Easting, and Elevation), Nominal Diameter(in), Length (ft), Pipe Material, Depth (ft-in), Valve/Hydrant Number, Valve Size, and Valve Type.

b) Sanitary Sewer

(1) Label, Coordinates (Northing, Easting, and Elevation), Diameter (in), Length (ft), Pipe Material, Invert Elevation, Manhole Number, and Manhole Construction.

c) Storm Sewer

(1) Label, Coordinates (Northing, Easting, and Elevation), Diameter (in), Length (ft), Pipe Material, Invert Elevation, Manhole Number, and Manhole Construction

d) Electrical

(1) Label, Coordinates (Northing, Easting, and Elevation), Conduit Size, Cable Size, Transformer Size, Transformer Type, and Hand Hole Type

e) Natural Gas

(1) Label, Coordinates (Northing, Easting, and Elevation), Diameter (in), Length (ft), Pipe Material, Depth (ft-in), Valve/Meter Type, and Regulator Pressures

f) Liquid Fuels

(1) Label, Coordinates (Northing, Easting, and Elevation), Diameter (in), Length (ft), Pipe Material, Depth (ft-in), and Valve/Meter Type

g) Cathodic Protection

(1) Label, Coordinates (Northing, Easting, and Elevation), Anodes Size

h) Navigation Aids

(1) Label, Coordinates (Northing, Easting, and Elevation

i) Communication

(1) Label, Coordinates (Northing, Easting, and Elevation), Conduit Size, Cable Count.

j) Traffic (Foot and Automotive)

(1) Label, Coordinates (Northing, Easting, and Elevation) Material, Pavement Thickness, and Pavement Type

I. CAD DELIVERY FORMAT

Note: No deviations from the Government's established standards will be permitted unless prior written approval of such deviation has been issued by the Project Manager or the GeoBase office. All linkages of non-graphical data with graphic elements, relationships between data objects and attributes, and report formats shall be maintained.

1. These deliverables include, but are not limited to:

a) As-built drawings, Master Plan drawings and Engineering designs

(1) Site plans

(2) Floor plans

(3) Pavement, Grading, or Excavation plans

(4) HVAC, Electrical, Plumbing plans

(5) Any other system plans needed for completions of project

b) Studies, Surveys and other collected data

(1) Topographic surveys or studies

(2) Boundary or Cadastral surveys

(3) Utility (water, sewer, power, storm, etc.) designs, plans, surveys and studies

(4) Soil/Geology studies or surveys

(5) Environmental assessments, surveys, studies or plans

(6) Historical or Archaeological surveys, studies or plans

2. All data deliverables shall be in a digital (electronic information) format and shall be delivered in a format that conforms to the A/E/C CAD Standards version 6.1 (or latest version available) at https://www.wbdg.org/ffc/army-coe/cad-bim-technology-center .

3. The following procedures must be performed before a file is placed on the delivery media:

a) Include all files, both graphic and non-graphic, required for the project. Make sure all files are in the same directory, and that references to those files do not require device or directory specifications.

b) All files to use the A/EC naming convention as listed using section 2.4 of the A/E/C Standards. Further guidance is given below in section labeled “FILE

NAME FORMAT DESCRIPTION”

c) All CAD objects shale be drawn on the correct layers and layers shale be symbolized correctly as defined on tables located in Appendix A of the A/E/C Standards.

d) Ensure all reference (external reference) files are attached, not bound, and are referenced using relative path to the referenced file.

e) Site plans, Floor plans, Utility plans and other plans as specified by the GeoBase office must be georeferenced as to be in the correct location when referenced in

GIS.

f) Remove all extraneous graphics/text outside the project border area, and set the active parameters to a standard setting (or the setting contained in the seed or prototype file).

g) Include any standards sheets (abbreviations, symbols libraries, font libraries, color tables, pen tables, plot configuration files, user command files, etc.)

necessary for a complete project.

h) Compress and/or reduce all files using the appropriate utilities. A digital media copy of the decompression utility should be provided with the delivered data, if necessary.

4. FILE NAME FORMAT DESCRIPTION

a) SHEET FILES (Example Sheet File: SHT05_QYZH082345AD102xxx)

(1) SHEET PAGE NUMBER – Use the letters “SHT” followed by the page number for the project. In the example SHT05_QYZH082345AD102xxx the SHT05 shows it is the fifth page of the project set

(2) INSTALLATION CODE - Use the four alpha character installation code.

Use the following for each location

(a) QYZH for locations at Mountain Home AFB

(b) GGWR for locations at Juniper Butte

(c) VAPM for locations at Saylor Creek Range

(d) You may obtain other installation codes from the IGI&S or Real Property Office.

(3) PROJECT NUMBER - 082345

(a) Use the assigned 6-digit project number provided by the contracting officer. For projects with more than one project number, use the most recent. For example, QYZH992345 would be less recent than QYZH082345. Use extensions A B or C only if these are actual designations for projects awarded separately.

(4) DISCIPLINE DESIGNATOR – AD (Architectural demolition)

(a) As defined in the A/E/C CADD Standard, Release 6.1 (2018) Sheet File Naming Convention Table 2-3.

(5) SHEET TYPE DESIGNATOR – 1 (Plan view)

(a) As defined in the A/E/C CADD Standard, Release 6.1 (2018) Sheet File Naming Convention Table 2-4.

(b) 1 = Plans, 2 = Elevations, 3 = Sections, etc.

(6) SHEET SEQUENCE NUMBER - 02

(a) The number of the sheet within its sequence. This is page 2 of the Architectural demolition section.

(7) USER DEFINABLE xxx (Three digit user defined as needed)

b) MODEL FILES (Example Model File: QYZH082345A-XD0001)

(1) INSTALLATION CODE - QYZH (Mountain Home AFB)

(a) Use the four alpha character installation code. Use the following for each location.

(b) QYZH for locations at Mountain Home AFB

(c) GGWR for locations at Juniper Butte

(d) VAPM for locations at Saylor Creek Range

(e) You may obtain other installation codes from the IGI&S or Real Property Office.

(2) PROJECT NUMBER - 082345

(a) Use the assigned 6-digit project number provided by the contracting officer. For projects with more than one project number, use the most recent. For example, QYZH992345 indication a year of 99 (1999) would be less recent than QYZH082345 which is indicating a year of 08 (2008).

Use extensions A B or C only if these are actual designations for projects awarded separately.

(3) DISCIPLINE DESIGNATOR – A- (Architectural General)

(4) MODEL FILE TYPE – XD (Existing/Demolition plan)

(5) USER DEFINABLE xxxx (Four digit user defined as needed)

(a) If the sheets for an individual discipline such as Architectural are included in a single sheet file then the discipline designator would be A-and the sheet type designator and sheet sequence number would be of the lowest designation for what is shown on the page. Using the previous example if the sheet were to include an Architectural floorplan, elevations and a reverse ceiling plan the file name would change from QYZH082345AD102xxx to QYZH082345A-102xxx with “A-“ indicating a general architectural drawing and the “1” in the 102 indicating a plan view, as the floor plan and the reverse ceiling plan have the lowest designator, as per table 2-4. “Sheet type designators” found in the A/E/C standards.

5. Each sheet or page for the project shall have its own CAD file, each sheet can have several model files Xrefed into it. All XREFs will remain unbound and file names and paths will be “Relative”, as stated under the Path Type in the XREF dialog box.

a) For more documentation or clarification of Mountain Home Air Force Base’s Drawings deliverables, contact the base Installation GeoBase office.

J. AS-BUILT DRAWINGS & SPECIFICATIONS

1. The contractor shall submit plans and elevations drawings drawn to ¼” equals 1’ scale if the contractor purposes a piece of equipment and/or accessories on other than that specified. During the course of construction, the contractor shall keep an accurate record of differences in as-built drawings from the original designed or specified, by means of editing computer-aided design (CAD) files of contract drawings and word-processing files of specifications, saving them as separate files without overwriting the originals. When available, the government may provide record drawings of applicable facilities for use by the contractor to aid in developing as-built drawings. Drawings shall be editable in AutoCAD 2020 and specifications in Microsoft Word 2016 or PDF compatible. The contractor is responsible for providing any computer hardware and software required to prepare as-built drawings and specifications.

a) All variations from the contract drawings and specifications, including those made in consequence of the selection of optional or alternate materials, shall be clearly indicated. They shall be shown in the same general detail utilized in the original versions. The as-built hard copy drawings and specifications shall be kept current during construction and readily available for review by the PM and construction inspector at all times hard copy. The final as-built drawings shall be furnished to the CO not later than 14 calendar days after the final inspection date.

K. Contractor shall mark the location and dimension of any changes within the building or structure, as well as the accurate location and dimension of underground utilities and facilities. Mark the locations and description of any utility lines and other installations of any kind or description known to exist within the construction area. This includes all marked and unmarked utilities discovered during excavation. These locations include dimensions to permanent features such as corners of buildings, permanent survey markers, fire hydrants, etc. The contractor shall also submit the associated updated geodatabase electronic file. All map data shall use a Coordinate System of WGS 84, UTM Zone 11 N meters; all GPS coordinates shall be first order accuracy (+/- 2 cm).

Any and all errors, changes, or modifications to existing site features shall be reflected on the map and associated geodatabase.

1. All existing or abandoned utilities identified during construction, and all those installed, shall be surveyed, collecting latitude, longitude, elevation, material type, utility type, and size of utility. In the case for new utilities installed during construction; they shall be surveyed at every change in direction, intersection, connection point, or major change in elevation.

L. Mark changes in details of design, or additional information obtained from working drawings prepared and/or furnished by the Contractor including, but not limited to, fabrication, erection, installation, and planning details, pipe sized, insulation material dimensions of equipment, foundations, etc.

1. Mark all changes or modifications from the original design and the final inspection.

2. Wherever contract drawings or specifications allow options, only the option actually used in the construction shall be shown on the as-built drawings. The option(s) not used shall be deleted.

3. The contractor shall supplement the as-built field data with the as-built shop drawings for all HVAC, irrigation, structural steel, etc.

M. DELIVERY MEDIA:

1. ASCII survey point file on CD containing all survey points and a report containing a narrative of the equipment and the procedures used to meet the specified requirements.

2. A digital data file shall be provided to Mountain Home Air Force base in one of the following formats unless specified by Mountain Home AFB:

a) DWG (AutoCAD drawing file) – contact the base IGI&S (GeoBase) office for version required

b) SHP (ESRI shape file)

c) GDB (ESRI Geodatabase)(preferred method)

d) DXF (AutoCAD drawing exchange file)

3. Department of Defense Secure Access File Exchange (DoD SAFE)

a) Files can be submitted by requesting a DoD SAFE Drop-off.

(1) This web page will allow you to drop-off (upload) one or more files (up to 8 GB total) for anyone (either a DoD user or others). The recipient will receive an automated email containing the information you enter and instructions for downloading the file.

(2) DoD SAFE does not guarantee delivery of documents within a specified time period under 4 hours.

(3) No Classified information is allowed on DoD SAFE.

(4) A transmittal sheet must accompany the media containing the information included, total number of volumes being delivered and a list of file names and file descriptions on each volume. The transmittal sheet must also include instructions for reading, restoring, or transferring the files from the deliverable. File transfers of malware or malicious files are not supported.

4. CD-ROM

a) Digital Media must have an external label listing format and version of the operating system on which the media was created (e.g. Windows10), utility (command) used for writing the files to the media, a short description of contents, a sequence number if there are multiple volumes, and the date of CD creation.

(1) A transmittal sheet must accompany the media containing the information included on the external labels, total number of volumes being delivered and a list of file names and file descriptions on each volume. The transmittal sheet must also include instructions for reading, restoring, or transferring the files from the media, and certification that all delivery media is free of known computer viruses including the name(s) of the virus scanning software and the date the virus scan was performed.

N. GOVERNMENT FURNISHED MATERIALS

1. The Government will provide the contractor with data and information concerning all necessary and pertinent functions and principal features of the identified project.

These items will include:

2. The installation's latest georeferenced digital planimetric data and/or base map in ESRI ArcGIS Desktop version 10.8 format, with associated data files.

a) An empty File geodatabase (FGDB) with the appropriate schema can be provided by the Geobase office via Air Force DoD SAFE

3. The installation’s latest orthorectified imagery and specified geospatial parameters (coordinate system, datum, projection, distance units).

4. Any pertinent and necessary prototype or seed files.

5. Other data or schematics deemed necessary for project completion, pending approval from the Project Manager or the GeoBase office.