01 78 30.00 22 _ July2020 Amend3 Attach 1.pdf

SPECDEV

SECTION 01 78 30.00 22

GIS DATA DELIVERABLES

07/20

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 shall provide 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.

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:

Resident Officer In Charge Of Construction Public Works Division 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 (910) 451-5507 ext 3264

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 00

SUBMITTAL PROCEDURES 01 33 00.05 20 CONSTRUCTION SUBMITTAL PROCEDURES:

SD-11 Closeout Submittals

GIS Data Deliverables; G

1.3 GOVERNMENT GEOSPATIAL DATA AND SCHEMA

1. The IGI&S repository model schema is based on the Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) GEOFidelis Data Model with recurring business driven modifications and or adaptations.

a. Data will be created and delivered by developing an ARCGIS Personal GEODatabase using ArcGIS 10.1 or higher if a higher version is being utilized by the Government at the time the deliverable is being developed.

b. Request the existing GIS Data, Schema and Domain Properties by means of a Data Request Package (DRP). Receipt of request will include Geospatial Database table structure, schema, Domain configuration, Attribute text format, i.e., case size as well as

SECTION 01 78 30.00 22 Page 1

Meta Data information.

c. The DRP should be submitted prior to the start of data collection efforts and again every 6 months for the duration of the contract.

Ensure that all GIS data has been created and delivered utilizing the most up to date IGI&S GEODatabase schema at the time of delivery. Please be on notice that the schema for the GIS deliverable may change prior to delivery.

d. In order to to comply with the above section, it is necessary to verify the schema, via the CM and the PWD GIS Office. All GIS DATA DELIVERABLES will be created in accordance with the current schema at the time of deliverable. Contractor redline drawings must be submitted in PDF format with the GIS Deliverable package.

2. Submit a request for a Geospatial DRP to the CM or the Project Manager.

a. Request to be completely filled out and include all the information as instructed on the data request form.

b. Request only GIS data and or schema for feature classes that are relevant to the contract and within the boundary of project area.

c. Attach Scope of Work, which is defined by this GIS DATA DELIVERABLES section for each project request.

d. Return the DRP to the CM or Project Manager for sponsorship and submittal to the Installation Geospatial Information & Services (IGI&S) Office.

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

1.3.1 Global Positioning System (GPS) and Spatial Reference Properties

GPS data shall be completed in accordance with the GPS Data Collection and Documentation Standards, Version 4 (or higher version if available at the time of this project) as prepared by Geographic Information Coordinating Council (GICC) Statewide Mapping Advisory Committee (SMAC) and adopted by the North Carolina Geographic Information Coordinating Council.

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

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

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

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

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

a. Spatial accuracy requirements for Survey and Sub-Foot grade data collection are as follows:

SECTION 01 78 30.00 22 Page 2

i. Sub-Foot requirements:

1) All points shall be within + 12 inches

2) 95 percent accuracy rate for all points.

ii. Survey Grade requirements:

1) All points shall be within + 1 centimeter

2) 98 percent accuracy rate for all points

6. Make every effort to capture feature locations without using offsets.

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

7. Excessive offsets included in the Final Data, which will be referenced in the Final Report, will be reviewed for quality control.

a. Resubmittal of data will be required if PDOP planning was not observed per this specification.

The following GEODatabase Coordinate Systems and Spatial Reference Properties should be utilized for Camp Lejeune:

1. Transverse Mercator (UTM) Zone 18N

a. GRS 1980 spheroid

b. North American Datum 1983 (NAD83) horizontal datum

c. North American Vertical Datum 1988 (NAVD88) vertical datum.

2. Domain precision of 1000 which will result in a database accuracy of 1/1000 m

1.3.2 Demolished and Abandoned in Place (AIP) Features

Reference all Demolished and or AIP features in the data delivered. Should the current feature data class attributes and or domains not reference AIP or demolished features, the Contractor will be responsible for appropriately delivering these features by creating an associated "Demolished" or AIP feature class for all point and polyline data, i.e., CLJN.CL.WastewaterUtilitySegment and CLJN.CL.WateUtilNode_wHydrant, etc.

1. Utilize a blank schema for the associated feature class.

2. Rename associated feature class and add DEMO or AIP as a prefix, i.e., DEMO.CLJN.CL.WastewaterUtilitySegment, AIP.CLJN.CL.WastewaterUtilitySegment.

3. All demolished and or AIP features should provide existing spatial and non-spatial data which may be copied from existing data.

4. Update attributes appropriately to include the following:

a. Contract Number.

b. Drawing Number.

SECTION 01 78 30.00 22 Page 3

c. isDemolished.

d. dateDemolished or dateAIP.

e. Status.

1.3.3 Creating a New Feature Class

Should a new feature class be required that is not readily available in the current GIS schema provided by the Government. Contact the CM or Project Manager for guidence and schema format.

1.3.4 GIS Topology Rules

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

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

2. Polygons must not have slivers.

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

4. Features will be snapped to the appropriate item.

5. Data will be created to represent the real world, for example, water, sewer, and transportations systems, etc. will be drawn and or created in the direction of flow.

6. Utility and transportation systems will be created from source to sink, etc.

