FLTP Road and Recreation Data Model Examples 2022.xlsx

XLSX spreadsheet 44 KB Posted Aug 3, 2022

Attached to: Recreational Road Inventories at USACE Project Sites
Opportunity number: W912DR22R0048
Issued by: Department of the Army Corps of Engineers

About this file

From the source

Department of Defense (DoD) Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE),

View the file

Other files

File	Type	Posted
Line Item Structure for W912DR22R0048.docx	DOCX document	Aug 19, 2022
W912DR22R0048 - Attachment A_Inventory Mapping (MAY 2022).xlsx	XLSX spreadsheet	Aug 3, 2022

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

BridgeToAdaptationTable

Entity Name

Entity Adaptation? (Yes/No)

Geometry

Attribute Name

Attribute Adaptation? (Yes/No)

Data Type

Field Length

Definition (3.1 Gold)

Definition (FLTP model)

Description

Note

Attribute Justification

Default Value

Enumeration

Enumeration Adaptation? (Yes/No)

Enumeration Definition

Subtype

Is List

Enumeration Justification

List of Enumerants (SDSFIE naming convention)

Enumerants Requiring Adaptation

Enumerant Justification

roadSegFLTP

Yes

Line

sdsId

No, SDSFIE 3.1 Gold

GUID

A unique identifierfor all features and objects in SDSFIE.

roadSegIdPK

Yes, Attribute Change to increase length to 25

String

Primary Key. A unique, user defined identifier for each record or instance of an entity.

RoadSegment

Attribute Name (FY20 Update)

Attribute Alias

SDSFIE RoadSegment GIS Required

Included in Related Attribute Table

FLH Required

Collect in Field or Option to Pre/Post Process

Data Type

Field Length

Definition

Description

Note

Enumeration

List of Enumerants

List of Enumerants Alternative Names

Symbology

Notes on crosswalk to FLH

featureDescription

Feature Description

yes

Collect in field

String(MAX)

The narrative describing the feature.

See Element Sheet

TBD

featureName

Feature Name

yes

RTE_NAME

Collect in field, verify with Project staff

String

The common name of the feature.

See Element Sheet

TBD

fieldMeasure

Field Measure

yes

RTE_LENGTH

Post (will use length calculated in GIS)

Real

The length of segment as determined in the field.

If isAnchorSection is True, then this is the official length of the segment for the linear reference system.

Per FLH: Total centerline length of route in miles (may include paved and unpaved). Distance between “From” and “To” points.

See Element Sheet

TBD

isAnchorSection

Is Anchor Section

yes

Post (always going to be "yes")

YesOrNo

The yes or no indicator of whether the RoadPoint is an anchor point.

An anchor point represents a physical location in the field that can be unambiguously described so that it can be clearly located in the real world using the point description. An anchor point is a link between the computer representation of the road system and the real world. An anchor point shall occur at the ends of an anchor section.

See Element Sheet

TBD

length

Segment Length

yes

Post, use miles (calculated length in GIS)

Real

The dimension of a feature taken along its primary alignment of use and generally in the horizontal plane.

The length of the RoadSeg feature may differ from the field-measured length due to differences in calculation.

Use miles.

See Element Sheet

TBD

mediaId

Media Identifier

yes

Leave Empty

String

Used to link the record to associated multimedia records that reference data.

Example media types include imagery, video, audio, scanned documents, and drawings.

See your DoD Component service implementation guidance for details as to the content of this attribute.

See Element Sheet

TBD

metadataId

Metadata Identifier

yes

Leave Empty

String

Used to represent or link to feature level metadata.

See Element Sheet

TBD

roadPathIdfk

Road Path Foreign Key Identifier

yes

Leave Empty

String

The foreign key used to link the record to the associated Road Path record.

See Element Sheet

TBD

roadSegmentIdpk

Primary Key Identifier

yes

FLMA_ROUTE_IDENT

Post process based on PSID, PSAID, Cat Code, Sequence, Suffix

String

Primary Key. A unique, user defined identifier for each record or instance of an entity.

See Element Sheet

TBD

roadSegStatus

Road Segment Status

yes

Collect

String

The category of status for the usage and existence of the feature.

For example, proposed, under construction, open to traffic, and abandoned.

RoadSegStatusType

See Element Sheet

TBD

rpnId

Real Property Network Identifier

yes

Leave Empty

String

The designator that distinguishes one real property network (RPN) from another within a RPI database.

Each Real Property Network Identifier is system dependent (likely system generated) at the base/installation-level. For combined data from multiple databases and upward reporting, the Real Property Network Identifier can be concatenated with the Real Property Site Unique Identifier (RPSUID) to identify the specific network. Each real property network shall have an installation unique Real Property Network Identifier in the base/installation RPI database. A site/installation may have multiple real property networks of the same type; each independent network must have its own Real Property Network Identifier. There must be at least one linear structure assigned to each Real Property Network Identifier.

All of the characters in the RPNID value must be alphanumeric [0-9a-zA-Z]. Definition Source: RPIM Version 8.1, March 31, 2015.

See Element Sheet

TBD

sdsId

Globally Unique Identifier

yes

Post process

GUID

The unique identifier for all entities in the SDSFIE.

See Element Sheet

TBD

segmentLengthUom

Segment Length Units of Measure

yes

Post, use miles

String

The segment length unit of measure.

GsipLengthUom

See Element Sheet

TBD

assetType

Asset Type

yes

ASSET_TYPE

Collect

String

Type of asset for vehicular use with improved surface

enumeration is "AssetType" [road, wayside, boatRamp, driveway, campingSpur, travelRoute]

