Amendment 0009 - 01 78 30.00 22 - GIS DATA DELIVERABLES.pdf

2ND RADIO BATTALION COMPLEX PHASE II 19P1458

MCB CAMP LEJEUNE, NC ePROJECTS W.O. NO.: 1397586

SECTION 01 78 30.00 22

GIS DATA DELIVERABLES

03/22

PART 1 GENERAL

1.1 OBJECTIVE

The primary objective of this section is to provide detailed specifications for collection and delivery of geospatial data commonly referred to as Geographic Information System (GIS) data. Additionally, this section provide s guidance to ensure that all GIS data delivered is compatible and will add value to the Marine Corps Base (MCB) Camp Lejeune Installation Geospatial Information and Services (IGI&S) GEOdatabase MCAS Cherry Point's Installation Geospatial Information and Services (IGI&S) GEOdatabase MCAS Beaufort Installation Geospatial Information and Services (IGI&S) GEOdatabase .

Failure to comply with the specifications outlined in this document will result in non-acceptance of data deliverables.

1.1.1 Point of Contact for MCB Camp Lejeune

The Points of Contact (POC) for assistance in preparation of GIS deliverables are as follows:

Resident Officer In Charge Of Construction Public Works Assigned Construction Manager (CM) GIS Data Manager 1005 Michael Drive 1005 Michael Road Camp Lejeune, NC 28547-2521 Camp Lejeune, NC 28547-2521

(910) 451-2581 (Main Number) (910) 000-0000 ext 0000 TBD Lejeune_PWD_GIS@usmc.mil

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 10.05 20

DESIGN SUBMITTAL PROCEDURES 01 33 00.05 20 CONSTRUCTION SUBMITTAL

PROCEDURES:

SD-11 Closeout Submittals

GIS Data Deliverables ; G

1.3 GOVERNMENT GEOSPATIAL DATA, SCHEMA, AND DOMAINS

Geo-spatial data is based on the Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) GEOFidelis Data Model. Because there are recurring business driven modifications and or adaptations within the SDSFIE schema, provide all spatial and non-spatial data in the most current version by the USMC utilized at the time of delivery.

1.3.1 Data Request Package Requirements

Request the existing GIS Data, Schema and Domain Properties by utilizing a

SECTION 01 78 30.00 22 Page 1

Data Request Package (DRP), which is supplied via the government sponsor.

a. The DRP must be submitted prior to the start of data collection efforts and again 4 weeks prior to data delivery to ensure that GIS data has been created and must be delivered utilizing the most up to date SDSFIE schema.

1.3.1.1 Instruction for submitting a Geospatial DRP to the CM or the Project Manager (PM)

a. Each CM or PM must provide DRP forms upon request from the contractor. Complete the request and include all information as instructed on the data request form.

b. Request only GIS data, schema and domains for feature classes that are relevant to the contract and within the boundary of project area and provide justifications as necessary.

c. Attach the Scope of Work, which is defined by this GIS DATA DELIVERABLES section for each DPR submittal.

d. Return the DRP to the CM or PM for sponsorship and submittal as instructed with required attachments and justifications for submittal.

e. Incomplete forms may delay receipt of the requested GIS data.

f. GIS data deliverables do not supplement or replace as-built drawings.

1.3.2 Data Collection and Utility Locates

a. Utilize the most up to date SDSFIE Schema when delivering GIS Data.

b. Prior to GPS efforts all underground utilities are to be located utilizing a utility locating service in order to obtain and verify accurate feature locations.

c. Actual conditions in the field always supersede drawings. Locate and field verify all features to ensure location is correctly recorded.

d. Data must be created to represent the real world, for example, water, sewer, and transportations systems must be connected. All segments must be created from source to sink in the direction of flow.

e. Research may be required to collect data. Verification of existing data which is located in the Technical Records in the Public Works Department at 1005 Michael Street, MCB Camp Lejeune. in the Public Works Department.

f. Infrastructure data, as identified in paragraph "ATTRIBUTE DATA COLLECTION AND GPS REQUIREMENTS FOR SPECIFIC FEATURES" may be collected utilizing Sub-Foot or better GPS data collection methods.

g. Utility data, as identified in paragraph "ATTRIBUTE DATA COLLECTION AND GPS REQUIREMENTS FOR SPECIFIC FEATURES" must be collected utilizing Survey Grade GPS data collection methods.

1.3.3 Attribute Data Requirements

a. All attributes must be populated in accordance with paragraph

SECTION 01 78 30.00 22 Page 2

ATTRIBUTE DATA COLLECTION AND GPS REQUIREMENTS FOR SPECIFIC FEATURES

and must be obtained via contract specifications, plans and record drawings.

b. Demolished / Removed Real Property data must be captured, attributed and delivered in the Disposal feature classes which include Disposal Facility Area, Disposal Facility Line and Disposal Facility Point.