7. Abandoned In Place (AIP) utility lines will be located and updated in the current feature data set and identified as AIP in the attribute tableor provide in a feature data set as specified in paragraph "Demolished and Abandoned in Place (AIP) Features" with CM approval.

1.3.5 Creation of Geographic Data Documentation (METADATA)

For each digital file delivered containing geographic information, provide documentation consistent with the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM).

Metadata generation tools included in the ArcGIS suite of software (or equivalent technology) will be used in the production of the required metadata in XML format. Regardless of the tools used for metadata creation, must ensure that the metadata is delivered in XML format and can be easily imported into the IGI&S GEODatabase.

(NOTE: The metadata should be formatted from the Government perspective, not the Contractor project perspective. Therefore such items as Point of Contact (POC) should be the POC currently associated with the data and NOT the Contractor's Project Manager. Use language and format consistent with existing metadata.)

SECTION 01 78 30.00 22 Page 4

1.3.6 GIS Submittals Guidelines

All GIS Submittals will 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 data deliverables.

1. Prior to any database development, provide the Government with a technical approach document, in PDF format, for review and approval.

The Technical Approach document will describe in detail the Contractor's technical approach to designing and developing the database.

2. All attributes will be populated in accordance with the "ATTRIBUTE DATA COLLECTION AND GPS REQUIREMENTS FOR SPECIFIC FEATURES" and will be obtained via contract specifications, plans and record drawings.

3. Reasearch may be required to be conducted to collect data and make copies of reports and studies as necessary to verify existing and/or record drawing data. Record drawing data and closed contracts can be located in the Technical Records Section in the Public Works Department which is located at 1005 Michael Street, MCB Camp Lejeune.

4. Raw GPS data and collection data files will be included with every phase of delivery.

5. Actual spatial and non-spatial conditions in the field always supersede drawings. Locate and field verify all features to ensure attribute data and location is correctly recorded.

6. Submit a preliminary review of data at 25 percent contract completion to ensure specifications compliance.

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

a. All maps of GIS DATA DELIVERABLES will be ANSI C size and include a project title, contract number, scale, legend, standard symbology, attributes, i.e., building numbers, road names, segment diameters, etc. Also provide a PDF copy of all maps.

8. When required, provide a technical consultant to meet on site.

9. 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.

10. When projects are constructed in phases, deliver GIS Data at the end of each phase for all Phased Projects and Construction projects.

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

12. The data will be analyzed for discrepancies in subject content, correct format in accordance with this statement of work, and compatibility with the existing GIS system as well as all other specifications in

SECTION 01 78 30.00 22 Page 5 this section.

1.3.7 Formats, Versions and Guidelines

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

1. GIS data will be provided in an ArcGIS 10.1 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.

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

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

4. All text, spreadsheet, database files, reports, and maps will be delivered on Digital Versatile Disc read - only memory (DVD-ROM).

5. Verify required version(s) of software and schema, via the CM or PM.

6. Map submittals will accompany each geospatial deliverable.

a. Include ANSI C map for each project/area.

b. Data should be labeled and attributed per specification.

c. All maps should include the date, a legend, scale, contract title, and number.

d. Each map should be exported on a .pdf and delivered electronically with the project.

1.3.8 Final Report Requirements with additional Guidelines

Follow the following:

1. Specific procedures and list of equipment, software and versions that were utilized for the GPS data collection and creation of geospatial data.

2. Submit all GPS data files.

3. Provide the date(s) the IGI&S schema and geospatial data was received.

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

5. Describe all modifications to the geodatabase to include the name of all new features classes, i.e., new, demolished or AIP.

6. Provide the source that was utilized for required attributes.

a. Include an ANSI C size copy of all design drawings that were referenced in the attribute data. This information should be included in all phases of delivery to include draft and final reviews.

SECTION 01 78 30.00 22 Page 6

b. Provide the overall utility site plan drawing(s)with each submittal.

c. Provide a seperate map for communication which includes infrastructure in PDF format.

7. Specify Deliverable "Draft #" or "Final Submittal" when data is submitted to the CM or PM for review.

8. Provide the name and contact information for the GIS Technical Point of Contact who can answer questions regarding the data deliverable.

9. GIS DATA DELIVERABLES must be provided in a format that does not require translation or pre/post processing prior to being loaded into the IGI&S GEODatabase.

10. Provide any miscellaneous information that is deemed significant.

11. Provide the current version of the GIS DATA DELIVERABLES specification utilized for this contract submittal.

1.3.9 Ownership

All digital files, final 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 will not be issued, posted, distributed, or published by the Contractor. All documentation will be delivered in the final delivery.

Note: No endorsement of software or hardware is implied.

1.4 ATTRIBUTE DATA COLLECTION AND GPS REQUIREMENTS FOR SPECIFIC FEATURES

GPS and collect attribute data as specified for each feature listed with (GPS) accuracy as described in paragraph "Global Positioning System (GPS) and Spatial Reference Properties". 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.

1.4.1 CLJN.CL.Common

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.Sign A structure that conveys directional, warning, or other information.

a) numberOfSigns

b) assemblyOffset

c) SignText

d) SignType - Directional, Standard Identifier, Safety Warnings, SECTION 01 78 30.00 22 Page 7

Regulatory, etc.

e) SymbolCode - Utilize manual for Uniform Traffic Control Devices Code as issued by the Federal Highway Administration