[Road, Wayside, Boat Ramp, Driveway, Camping Spur, Travel Route]

TBD

userAccess

User Access

yes

USER_ACCESS

Collect

String

Indicates if the segment is open to the public or not.

Per 23 USC 125, public roads are defined as “a road that, except during scheduled periods, extreme weather conditions, or emergencies, the road is open to the general public for use with a standard passenger vehicle without restrictive gates or prohibitive signs or regulations, other than for general traffic control or restrictions based on size, weight, or class of registration.” Roads not meeting this definition should be enumerated as non-public.

enumeration is "UserAccessType" [public, nonPublic]

[Public, Non-Public]

TBD

allowPublicNonmotorized

Allow Public Non-Motorized

yes

Collect

String

For service roads only. Indicate if Public use is permitted by non-motoried means for recreation.

For example use of service roads by pedestrians or bicycles for recreation activity.

Use NA if Functional Class is 1, 2, 5 or 6. This field is only to provided additional info about service roads.

[NA, Yes, No]

TBD

managingAgencyType

Managing Agency Type

yes

Pre-process where possible, some won't be obvious. Consult with local staff in pre-meeting and verify in post meeting.

String

Indicates the entity, organization, or agency in which road maintenance and management responsibility is vested.

Source of enumerates is Operations and Maintenance Buisness Information Link managed by variable under Recreation. For Recreation Project Site Areas value should match OMBIL unless lease/easement specifies a different responsibility for roads.

enumeration is "ManagedByType" [allOthersQuasiPublic, concessionaire, corpsOfEngineers, localGovernment, otherFederalAgency, state]

[All Others (Quasi Public), Concessionaire, Corps of Engineers, Local Government, Other Federal Agency, State]

TBD

Want to keep our OMBIL managed by categories. Need to crosswalk to FLH (pg 4-128). Ex. 21, 25, 60, 80, 70. Consessionaire will equal 80 "other"

ownership

Ownership

yes

Consult with local staff in pre-meeting and verify in post meeting.

Short Integer

Entity that represents the road segment owner.

Code the level of government that best represents the highway owner irrespective of whether agreements exist for maintenance or other purposes.

Source is HPMS Chapter 4 Item 6. Plus fields added by USACE to represent non-government ownership

TBD

fltp

FLTP

yes

FLTP

Post process based on managedBy and userAccess attribute fields

String

Indicator is the road segment is included in the the Agencies FLTP network .

All USACE public road are included in the FLTP Network.

enumeration is "ManagedByFLTP" [yes, no, partial]

[Yes, No, Partial]

TBD

state

State

yes

STATE

pre or post process

String

State abbreviation in which route resides

TBD

district

District

yes

FLMA_REGION

pre or post process

String

Three character code that indicates USACE district.

For Recreation areas, this would come from the OMBIL PSA list

TBD

psId

PSID

yes

pre process

String

Project Site ID from OMBIL

TBD

psaId

PSAID

yes

FLMA_UNIT_ID

pre process

Long Integer

Project Site Area ID from OMBIL.

Partner "Unit" code /name

enter "0" if road segment is not located in Project Site Area

TBD

categoryCode

Category Code

yes

FUNCT_CLASS

Collect

Short Integer

Functional class based on USACE Function Class table.

Partner defined function class

enumeration is "CategoryCode" [1, 2, 3, 7, 8, 9]

[1, 2, 3, 7, 8, 9]

TBD

roadSeq

Road Sequence

yes

Post process

String

Number assigned to segment. Start from 001 for each category code found in a Project Site Area. Start from 001 for Project category code roads.

Numbering should start from the outer boundary of the PSA working in and around the park in the manner in which roads are encountered. For project level roads start from the dam or resources office and work clockwise around the project.

TBD

roadSeqSuffix

Road Sequence Suffix

yes

Collect if parking pad, post optional for spurs and travel lanes

String

Additional value that can be added to indicate a spinter that is related to another road segment or transportation asset.

Use "s" plus sequential number (ex s1) as needed for a splintered portion of road (ex opposite side of gate house or tirangle intersection). Use "tp" plus sequential number for travel lane through parking lot. If camping parking pad, use c plus site number (ex c101)

TBD

fromDesc

From Description

yes

FROM_DESC

Post process using XY field calculations

String

Latitude and Longitude

Description of beginning point of route; Specific physical locations desired, such as route intersection name or landmark; lat/long acceptable as last resort.

TBD

toDesc

To Description

yes

TO_DESC

Post process using XY field calculations

String

Latitude and Longitude

Description of end point of route; Specific physical locations desired, such as route intersection name or landmark; lat/long acceptable as last resort

TBD

featureNameStatus

Feature Name Status

yes

Post process using project consultation meeting

String

Indicator if common name is official or unofficial name

enumeration is "FeatureNameStatus" [official, unofficial]

[Official, Unofficial]

TBD

alias

Alias

yes

Post process using project consultation meeting

String

Alternate name that the feature is known by.

TBD

pavementMaterial

Pavement Material

yes

SURF_TYPE

Collect

String

Type of material used to construct the feature surface. Primary surface type.

Use same PavementMaterial enumaration found in ParkingArea entity

TBD

width

Width

yes

RTE_WIDTH

Collect

Float

Average width of the road segment, measured in feet.

Does not include shoulder width

TBD

lanes

Lanes

yes

NO_LANES

Collect

Short Integer

Number of lanes on the majority of the road segment

TBD

facilityType

Facility Type

yes

FACILITY_TYPE

Collect, using enumeration dropdown

Short Integer

The operational characteristic of the roadway.