c. Demolished / Removed UTILITY data must be captured, attributed and delivered by creating a new feature class which must consist of adding DEMO to the feature's naming convention for each feature, such as, but not limited to the following examples; DEMO.WastUtilNode_SPump (point), DEMO.Feat_SwRetentionBasinArea,(polygon), and DEMO.WastUtilSegment (polyline)

1. The Contractor is responsible for properly delivering demolished features with the current attributes associated with the feature and additionally updating the new contract number, date of demolishment, and optional status.

d. Spatial and non-spatial data may be copied from existing data, with the exception of specific attributes. Potable water wells are an exception to this rule and must remain in the feature class and attributed as Removed or AIP.

e. Abandoned In Place (AIP) utility lines must be located and updated in the current feature data set and be attributed as AIP as required.

1.3.4 GIS Topology Rules for Geospatial Data

All data must be created using GIS topology rules for polygons, points and lines, such as, but not limited to the following examples:

a. Utility and transportation systems must be created from source to sink.

b. All utilities must be drawn in the direction of flow with no breaks in polyline except for fittings, manholes and other features nodes within the feature Dataset.

c. All utility or infrastructure system data, which is, but is not limited to, transportation system and electrical, water, thermal distribution, and wastewater collection, etc., must be created using GIS spatial connectivity rules which specify that vertex, edge and endpoints be snapped to features within the system.

d. All polygons must be closed without slivers and be topologically correct.

e. All polylines must be topologically correct, and must be connected to avoid undershoots, overshoots and dangles and will cross only if they share a point in common, at least one of which is not an endpoint.

f. For all Polygons, Polylines and points rules; please reference illustrating topology rules in ArcGIS at www.esri.com .

1.3.5 Global Positioning System (GPS) Data Collection

Utilize field survey GPS data collected by means of non-recreational GPS equipment

SECTION 01 78 30.00 22 Page 3

a. Only bench marks included in the North Carolina South Carolina Georgia Geodetic Survey Base Station Network are to be used for GPS data collection.

b. Mission planning is essential. Utilize the best Position Dilution of Precision (PDOP) values for data accuracy.

c. Mission planning for GPS collection must be conducted when positional dilution of precision (PDOP) value is 4 or less.

d. Spatial accuracy requirements

1. Survey and Sub-Foot GPS grade data collection requirements are as follows:

i. Sub-Foot requirements:

1) All points must be within plus or minus 12 inches

2) 95 percent accuracy rate for all points.

ii. Survey Grade requirements:

1) All points must be within plus or minus 1 centimeter

2) 98 percent accuracy rate for all points

e. Make every effort to capture feature locations without using Offsets.

All Offsets must be noted in the Final Report for each feature.

Deliver report in PDF format.

1. Resubmittal of data is required if PDOP planning was not observed per this specification.

1.3.6 Formats and Version Guidelines

All data deliverables must be presented in the following formats and/or versions.

a. GIS data must be provided in an ArcGIS 10.8 or higher if a higher version is being used by the Government at the time of this project.

Verify the ArcGIS version, via the CM or PM at the commencement of this contract.

b. Microsoft Windows 10 operating system, unless otherwise approved by the Government.

c. All reports and maps must be delivered as a hard copy and in a searchable Adobe Portable Document Format (PDF).

1.3.7 GIS Deliverable Submittal Requirements

All GIS Submittals must be submitted to the CM or PM and then analyzed by Government GIS personnel prior to final approval. Failure to comply with the specifications outlined in this document will result in non-acceptance of GIS data deliverables.

a. Prior to any spatial and non-spatial development, provide the

SECTION 01 78 30.00 22 Page 4

Government with a technical approach document, in PDF format, for review and approval. The Technical Approach document must describe in detail the Contractor's technical approach for developing GIS data to include utility locating, collecting, and attributing all GIS data.

b. Provide a GIS deliverable at the end of each phase and at each Beneficial Occupancy Date (BOD) when contracted efforts, studies or construction are delivered in phases.

c. To ensure specifications compliance and quality a preliminary GIS deliverable must be provided for review when 25 percent of the data has been collected and updated according to this specification.

d. Deliver digital geographic maps, GPS collection files and related data. All working text and documents and personal geodatabase must be included for review in the draft and final delivery of data in PDF format .

e. Do not deliver blank unused schema or feature class data with no attributes. Deliver only data pertinent to the contract that adds value to the Geodatabase per this section.

f. Do not include existing data in the GIS deliverable.

g. Spatial and non-spatial GIS data must be provided in a format that does not require translation or pre/post processing.

h. It is the Contractor's responsibility to perform quality assurance for all data and related materials required in this section prior to submitting product to the Government .

i. The data must be analyzed for discrepancies in subject content, correct format in accordance with this statement of work, and compatibility with the existing SDSFIE Schema as well as all other specifications included in this section.