f) GisFeatureCollectionMethod - Survey Grade GPS, Digitized, etc.

g) Contract Number

h) SdsFeatureDescription

i) signAssemblyType - Pedestal Pole, Wood 4x4, etc.

1.4.2 CLJN.CL.EMERGENCY_SERVICES

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) and Spatial Reference Properties". 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.RoadCenterline The center of the road area

a) roadClass - Major Roads/Local Roads/etc.

b) trackOrLaneCount

c) speedLimit

d) isPaved - YES / NO

e) oneWayDirection

f) fullStreetName

g) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

h) contractNumber

i) isTankTrail - YES / NO

j) contractNumber

k) isLighted - Yes / No

l) routeMinTravelledWayWidth

m) routeMinTravelledWayWidthUOM

n) routeTotalUsableWidth

o) routeTotalUsableWidthUOM

p) supportedByBridgeSpan - Yes / No

1.4.3 CLJN.CL.REAL.PROPERTY

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.AccessControl A structure manned or unmanned intended to control access to an area

a) controlType - gate, barricade, tire shedder, etc.

b) contractNumber

c) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

d) isRangeAccess - YES / NO

e) gateType -

f) Facility Number

SECTION 01 78 30.00 22 Page 8

g) sdsFeatureDescription - Location

CLJN.CL.AlternativeEnergyPoint Locations used for the production of alternative energy sources, such as wind turbines, photovoltaic, etc.

a) alternativeEnergyType - Photovoltaic, Natural Gas, etc.

b) contractNumber

c) designDrawingNumber

d) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

e) isPortable - YES / NO

f) wattage

g) operationalStatus - inservice, abandoned, etc.

h) panelType

i) sdsFeatureName

j) sdsFeatureDescription

k) wattage - Total per unit

l) hasInverter - YES / NO

m) isPartOfElectricalNetwork - YES / NO

n) photovoltaicPanelInstallation

CLJN.CL.AlternativeEnergyArea Locations used for the production of alternative energy sources

a) operationalStatus - inservice, abandoned, etc.

b) isPortable - YES / NO

c) panelType

d) wattage - total for area

e) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

f) contractNumber

g) sdsFeatureName - Facility Number

h) hasInverter - YES / NO

i) isPartOfElectricalNetwork - YES / NO

CLJN.CL.BoatRamp A partially submerged hard surfaced structure on a shoreline for launching or retrieving vessels or vehicles

a) boatRampIDPK - Facility Number

b) dateConstructed

c) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

d) contractNumber

e) sdsFeatureName

f) sdsFeatureDescription - Location

g) numberofLaunchLanes

CLJN.CL.Bridge A structure used by vehicles that allows passage over or under an obstacle such as a river, chasm, mountain, road or railroad

a) isFixed - YES / NO

b) TransportationSysetemType - Pedestrian, Road, Railway, etc.

c) FacilityNumber

d) verticalConstructionMaterial - Brick, Concrete, etc.

e) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

SECTION 01 78 30.00 22 Page 9

f) contractNumber

g) sdsFeatureDescription - Road Name if applicable

h) OperationalStatus - closed, operational, etc.

CLJN.CL.Building A roofed, floored and walled structure that is completely enclosed

a) facilityNumber

b) builtDate

a) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

c) contractNumber

d) sdsFeatureDescription - General Description of Building's Purpose

e) floorCount

f) material - Exterior material such as Brick, Concrete, etc.

g) operationalStatus - inService, abandoned, etc.

CLJN.CL.BuildingFloorPlan A linear representation of floor plans for buildings, provided in one feature per floor

a) buildingFloorLevel

b) buildingIDFK - Structure Number

c) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

d) contractNumber

e) sdsFeatureDescription Renovation Date

CLJN.CL.Disposal_RealProperty Real property demolished structures

a) sdsFeatureDescription

b) sdsFeatureName

c) facilityNumber

d) contractNumber

e) disposalDate

CLJN.CL.DocksAndWharfs A manmade water-land interface structure often for access to boats or ships

a) PurposeType - Fishing, Mooring, etc.

b) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

c) contractNumber

d) Facility Number - Structure Number

e) sdsFeatureDescription - Pier, boat ramp, dock, etc.

f) natureOfConstruction - concrete, earthen, steel

CLJN.CL.Fence A freestanding structure designed to restrict or prevent movement across a boundary

a) facilityIDFK - Structure Number

b) fenceType - metal, wood, etc.

c) fenceUse - agriculture, boundary, etc.

SECTION 01 78 30.00 22 Page 10

d) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

e) contractNumber

f) sdsFeatureName - Fence or Gate

g) sdsFeatureDescription

CLJN.CL.Marina Any facility or area for the exchange of people or materials from land to water such as a port, harbor, marina, launch area or small craft facility

a) marinaIDPK - Structure Number

b) marinaType

c) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

d) contractNumber

e) sdsFeatureName

f) createdDate - Construction Date

g) categoryOfCraftFacility - boat launch or landed, etc.

CLJN.CL.NavigationalAid A visual or electronic device, on the ground or airborne, which provides point-to-point guidance information or position data to aircraft in flight

a) navigationalAidIDPK - Structure Number

b) navaidType - TACAN, Radar station, Beacon, etc.

c) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

d) contractNumber