For determining public road mileage, for investment requirements modeling to calculate capacity and estimate roadway deficiencies and improvement needs, in the cost allocation pavement model, and in the national highway database; for the querying and analysis of data (e.g., transportation performance management (TPM) metrics, Federal-aid project information, etc.) by facility type.

See HPMS Item 3 description and code list located here ON PAGE 4-18: https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/hpms_field_manual_dec2016.pdf

enumeration is "FacilityType" [1, 2, 4, 5, 6, 7]

[One-Way Roadway, Two-Way Roadway, Ramp, Non Mainline, Non Inventory Direction, Planned/Unbuilt]

TBD

stripedYN

StripedYN

yes

Collect

String

Indicator is the feature at a minimum has center line striping.

YesOrNo enumeration [yes, no]

[Yes, No]

TBD

verificationDate

Verification Date

yes

VER_DATE

Post process, date of the verification meeting with Project

Date

Date that the Route ID Information was last verified via Route ID Meeting or Field Visit.

This can be done via a field visit or online meeting with Project

TBD

femId

Facilities Equipment and Maintenance Identifier

yes

Leave Empty

String

Asset ID from FEM

TBD

createBy

Create By

yes

Collect, Post process where necessary

String

Creator of the road segment feature in the layer

Use editor tracking in Arc

TBD

createDate

Create Date

yes

Collect, this will be logged in the GPS

Date

Date the road segment feature was created in the layer

Use editor tracking in Arc

TBD

editBy

Edit By

yes

Post process

String

Editor of the road segment feature in the layer

Use editor tracking in Arc

TBD

editDate

Edit Date

yes

Post process

Date

Date the road segment feature was edited in the layer

Use editor tracking in Arc

TBD

maintenanceOperations

Maintenance Operations

yes

MAINTENANCE_OPERATIONS

Post process based on managedBy PSA attribute in OMBIL. May be able to collect this in field for some sites. Consultation with project required

Short Integer

The legal entity that maintains and operates a roadway. Needed For administrative, legislative, analytical, and national highway database purposes.

See HPMS Item 68 description and code list located here ON PAGE 4-128: https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/hpms_field_manual_dec2016.pdf

Crosswalk to managedBy for now.

enumeration is "MaintenanceOperationsType" [1, 2, 3, 4, 11, 12, 21, 25, 26, 27, 31, , 32, 40, 60, 62, 63, 64, 66, 67, 68, 69, 70, 72, 73, 74, 80]

[State Highway Agency, County Highway Agency; Town or Township Highway Agency; City or Municipal Highway Agency; State Park, Forest, or Reservation Agency; Local Park, Forest or Reservation Agency; Other State Agency; Other Local Agency; Private (other than Railroad); Railroad; State Toll Authority; Local Toll Authority; Other Public Instrumentatlity; Other Federal Agency; Bureau of Indian Affairs; Bureau of Fish and Wildlife; U.S. Forest Service; National Park Service; Tennessee Valley Authority; Bureau of Land Management; Bureau of Reclamation; Corps of Engineers; Air Force; Navy/Marines; Army; Other

TBD

Want to keep our OMBIL managed by categories. Need to crosswalk to FLH (pg 4-128). Ex. 21, 25, 60, 80, 70. Consessionaire will equal 80 "other"

featureName

Feature Name

yes

RTE_NAME

Collect in field, verify with Project staff

String

The common name of the feature.

TBD

ParkingArea

Attribute Name (FY20 UPDATE)

Attribute Alias

SDSFIE ParkingArea GIS Required

Included in Related Attribute Table

FLH Required

Collect in Field or Option to Pre/Post Process

Data Type

Field Length

Definition

Description

Note

Enumeration

List of Enumerants

List of Enumerants Alternative Names

Symbology

featureDescription

Feature Description

yes

Collect in field

String(MAX)

The narrative describing the feature.

See Element Sheet

featureName

Feature Name

yes

RTE_NAME

Collect in field, verify with Project staff

String

The common name of the feature.

Typically this information will come from the District or Project.

See Element Sheet

isPaved

Is Paved

yes

PARKING_STATUS_TYPE

Collect in field

YesOrNo

The yes or no indicator of whether the feature has a paved surface.

Formerly had a field called "pavedStatus" which indicated "paved" or "unpaved." This will be a "yes" or "no."

See Element Sheet

mediaId

Media Identifier

yes

Leave Empty

String

Used to link the record to associated multimedia records that reference data.

Example media types include imagery, video, audio, scanned documents, and drawings.

See your DoD Component service implementation guidance for details as to the content of this attribute.

See Element Sheet

metadataId

Metadata Identifier

yes

Leave Empty

String

Used to represent or link to feature level metadata.

See Element Sheet

numberOfSpaces

Number of Spaces

yes

Collect in Field

Integer

The total parking spaces available in the area including handicapped or reserved spaces.

Sum of car and trailer spaces

See Element Sheet

operationalStatus

Operational Status

yes

Collect in field

String

The state of usability of the feature.

OperationalStatus

See Element Sheet

parkingAreaIdpk

Primary Key Identifier

yes

FLMA_ROUTE_IDENT

Post process

String

Primary Key. A unique, user defined identifier for each record or instance of an entity.

See Element Sheet

pavementMaterial

Pavement Material

yes

SURF_TYPE

Collect in field

String

The type of material used to construct the pavement feature.

PavementMaterial

See Element Sheet

propertyIdCode

Property ID Code

yes

Leave Empty

String

This unique identifier will be used to link Civil Works Real Property Assets to REMIS.

The attribute specifically supports the following USACE programs and/or functional areas: REMIS.

See Element Sheet

rpnId

Real Property Network Identifier

yes

Leave Empty

String

The designator that distinguishes one real property network (RPN) from another within a RPI database.

All of the characters in the RPNID value must be alphanumeric [0-9a-zA-Z]. Definition Source: RPIM Version 8.1, March 31, 2015.

See Element Sheet

rpsuid

Real Property Site Unique Identifier

yes

Leave Empty

Integer

A non-intelligent code used to permanently and uniquely identify a DoD real property site.

RPSUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).