1.3.8 GIS Deliverable Package Requirements

All reports must be provided in pdf format. Each GIS deliverable must contain the following information and be in the most up to date SDSFIE format utilized by the USMC at the time of delivery.

a. Digital and Paper Maps.

1. All maps of GIS DATA DELIVERABLES must be ANSI C size.

2. Each map must include a project title, contract number, scale, legend, standard symbology, attributes, i.e., building numbers, road names, etc.

3. All utilities must be labeled with direction of flow and segment line size.

4. Provide paper copy and pdf copies of Maps for project.

5. Provide a copy of all red-line construction drawings in pdf format.

6. Communication data must be provided on a separate map.

SECTION 01 78 30.00 22 Page 5

b. Provide all spatial and non-spatial data for review and acceptance.

c. Provide a report of specific procedures, list GPS equipment, software and versions that were utilized for the GPS data collection and creation of geospatial data.

d. Submit all GPS data files collected in the field.

e. Provide details on any offsets to include justification as to why offsets were utilized and which features and or points offsets were used.

f. Provide the source that was utilized for required attributes, such as redlines drawings and or field notes.

g. Summit DD form 1354, Transfer and Acceptance of DOD Real Property.

h. Provide a coversheet that specifies the CM / PM, contract number, contract title, point of contract for GIS related questions.

i. All geospatial data, pdf reports, spreadsheet, database files, reports, and maps must be submitted on a Digital Versatile Disc (DVD) platform .

j. Failure to comply will result in non – compliance and rejection of data .

1.3.9 Ownership

All digital files, hardcopy products, GPS raw data, source data acquired for this project, and related materials, including that furnished by the Government, will become the property of the Government and must not be issued, posted, distributed, or published by the Contractor. All documentation must be delivered in the final delivery.

Note: No endorsement of software or hardware is implied.

1.4 ATTRIBUTE DATA COLLECTION AND GPS REQUIREMENTS FOR REAL PROPERTY AND

OTHER MISCELLANEOUS FEATURES THAT ARE NOT CONSIDERED A UTILITY

For Attributes and Data Collection of specific MCAS Cherry Point features please consult the Cherry Point IGI&S Manager, chpt.facssoomb@usmc.mil, for a checklist and copy of the most recent Data Dictionary.

For Attributes and Data Collection of specific MCAS Beaufort features please consult the Beaufort IGI&S Manager, Joe Pergande, joseph.pergande@usmc.mil, for a checklist and copy of the most recent Data Dictionary.

For Attributes and Data Collection of specific MCRD Parris Island features please consult the Parris Island GIS Specialist, Gary Mobbs, gary.mobbs@usmc.mil, for a checklist and copy of the most recent Data Dictionary.

For Attributes and Data Collection of specific MCLB Albany features please consult the Albany GIS Specialist, Damon Drake, damon.drake@usmc.mil, for a checklist and copy of the most recent Data Dictionary.

Locate, GPS and collect attribute data as specified for each feature listed with (GPS) accuracy as described in paragraph "Global Positioning

SECTION 01 78 30.00 22 Page 6

System (GPS) Data Collection". Attribute fields may be associated with Domains, which are utilized to constrain the values allowed in a particular field, attribute table or feature class. Domains must be utilized when populating the feature where required. Items in this section that require Survey Grade GPS are property identified in the feature class description.

1.4.1 Feature Dataset CLJN.CL.AccessControl

Locate, GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) Data Collection". Attribute fields may be associated with Domains, which are utilized to constrain the values allowed in a particular field, attribute table or feature class. Domains must be utilized when populating the feature where required.

CLJN.CL.AccessControlPoint (point) -The location of a feature, manned or unmanned, intended to selectively restrict entrance to or use of a place or other resource.

a) accessControlType - The type of access control. Domain values, i.e., gate, tireShedder, barricade, etc.

b) builtDate - The calendar date on which the original construction was completed for a facility.

c) contractNumber - The contract number associated with the feature.

d) facilityNumber - Asset number used for visual identification of the facility.

e) featureDescription - The narrative describing the feature.

(Review current data for description)

f) featureName - The common name of the feature. (Review current data for common name)

g) gatePurposeType - Purpose that the gate exists and functions under. Domain values i.e., decorative, insternalSecurity, perimaterSecurity, recreation, residential, safely, vehicleBarrier, other, etc.

h) gateTypeMaterial - The type of material of the gate. Domain values i.e., metal, steel, wood, wroughtiron, etc.

i) isBaseEntryPoint -The Yes / No indicator of whether or not the location is an entry point for the military installation.

j) isCheckpoint - Indicator if location is where officials check vehicle contents or personnel. Yes / No

k) mediald - gpsDataCollected

l) MetadataId - metaID000072