e) sdsFeatureName - Type of navigational aid

CLJN.CL.PavementSectionAirfield A pavement section is a 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) pavementSectionType - apron, roadway, etc.

b) isLighted - YES / NO

c) operationalStatus - inService, abandoned, etc.

d) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

e) builtDate

f) contractNumber

g) runwayClassification - class A, class B, rotatory, etc.

h) sdsFeatureName

i) sdsFeatureDescription - MCBCL, MCASNR, Geiger, Stone Bay, etc.

CLJN.CL.PavementSectionParkingArea A vehicle parking area is an area used for parking vehicles not including residential streets and driveways.

a) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

b) operationalStatus - inService, abandoned, etc.

c) pavementSectionType - parking, slab, driveway, etc.

d) sdsFeatureDescription - Dumpster, Driveway, Transformer, Parking, etc.

e) sdsFeatureName - Pad, Slab, Parking, etc.

SECTION 01 78 30.00 22 Page 11

f) facilityNumber

g) builtDate

h) contractNumber

i) isLighted

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

a) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

b) operationalStatus - inService, abandoned, etc.

c) pavementSectionType - curb, roadway, etc.

d) facCode - Surfaced or Unsurfaced

e) divided - Yes / No

f) featureCode

g) oneWay - Yes / No

h) routeSurfaceComposition - concrete, asphalt, etc.

i) builtDate

j) contractNumber

k) isLighted - Yes / No

l) isTankTrail - Yes / No

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

a) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

b) operationalStatus - inService, abandoned, etc.

c) pavementSectionType - Sidewalks

d) sdsFeatureDescription - Named Area

e) routeSurfaceComposition - Concrete, Asphalt, etc.

f) builtDate

g) contractNumber

h) installationCode - M67001

i) isLighted - Yes / No

CLJN.CL.RailTrack A track is the main designation for describing a physical linear portion of the network

a) contractNumber

b) facilityNumber

c) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

d) NetworkSubtype - railroadTrack, craneTrack

e) operationalStatus - inservice, abandoned, etc.

f) sdsFeatureName - Start & finish Points

g) sdsFeatureDescription - Provide Street Name Cross cover

CLJN.CL.RecreationArea An area defined for recreational purposes

a) facilityNumber

b) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

c) contractNumber

SECTION 01 78 30.00 22 Page 12

d) sdsFeatureName - Type of recreation field

e) sdsFeatureDescription - Type of recreation feature

f) areaType - biking, boating, picnic, Hunting, etc.

CLJN.CL.RecreationTrail A location providing physical activities which are mentally relaxing, such as running/walking, biking, or hiking

a) recreationTrailIDPK - Facility or Structure Number

b) trailType - Mulit-use, horse riding, etc.

c) isPaved - YES / NO

d) dateConstructed

e) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

f) contractNumber

g) sdsFeatureName - Trail Name

h) sdsFeatureDescription - Area, Location or parallel street

CLJN.CL.StructureArea A facility classified as other than a building or linear asset

a) facilityNumber - Structure Number

b) builtDate

c) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

d) contractNumber

e) sdsFeatureName - Name of structure according to contract

f) sdsFeatureDescription - Description of item

g) heightAboveSurfaceLevel

h) heightAboveSurfaceLevelUOM - foot, inch, meter, etc.

CLJN.CL.StructurePoint Example: Flag poles; Point of Information Signs (POI) etc

a) facilityNumber - Structure Number

b) builtDate

c) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

d) contractNumber

e) sdsFeatureName - POI, Sign, Flagpole, bleacher, etc.

f) sdsFeatureDescription - Specific type of feature

CLJN.CL.Tower A vertical projection, higher than its diameter, generally used for observation, storage, or electronic transmission

a) towerUseType - communication, observation, etc.

b) heightMax

c) heightUOM - foot, inch, meter, etc.

d) contractNumber

e) towerType - Observation Tower, Guard Tower, etc.

f) facilityNumber - Structure number

g) sdsFeatureDescription

h) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

i) towerMaterial - wood, concrete, steel, etc.

SECTION 01 78 30.00 22 Page 13

CLJN.CL.TrafficControlLight A feature used to represent traffic lights

a) contractNumber

b) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

c) sdsFeatureName - Traffic Control Light, Traffic Signal control box, etc.

d) sdsFeatureDescription - Location such as streets that intersect

CLJN.CL.Wall A linear feature used for separation of facilities, ornamental decoration, or structural reinforcement (retaining wall

a) wallType - brick, timber, stone, concrete, etc.

b) wallHeight

c) wallHeightUOM - foot, inch, meter, etc.

d) dateConstructed

e) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

f) contractNumber

g) sdsFeatureName

h) sdsFeatureDescription - Dumpster enclosure, Utility Enclosure, Blast Protection, etc.

1.4.4 CLJN.CL.REAL_PROPERTY_RESTRICTED

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.Well A shaft dug or drilled into the Earth for the purpose of extracting fluids from the subsurface, collecting environmental samples, injecting fluids into the subsurface or extracting contamination or other impurities from the subsurface

a) facilityNumber - Structure Number

b) wellPurpose - extraction, injection, etc.

c) wellResource - WATER

d) operationalStatus - inservice, abandoned, etc.

e) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

f) contractNumber