Source: DoDI 4165.14, January 17, 2014.

See Element Sheet

rpuid

Real Property Unique Identifier

yes

Leave Empty

String

A non-intelligent code used to permanently and uniquely identify a DoD real property asset.

RPUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).

All of the characters in the RPUID value must be numeric [0-9]. Source: DoDI 4165.14, January 17, 2014.

See Element Sheet

sdsId

Globally Unique Identifier

yes

Post process

GUID

The unique identifier for all entities in the SDSFIE.

See Element Sheet

assetType

Asset Type

yes

ASSET_TYPE

Collect in field

String

Type of asset for vehicular use with improved surface

Types per EM 1110-2-410 chapter 7, Parking.

enumeration is "AssetType" [onRoad, offRoad, terminal]

[On-Road, Off-Road, Terminal]

userAccess

User Access

yes

USER_ACCESS

Collect in field

String

Indicates if the parking lot is open to the public or not.

Per 23 USC 125, public roads are defined as “a road that, except during scheduled periods, extreme weather conditions, or emergencies, the road is open to the general public for use with a standard passenger vehicle without restrictive gates or prohibitive signs or regulations, other than for general traffic control or restrictions based on size, weight, or class of registration.” Parking generally not meeting this definition should be enumerated as non-public.

enumeration is "UserAccessType" [public, nonPublic]

[Public, Non-Public]

flmaPartner

FLMA Partner

yes

FLMA_PARTNER

Pre or post process, will always be "USACE"

String

Indicates the Federal Lands Transportation Program participing agency fee boundary or easement the parking lot falls within.

Covers all transportation assets at Corps of Engineers projects. Managed by will allow for indicator of entity where maintenance responsibility is vested. Would cover roads in the fee boundary where the Corps of Engineers has a vested interest including outgrans, regardess of the managing entity. In the case of lease to other Federal Land Management Agency, this may result in duplication with their Federal Lands Transportation Program Inventory.

For Corps of Engineers, value will be USACE. Different from managed by……

managedBy

Managed By

yes

MANAGED_BY_TYPE

Consult with local staff in pre-meeting and verify in post meeting.

String

Indicates the entity (find better word that would be inclusive of busineesses) in which parking lot maintenance and management responsibility is vested.

enumeration is "ManagedByType" [allOthersQuasiPublic, concessionaire, corpsOfEngineers, localGovernment, otherFederalAgency, state]

[All Others (Quasi Public), Concessionaire, Corps of Engineers, Local Government, Other Federal Agency, State]

fltp

FLTP

yes

FLTP

Post process based on managedBy and userAccess

String

Indicator is the parking lot is included in the the Agencies FLTP network .

All USACE public transportation assets are included in the FLTP Network.

enumeration is "ManagedByFLTP" [yes, no, partial]

[Yes, No, Partial]

state

State

yes

STATE

pre or post process

String

Two character postal code to indicate the state in which the parking lot lies

district

District

yes

FLMA_REGION

pre or post process

String

Three character code that indicates USACE district.

psId

PSID

yes

pre process if possible

String

Project Site ID from OMBIL

psaId

PSAID

yes

FLMA_UNIT_ID

pre process if possible

Long Integer

Project Site Area ID from OMBIL.

categoryCode

Category Code

yes

FUNCT_CLASS

Collect and verify in project consultation meeting

Short Integer

Function class based on USACE transportation asset funciton class table

Function class 4 refers to project parking, class 5 refers to area parking, class 6 refers to service/adminitrative parking

enumeration is "CategoryCode" [4, 5, 6]

[4, 5, 6]

parkingSeq

Parking Sequence

yes

Post process

String

Number assigned to segment. Start from 001 for each Project Site Area parking lot. Start from 001 for Project parking lots.

Numbering should start from the outer boundary of the PSA working in and around the park in the manner in which roads are encountered. For project level transportation assets start from the dam or resources office and work clockwise around the Project.

parkingSeqSuffix

Parking Sequence Suffix

yes

Post process

featureNameStatus

Feature Name Status

yes

Post process using project consultation meeting

String

Indicator if common name is official or unofficial name

Only a District or Project can verify if a given name is official or not.

enumeration is "FeatureNameStatus" [official, unofficial]

[Official, Unofficial]

alias

Alias

yes

Post process using project consultation meeting

String

Alternate name that the feature is known by.

stripedYN

StripedYN

yes

Collect in field

String

Indicator is parking has striping for spaces

YesOrNo enumeration [yes, no]

[Yes, No]

numberOfCarSpaces

Number of Car Spaces

yes

Collect in field

Short Integer

The total car parking spaces available in the area including handicapped or reserved spaces.

numberOfTrailerSpaces

Number of Trailer Spaces

yes

Collect in field

Short Integer

The total trailer parking spaces available in the area including handicapped or reserved spaces.

squareFeet

Square Feet

yes

SQ_FEET

Post process using GIS

Double

Parking square foot area

femId

Facilities Equipment and Maintenance Identifier

yes

Leave Empty

String

Asset ID from FEM

createBy