m) isManned - Yes / No

n) isRangeAccess - Yes / No

o) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.AccessControlLine (polyline) - The location of a feature, manned or unmanned, intended to selectively restrict entrance to or use of a place or other resource.

a) accessControlTypeThe type of access control. Domain AccessControlType

b) builtDate - The calendar date on which the original construction was completed for a facility.

SECTION 01 78 30.00 22 Page 7

c) contractNumber- The contract number associated with the feature.

d) facilityNumber - Asset number used for visual identification of the facility.

e) featureDescription - The narrative describing the feature.

(Review current data for description)

f) featureName - The common name of the feature. (Review current data for common name)

g) gatePurposeType- - Purpose that the gate exists and functions under. Domain values i.e., decorative, insternalSecurity, perimaterSecurity, recreation, residential, safely, vehicleBarrier, other, etc.

h) gateTypeMaterial - The type of material of the gate. Domain values i.e., metal, steel, wood, wroughtiron, etc.

i) gateUse - The type of a gate (or similar route barrier) based on its intended use.

j) mediald - gpsDataCollected

k) MetadataId - metaID000072

l) isBaseEntryPoint - Yes / No

m) isCheckpoint - Yes / No

n) isManned - Yes / No

o) isRangeAccess - Yes / No

p) operationalStatus- The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.BarricadePoint (point) - The coordinated series of obstacles designed or employed to channel, direct, restrict, delay, or stop the movement of personnel, equipment, or an opposing force and to impose additional losses in personnel, time, and equipment on the opposing force. Barricades can exist naturally, be man-made, or a combination of both.

a) accessControlType - The type of access control. Domain values, i.e., gate, tireShedder, barricade, etc.

b) builtDate - The calendar date on which the original construction was completed for a facility.

c) contractNumber - The contract number associated with the feature.

d) facilityNumber - Asset number used for visual identification of the facility.

e) featureDescription - The narrative describing the feature.

(Review current data for description)

f) featureName - The common name of the feature. (Review current data for common name)

g) barricadeType -The type of barricade. Domain values i.e., bollard, bollardPipe, pedestrianBarrier, other, etc.

h) barricadeUse - The intended use of the barricade Domain values i.e., pedestrianTraffic, security, vehicularTraffic, etc.

i) gatePurposeType - Purpose that the gate exists and functions under. Domain values i.e., internalSecurity, perimeterSecurity, recreation, residential, safety, vechicleBarrier, etc.

j) gateTypeMaterial - The type of material of the gate. Domain values i.e., metal, steel, wood, wroughtiron, etc.

k) gateUse - The type of a gate (or similar route barrier) based on its intended use.

l) operationalStatus - The state of usability of the feature

SECTION 01 78 30.00 22 Page 8 i.e., inService, notInService, abandoned, etc .

CLJN.CL.BarricadeLine (polyline) - The coordinated series of obstacles designed or employed to channel, direct, restrict, delay, or stop the movement of personnel, equipment, or an opposing force and to impose additional losses in personnel, time, and equipment on the opposing force. Barricades can exist naturally, be man-made, or a combination of both.

a) accessControlType - The type of access control. Domain values, i.e., gate, tireShedder, barricade, etc.

b) barricadeUse - The intended use of the barricade Domain values i.e., pedestrianTraffic, security, vehicularTraffic, etc.

c) builtDate - The calendar date on which the original construction was completed for a facility.

d) contractNumber - The contract number associated with the feature.

e) facilityNumber - Asset number used for visual identification of the facility.

f) featureDescription - The narrative describing the feature.

(Review current data for description)

g) featureName - The common name of the feature. (Review current data for common name)

h) gatePurposeType - Purpose that the gate exists and functions under. Domain values i.e., internalSecurity,

i) perimeterSecurity, recreation, residential, safety, vechicleBarrier, etc.

j) mediald - gpsDataCollected

k) l) MetadataId - metaID000072

l) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

m) gateTypeMaterial - The type of material of the gate. Domain values i.e., metal, steel, wood, wroughtiron, etc.

1.4.2 Feature Dataset CLJN.CL.CivilWorks

Locate, GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) Data Collection". Attribute fields may be associated with Domains, which are utilized to constrain the values allowed in a particular field, attribute table or feature class. Domains must be utilized when populating the feature where required.

CLJN.CL.PitOrQuarry (Polygon) - The location where material has been or is being excavated or extracted for use at another location.

a) featureDescription - The narrative describing the feature.

(Review current data for description)

b) featureName - The common name of the feature. (Review current data for common name)

c) contractNumber - The contract number associated with the feature.

d) mediald - gpsDataCollected

e) MetadataId -metaID000072

f) isWaterFilled - Yes / No

g) operationalStatus - The state of usability of the feature

SECTION 01 78 30.00 22 Page 9 i.e., inService, notInService, abandoned, etc.