g) sdsFeatureName - potable or nonpotable

h) sdsFeatureDescription - operational status source

i) ProjectID - Name of Plant this well services

j) wellType - artesian, drilled, etc.

k) operationalStatus - inservice, abandoned, removed, etc

SECTION 01 78 30.00 22 Page 14

1.4.5 CLJN.CL.COMMUNICATIONS_RESTRICTED

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System GPS and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.CommCartographicFeatureArea Graphic features that aid in visually associating CommAnnotation features to the appropriate communication infrastructure feature.

a) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

b) sdsFeatureName

c) sdsFeatureDescription

d) commProjectName - Contract Number

e) operationalStatus - In service, Removed, Abandon in Place, etc.

CLJN.CL.CommCartographicFeatureLine Graphic features that aid in visually associating CommAnnotation features to the appropriate communication infrastructure feature.

a) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

b) sdsFeatureName

c) sdsFeatureDescription

d) commProjectName - Contract Number

e) operationalStatus - In service, Removed, Abandon in Place, etc.

CLJN.CL.CommCartographicFeaturePoint Graphic features that aid in visually associating CommAnnotation features to the appropriate communication infrastructure feature.

a) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

b) sdsFeatureName

c) sdsFeatureDescription

d) commProjectName - Contract Number

e) operationalStatus - In service, Removed, Abandon in Place, etc.

CLJN.CL.CommUtilityNode A subdivision of a communications network, particularly an asset that participates in the transmission of a signal but that is not a cable.

a) commUtilityNodeIDPK - Structure Number

b) commNodeType - connection or two or more sheaths, Devise Used to detect & measure various environmental conditions, Devise converts electrical signal in to sound, etc.

c) operatingSpectrum

d) transmissionPower

e) powerUOM

f) operationalStatus - In service, Removed, Abandon in Place, SECTION 01 78 30.00 22 Page 15 etc.

g) commProjectName - Contract Number

h) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

i) sdsFeatureName - MNS - Big Voice, MNS - Little Voice, MSN - Control Station, etc.

j) sdsFeatureDescription - MNS - Big Voice, Field Antenna, Antenna Communication, etc.

CLJN.CL.CommUtilitySegment A subdivision of a communications network, particularly a cable for the transmission of a signal.

a) cableMaterial - Fiber Optical, PB, CU, Steel, ABS, etc.

b) cableSheathing - PE, XLPE, Cross Ply, etc.

c) availableFibers -

d) usedFibers

e) numberOfMultiModeFibers

f) numberOfPairs

g) numberOfSingleModeFibers

h) installationTypeCode - Underground, above ground, etc.

i) operationalStatus - In service, Removed, Abandon in Place, etc.

j) cableInstaller -

k) cableRoute -

l) cableCount -

m) numberOfStrands -

n) wireGauge -

o) commProjectName - Contract Number

p) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

q) sdsFeatureName - Non-direct Buried Lines, Direct Buried Lines, etc.

r) sdsFeatureDescription - communications line, etc.

CLJN.CL.UtilityFeature_cDuctBank One or more ducts routed in parallel between two nodes.

a) networkType - A network used for the transmission of a signal.

b) networkSubType - The communication network subtype.

c) utilityFeatureType - One or more ducts routed in parallel between two nodes. (L), etc.

d) diameter

e) diameterUOM - Inches, Feet, meters, etc.

f) ductDepth

g) ductDepthUOM - Inches, Feet, meters, etc.

h) interDuctDiameter

i) interDuctDiameterUOM - Inches, Feet, meters, etc.

j) isEncased - Yes or No

k) numberOfDucts

l) numberOfInserts

m) operationalStatus - In service, Removed, Abandon in Place, etc.

n) commProjectName - Contract Number

o) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

CLJN.CL.UtilityFeature_cManhole An enclosed structure (manhole, or handhole)

SECTION 01 78 30.00 22 Page 16

a) utilityFeatureIDPK - MH Number - See project Manager

b) networkType - Network used for transmission of signal,

c) networkSubType - Communication network subtype

d) utilityFeatureType - Manhole, hand hole, etc.

e) cManholeType - T, R2A, L, j4, JC9C, etc.

f) cManholeMaterial - steel, plastic, aluminum, fiberglass, etc.

g) isHandhole - Yes or No

h) widthValue

i) widthUOM - Inches, Feet, meters, etc.

j) lengthValue

k) lengthUOM - Inches, Feet, meters, etc.

l) heightValue

m) heightUOM - Inches, Feet, meters, etc.

n) diameter

o) diameterUOM - Inches, Feet, meters, etc.

p) cManholeDepth

q) cManholeDepthUOM - Inches, Feet, meters, etc.

r) operationalStatus - In service, Removed, Abandon in Place, etc.

s) commProjectName - Contract Number

t) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

CLJN.CL.UtilityFeature_cPedestal An above-ground enclosed structure that provides access to buried plant and a place to house splices, terminals, etc.

a) networkType - A network used for the transmission of a signal.

b) networkSubType - The communication network subtype.

c) utilityFeatureType - above-ground enclosed structure that provides access to buried plant and a place to house splices, terminal, etc.

d) pedestalType - rectangular box type, etc.

e) operationalStatus - In service, Removed, Abandon in Place, etc.

f) commProjectName - Add Contract Number

g) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

h) sdsFeatureDescription

CLJN.CL.UtilityFeature_cVault An enclosed structure in a facility used for cable entrance.

a) utilityFeatureType

b) networkType - A network used for the transmission of a signal.

c) networkSubType - The communication network subtype.

d) heightValue

e) heightUOM - Inches, Feet, meters, etc.

f) widthValue

g) widthUOM - Inches, Feet, meters, etc.

h) vaultDepth

i) vaultDepthUOM - Inches, Feet, meters, etc.

j) diameter

k) diameterUOM - Inches, Feet, meters, etc.

l) operationalStatus - In service, Removed, Abandon in Place, etc.

m) commProjectName - Contract Number

n) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

SECTION 01 78 30.00 22 Page 17

o) sdsFeatureDescription

1.4.6 CLJN.CL.UTILITIES_ELECTRICAL

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System (GPS) and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.ElecUtilNode_eExteriorLight Exterior lighting is supplied by local distribution systems and is generally the only service for which the electric utility installs, operates and maintains utilization equipment

a) electricalUtilityNodeIDPK

b) exteriorLightType - streetLight, parkingLotLight, etc.

c) electricalNodeType - eExteriorLight

d) operationalStatus - inservice, abandoned, etc.

e) bulbType LED, INCA, etc.

f) circuitID - This available from CM or PM

g) hasSensor - YES / NO

h) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

i) contractNumber

j) dateInService

k) sdsFeatureName

l) Voltage

m) Wattage

CLJN.CL.ElecUtilNode_eGenerator Generator is a power source for providing electricity. Generators may be primary or standby power sources

a) FacilityNumber - structure number

b) electricalNodeType - eGenerator

c) operationalStatus inservice, abandoned, etc.

d) voltage

e) kvaRate

f) circuitID - List is available from CM or PM

g) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

h) contractNumber

i) dateInService

j) sdsFeatureName - Manufacturer

k) generatorType - Primary, backup, emergency, etc.

CLJN.CL.ElecUtilNode_eMeterPoint A electrical meter point represents the location of the metering device

a) electricalNodeType - Description

b) operationalStatus - inservice, abandoned, etc.

c) circuitID - List is available from CM or PM

d) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

e) contractNumber

SECTION 01 78 30.00 22 Page 18

f) dateInService

g) sdsFeatureName

h) sdsFeatureDescription -

i) mountingType

j) utilityOwner

k) voltage - 208Y-120V, 480Y-277V, etc.

CLJN.CL.ElecUtilNode_eSwitch Electrical Switches are installed at strategic locations throughout distribution feeder circuits

a) electricalNodeType

b) switchPosition - closed, open, etc.

c) operationalStatus - inservice, abandoned, etc.

d) electricalSwitchType - switches

e) circuitID - List is available from CM or PM

f) numberOfPhases single, three, two

g) switchPosition - Open, closed, etc.

h) voltage - 208Y-120V, 480Y-277V, etc.

i) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

j) contractNumber

CLJN.CL.ElecUtilNode_eTransformer The Transformer feature class captures information about distribution and power transformers

a) electricalNodeType - Transformer

b) transformerType - stepdown, step up, etc.

c) mountingType - pool or pad

d) numberOfPhases - 1, 2, 3, etc.

e) primaryVoltage 208Y-120V, 480Y-277V, etc.

f) secondaryVoltage 208Y-120V, 480Y-277V, etc.

g) totalKVA

h) circuitID - List is available from CM or PM

i) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

j) contractNumber

k) sdsFeatureName - Manufacturer

l) operationalStatus - inservice, abandoned, etc.

CLJN.CL.ElecUtilNode_eVoltageRegulator Voltage regulators vary the ac supply or source voltage to the customer to maintain the voltage within desired limits

a) electricalNodeType - VoltageRegulator

b) operationalStatus - inservice, abandoned, etc.

c) primaryVoltage - 208Y-120V, 480Y-277V, etc.

d) secondaryVoltage - 208Y-120V, 480Y-277V, etc.

k) numberOfPhases - 1, 2, 3,

e) circuitID - This available from CM or PM

f) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

g) contractNumber

CLJN.CL.UtilFeat_eSupportStructure A structure that supports electric devices

SECTION 01 78 30.00 22 Page 19

a) utilityFeatureType - Utility, Guy, Poles, etc.

b) networkType - electrical

c) heightValue -

d) heightUOM foot, inch, meter, etc.

e) utilityOwner

f) operationalStatus - inservice, abandoned, etc.

g) cableCircuitName - List is available from CM or PM

h) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

i) contractNumber

j) sdsFeatureName - Utility Pole, etc

k) sdsFeatureDescription - Number of circuits attached to pole

CLJN.CL.UtilFeat_eUndergroundStructure Underground Structure is a simple junction feature that includes vaults and manholes that house and protect electrical equipment

a) utilityFeatureIDPK - Structure Number

b) utilityFeatureType - Underground, surface structure, etc

c) networkType - electrical

d) operationalStatus - inservice, abandoned, etc.

e) electricalJunctionType - Manhole, Junction Box, Handhole, etc.

f) numberOfCables -

g) rimElevation -

h) rimElevationUOM foot, inch, meter, etc.

i) cableCircuitName List is available from CM or PM

j) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

k) contractNumber

CLJN.CL.ElecUtilSegment A subdivision of an electrical distribution network, particularly a line for the transmission of electricity

a) electricalSegmentType - OH Primary, UG Primary, OH Secondary, UG Secondary, etc.

b) cableMaterial - AL, copper, etc.

c) location - aboveground, underground, etc.

h) voltage - 208Y-120V, 480Y-277V, etc.

d) utilityOwner -

e) operationalStatus - inservice, abandoned, etc.

f) insulationMaterial - polyCross, none, etc.

g) conductorSize -

h) neutralSize -

i) numberOfConduct -

j) numberOfNeutral -

k) numberOfPhases - 1, 2, 3, etc.

l) circuitID - List is available from CM or PM

m) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

n) contractNumber -

o) dateInService -

p) sdsFeatureName - Electrical Distribution, exterior lighting, etc.

q) sdsFeatureDescription - Armless mount, cross arm, etc.

CLJN.CL.UtilFeat_eElecFacilitySite Polygon feature class to define boundaries of electrical facility stations

SECTION 01 78 30.00 22 Page 20

a) utilityFeatureType - Electrical Facility station

b) operationalStatus - inservice, abandoned, etc.

c) numberOfCircuits

d) numberOfSpareBays

e) numberOfTransformers

f) voltageIn - 208Y-120V, 480Y-277V, etc.

g) utilityOwner

h) gisFeatureCollectionMethod - - CAD, Survey Grade GPS, etc.

i) contractNumber

j) equipmentInstallationDate

k) sdsFeatureDescription - Location of substation

l) facilityIDFK - structure number

1.4.7 CLJN.CL.UTILITIES_POL

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System GPS and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.POLUtilNode_oDispenser A fuel dispenser is a machine at a fueling station that is used to pump fuel into vehicles or AGE equipment

a) polNodeType - Fuel dispenser

b) networkSubType - automotive_diesel, jpts, etc.

c) operationalStatus - inservice, abandoned, etc.

d) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

e) contractNumber

f) dateInService

g) sdsFeatureName - Fuel Dispenser

h) sdsFeatureDescription - Type of fuel, unleaded, ethanol diesel, etc.

CLJN.CL.UtilFeat_oPumpingFacility A structure, typically a building, containing pumps, filters, and controls as part of a larger fuel handling system

a) utilityFeatureIDPK

b) utilityFeatureType - off-loading pumping facility

c) networkSubType automotive_diesel, jpts, etc.

d) operationalStatus - inservice, abandoned, etc.

e) gisFeatureCollectionMethod - - CAD, Survey Grade GPS, etc.

f) contractNumber

g) equipmentInstallationDate

h) sdsFeatureDescription -

1.4.8 CLJN.CL.UTILITIES_STORMWATER

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System GPS and Spatial Reference Properties." Attribute fields may be associated with

SECTION 01 78 30.00 22 Page 21

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.

GPS and collect the following attributes:

CLJN.CL.Impoundment_Stormwater An accumulation of storm water that is impounded by a dam or weir

a) permitID - Permit Number

b) impoundmentType - minimumPool, topOfFloodControl, etc.

c) waterSurfaceElevation

d) waterSurfaceElevationUOM - foot, inch, meter, etc.

e) dateConstructed

f) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

g) contractNumber

h) operationalStatus - inservice, abandoned, etc.

i) stormwaterTreatmentType - Infiltration Basin, Constructed Wetlands, etc.

j) utilityOwner

CLJN.CL.StormwaterUtilityNode_swInlet The location at which stormwater is collected/received into the stormwater network

a) stormwaterUtilityNodeIDPK - Structure ID

b) stormwaterNodeType - swInlet description

c) networkSubType - stormWater

d) stormwaterInletType - Inlet, Headwall, etc.

e) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

f) contractNumber

g) equipmentInstallationDate

h) sdsFeatureDescription -

i) operationalStatus inservice, abandoned, etc.

CLJN.CL.StormwaterUtilitySegment A subdivision of a stormwater network, particularly a pipeline or drainage ditch for the transport of stormwater, between the source, holding facilities, and/or treatment facilities

a) diameter

b) diameterUOM - inch

c) pipeMaterial - cement, plastic, etc.

d) isLined - YES / NO

e) downstreamInvertElevation

f) upstreamInvertElevation

g) gisFeatureCollectionMethod - - CAD, Survey Grade GPS, etc.

h) contractNumber

i) equipmentInstallationDate

j) sdsFeatureName - Stormwater pipe, Open Ditch, etc.

k) sdsFeatureDescription

l) operationalStatus - inservice, abandoned, etc.

m) stormwaterPipeStyle

n) stormwaterSegmentType - open ditch, closed under other feature type, etc.

SECTION 01 78 30.00 22 Page 22

CLJN.CL.StorUtilNode_swManhole A storm water manhole is an underground concrete structure with a top opening used for collecting and routing storm water runoff through underground pipes

a) stormwaterNodeType

b) stormwaterUtilityNodeIDPK - Structure Number

c) numberOfPipes

d) operationalStatus - inservice, abandoned, etc.

e) stormwaterBasinIDFK - Basin id

f) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

g) contractNumber

h) equipmentInstallationDate

i) sdsFeatureName