Create By

yes

Collect or Post process

String

Creator of the parking lot feature in the layer

Use editor tracking in Arc

TBD

createDate

Create Date

yes

Collect, Post process where necessary

Date

Date the parking lot feature was created in the layer

editBy

Edit By

yes

Post process

String

Editor of the parking lot feature in the layer

editDate

Edit Date

yes

Post process

Date

Date the parking lot feature was edited in the layer

maintenanceOperations

Maintenance Operations

yes

MAINTENANCE_OPERATIONS

Post process based on managedBy. May be able to collect this in field for some sites. Consultation with project required

Short Integer

The legal entity that maintains and operates a roadway. Needed For administrative, legislative, analytical, and national highway database purposes.

See HPMS Item 68 description and code list located here ON PAGE 4-128: https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/hpms_field_manual_dec2016.pdf

Crosswalk to managedBy for now.

enumeration is "MaintenanceOperationsType" [1, 2, 3, 4, 11, 12, 21, 25, 26, 27, 31, , 32, 40, 60, 62, 63, 64, 66, 67, 68, 69, 70, 72, 73, 74, 80]

TBD

Want to keep our OMBIL managed by categories. Need to crosswalk to FLH (pg 4-128). Ex. 21, 25, 60, 80, 70. Consessionaire will equal 80 "other"

facilityType

Facility Type

yes

FACILITY_TYPE

Collect in field

Short Integer

The operational characteristic of the roadway.

See HPMS Item 3 description and code list located here ON PAGE 4-18: https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/hpms_field_manual_dec2016.pdf

enumeration is "FacilityType" [1, 2, 4, 5, 6, 7]

[One-Way Roadway, Two-Way Roadway, Ramp, Non Mainline, Non Inventory Direction, Planned/Unbuilt]

TBD

featureName

Feature Name

yes

RTE_NAME

Collect in field, verify with Project staff

String

The common name of the feature.

Typically this information will come from the District or Project.

Campsite

Attribute Name	Attribute Alias Name	SDSFIE Required	Collect in Field or Option to Pre/Post Process	Data Type	Field Length	Definition	Description	Note	Enumeration	List of Enumerants	List of Enumerants Alternative Names
campsiteUseType	Campsite Use Type	yes	Collect in field, verify with Project	String	19	The description of the primary use type for the campsite.			CampsiteUseType	See Element Sheet	See Element Sheet
featureDescription	Feature Description	yes	Collect in field	String(MAX)	0	The narrative describing the feature.				See Element Sheet	See Element Sheet
featureName	Feature Name	yes	Collect in field	String	80	The common name of the feature.				See Element Sheet	See Element Sheet
isReservableViaNrrs	Is Reservable Via NRRS	yes	Either Collect or Post process and verify with Project	YesOrNo	0	The yes or no indicator of whether the site is reservable via the National Recreation Reservation Service (NRRS).				See Element Sheet	See Element Sheet
mediaId	Media Identifier	yes	Leave empty	String	40	Used to link the record to associated multimedia records that reference data.	Example media types include imagery, video, audio, scanned documents, and drawings.	See your DoD Component service implementation guidance for details as to the content of this attribute.		See Element Sheet	See Element Sheet
metadataId	Metadata Identifier	yes	Leave empty	String	80	Used to represent or link to feature level metadata.				See Element Sheet	See Element Sheet
nrrsCampsiteId	NRRS Campsite Identifier	yes	Post process, verify with Project	String	10	The National Recreation Reservation Service (NRRS) identifier for the campsite.				See Element Sheet	See Element Sheet
propertyIdCode	Property ID Code	yes	Leave empty	String	20	This unique identifier will be used to link Civil Works Real Property Assets to REMIS.		The attribute specifically supports the following USACE programs and/or functional areas: REMIS.		See Element Sheet	See Element Sheet
recreationBoundaryIdfk	Recreation Boundary Foreign Key	yes	Leave empty	String	40	The foreign key used to link the record to the associated Recreation Boundary record.				See Element Sheet	See Element Sheet
recreationFeatureIdpk	Primary Key Identifier	yes	Post process based on PSID, PSAID, Cat Code, Campsite Number	String	40	Primary Key. A unique, user defined identifier for each record or instance of an entity.				See Element Sheet	See Element Sheet
recreationFeatureType	Recreation Feature Type	yes	Post process, will always be campsite	String	25	The type of recreation feature.			RecreationFeatureUseType	See Element Sheet	See Element Sheet
rpsuid	Real Property Site Unique Identifier	yes	Leave empty	Integer	0	A non-intelligent code used to permanently and uniquely identify a DoD real property site.	RPSUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).	Source: DoDI 4165.14, January 17, 2014.		See Element Sheet	See Element Sheet
rpuid	Real Property Unique Identifier	yes	Leave empty	String	18	A non-intelligent code used to permanently and uniquely identify a DoD real property asset.	RPUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).	All of the characters in the RPUID value must be numeric [0-9]. Source: DoDI 4165.14, January 17, 2014.		See Element Sheet	See Element Sheet
sdsId	Globally Unique Identifier	yes	Post process	GUID	0	The unique identifier for all entities in the SDSFIE.				See Element Sheet	See Element Sheet
recProjectSiteId	Project Site Identifier	no	Pre or Post process	Double		Project Site ID
recProjectSiteAreaId	Project Site Area Identifier	no	Pre or Post process	Double		Project Site Area ID
grill	Grill	no	Collect in field	String	3	Indicates the presence of a grill at the campsite			YesNo	yes, no	Yes, No
shadeShelter	Shade Shelter	no	Collect in field	String	3	Indicates the presence of a shade shelter at the campsite			YesNo	yes, no	Yes, No
firepit	Firepit	no	Collect in field	String	3	Indicates the presence of a firepit at the campsite			YesNo	yes, no	Yes, No
picnicTable	Picnic Table	no	Collect in field	String	3	Indicates the presence of a picnic table at the campsite			YesNo	yes, no	Yes, No
drivewayType	Driveway Type	no	Collect in field	String	12	Indicates the primary method by which a user of the campsite may access the site			DrivewayType	backIn, nA, other, pullThrough, walkTo	Back-In, NA, Other, Pull-Through, Walk To
drivewaySurface	Driveway Surface	no	Collect in field	String	11	The type of material used to construct the pavement feature.			PavementMaterial	See ParkingArea Element Sheet	See ParkingArea Element Sheet
water	Water	no	Collect in field	String	3	Indicates the presence of a water spigot at campsite			YesNo	yes, no	Yes, No
electricAmperage	Electric Amperage	no	Collect in field	String	3	Indicates the amount of amperage of an electrical outlet IF one is provided at the campsite.			ElectricAmperage	0, 20, 30, 50, 100	0, 20, 30, 50, 100
sewage	Sewage	no	Collect in field	String	3	Indicates the presence of sewage access at campsite			YesNo	yes, no	Yes, No