1.4.3 Feature Dataset CLJN.CL.HarbourArea

Locate, GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) Data Collection". Attribute fields may be associated with Domains, which are utilized to constrain the values allowed in a particular field, attribute table or feature class. Domains must be utilized when populating the feature where required.

CLJN.CL.BoatRampPoint - (Point) - The partially submerged hard surfaced or non-hardsurface structure on a shoreline for launching or retrieving vessels or vehicles.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - The common name of the feature. (Review current data for common name)

f) isLighted - Yes / No

g) mediald - gpsDataCollected

h) MetadataId - metaID000072

i) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.DockOrWharf (Polygon) - The location of a manmade water-land interface structure often used for access to boats, ships, or barges.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) dockType - The kind or type of the dock. Domain values i.e., access ramp, pier, slipway, general, etc.

d) dockUseType - The predominant use. Domain values i.e., fishing, fueling, loading, staging, etc.

e) facilityNumber - Asset number used for visual identification of the facility.

f) featureDescription - The narrative describing the feature.

(Review current data for description)

g) featureName - The common name of the feature. (Review current data for common name)

h) materialType - The material composition of the feature.

Domain values i.e., concrete, steel, wood, etc.

i) mediald - gpsDataCollected

j) MetadataId - metaID000072

k) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

l) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

SECTION 01 78 30.00 22 Page 10

CLJN.CL.MarineNavigationAid (Point) - The physical object that serves as an aid to navigation. *Requires Survey Grade GPS.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - The common name of the feature. (Review current data for common name)

f) heightAboveSurfaceLevel - The vertical distance measured from the lowest point of the base of the feature at ground or water level to the tallest point of the feature.

g) heightAboveSurfaceLevelUom - The unit of measure Domain values i.e. 0.3048 metres, feet, etc.

h) isLighted - Yes / No

i) mediald - gpsDataCollected

j) MetadataId - metaID000072

k) navaidType - Type of the navaid. Domain value i.e., buoyMarkerDangerPoint, buoyMarkerDangerPoint etc.

l) operationalStatus - The state of usability of the feature i.e., inService, notInService, closed, abandoned, etc.

1.4.4 Feature Dataset CLJN.CL.RealProperty

Locate, GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) Data Collection". Attribute fields may be associated with Domains, which are utilized to constrain the values allowed in a particular field, attribute table or feature class. Domains must be utilized when populating the feature where required.

Specific instruction for all Disposal polygons, polylines and points. All demolished or removed property must be accounted for in the following 3 disposal features. A simple copy and paste with the following exceptions as explains in the disposal area, polyline and point may be permitted with the exception of the directions for attribution for each feature as noted. However, under no circumstance should potable water wells be removed from their original feature class. Potable wells are never deleted from their main feature, all that is required is the water wells are attributed in such a way that indicated if they are abandoned in Place (AIP) or Removed.

CLJN.CL.Disposal_FacilityArea (polygon)- The location of a facility asset in the DoD real property inventory for which a disposal action is being or has been taken to physically demolish, remove, or release the DoD of accountability for and control of the asset.

a) abandonedDate - The date the feature was abandoned. Leave blank if removed.

b) builtDate - The calendar date on which the original construction was completed for a facility.

c) contractNumber - The contract number associated with the feature demolishment or abandonment.

SECTION 01 78 30.00 22 Page 11

d) ClassType - Population is contingent only if data is currently available for feature.

e) disposalCompletionDate - The actual calendar date of the disposal or abandonment of the asset.

f) facilityNumber - Asset Identification such as building or structure number.

g) featureDescription -Population is contingent only if data is currently available for feature.

h) featureName (Mandatory) - Feature Name and subtype

i) facilityIdfk - Population is contingent only if data is currently available for feature.

j) operationalStatus - The state of usability of the feature.

Domain values i.e., removed, abandoned, etc.

k) owner - Population is contingent only if data is currently available for feature.

l) removedDate - The date the feature was removed. Leave blank if abandoned.

m) realPropertyJurisdictionType - Population is contingent only if data is currently available for feature.

n) registryIdentifier - Population is contingent only if data is currently available for feature.

o) sourceFeatureClass (Mandatory) - The feature class containing the polygon feature.

CLJN.CL.Disposal_FacilityLine (polyline) - The location of a personal property asset in the DoD real property inventory for which a disposal action is being or has been taken to physically demolish, remove, or release the DoD of accountability for and control of the asset.

a) abandonedDate - The date the feature was abandoned. Leave blank if removed.

b) builtDate - The calendar date on which the original construction was completed for a facility.

c) contractNumber - The contract number associated with the feature demolishment or abandoned.

d) classType - Population is contingent only if data is currently available for feature.

e) disposalCompletionDate - The actual calendar date of the disposal or abandonment of the asset.