j) sdsFeatureDescription

1.4.9 CLJN.CL.UTILITIES_THERMAL

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System GPS and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.GeothermalWell A geothermal well is part of a central heating and/or cooling system that pumps heat to or from the ground

a) geothermalWellIDPK - Well ID

b) pipeMaterial - AL, stainless_steel, etc.

c) geothermalWellCasingMaterial

d) thermalInsulationMaterial - MINERAL_FIBER, ARMAFLEX, etc.

e) geothermalWellDepth

f) geothermalWellDepthUOM - foot, inch, meter, etc.

g) downholePipeDiameter

h) downholePipeDiameterUOM - foot, inch, meter, etc.

i) hasBentoniteSeal - YES / NO

j) hasPump - YES / NO

k) operationalStatus - inservice, abandoned, etc.

l) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

m) contractNumber

n) designDrawingNumber

o) equipmentInstallationDate

p) sdsFeatureDescription - Associated Building Number

q) geothermalPipeType

r) xLocation

s) xLocationUOM - foot, inch, meter, etc.

t) yLocation

u) yLocationUOM - foot, inch, meter, etc.

CLJN.CL.TherUtilNode The Thermal Fitting Type bend, cap, tee, etc. subclass represents the joint between two lines

SECTION 01 78 30.00 22 Page 23

a) thermalUtilityNodeIDPK

b) thermalNodeType - tFittingType bend, cap, tee, etc.

c) diameter

d) diameterUOM - foot, inch, meter, etc.

e) operationalStatus - inservice, abandoned, etc.

f) fittingType - bend, cap, tee, etc.Type bend, cap, etc.

g) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

h) contractNumber

i) dateInService

j) sdsFeatureName

k) sdsFeatureDescription

l) depth

m) depthUOM - foot, inch, meter, etc.

n) facilityNumber

o) fittingType - bend, cap, tee, etc.Material

p) projectID

q) utilityOwner

CLJN.CL.TherUtilSegment A subdivision of a thermal distribution network, particularly a pipeline for the transmission of chilled water, refrigerant, hot water, or steam

a) thermalSegmentType - tMainLine, tServiceLine

b) networkSubType

c) operationalStatus - inservice, abandoned, etc.

v) material - AL, stainless_steel, etc.

d) pipeLocation - aboveground, underground, etc.

e) diameter

f) diameterUOM - foot, inch, meter, etc.

g) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

h) contractNumber

i) dateInService

j) sdsFeatureName

k) sdsFeatureDescription

l) cathodicProtection - YES / NO

m) depth

n) depthUOM - foot, inch, meter, etc.

o) facilityNumber

p) pipeType - circular, box, etc.

q) projectID

r) utilityOwner

CLJN.CL.TherUtilNode_tProdStruc Thermal production structures are facilities which produce steam, high-temperature water, low-temperature water, dual-temperature water or chilled water

a) thermalNodeType - facility which produce steam, etc.

b) Capacity

c) CapacityUOM - foot, inch, meter, etc.

d) operationalStatus - inservice, abandoned, etc.

e) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

f) contractNumber

g) dateInService

h) sdsFeatureName

i) sdsFeatureDescription

SECTION 01 78 30.00 22 Page 24

j) facilityNumber

k) utilityOwner

CLJN.CL.TherUtilNode_tSystemValve A thermal system valve is a device installed in a pipeline to isolate flow

a) thermalNodeType

b) systemValveType - gate, ball, etc.

c) diameter

d) diameterUOM - foot, inch, meter, etc.

e) operationalStatus - inservice, abandoned, etc.

f) mediaID - GIS Collection Method - CAD, Survey Grade GPS, etc.

g) contractNumber

h) dateInService

i) depth

j) depthUOM - foot, inch, meter, etc.

k) utilityOwner

l) valveMaterial - AL, stainless_steel, etc.

CLJN.CL.UtilFeat_tUGEnclosureAccess A point feature class for locating the access point to a thermal manhole junction

a) utilityFeatureType - SCADA, UGEnclosureAccess point, etc.

b) networkSubType - steamSupply, steamReturn, etc.

c) networktype -

d) operationalStatus - inservice, abandoned, etc.

e) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

f) contractNumber

g) diameter

h) diameterUOM - inch, feet, meter

i) sdsFeatureName - steam pit, etc.

1.4.10 CLJN.CL.UTILITIES_WASTEWATER

GPS and collect attribute data as specified for each feature listed with GPS accuracy as described in paragraph "Global Positioning System GPS and Spatial Reference Properties." 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.

GPS and collect the following attributes:

CLJN.CL.UtilFeat_sPretreatmentDevice A wastewater pretreatment device is a piece of equipment that removes contaminants before they enter the waste system, etc.

a) utiltyFeatureIDPK - Structure Number

b) utilityFeatureType - Pretreatment Device see existing data

c) operationalStatus - inservice, abandoned, etc.

d) pretreatmentDeviceType - OWS, Trap, etc.

e) gisFeatureCollectionMethod - CAD, Survey Grade GPS, etc.

f) contractNumber

g) equipmentInstallationDate

SECTION 01 78 30.00 22 Page 25

h) sdsFeatureDescription - detailed description

CLJN.CL.UtilityFeature_sPumpStation This is a collection of waste water Pump Station…