ReceationFeature_PicnicSite

Attribute Name	Attribute Alias Name	SDSFIE Required	Collect in Field or Option to Pre/Post Process	Data Type	Field Length	Definition	Description	Note	Enumeration	List of Enumerants	List of Enumerants Alternative Names
district	District	yes	Pre or Post process	String	3	Three character identifier for Civil U.S. Army Corps of Engineers District.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.	DistrictCode	See Element Sheet	See Element Sheet
division	Division	yes	Pre or Post process	String	3	Three character identifier for Civil U.S. Army Corps of Engineers Division.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.	DivisionCode	See Element Sheet	See Element Sheet
featureDescription	Feature Description	yes	Collect in field	String(MAX)	0	The narrative describing the feature.				See Element Sheet	See Element Sheet
featureName	Feature Name	yes	Collect in field, use signage and name of area in the picnic site name	String	80	The common name of the feature.				See Element Sheet	See Element Sheet
feeAreaClass	Fee Area Class	yes	Collect if possible, post process if needed and consult/verify with project	String	3	Classification of fees for campgrounds and day use facilities.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.	FeeAreaClass	See Element Sheet	See Element Sheet
feeIndicator	Fee Indicator	yes	Collect if possible, post process if needed and consult/verify with project	String	3	The indicator of whether the area is considered a Corps "fee" area; outgranted area fees are not tracked.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.	FeeIndicator	See Element Sheet	See Element Sheet
foundationalId	Foundational ID	yes	Leave empty	Integer	30	This is the unique ID for the CPN (Corps Project Notebook) polygons - Foundational Projects.				See Element Sheet	See Element Sheet
internalId	Internal ID	yes	Leave empty	Integer	30	The CPN (Corps Project Notebook) ID.				See Element Sheet	See Element Sheet
managingAgencyType	Managing Agency Type	yes	Collect if possible, post process if needed and consult/verify with project	String	29	The type of agency with the primary management responsibility for this project site area.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.	ManagingAgencyType	See Element Sheet	See Element Sheet
mediaId	Media Identifier	yes	Leave empty	String	40	Used to link the record to associated multimedia records that reference data.	Example media types include imagery, video, audio, scanned documents, and drawings.	See your DoD Component service implementation guidance for details as to the content of this attribute.		See Element Sheet	See Element Sheet
metadataId	Metadata Identifier	yes	Leave empty	String	80	Used to represent or link to feature level metadata.				See Element Sheet	See Element Sheet
primaryAreaSubType	Primary Area SubType	yes	Pre or Post process using OMBIL data, verify with Project staff	String	17	Recreation area type that best describes the primary function of a project site area.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.	PrimaryAreaSubType	See Element Sheet	See Element Sheet
projectAreaStatus	Project Area Status	yes	Pre or Post process using OMBIL data, verify with Project staff	String	16	The operational status of the project area site.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.	ProjectSiteAreaStatus	See Element Sheet	See Element Sheet
propertyIdCode	Property ID Code	yes	Leave empty	String	20	This unique identifier will be used to link Civil Works Real Property Assets to REMIS.		The attribute specifically supports the following USACE programs and/or functional areas: REMIS.		See Element Sheet	See Element Sheet
recProjectSiteAreaId	Rec Project Site Area Identifier	yes	Pre or Post process	Real	10	The identifier assigned to a Recreation Project Site Area.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.		See Element Sheet	See Element Sheet
recProjectSiteAreaName	Rec Project Site Area Name	yes	Pre or Post process	String	70	The name of a logical or physical subset or component of a recreation project site or single management unit.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.		See Element Sheet	See Element Sheet
recProjectSiteId	Rec Project Site Identifier	yes	Pre or Post process	Real	10	The identifier assigned to a Project Site.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.		See Element Sheet	See Element Sheet
recProjectSiteName	Rec Project Site Name	yes	Pre or Post process	String	70	The name of a primarily contiguous, completed, legally funded, geographic location of a recreation site within a single USACE District.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.		See Element Sheet	See Element Sheet
recreationBoundaryIdfk	Recreation Boundary Foreign Key	yes	Leave empty	String	40	The foreign key used to link the record to the associated Recreation Boundary record.				See Element Sheet	See Element Sheet
recreationFeatureIdpk	Primary Key Identifier	yes	Post process based on PSID, PSAID, Cat Code, Picnic site number (or sequential number)	String	40	Primary Key. A unique, user defined identifier for each record or instance of an entity.				See Element Sheet	See Element Sheet
recreationFeatureType	Recreation Feature Type	yes	Post process, will always be picnic site or picnic shelter. Picnic shelters will be copied over to structure feature class as well and stored using the structure data model. This will result in the data stored in 2 places for 2 separate purposes.	String	25	The primary recreational use of the feature.			RecreationFeatureUseType	See Element Sheet	See Element Sheet
rpsuid	Real Property Site Unique Identifier	yes	Leave empty	Integer	0	A non-intelligent code used to permanently and uniquely identify a DoD real property site.	RPSUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).	Source: DoDI 4165.14, January 17, 2014.		See Element Sheet	See Element Sheet
rpuid	Real Property Unique Identifier	yes	Leave empty	String	18	A non-intelligent code used to permanently and uniquely identify a DoD real property asset.	RPUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).	All of the characters in the RPUID value must be numeric [0-9]. Source: DoDI 4165.14, January 17, 2014.		See Element Sheet	See Element Sheet
sdsId	Globally Unique Identifier	yes	Post process	GUID	0	The unique identifier for all entities in the SDSFIE.				See Element Sheet	See Element Sheet
versAreaCode	VERS Area Code	yes	Post process, verify with Project staff	Real	3	The three-digit number that identifies the project site area in the Visitation Estimation and Reporting System (VERS) program.		The attribute specifically supports the following USACE programs and/or functional areas: Recreation.		See Element Sheet	See Element Sheet
grill	Grill	no	Collect in field	String	3				YesOrNo	yes, no	Yes, No
shadeShelter	Shade Shelter	no	Collect in field	String	3				YesOrNo	yes, no	Yes, No
firepit	Firepit	no	Collect in field	String	3				YesOrNo	yes, no	Yes, No
picnicTable	Picnic Table	no	Collect in field	String	3				YesOrNo	yes, no	Yes, No
water	Water	no	Collect in field	String	3				YesOrNo	yes, no	Yes, No
electricAmperage	Electric Amperage	no	Collect in field	String	3				ElectricAmperage	0, 20, 30, 50, 100	0, 20, 30, 50, 100
adaSite	ADA Site	no	Collect in field	String	3				YesOrNo	yes, no	Yes, No