f) facilityNumber - Asset Identification RoadName, fence, utility line, fence gate information, etc.

g) featureDescription - Population is contingent only if data is currently available for feature.

h) featureName (Mandatory) - Feature Name and subtype

i) operationalStatus - The state of usability of the feature.

Domain values i.e., removed, abandoned, etc.

j) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

k) removedDate - The date the feature was removed. Leave blank if abandoned.

l) realPropertyJurisdictionType - The type of real property jurisdiction. Domain values i.e., tbd, etc.

m) registryIdentifier - Population is contingent only if data is currently available for feature.

n) sdsId - Population is contingent only if data is currently available for feature.

o) sourceFeatureClass (Mandatory) - The feature class containing the line feature.

SECTION 01 78 30.00 22 Page 12

CLJN.CL.Disposal_FacilityPoint (point) - The location of a personal property asset in the DoD real property inventory for which a disposal action is being or has been taken to physically demolish, remove, or release the DoD of accountability for and control of the asset.

a) abandonedDate - The date the feature was abandoned. Leave blank if removed.

b) builtDate - The calendar date on which the original construction was completed for a facility.

c) contractNumber - The contract number associated with the feature demolishment or abandoned.

d) ClassType - Population is contingent only if data is currently available for feature.

e) disposalCompletionDate - The actual calendar date of the disposal or abandonment of the asset.

f) facilityNumber - Asset Identification such as generator, ows, towers, etc.

g) featureDescription - Population is contingent only if data is currently available for feature.

h) featureName (Mandatory) - Feature Name and subtype

i) facilityIdfk - Population is contingent only if data is currently available for feature.

j) operationalStatus - The state of usability of the feature.

Domain values i.e., removed, abandoned, etc.

k) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

l) removedDate - The date the feature was removed. Leave blank if abandoned.

m) realPropertyJurisdictionType - The type of real property jurisdiction. Domain values i.e., tbd, etc.

n) registryIdentifier - Population is contingent only if data is currently available for feature.

o) sdsId - Population is contingent only if data is currently available for feature.

p) sourceFeatureClass (Mandatory) - The feature class containing the point feature.

CLJN.CL.Bridge - Bridge (polygon) - The structure erected over a depression or an obstacle such as a body of water, railroad, etc., to provide a pathway for vehicles, rail services, pedestrians or to carry utility services.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the

c) facilityNumber - Asset number used for visual identification of the facility.

d) contractNumber - The contract number associated with the feature.

e) featureDescription - The narrative describing the feature.

Value Base Area or Road Name Crossing

f) featureName - The common name of the feature. Pedestrian, Railroad, Road, other, etc.

g) heightAboveSurfaceLevel - The vertical distance measured from the lowest point of the base of the feature at ground or water level to the tallest point of the feature.

SECTION 01 78 30.00 22 Page 13

h) heightUom - The unit of measure Domain values i.e. 0.3048 metres, feet, etc.

i) mediald - gpsDataCollected

j) MetadataId - metaID000072

k) isFixed - Indicator of whether the bridge cannot be opened for navigation or other purposes. Yes / No

l) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.Building - Building (polygon) - The roofed and floored facility enclosed by exterior walls and consisting of one or more levels.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature if feature function does not accuracy address the description of building.

e) featureName - The common name of the feature. (Review current data for common name)

f) featureFunction - The purpose(s) of, or intended role(s) served by, the feature. Domain values i.e., Fishing (3), Aircraft Repair (341), Motor Vehicle Repair (343), Utilities (350), Water Treatment (362), Water Distribution (363), Residence (563), Guard (781), Government (811), Recreation

(921) etc.

g) floorCount - The number of floors

h) mediald - gpsDataCollected

i) MetadataId - metaID000072

j) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.Fence (polyline) - The freestanding structure designed to restrict or prevent movement across a boundary.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - FENCE or GATE.

f) FenceDesignType - The configuration of fabricated fence materials in a particular manner to build a fence. This may or may not include specifications of the post type(s).

Domain values i.e., cross, postAndFrame, metalRail, postAndFrame, etc.

g) fenceFabricatedMaterialType - The fabricated material of the fence. Domain values i.e., barbedWire, chainLink, wroughtIron, metalOther, steel, wood, etc.

h) fencePrimaryMaterialType - The fundamental or raw substance

SECTION 01 78 30.00 22 Page 14 of the fence. Domain values i.e., jute, metalOther, steel, wood, wroughtIron, etc.

i) fenceTopType - The fabricated material used as an upper barrier on the fence. Domain values i.e., spiked, electricfiedWire, etc.

j) fenceUseType - The purpose that the fence serves. Domain values, i.e., internalSecurity, perimeterSecurity, recreation, residential, safety, vechicleBarrier, etc.

k) heightAboveSurfaceLevel - The vertical distance measurement in feet.

