ID07180034_Supporting_Documents_Part_7.pdf

PDF 5 MB Posted

Attached to
Fence-to-Fence Environmental Services @ Beale AFB, CA
Solicitation number
ID07180034
Issued by

About this file

Supporting Documents Part 7

View the file

Other files

File Type Posted
Beale_WDR_permit.pdf PDF
ID07180034_Appendix_C_Beale_AFB_Previous_Experience_Information_Sheet_Revised_2.4.18.pdf PDF
2018_Beale_F2F_Presentation.pdf PDF
ID07180034_PWS_F2F_Beale_FINAL_2.1.19_Revised.pdf PDF
ID07180034_Supporting_Documents_Part_15.pdf PDF
ID07180034_Appendix_D_Beale_AFB_Past_Performance.pdf PDF
ID07180034_Supporting_Documents_Part_4.pdf PDF
ID07180034_Supporting_Documents_Part_16.pdf PDF
ID07180034_Appendix_E_Beale_AFB_Pricing_Worksheet_Final.xlsx XLSX spreadsheet
ID07180034_Supporting_Documents_Part_12.pdf PDF
ID07180034_Supporting_Documents_Part_2.pdf PDF
ID07180034_Supporting_Documents_Part_14.pdf PDF
ID07180034_Supporting_Documents_Part_13.pdf PDF
ID07180034_Supporting_Documents_Part_9.pdf PDF
ID07180034_PWS_F2F_Beale_FINAL_1.24.19.pdf PDF
ID07180034_Appendix_C_Beale_AFB_Previous_Experience_Information_Sheet.pdf PDF
ID07180034_Supporting_Documents_Part_8.pdf PDF
ID07180034_Supporting_Documents_Part_5.pdf PDF
ID07180034_Site_Visit_Sign_in_Sheet.pdf PDF
ID07180034-RFQ_NOTICE_-READ_ME_FIRST.pdf PDF
ID07180034_Supporting_Documents_Part_1.pdf PDF
ID07180034_Supporting_Documents_Part_6.pdf PDF
ID07180034-AFCEC_Beale_AFB-Site_Visit_(Q&A's).pdf PDF
ID07180034_Supporting_Documents_Part_3.pdf PDF
ID07180034_Supporting_Documents_Part_10.pdf PDF
ID07180034_Supporting_Documents_Part_11.pdf PDF
ID07180034_Attachment_6_CTP_Form_and_Instructions.pdf PDF
Show all 27

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

United States Air Force

Environmental GIS Program

Data Layer Specifications for:

Fuel Management Area

March 01, 2018

Data Layer Specification – Fuel Management Area

2 | P a g e

Revision History Date: Version: Description of Revision:

12/12/2016 FuelManagement Area_20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

6/23/2016 FuelManagement Area_20160623

Updated “Positional Accuracy” section.

3/9/2017 FuelManagement Area_20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

6/8/2017 FuelManagement Area_20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

3/1/2018 FuelManagement Area_20180301

Updated Definition, Geometry/Topology, Positional Accuracy, and Attributes sections.

3 | P a g e

This Data Layer Specification (DLS) defines geospatial data specifications for the FuelMgtArea_A data layer implemented under the United States Air Force Civil Engineer Center (AFCEC)

Environmental GIS Program.

Definition Non-linear areas within which fuels characteristics have been altered that produce, either intentionally or coincidentally, more manageable fire behavior. Non-fire fuels treatments, such as mechanical or chemical reduction of fuels, are examples of actions that may coincidentally serve to maintain Fuel Management Areas.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

FuelMgtArea_A

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalNaturalResources

Previous Layer Names: None

Geometry Type: Polygon

Data Steward Organization (Program Area):

Program Area: Natural Resources

Data Steward POC: AFCEC/CZTQ Air Force Natural Resources Program SME

Representation:

Fuel management areas are represented as closed polygons depicting the outermost extent of the area.

Each individual fuel management area is represented by a single area feature.

Implementing Authorities and Regulations

Implementing Program(s):

Driver(s):

HQ AF/A7CAN

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 17 September 2004

AFI32-7065, Cultural Resources Management Program, 1 June 2004

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

4 | P a g e

Implementing Program(s):

Driver(s):

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Geometry/Topology Polygon Features:

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design

(CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 12 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated accuracy threshold value.

Vertical Accuracy: Not applicable.

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

Coordinate System The bounding coordinates to capture the north, south, east, and west most spatial extents of the

FuelMgtArea_A layer will be based on the Universal Transverse Mercator (UTM) Zone, meters.

Datasets within the database should have a spatial reference with a precision of 1000. The

5 | P a g e horizontal datum to be utilized for all data is World Geodetic System 1984 (WGS84), and the projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the FuelMgtArea_A data layer.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate fuelMgtAreaIDPK

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7 digit unique number starting with 0000001.

String (20)

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

sdsFeatureName The common name of the feature.

Any common name used to describe the Fuel Management

Area.

String (80)

SDSFIE

sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the

Fuel Management Area that is not already included in the attribute table.

String (255)

SDSFIE

sdsMetadataID The foreign key to a metadata record.

(80)

SDSFIE

areaSize The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

D areaSizeUOM The unit of measure for the area of the calculated area.

acre

String

AF

6 | P a g e

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate perimeterSize The value of the measured perimeter.

Recorded to the 1/1000 of a foot.

Double AF

D perimeterSizeUOM The perimeter unit of measure.

foot

String (25)

AF

latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF longitude

The longitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

Latitude and Longitude values.

(15)

AF

maintFreq

The actual average interval between maintenance cycles for the fuel management area in months.

Double AF maintDate

The date the fuel management area was last maintained.

Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915).

Integer (Long)

AF

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

7 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (100)

AF

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

dataSteward

The data steward is the entity that oversees the data content, context, and associated business rules of the feature class.

AF

https://www.extranet.nga.mil/

8 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF creator

Person who created the feature. Last name of the person and first initial. Example: Jane

Smith would be attributed as "SmithJ."

(30)

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created or generated the feature.

(100)

AF

http://www.nationsonline.org/oneworld/country_code_list.htm http://www.nationsonline.org/oneworld/country_code_list.htm

9 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, Jane Smith would be attributed as SmithJ.

AF

dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was created or edited and why.

(255)

AF

mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, and other digital media.

AF

narrative Any additional comments or notes.

AF

GEOLOC

JOPES geolocator code.

(4)

AF

SHAPE_Length ESRI-generated field. ESRI

SHAPE_Area ESRI-generated field. ESRI

Business Tables The business table will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. Additional attributes to be determined by the Program Area Manager. The business table for FuelMgtArea_A is:

Table Name Identifier Source nr_FuelMgtArea fuelMgtAreaIDFK Program Area Manager

10 | P a g e

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

For Empty Text Values TBD (To Be Determined) – A value is required but the value has yet to be determined.

unknown The value cannot be reasonably determined.

NA (Not Applicable) No value exists.

For Empty Integer Values 99999 (To Be Determined) – A value is required but the value has yet to be determined.

88888 The value cannot be reasonably determined.

77777 (Not Applicable) No value exists.

For Empty Date Values 9/9/9999 (To Be Determined) – A value is required but the value has yet to be determined.

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete FGDC compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are made or as necessary.

Theme Keywords: Natural Resources, Fuel Management Area

Habitat Disturbance

Data Layer Specification – Habitat Disturbance

3/1/2018 HabitatDisturbance _20180301

Created Data Layer Specification for Habitat Disturbance.

This Data Layer Specification (DLS) defines geospatial data specifications for the

HabitatDisturbance_A data layer implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition Areas that have been impacted by disturbance of some sort, either natural or human caused.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

HabitatDisturbance_A

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalNaturalResources

Previous Layer Names: None

Geometry Type: Polygon

Data Steward Organization (Program Area):

Program Area: Natural Resources

Data Steward POC: AFCEC/CZTQ Air Force Natural Resources Program SME

Representation:

Habitat disturbance areas are represented as closed polygons depicting the outermost extent of the area.

Each individual habitat disturbance area is represented by a single area feature.

Implementing Authorities and Regulations

Implementing Program(s):

Driver(s):

HQ AF/A7CAN

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 17 September 2004

AFI32-7065, Cultural Resources Management Program, 1 June 2004

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Geometry/Topology Polygon Features:

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design

(CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 6 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated accuracy threshold value.

Vertical Accuracy: Not applicable.

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

Coordinate System The bounding coordinates to capture the north, south, east, and west most spatial extents of the

HabitatDisturbance_A layer will be based on the Universal Transverse Mercator (UTM) Zone, meters. Datasets within the database should have a spatial reference with a precision of 1000. The horizontal datum to be utilized for all data is World Geodetic System 1984 (WGS84), and the projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the HabitatDisturbance_A data layer.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

(D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate habDisturbanceIDPK

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

sdsFeatureName The common name of the feature.

Any common name used to describe the Habitat Disturbance.

String (80)

SDSFIE

sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the Habitat Disturbance that is not already included in the attribute table.

String (255)

SDSFIE

sdsMetadataID

SDSFIE

areaSize The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

D areaSizeUOM The unit of measure for the area of the calculated area.

acre

String (20)

AF

perimeterSize The value of the measured perimeter.

Recorded to the 1/1000 of a foot.

Double AF

D perimeterSizeUOM The perimeter unit of measure.

foot

String (25)

AF

latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF

Attribute Name Definition Allowed Values Data Type

(Length) Advocate longitude

The longitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

(15)

AF

D disturbanceSurveyTyp e

Indicates the type of survey conducted to assess and delineate the disturbance.

For a list of domain values, see

DisturbanceSurveyTyp e in Appendix 1.

String (20)

AF

D disturbanceType Indicates the general type of disturbance.

For a list of domain values, see

DisturbanceType in Appendix 1.

String (20)

AF

disturbanceCause A narrative describing the specific cause of the disturbance.

AF

D disturbanceDuration

Indicates whether the disturbance is temporary or permanent in nature.

Temporary disturbance would be expected to repair itself naturally without assistance, whereas permanent disturbance would require restoration/reclamatio n actions.

For a list of domain values, see

DisturbanceDuration in Appendix 1.

String (10)

AF

disturbanceDate

The date the disturbance occurred.

Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915).

Attribute Name Definition Allowed Values Data Type

(Length) Advocate disturbProjectName

The locally assigned name of the project that caused the disturbance.

(150)

AF

disturbProjectID

The locally assigned ID of the project that caused the disturbance.

AF

D isRemediated

Indicates whether remediation of the disturbance has occurred.

NA, no, TBD, yes String

(3)

AF

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

AF

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (100)

AF

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

dataSteward

The data steward is the entity that oversees the data content, context, and associated business

AF

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF https://www.extranet.nga.mil/ https://www.extranet.nga.mil/ http://www.nationsonline.org/oneworld/country_code_list.htm

Attribute Name Definition Allowed Values Data Type

(Length) Advocate creator

Person who created the feature. Last name of the person and first initial. Example: Jane

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created

AF

editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, AF dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was

Attribute Name Definition Allowed Values Data Type

(Length) Advocate mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, AF narrative

AF

GEOLOC

AF

SHAPE_Length ESRI-generated field. ESRI

SHAPE_Area ESRI-generated field. ESRI

Business Tables The business table will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. Additional attributes to be determined by the Program Area Manager. The business table for HabitatDisturbance_A is:

Table Name Identifier Source nr_HabitatDisturbance habDisturbanceIDFK Program Area Manager

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

For Empty Text Values TBD (To Be Determined) – A value is required but the value has yet to be determined.

11 | P a g e

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete FGDC compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are made or as necessary.

Theme Keywords: Natural Resources, Habitat Disturbance

12 | P a g e

Appendix 1: SDSFIE 3.1.1 AF AFCEC/CZ Adaptation

Attribute Domain Tables DOMAIN TABLE NAME: DisturbanceDuration

ATTRIBUTE NAME: disturbanceDuration

CODED DOMAIN DEFINITION

NA Not Applicable: No value exists.

other Other. Must be described in the sdsFeatureDescription attribute.

permanent The disturbance is considered permanent and unlikely to regenerate naturally.

TBD To Be Determined: A value is required but the value has yet to be determined.

temporary The disturbance is considered temporary and likely to regenerate naturally.

DOMAIN TABLE NAME: DisturbanceSurveyType

ATTRIBUTE NAME: disturbanceSurveyType

CODED DOMAIN DEFINITION

damageAssessment A Damage Assessment of unplanned disturbance was conducted.

disturbDelineation A Disturbance Delineation of planned disturbance was conducted.

NA Not Applicable: No value exists.

other Other. Must be described in the sdsFeatureDescription attribute.

DOMAIN TABLE NAME: DisturbanceType

ATTRIBUTE NAME: disturbanceType

CODED DOMAIN DEFINITION

burn The disturbance was caused by fire.

clearing The disturbance was caused by vegetation clearing activities.

construction The disturbance was caused by construction activities.

historicDisturbance The disturbance is associated with historical land use.

NA Not Applicable: No value exists.

other Other. Must be described in the sdsFeatureDescription attribute.

TBD To Be Determined: A value is required but the value has yet to be determined.

vandalism The disturbance was caused by vandalism.

vehicularImpact The disturbance was caused by a vehicle or other equipment unrelated to construction activities.

Habitat Protective Zone

Data Layer Specification – Habitat Protective Zone

12/12/2016 HabitatProtectiveZone _20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

3/9/2017 HabitatProtectiveZone _20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

6/8/2017 HabitatProtectiveZone _20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

3/1/2018 HabitatProtectiveZone _20180301

Updated Geometry/Topology, Positional Accuracy, and Attributes section.

HabitatProtectiveZone_A data layer implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition An area surrounding an identified habitat where recreation, training or other activities are restricted. This is a specific zone delineated by an agreement or law that extends beyond the actual habitat limits.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

HabitatProtectiveZone_A

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalNaturalResources

Previous Layer Names: habitat_protective_zone_area

Geometry Type: Polygon

Data Steward Organization (Program Area):

Program Area: Natural Resources

Data Steward POC: AFCEC/CZTQ Air Force Natural Resources Program SME

Representation:

Habitat protective zone areas are represented as closed polygons depicting the outermost extent of the area.

Each individual habitat protective zone area is represented by a single area feature.

Habitat protective zone areas include the species specific habitat area that is being protected.

Implementing Authorities and Regulations

Implementing Program(s):

Driver(s):

HQ AF/A7CAN

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 18 November 2014

AFI32-7065, Cultural Resources Management Program, 19 November

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Driver(s):

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Fish and Wildlife Migratory Bird Act

Bald and Golden Eagle Protection Act

Geometry/Topology

Polygon Features:

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design

(CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 3 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated accuracy threshold value.

Vertical Accuracy: Not applicable.

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

Coordinate System The bounding coordinates to capture the north, south, east, and west most spatial extents of the

HabitatProtectiveZone_A will be based on the Universal Transverse Mercator (UTM) Zone, meters.

Datasets within the database should have a spatial reference with a precision of 1000. The horizontal datum to be utilized for all data is World Geodetic System 1984 (WGS84), and the projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the HabitatProtectiveZone_A data layer.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate habProtectiveZoneIDP

K

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

sdsFeatureName The common name of the feature.

Any common name used to describe the Habitat Protective

Zone.

String (80)

SDSFIE

sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the

Habitat Protective Zone that is not already included in the attribute table.

String (255)

SDSFIE

sdsMetadataID

SDSFIE

areaSize The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D areaSizeUOM The unit of measure for the area of the calculated area.

acre

String (20)

AF

perimeterSize The value of the measured perimeter.

Recorded to the 1/1000 of a foot.

Double AF

D perimeterSizeUOM The perimeter unit of measure.

foot

String (25)

AF

latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF longitude

The longitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

AF

D speciesCat The code indicating the class of flora or fauna.

For a list of domain values, see SpeciesCat in Appendix 1.

String (15)

AF

restrictDateStart

The month and day land use restriction begins, if seasonal.

Format for date is

MMDD (i.e.

September 15 = 0915).

AF

restrictDateEnd

The month and day land use restriction ends, if seasonal.

Format for date is

MMDD (i.e.

September 15 = 0915).

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

AF

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (100)

AF

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

Attribute Name Definition Allowed Values Data Type

(Length) Advocate dataSteward

The data steward is the entity that oversees the data content, context, and associated business

AF

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF creator

Person who created the feature. Last name of the person and first initial. Example: Jane

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

http://www.nationsonline.org/oneworld/country_code_list.htm

Attribute Name Definition Allowed Values Data Type

(Length) Advocate dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created

AF

editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, AF dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was

AF

mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, AF narrative

AF

GEOLOC

AF

SHAPE_Length ESRI-generated field. ESRI

SHAPE_Area ESRI-generated field. ESRI

Business Tables The business table will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. Additional attributes to be determined by the Program Area Manager. The business table for HabitatProtectiveZone_A is:

Table Name Identifier Source nr_HabitatProtectiveZone habProtectiveZoneIDFK Program Area Manager

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

For Empty Text Values TBD (To Be Determined) – A value is required but the value has yet to be determined.

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete Federal Geographic Data Committee (FGDC) compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are made or as necessary.

Theme Keywords: Natural Resources, Habitat Protective Zone

DOMAIN TABLE NAME: SpeciesCat

ATTRIBUTE NAME: speciesCat

CODED DOMAIN DEFINITION

amphibia Amphibian species.

aves Avian (Birds) species.

bryoid Bryoid species.

crustacea Crustacean species.

epiphyte Epiphyte species.

general An aggregate of more than one species.

herb Herb species.

insecta Insect species.

liana Liana species.

mammalia Mammal species.

mollusca Mollusk species.

NA Not Applicable: No value exists.

other Other. Must be described in the sdsFeatureDescription attribute.

pisces Pisces (Fish) species.

reptilia Reptile species.

shrub Shrub species.

TBD To Be Determined: A value is required but the value has yet to be determined.

thallophyte Thallophyte species.

tree Tree species.

Hazardous Suppression

Area

Data Layer Specification – Hazardous Suppression Area

12/12/2016 HazardousSuppression Area_20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

6/23/2016 HazardousSuppression Area_20160623

Updated “Positional Accuracy” section.

3/9/2017 HazardousSuppression Area_20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

6/8/2017 HazardousSuppression Area_20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

3/1/2018 HazardousSuppression Area_20180301

Updated Definition, Geometry/Topology, Positional Accuracy, and Attributes sections.

HazSuppressionArea_A data layer implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition Areas in which fire management has potential hazardous risks to assets or personnel managing the fire. Some of these areas may be off-limits to fire fighting. For example, UXO contamination, QD arcs, and ammunition storage areas are some features that should be tracked within this data layer.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

HazSuppressionArea_A

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalNaturalResources

Previous Layer Names: None

Geometry Type: Polygon

Data Steward Organization (Program Area):

Program Area: Natural Resources

Data Steward POC: AFCEC/CZTQ Air Force Natural Resources Program SME

Representation:

Hazardous suppression areas are represented as closed polygons depicting the outermost extent of the area.

Each individual hazardous suppression area is represented by a single area feature.

Implementing Authorities and Regulations Implementing Program(s):

Driver(s):

HQ AF/A7CAN

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 18 November 2014

AFI32-7065, Cultural Resources Management Program, 19 November

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Driver(s):

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Geometry/Topology Polygon Features:

Polygons must not overlap.

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design

(CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 6 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated accuracy threshold value.

Vertical Accuracy: Not applicable.

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

Coordinate System

HazSuppressionArea_A layer will be based on the Universal Transverse Mercator (UTM) Zone, meters. Datasets within the database should have a spatial reference with a precision of 1000. The projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the HazSuppressionArea_A data layer.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

Domain (D)

Attribute Name Definition Allowed Values Data Type hazSuppressionAreaID

PK

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

sdsFeatureName The common name of the feature.

Any common name used to describe the

Hazardous Suppression Area.

String (80)

SDSDFIE

sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the

Hazardous Suppression Area that is not already included in the attribute table.

String (255)

SDSFIE

sdsMetadataID

SDSFIE

areaSize The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

D areaSizeUOM The unit of measure for the area of the calculated area.

acre

String

Attribute Name Definition Allowed Values Data Type

(Length) Advocate perimeterSize The value of the measured perimeter.

Recorded to the 1/1000 of a foot.

Double AF

D perimeterSizeUOM The perimeter unit of measure.

foot

String (25)

AF

latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF longitude

The longitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

AF

D suppressType The type of suppression authorized.

For a list of domain values, see

SuppressionType in Appendix 1.

String (8)

AF

D groundDisturb

Whether or not ground disturbing activities are authorized.

For a list of domain values, see

GroundDisturbance in Appendix 1.

String (15)

AF

D attackMethod Authorized methods to attack a fire.

For a list of domain values, see

FireAttackMethod in Appendix 1.

String (15)

AF

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (100)

AF

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

dataSteward

The data steward is the entity that oversees the data content, context, and associated business

AF

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF creator

Person who created the feature. Last name of the person and first initial. Example: Jane

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created

AF

http://www.nationsonline.org/oneworld/country_code_list.htm

Attribute Name Definition Allowed Values Data Type

(Length) Advocate editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, AF dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was

AF

mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, AF narrative

AF

GEOLOC

AF

SHAPE_Length ESRI-generated field. ESRI

SHAPE_Area ESRI-generated field. ESRI

Business Tables The business table will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. Additional attributes to be determined by the Program Area Manager. The business table for HazSuppressionArea_A is:

Table Name Identifier Source nr_HazSuppressionArea hazSuppressionAreaIDFK Program Area Manager

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

For Empty Text Values TBD (To Be Determined) – A value is required but the value has yet to be determined.

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete Federal Geographic Data Committee (FGDC) compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are

Theme Keywords: Natural Resources, Hazardous Suppression Area

DOMAIN TABLE NAME: FireAttackMethod

ATTRIBUTE NAME: attackMethod

CODED DOMAIN DEFINITION

all All fire attack methods are authorized.

NA Not Applicable: No value exists.

other Other. Must be described in the sdsFeatureDescription attribute.

plowing The fire may be attacked with plowing only.

TBD To Be Determined: A value is required but the value has yet to be determined.

water The fire may be attacked with water only.

waterPlowing The fire may be attacked with water and plowing only.

DOMAIN TABLE NAME: GroundDisturbance

ATTRIBUTE NAME: groundDisturb

CODED DOMAIN DEFINITION

authorized Ground disturbance activities are authorized.

NA Not Applicable: No value exists.

notAuthorized Ground disturbance activities are not authorized.

other Other. Must be described in the sdsFeatureDescription attribute.

DOMAIN TABLE NAME: SuppressionType

ATTRIBUTE NAME: suppressType

CODED DOMAIN DEFINITION

full Full suppression is authorized.

NA Not Applicable: No value exists.

none No suppression is authorized.

other Other. Must be described in the sdsFeatureDescription attribute.

road Suppression methods only requiring road access are authorized.

surface Suppression methods requiring surface attack methods are authorized.

Historic River Alignment

Data Layer Specification – Historic River Alignment

12/12/2016 HistoricRiverAlignment _20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

6/23/2016 HistoricRiverAlignment _20160623

Updated “Positional Accuracy” section.

3/9/2017 HistoricRiverAlignment _20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

6/8/2017 HistoricRiverAlignment _20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

3/1/2018 HistoricRiverAlignment _20180301

Updated Geometry/Topology,…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.