RecreationTrailFeature

Attribute Name	Attribute Alias Name	SDSFIE Required	Collect in Field or Option to Pre/Post Process	Data Type	Field Length	Definition	Description	Note	Enumeration	List of Enumerants	List of Enumerants Alternative Names
featureDescription	Feature Description	yes	Collect in field	String(MAX)	0	The narrative describing the feature.				See Element Sheet	See Element Sheet
featureName	Feature Name	yes	Collect in field	String	80	The common name of the feature.				See Element Sheet	See Element Sheet
mediaId	Media Identifier	yes	Leave Empty	String	40	Used to link the record to associated multimedia records that reference data.	Example media types include imagery, video, audio, scanned documents, and drawings.	See your DoD Component service implementation guidance for details as to the content of this attribute.		See Element Sheet	See Element Sheet
metadataId	Metadata Identifier	yes	Leave Empty	String	80	Used to represent or link to feature level metadata.				See Element Sheet	See Element Sheet
propertyIdCode	Property ID Code	yes	Leave Empty	String	20	This unique identifier will be used to link Civil Works Real Property Assets to REMIS.		The attribute specifically supports the following USACE programs and/or functional areas: REMIS.		See Element Sheet	See Element Sheet
recreationTrailFeatureIdpk	Primary Key Identifier	yes	Post Process	String	40	Primary Key. A unique, user defined identifier for each record or instance of an entity.				See Element Sheet	See Element Sheet
recreationTrailFeatureType	Recreation Trail Feature Type	yes	Collect in field, verify with Project staff	String	23	The type of recreation trail feature.			RecreationTrailFeatureType	See Element Sheet	See Element Sheet
rpnid	Real Property Network Identifier	yes	Leave Empty	String	4	The designator that distinguishes one real property network (RPN) from another within a RPI database.	Each Real Property Network Identifier is system dependent (likely system generated) at the base/installation-level. For combined data from multiple databases and upward reporting, the Real Property Network Identifier can be concatenated with the Real Property Site Unique Identifier (RPSUID) to identify the specific network. Each real property network shall have an installation unique Real Property Network Identifier in the base/installation RPI database. A site/installation may have multiple real property networks of the same type; each independent network must have its own Real Property Network Identifier. There must be at least one linear structure assigned to each Real Property Network Identifier.	All of the characters in the RPNID value must be alphanumeric [0-9a-zA-Z]. Definition Source: RPIM Version 8.1, March 31, 2015.		See Element Sheet	See Element Sheet
rpsuid	Real Property Site Unique Identifier	yes	Leave Empty	Integer	0	A non-intelligent code used to permanently and uniquely identify a DoD real property site.	RPSUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).	Source: DoDI 4165.14, January 17, 2014.		See Element Sheet	See Element Sheet
rpuid	Real Property Unique Identifier	yes	Leave Empty	String	18	A non-intelligent code used to permanently and uniquely identify a DoD real property asset.	RPUIDs are exclusively issued by the Real Property Unique Identifier Registry (RPUIR).	All of the characters in the RPUID value must be numeric [0-9]. Source: DoDI 4165.14, January 17, 2014.		See Element Sheet	See Element Sheet
sdsId	Globally Unique Identifier	yes	Leave Empty	GUID	0	The unique identifier for all entities in the SDSFIE.				See Element Sheet	See Element Sheet
recProjectSiteId	Project Site Identifier	no	Pre or Post Process	Double		Project Site ID
recProjectSiteAreaId	Project Site Area Identifier	no	Pre or Post Process	Double		Project Site Area ID
recreationalTrailUse	Recreational Trail Use	no	Collect in field, consult OMBIL, verify with Project staff	String	22				RecreationTrailUseType	4wd, atv, bike, crossCountrySki, dogSled, equestrianOrPack, hike, motorcycle, multiple, multiUseNonMotorized, other, snowmobile, showshoe, tbd, useNotSpecified, watercraftMotorized, watercraftNonMotorized,	Four-Wheel Drive, All-Terrain Vehicle, Bike, Cross Country Ski, Dog Sled, Equestrian Or Pack, Hike, Motorcycle, Multiple, Multi-Use Non-Motorized, Other, Snowmobile, Snowshoe, To Be Determined, Use Not Specified, Motorized Watercraft, Non-Motorized Watercraft