l) heightUom - The unit of measure for the height measurement.

Domain values 0.3048 metres or feet, etc.

m) mediald - gpsDataCollected

n) MetadataId - metaID000072

o) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.Gate (polyline) - A movable barrier that closes an opening in a fence, wall, or other enclosure or enclosure.

a) accessControlType - The type of access control. Domain values, i.e., gate etc.

b) builtDate - The calendar date on which the original construction was completed for a facility.

c) contractNumber - The contract number associated with the feature.

d) facilityNumber - Asset number used for visual identification of the facility.

e) featureDescription - The narrative describing the feature.

(Review current data for description)

f) featureName - The common name of the feature. (Review current data for common name)

g) gateTypeMaterial - The type of material of the gate. Domain values i.e., metal, steel, wood, wroughtiron, etc.

h) gatePurposeType - Purpose that the gate exists and functions under. Domain values i.e., decorative, insternalSecurity, perimaterSecurity, recreation, residential, safely, vehicleBarrier, other, etc.

i) gateTopType - The fabricated material used as an upper barrier on the fence. Domain values i.e., spiked,

j) isBaseEntryPoint - Yes or No

k) isCheckpoint - Yes or No

l) isManned - Yes or No

m) isPortable - Yes or No

n) isRangeAccess - Yes or No

o) mediald - gpsDataCollected

p) metadataId - metaID000072

q) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.RecreationBoundary (polygon) - The area designated for recreational purposes.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

SECTION 01 78 30.00 22 Page 15

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - The common name of the feature. (Review current data for common name)

f) isFormallyDelineated Yes / No

g) isHandicappedAccessible Yes / No

h) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.OpenStorage - Open Storage (polygon) - The non-covered and/or covered storage areas, paved or otherwise established, for the storage of general supply materials or the receipt, processing, staging and issue of materials.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - The common name of the feature. (Review current data for common name)

f) mediald - gpsDataCollected

g) MetadataId - metaID000072

h) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.PavementSectionAirfieldArea - Pavement Section Airfield (polygon) - The location of a surface feature that comprises a section of a military airfield area. *Requires Survey Grade GPS.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) airfieldPavementUse - The use of the airfield. Domain values i.e., apron, fueling area, helipad, runway, taxiway, etc.

e) featureDescription - The narrative describing the feature.

Values must include Area i.e., MCAS NEW RIVER, HADNOT POINT, RIFLE RANGE, MCOLF CAMP DAVIS, GSRA, HOSPITAL, etc.

f) featureName - The common name of the feature. (Review current data for common name)

g) highestElevation - The elevation from a specified vertical datum to the highest point on a feature.

h) highestElevationUom - The unit of measure Domain values i.e.

0.3048 metres, feet, etc.

i) isLighted - Yes / No

j) isPaved - Yes / No

k) mediald - gpsDataCollected

l) MetadataId - metaID000072

m) operationalStatus - The state of usability of the feature

SECTION 01 78 30.00 22 Page 16 i.e., inService, notInService, abandoned, etc.

n) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

o) runwayClassification - Classification of the runway. Domain values i.e., classA, classB, rotary, olf, etc.

CLJN.CL.PavementSectionParkingArea (polygon) - The area used for parking vehicles not including residential streets and driveways.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - The common name of the feature. (Review current data for common name)

f) isLighted - Yes / No

g) mediald - gpsDataCollected

h) MetadataId - metaID000072

i) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

j) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

k) pavementSurfaceType - The type of material used to construct the surface of the pavement feature. Domain values i.e., asphalt, gravel, asphaltOverAsphaltConcrete, portlandCementConcrete, etc.

l) vehicleType - The type of vehicle permitted on the pavement section. Domain value i.e., all, gov, mil, pov, etc.

CLJN.CL.PavementSectionRoadway (polygon) - The surface area that comprise a road area, upon which vehicles drive and park.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - FULL Road Name All Capital Letters, i.e., D

STREET, SIXTH STREET, FOSTER BOULEVARD, PORTLAND COURT

f) isPaved - Yes / No

g) mediald - gpsDataCollected

h) MetadataId - metaID000072

i) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

j) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

k) pavementSurfaceType - The type of material used to construct the surface of the pavement feature. Domain values i.e., gravel, asphalt, asphaltOverAsphaltConcrete, portlandCementConcrete, etc.

SECTION 01 78 30.00 22 Page 17

l) roadSectionType - The type of road asset represented by this section. Domain values i.e., roadway, stagingArea, etc.

m) vehicleType - The type of vehicle permitted on the pavement section. Domain value i.e., all, gov, mil, pov, etc .

CLJN.CL.PavementSection - Pavement Section (polygon) - The portion of a pavement branch that differs in some aspect from other sections such that further segmentation is required to uniquely identify that section.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

Value i.e., GENERATOR PAD, TRANSFORER PAD, DUMPSTER PAD, BLEACHER PAD, UTILITY PANEL PAD, etc.

e) FeatureName - Slab.

f) featureName - The common name of the feature. (Review current data for common name)

g) mediald - gpsDataCollected

h) MetadataId - metaID000072

i) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

j) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

CLJN.CL.PavementSectionSidewalk (polygon) - The paved pedestrian walkway prepared to facilitate travel on foot. It may or may not be adjacent to a street/road.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - The common name of the feature. (Review current data for common name)

f) isLighted - Yes / No

g) isPaved - Yes / No

h) materialType - The material composition of the feature.

Domain values i.e., asphalt, concrete, etc.

i) mediald - gpsDataCollected

j) MetadataId - metaID000072

k) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

l) owner - The entity that owns the feature. Domain values, i.e., ppv, usmc, usn, leased, federalOther, etc.

CLJN.CL.StructureArea - Structure (polygon) - The facility, other than a building or linear structure, which is constructed on or in the land.

SECTION 01 78 30.00 22 Page 18

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

Values i.e., Picnic Pavilion, Gazebo, Postal Shelter, Buss Stop, Golf Shelter, Vehicle Wash Platform, Outdoor Classroom,

e) featureName - The common name of the feature. Values i.e., CANOPY, PLATFORM, PAVILLION, RAMP, WEIGH STATION, etc.

f) mediald - gpsDataCollected

g) MetadataId - metaID000072

h) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.TowerPoint (point) - The vertical projection, higher than its diameter, generally used for observation, etc.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

I.e., Range, Observation, Cell, etc.

e) featureName - Common name utilized for Range Area name.

f) heightMax - Maximum height of structure in feet.

g) heightUom - The unit of measure for the height measurement.

Domain values .3048 metres or feet, etc.

h) mediald - gpsDataCollected

i) MetadataId - metaID000072

j) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

k) towerUseType - The primary operational use of the tower.

Domain values, i.e., fire, observation, communication, training, etc.

CLJN.CL.TrafficControlLight (point) - A feature used to represent traffic lights.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

(Review current data for description)

e) featureName - The common name of the feature. (Review current data for common name)

f) heightAboveSurfaceLevel - Maximum height of structure in feet.

g) heightAboveSurfaceLevelUom - The unit of measure for the height measurement. Domain values .3048 metres or feet, etc.

h) mediald - gpsDataCollected

SECTION 01 78 30.00 22 Page 19

i) MetadataId - metaID000072

j) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.WallLine - Wall - The linear feature used for separation of facilities, ornamental decoration, or structural reinforcement.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature.

Values i.e., BENCH, DUMSPTER ENCLOSURE, UTILITY ENCLOSURE, RETAINING WALL, BLAST PROTECTION, BAFFLE WALL, MECHANICAL

YARD, etc.

e) featureName - The common name of the feature. (Review current data for common name)

f) height - The height of the feature in feet.

g) heightUom - The unit of measure for the height measurement.

Domain values .3048 metres or feet, etc.

h) mediald - gpsDataCollected

i) MetadataId - metaID000072

j) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

k) wallMaterialType - The material from which the majority of the wall is constructed. Domain values i.e., brick, cinderblock, grass, glassBlock, masonry, wood, etc.

1.4.5 Feature Dataset CLJN.CL.Recreation

Locate, GPS and collect attribute data as specified for each feature listed with (GPS) accuracy as described in paragraph "Global Positioning System (GPS) Data Collection". Attribute fields may be associated with Domains, which are utilized to constrain the values allowed in a particular field, attribute table or feature class. Domains must be utilized when populating the feature where required.

CLJN.CL.RecreationTrail - Recreation Trail (Polyline) - The path or walkway providing opportunity for physical activities.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) facilityNumber - Asset number used for visual identification of the facility.

d) featureDescription - The narrative describing the feature area. Values i.e., HADNOT POINT, FRECH CREEK, WALLAS CREEK, MCAS, etc.

e) featureName - The common name of the feature such as common trail name. Values, i.e., GREENWAY, MCAS, KNOX, etc.

f) Mediald - gpsDataCollected

g) MetadataId - metaID000072

h) meterialType - The material composition of the feature.

Domain values i.e., asphalt, concrete, etc.

SECTION 01 78 30.00 22 Page 20

i) officialLength - The officially reported length of the feature in feet.

j) officialLengthUom - The official length. Domain values i.e.

0.3048 metres, feet, etc.

k) operationalStatus - The state of usability of the feature i.e., inService, notInService, abandoned, etc.

CLJN.CL.Playground - Playground (Polygon) The area designed for children to play outdoors.

a) builtDate - The calendar date on which the original construction was completed for a facility.

b) contractNumber - The contract number associated with the feature.

c) featureDescription - The narrative describing the…