RoadPoint

Attribute Name	Attribute Alias Name	SDSFIE Required	Collect in Field or Option to Pre/Post Process	Data Type	Field Length	Definition	Description	Note	Enumeration	List of Enumerants	List of Enumerants Alternative Names
featureDescription	Feature Description	yes	Pre or Post Process	String(MAX)	0	The narrative describing the feature.				See Element Sheet	See Element Sheet
featureName	Feature Name	yes	Pre or Post Process	String	80	The common name of the feature.				See Element Sheet	See Element Sheet
isAnchorPoint	Is Anchor Point	yes	Post Process	YesOrNo	0	The yes or no indicator of whether the RoadPoint is an anchor point.	An anchor point represents a physical location in the field that can be unambiguously described so that it can be clearly located in the real world using the point description. An anchor point is a link between the computer representation of the road system and the real world. An anchor point shall occur at the ends of an anchor section (see RoadSeg).			See Element Sheet	See Element Sheet
mediaId	Media Identifier	yes	Leave Empty	String	40	Used to link the record to associated multimedia records that reference data.	Example media types include imagery, video, audio, scanned documents, and drawings.	See your DoD Component service implementation guidance for details as to the content of this attribute.		See Element Sheet	See Element Sheet
metadataId	Metadata Identifier	yes	Leave Empty	String	80	Used to represent or link to feature level metadata.				See Element Sheet	See Element Sheet
roadPointIdpk	Primary Key Identifier	yes	Post Process	String	40	Primary Key. A unique, user defined identifier for each record or instance of an entity.				See Element Sheet	See Element Sheet
sdsId	Globally Unique Identifier	yes	Leave Empty	GUID	0	The unique identifier for all entities in the SDSFIE.				See Element Sheet	See Element Sheet
recProjectSiteId	Project Site Identifier	no	Pre or Post Process	Double		Project Site ID
recProjectSiteAreaId	Project Site Area Identifier	no	Pre or Post Process	Double		Project Site Area ID

TrafficCounter

Attribute Name	Attribute Alias Name	SDSFIE Required	Collect in Field or Option to Pre/Post Process	Data Type	Field Length	Definition	Description	Note	Enumeration	List of Enumerants	List of Enumerants Alternative Names
featureDescription	Feature Description	yes	Collect in field	String(MAX)	0	The narrative describing the feature.				See Element Sheet	See Element Sheet
featureName	Feature Name	yes	Collect in field	String	80	The common name of the feature.				See Element Sheet	See Element Sheet
manufacturerName	Manufacturer Name	yes	Post Process	String	80	The manufacturer of the traffic counter.				See Element Sheet	See Element Sheet
mediaId	Media Identifier	yes	Leave empty	String	40	Used to link the record to associated multimedia records that reference data.	Example media types include imagery, video, audio, scanned documents, and drawings.	See your DoD Component service implementation guidance for details as to the content of this attribute.		See Element Sheet	See Element Sheet
metadataId	Metadata Identifier	yes	Leave empty	String	80	Used to represent or link to feature level metadata.				See Element Sheet	See Element Sheet
sdsId	Globally Unique Identifier	yes	Leave empty	GUID	0	The unique identifier for all entities in the SDSFIE.				See Element Sheet	See Element Sheet
trafficCounterIdpk	Primary Key Identifier	yes	Post Process	String	40	Primary Key. A unique, user defined identifier for each record or instance of an entity.				See Element Sheet	See Element Sheet
recProjectSiteId	Project Site Identifier	no	Pre or Post Process	Double		Project Site ID
recProjectSiteAreaId	Project Site Area Identifier	no	Pre or Post Process	Double		Project Site Area ID
versAreaCode	VERS Area Identifier	no	Pre or Post Process if data is provided	Double		VERS Vehicle Access Compartment ID
modelNumber	Model Number	no	Collect or Post Process, verify with Project staff	String	50			verify VERS data visually and/or with project. VERS variable = meter model
installationDescription	Installation Description	no	Collect or Post Process, verify with Project staff	String(MAX)	0			verify VERS data visually and/or with project	InstallationDescription	belowGround, onGround, aboveGroundPost, aboveGroundContainer	Below Ground, On Ground, Above Ground-Post, Above Ground-Container
mountHeight	Mount Height	no	Collect or Post Process, verify with Project staff	Float				ONLY required to measure device height if the meter is one of the three infrared types. Use inches from surface of ground as unit of measurement. VERS variable = meter beam.

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. Updated Aug 5, 2022.