J8-StormWaterSOP-20220404

00 111 E !
PUBLIC WORKS GIS UNIT (PWGIS)
Iw Standard Operating Procedures (SOP)
1 8 6 9 Utility Mapping (Stormwater)
CITY OF MEDICINE
December 16, 2021
"...the art and science of asking questions is the source of all knowledge."— Thomas Berger

I. INTRODUCTION..................................................................................................................................................4
GLOSSARYOF TERMS......................................................................................................................................................4
Easements.............................................................................................................................................................4
Right -of --Way (ROW).............................................................................................................................................4
GeometricNetwork...............................................................................................................................................5
AttributeAssistant (AA)........................................................................................................................................5
GRAVITY SYSTEM DESCRIPTION AND DIAGRAM....................................................................................................................6
STORMWATER FEATURE DATASET ELEMENTS.......................................................................................................................6
II. MAPPING STORMWATER INFRASTRUCTURE......................................................................................................9
UNDERSTANDINGTHE PROJECT SCOPE...............................................................................................................................9
REMOVING/ABANDONING EXISTING INFRASTRUCTURE........................................................................................................10
How to Move Features from One Feature Class to Another Feature Class.........................................................11
ADDINGNEW INFRASTRUCTURE......................................................................................................................................12
Digitizing the Stormwater System.......................................................................................................................13
Using the Digital Importer to add GIS Data........................................................................................................18
CONNECTING TO EXISTING INFRASTRUCTURE.....................................................................................................................18
EDITING EXISTING INFRASTRUCTURE................................................................................................................................20
REVIEWINGEDITS.........................................................................................................................................................21
Common Stormwater Errors...............................................................................................................................22
UNIQUE STORMWATER CONFIGURATIONS.......................................................................................................................204
III. STORMWATER ATTRIBUTION AND REFERENCE............................................................................................
255
STORMWATER INFRASTRUCTURE OWNERSHIP....................................................................................................................25
STORMWATER STRUCTURES("SWNODES").......................................................................................................................28
FeatureTypes......................................................................................................................................................28
FeatureAttributes...............................................................................................................................................32
STORMWATER PIPES("SWPIPES")...................................................................................................................................35
FeatureTypes......................................................................................................................................................35
FeatureAttributes...............................................................................................................................................36
SplittingPipes......................................................................................................................................................40
CurvedPipes........................................................................................................................................................41
STORMWATERCHANNELS..............................................................................................................................................41
SCM (STORMWATER CONTROL MEASURES).....................................................................................................................43
Mapping Infrastructure Associated with Stormwater Control Measures(SCMs)...............................................43
AboveGround Structures....................................................................................................................................44
Underground Structures(swEnclosures).............................................................................................................47
APPENDIX............................................................................................................................................................
63
APPENDIX A: CLASSIFICATION OF STORMWATER STRUCTURES..............................................................................................64
Stormwater Structure Examples (Photos)...........................................................................................................64
EndSection Examples..........................................................................................................................................66
HeadwallExamples.............................................................................................................................................67
APPENDIX B: VALID STRUCTURE FORM AND TASK ATTRIBUTES..........................................................................................68

APPENDIX C: RESERVED FACI LITYI D RANGES..................................................................................................................69
APPENDIX D: GEOMETRIC NETWORK PARAMETERS............................................................................................................70
APPENDIX E: GEOREFERENCING THE AS -BUILT [REMOVE].................................................................................................71
APPENDIX F: QAQC ERROR LAYERS [REMOVE?]................................................................
ERROR! BOOKMARK NOT DEFINED.
APPENDIX G: ATTRIBUTE ASSISTANT [REMOVE]..................................................................
ERROR! BOOKMARK NOT DEFINED.
APPENDIX H: EASEMENT EXAMPLES [REMOVE]..............................................................................................................74
APPENDIX I: DOCUMENT FORMAT STANDARDS.................................................................................................................76
APPENDIX.J: ADDING PHOTOS TO STORMWATER STRUCTURES .............................................................................................77
APPENDIX K: REVISION HISTORY.....................................................................................................................................79

I. Introduction
The City of Durham Public Works GIS team is responsible for maintaining feature datasets that reflect
the existing public and private water, sewer, and stormwater utilities in the City (for stormwater and
sewer) or County (water). This SOP details the database design for the stormwater only, an overview of
design standards for stormwater, specifics about individual feature classes, and the methodology for
adding new infrastructure to the system manually and using our digital importer tool.
Glossary of Terms
Easements
The term "utility easement" is often used as a catch-all for both dedicated easements and
encroachment agreements. In general, the difference between the two is as follows:
Encroachment agreements are typically granted by other public utilities or governmental agencies (i.e.
NC -DOT, U.S. Army Corps of Engineers, NCRR, etc.) when the utility owner (i.e. the City of Durham)
wishes to place public utility lines within or across a dedicated ROW or across lands owned by the other
governmental agencies.
A utility easement is granted by a private property owner when the utility owner (i.e. the City of
Durham) wishes to place public utility lines within or across the subject property.
For more info, see Appendix: Easement Examples.
Public Works GIS does not map utility easements in the GIS. Additionally, there is no current process in
place within Public Works GIS to track and/or index new utility easements. Public Works GIS does have
some historical indices of public utility easements, but those indexes were last updated/maintained in
the early 2000's when the employee tasked with maintaining those indexes retired and the work task
was not passed on to a new employee within Public Works.
Easements are used in determining ownership of the public utilities. Water and sewer mains that lie in
City of Durham Public Utility easements are owned by the City after they are accepted by the City for
maintenance. Currently, almost all utility easements are dedicated by commercial and residential plats
as part of the development review and approval process. Locating this easement is usually
accomplished by obtaining the plat reference from a localized property record after identifying the
parcel in the GIS.
For older sewer outfalls, obtaining the easement number by identifying one of the mains will allow the
user to browse to the directory where the easements are located and then searching for that number.
Right -of -Way (ROW)
A right-of-way (ROW) is an easement that is specifically granted for the purpose to transportation. A
ROW (also abbreviated as R/W or R-O-W) must be designated on a plat.
:l

For the purpose of mapping utilities, ROWS are important because all stormwater infrastructure in a
public ROW will be maintained by the entity that maintains the ROW (City of Durham, NCDOT, or
private). In terms of sewer and water services to individual homes or businesses, services that are
within 10 feet of the public ROW are publicly maintained. Anything beyond this point is private.
Geometric Network
From the ArcMap help documents: "A geometric network is a set of connected edges (lines) and
junctions (points), along with connectivity rules, which are used to represent and model the behavior of
a common network infrastructure in the real world." The network itself is a complex data type (similar
to Terrains, Network Datasets, and Topologies) in that feature classes are used as the data sources to
define the geometric network. Each of the utilities has its own geometric network.
The network has two purposes:
(1) it allows editors to identify connection errors in the system (i.e., where a point or line has not been
"snapped" to the adjacent feature;
(2) it allows users to perform a "trace" that identifies the extent of the network.
The latter can be helpful for a variety of reasons, including assessing the number of service connections
associated with a pump station or identifying the extent of an upstream stormwater network to help
investigators locate pollution sources.
Related section, Appendix: Geometric Network Configuration
Attribute Assistant (AA)
Attribute Assistant is an ESRI editor extension with 71 pre -defined methods that can be used to attribute
values when creating new, or editing existing, features. For Attribute Assistant to work the ArcMap
document must have the toolbar loaded, the Attribute Assistant must be "On," and the correct feature
classes and tables must be loaded. For details about how to add these items and which methods are
used for which feature classes, please read the Database Overview and Editor Set-up SOP.

Gravity System Description and Diagram
As the name implies, gravity systems rely solely on gravity to move sewage (in the sanitary sewer
system) or rain water (in the stormwater system) from one location to another. Put another way,
energy is generated in the system by creating an elevation difference between the beginning and end of
a pipe — water flows downhill. Otherwise, there will not be enough energy and the water or waste will
pool at the lowest elevation.
Stormwater Gravity System
Arrows represent direction of flow in a gravity -driven system
Stormwater Feature Dataset Elements
This is an overview of all of the feature classes found in the Stormwater Feature Dataset. Any features
that will be edited are detailed in the Stormwater Attribution and Reference section below.
A

Feature Class Name
Layer Name in Editor MXD
Description
PMPlndexGrid
Index grid for the Proactive Maintenance Program. The grid is used as
Reference/Storm/PMP Index
an aid to guide and help organize proactive maintenance efforts by
Stormwater Maintenance. This index grid divides each of the regions
represented by the "PMPlndexGridMajor" feature class into six
retangular regions and are assigned a letter designation from "A" to "F".
PMPlndexGridMajor
Index grid for the Proactive Maintenance Program. The grid is used as
Reference/Storm/PMP Index (Major)
an aid to guide and help organize proactive maintenance efforts by
Stormwater Maintenance. This index grid forms the major tessalation
of a regular 5000 foot by 5000 foot grid across the City of Durham.
StormWaterGN
The geometric network for the stormwater feature classes. (Not edited.)
None
StormWaterGN_ Junctions
A Network Junction Error is created whenever a line is missing a
Orphan Junctions
coincident point feature on either end of the line segment. Network
Junction Errors are automatically removed when network connectivity is
restored, by snapping the appropriate point feature to the end of the
line segment. "Orphaned" network junction errors can be created and
should be deleted if an attached line segment is deleted.
swChannels
A line feature class that includes both natural (streams and rivers) and
Channels
human -made (ditches) channels.
swEnclosure
A polygon feature class that represents the general outline of and
Enclosure
underground SCM.
swNodes
A point feature class representing features such as inlets, outlets, riser
Structures
pipes, headwalls, and other single -location features.
swNodesABANDONED
A point feature class representing swNodes (Structures) that are no
Abandoned Stormwater/Stormwater
longer in use but are still present.
Structures (Abandoned)
swPipes
A line feature class representing stormwater pipes, generally of 12" or
Pipes
greater diameter, that make up the stormwater system.
swPipesABANDONED
A line feature representing pipes that are no longer in use but are still
Abandoned Stormwater/Stormwater Pipes
present.
(Abandoned)
swSCMs

Stormwater Control Facilities
A point feature class that represents the approximate location of every
city -monitored stormwater control measure (SCM). These features are
created automatically with a script based on data in the SCM Tool SQL
database and the feature is not edited directly in the GIS
swStormSewersheds
A polygon feature class that represents the boundaries of the local
Reference/Storm/Storm Sewersheds
watersheds that overlay the City of Durham and Durham County. The
catchements correspond generally with USGS HUC12 level watersheds
with the exeception of two additional watersheds recognized/defined
by City of Durham Stormwater Division.
swVirtualEdge
A line feature class that includes "flowlines," which help connect the
Virtual Edge
system and represent the direction of non-channelized flow from the
system, through and SCM or to a natural channel
swVirtualJ unction
A point feature class used to eliminate junction errors created when two
Virtual Junction
line features are connected without a point feature. Used specifically for
the end of driveway pipes, at the confluence of two natural channels,
the confluence of a natural channel and non-channelized flow from the
stormwater system, and at points where pipes intersect with open -
chamber underground systems
[Query Layer]
A view (non-editable) of the Stormwater Control Measures (SCM)
SCMDB (LIVE)
locations as recorded in the SCM database.
Planning/StormwaterRegulatoryBasins
A polygon feature class which is used to deliniate three separate
jurisdictions of stormwater development rules and requirements within
Reference/Storm/Regulatory Basins
Durham County.

II. Mapping Stormwater Infrastructure
New sewer, stormwater, and water infrastructure data are added to the GIS on a daily basis. The bulk of
these data are associated with new construction and come through the Public Works Department's As -
built process. This process is covered in detail in the Project Tracking SOP.
Prior to adding any data, it is essential that the editor review the construction drawing and as -built so
that they understand the project limits, demolition plan, and overall site plan. This is all covered in the
first section below. The next section addresses how to manually add features based on an as -built
drawing. A third section details the automated digital submittal import process, and the last section
explains how to connect the new infrastructure to the existing systems.
Understanding the Project Scope
Before starting to edit it is important to understand both what the developers intended to build (as
represented in the construction drawing) and what they actually built (as shown in the as-builts).
Pan to the project location in a utility -editing MXD and with the construction drawing and as-builts open
review the following.
Overall Project/Existing Conditions
• What are the project limits, in other words what are the physical extents of what they planned
to build? Comparing the as-builts and construction drawings, do the limits appear to have
changed?
• Does the construction drawing's Existing Conditions page indicate there are existing utilities on
the site? Do we have them in the GIS? The topic of adding existing infrastructure into the GIS is
covered later in the section Editing Existing Infrastructure.
• Does the Existing Conditions indicate that any of the existing infrastructure will be abandoned or
removed? (There may also be a separate Demolition Plan page.) Handling this infrastructure is
discussed in the Abandoning/Removing Infrastructure section.
• Which utilities (sewer/storm/water) are included in the construction drawing? Are the same
ones depicted on the as-builts?
Sewer
• Are there any sewer drop or doghouse manholes depicted on the drawings?
• Is there a force main associated with the project?
• Are there any sewer outfalls?
• Where does the system connect to existing systems? Do we have those systems in the GIS?
• Are there any streams that will be crossed by sewer lines? These may be considered High
Priority Lines.
Stormwater
E

• Are there stormwater control measures (SCMs) shown in the construction drawing? Using the
latest aerial imagery, can you identify their location(s) on the site?
• Are there any streams shown in the project area in the GIS? Are they on the construction
drawing and will they be affected by construction?
Water
• Have the hydrants already been added for the project?
• Where does the water system connect to the existing system? Do we have the existing system in
the GIS?
• Are there any blow -offs that will need to be removed?
Removing/Abandoning Existing Infrastructure
Abandoned infrastructure is infrastructure that is no longer in use, but has been left in the ground.
Consult the project's Construction Drawing for guidance on whether previously existing infrastructure
has been modified or removed. The beginning pages of the Construction Drawing will typically have a
page titled Existing Conditions or Demolition Plan. These pages contain drawings of the site including
existing infrastructure and what the intended results will be. The four potential options associated with
existing infrastructure (with some common indicators) are:
1. Infrastructure will remain unmodified. [Existing, Ex., To Remain, etc.]
2. Feature Infrastructure (such as hydrants) will be moved. [Relocated, Reloc., etc.]
3. Abandoned in place. [Abandoned, Aband., Filled in place, Filled, etc.]
4. Removed [To be Removed, Removed, Rem., TBR, etc.]
_ RELOCATED
I
Ex- Asphalt
Ex. Asphalt ` Drivewav
Lot I }� �+ TO RE1MMN
orce Main TO B _
[ ABANDONED IN
ACCORDANCE
( WITH C.O Ex. Power Pole
[ STANDARDS 1 y TO BE
RELOCATED
Ex.18"RCP
Ex 18" RCP
=. • ! TO BE REMOVED
10

If there are outstanding questions about whether existing infrastructure was removed or modified,
speak with the inspector in the Engineering Inspections group who reviews new developments in the
region.
Abandoned infrastructure will be removed from the "active" sewer feature class and added into the
associated abandoned feature class (see table below.) Removed infrastructure is deleted entirely.
Relocated infrastructure should be included on the as -built and needs to be handled on a case -by -case
basis.
Abandoned Feature Classes
Active Feature Class
I Abandoned Feature Class
Stormwater System
swNodes
swNodesABANDONED
swPipes
swPipesABANDONED
Sewer System
snForceMain
snForceMainABANDONED
snGravityMain
snGravityMainABANDONED
snManhole
snManholeABANDONED
Water System
wnSystemValve
AbndSystemValve
wnWaterMain
AbndWaterMain
Note that sewer cleanouts, meters, and sewer and water laterals do not have equivalent abandoned
feature classes. These features are just deleted from the GIS if the service no longer exists. However,
taps and saddles associated with removed services are not deleted. They are left in place because in the
field they are left in place.
How to Move Features from One Feature Class to Another Feature Class
1. Start an edit session, making sure both the feature class that contains the features and the
feature class into which the features will be added are both editable.
2. Highlight the features in one feature class that need to be copied. For example, if there are
several legs of gravity main and associated manholes that need to copied to the abandoned
gravity main and manhole feature classes, first highlight just the gravity main features.
3. Right -click on the map and select "Copy."
4. Unselect the highlighted featues and then right -click on the map and select "Paste." (Note: if
more than one feature class is selected, Paste will not work.)
S. A pop-up box will appear. Select the correct layer into which the copied features will be pasted.
Hit OK.
11

Paste X
Choose a layer to create feature(s) in:
Target; IV Gravity Main (Abandoned)
OK cancel
6. The pasted features will now be selected. If adding features into one of the abandoned layers
update the AbandonedDate and AbandonedProjectlD fields. Do not update the values in the
other fields.
7. The features have now been pasted into the new feature class, but they still need to be deleted
from the original feature class. Select them again and delete them in the Attribute table on the
editing window.
8. Repeat this process for other features in other feature classes.
Adding New Infrastructure
This section covers how each utility is visually represented in the GIS. For information about the
function and attribution of various infrastructure components please consult the Stormwater
Attribution and Reference section in this SOP. Manually adding new infrastructure to the GIS essentially
involves adding the project's geo-referenced utility plan to the editor's editing MXD and tracing the
utility data into the GIS. For step-by-step instructions on how to geo-reference a plan please see the
instructions in the appendix. Whichever utilities are being added, the standard procedure is to draw in
all of the point features associated with each utility and then add in the associated line (pipe) features.
You will fill in attributes later, based on the information in the Stormwater Attribution and Reference
section.
To avoid confusion, digitize one utility at a time.
Before digitizing anything, review the project's legend so you can distinguish among the correct utilities.
LEGEND
A
F HS'DA NT
WATEREfEI'ER
�
AATFA CALVE
®
SACSGYWa'PREl'E`Tl'ER
�Gv
GAS VALVE
CATCHEASIN
8 �
4'ABOIIvI.EI. ABTA DRALV
O sw
SCMAM SEWERWICLE.i
�s
SAlvil'A SElO2RWI+1I�i
Q
PLA6FDE`vD SECTION
SIORM DkAENAGE PIPE
WAT@L!!AL
� ^
D034iRTC IA=
h
FIRE PBO'IECIION iCA'IFIL
w
PORGY AfALV
.,
GAS SGtLN
L�^
EXfCIR G reYEexaL�. ce
$
tiIILTII'POLE
LEGEND
@
SrORWATER LL LE
®
DROP INLES
®
CURB INLET
ROCO
ROOF DRkH CLEANOIR
®
CANRaRY CFWFR CA FAW�IR
✓�
SANRA SEWER N#J F
-
NNOEjiRROI,WC SMRM
_
NNOERRR D SANRARY
Example Legends
12

Digitizing the Stormwater System
Drawing an individual system
1. Add any stormwater structures associated with pipes that are 12" or greater in diameter into the
GIS. Be sure to select the correct Type of structure from the Create Features template. Use the
listed ID on the as -built, the abbreviations listed in stormwater portion of the Stormwater
Attribution section of this SOP, and aerial imagery to intuit what type of structure it is.
In the figure below, CB stands for catch basin and DI stands for drop inlet. JB stands for junction box,
but use the manhole Type because any new junction structure will be accessed using a manhole lid
and is therefore coded as a manhole. Other common abbreviations are YI for yard inlet (which we
code as a drop inlet), Cl for curb inlet, and FES for flared end section, which is coded as an end
section with the form 'Flared'.
• RCP
\\
\1
0 i83. 0LF .77Z
CB-303
\
\
` I
CONVERTED EXISTING
{ I
`
GRAYED INLET To
{ I
CATCH BASIN
,
_.
51.o LF 18" RCP
, Ex. l8"
EX. 01-113
I
`
BUILDING
ROB BRAIN -
8- ROOF DRAIN S 5®SF e \
RECYcurlGs/ /
l
FF8 377.00
/
/ 1
BB 81.8 LF 18" RCP EX. JBi 142
1f
S"'ROOF DRAIN `l�.
-182
r
— r
\ RCP
24. RCP 25 Sf'E;A
24
FX.
Depiction of Stormwater Structures on an As -built
2. Some as-builts indicate that a "double catch basin" or "double curb inlet" has been installed. If the
double catch basin/curb inlet consists of two catch basin grates over one large box then depict the
structure in the GIS with one point and indicate in the Comment attribute that it is a double basin.
Such a structure exists at the Montessori Children's House of Durham, as depicted in the as -built
below.
13

3
4.
r
,
S r
V.
DOUBLE $
-f �
"l�oLET
dURB, Nut.
•.� v ::=++ ....... t�•f.flif V7tiLlLfiU
If, however, there is a pipe that connects the two structures then represent each distinct structure
in the GIS and connect them with a short length of stormwater pipe.
After you have added the structures, add the stormwater pipes that are 12" or greater. Each
stormwater pipe must begin and end with a stormwater structure. Draw the stormwater pipes in
the direction of flow. On some as-builts you can determine flow direction by looking at the overall
stormwater drainage plan and identifying where the stormwater "daylights," that is, where the
stormwater leaves the piped system. On others you may need to look at the profile and assess the
direction of flow for each individual pipe.
Some as-builts will indicate that there are parallel stormwater pipes as part of the system. Typically,
this occurs with culverts that carry existing streams. How these parallel pipes (also referred to as
"barrels") are represented in the GIS depends on whether each of those multiple barrels has its own
end section. If each pipe can be said to have its own end section then each pipe is represented
discretely with its own node at the beginning and end of the pipe:
14

If, however, there is one headwall containing all the pipes, then the editor should represent the
structure by creating a single headwall to represent the upstream structure and a single headwall to
represent the downstream structure. These structures are not snapped directly to any of the
multiple barrels. Instead they are offset and a swChannel with a Type "Stream" connects the
headwall to each pipe:
5. If a stormwater structure (typically a curb inlet, combo inlet, or drop inlet) discharges directly into a
culvert, the editor should take one of two approaches to show the connectivity:
a. If the structure appears in the GIS to be adjacent to the culvert then the structure should be
moved to sit directly on top of the pipe; however, the pipe should not be split;
b. If the structure is further away, it should be connected by a flowline to the culvert, instead of a
pipe.
6. If there are any stormwater control measures associated with the project, see the section Mapping
Infrastructure associated with Stormwater Control Measures below.
/, /
ggi
Mc
SdMH �w
�1�r
-n 'v = �qb �y •`. lP RUSH
eisw � '.• t _

Depiction of Stormwater SCM (Wetland Pond)
Turn on the swChannels and swVirtualEdge layers. Natural channels (rivers, streams, and ditches)
are represented in the swChannels layer. Features in the swVirtualEdge layer are designed to show
the connection between the end of the stormwater system and natural channels. If there are
streams in the area, read the section Guidelines for Digitizing Flowlines to determine if the outlet
structures should be connected to a natural channel using the swVirtualEdge and the
swVirtualJunction features.
7. If connections need to be made to existing stormwater infrastructure, see the section Connecting to
Existing Infrastructure below.
8. Once the system has been drawn, it needs to be attributed. See the tables in the Stormwater
System Overview section in section one of this SOP for which fields to attribute for each feature
class and the source for that data.
Guidelines for Digitizing Flowlines (aka swVirtualEdge)
The swVirtualEdge feature is used for two reasons. To create connectivity between the stormwater
system and the natural system of rivers, creeks, and streams and to create connectivity between the
stormwater features cross the surface of an SCM (like a dry/wet pond) or through an SCM (like an
underground sand filter/storage device). The swVirtualEdge is based upon the concept of an "artificial
path" that can be found in the USGS NHD databases. It functions to connect portions of the system that
cannot be represented by an actual pipe or stormwater channel. This connectivity allows us to use the
geometric network tool and it is a best practice for stormwater modelling. To determine if a
constructed system can be connected to the natural system follow these steps:
1. Turn on the topographic lines and the swChannels layer.
2. Determine if there is a natural channel in the area.
3. Use the topo lines to confirm if there could be discharge from the stormwater system, to the natural
channel. Ignore other hydrologic factors such as total rainfall, soil type, surface roughness, etc.
4. Only the topo lines, the stormwater system, and natural channels will be used to make this
assumption, for the purpose of stormwater network connectivity.
i
In the image above, the stream is at a lower elevation than the headwall, so it does make sense to connect the constructed
system to the natural channel.
16

5. Flowlines must be drawn perpendicular to the topo lines, so to connect to a stream it has to be
possible to follow that fundamental rule.
In the figure above, there are several valid ways to map the flowline from the headwall to the stream, however the one
depicted by the dashed line is not one of them. The figure below shows one valid alignment for the flowline.
6. Use a swVirtualJunction to connect the swChannel and flowline (swVirtuaIEdge).
7. Flowlines are also used to connect outlet pipes into a Stormwater Control Measure (SCM) to the
riser pipe or other structure that serves to move water out of the SCM. Refer to the SCM
Mapping section above for more details.
17

Using the Digital Importer to add GIS Data
The entire digital submittal review process is covered in the Project Tracking SOP.
Connecting to Existing Infrastructure
New infrastructure is often connected to existing infrastructure. Sometimes engineers will provide the
pipes and structures for these connections in the data files (for example, listing "existing" sanitary sewer
manholes), other times they will not.
If the data are provided, make the following checks when evaluating the data:
• Have duplicate structures and/or pipes been created in the GIS database when the data were
imported?
121
Ja+ z- x-
Line measurement (Planar)
Segment: 0.943349 Feet
Length: 0.943349 Feet
New infrastructure may not
always match the location of
r existing infrastructure.
• If yes, do the attributes for these pipes and/or structures match those of the existing pipes and
structures? Specifically pay attention to the X, Y, Z, inverts, material, and pipe diameter attributes.
• If the material and pipe diameters match and there are minor variations in the X, Y, Z, and inverts
(+/-0.5 feet) then delete the new duplicate features and make sure to connect the new parts of the
system to the existing parts of the system. Be sure to have the network junctions layer on during
this process.
• If the material and pipe diameters do not match check the as -built to confirm the data provided in
the new data files matches what is shown on the as -built. If the data does match, review the
construction drawing to see whether there is an indication that structures have been rebuilt or pipes
replaced. Were the existing structures actually removed or abandoned? If so, return to the
Removing/Abandoning Existing Infrastructure section. If there is no indication that the existing
infrastructure was removed, the editor needs to evaluate what the most likely source of the
discrepancy between the two different sets of data. Editors should feel free to reach out to other
PWGIS staff or Public Works inspectors for guidance.
• If you choose to use the newly imported data, be sure to retain any pertinent project information or
other attributes that were on the original feature in the GIS. For example, Facility ID, Project ID, and
any Comments should remain with the feature. You WILL want to update the feature source, and
add a comment that the new data were imported with project number [the new project number].
If the data are not provided, make the following checks when evaluating the data:
I

• Review the construction drawing and the as -built to see if there is any indication in terms of how the
new and existing infrastructure will be connected.
• Review any construction drawings or as-builts associated with adjacent projects, especially if this is
part of a larger phased project.
• If the connection to the system can be reasonably determined, draw a connection to the existing
system and ask a supervisor to review it. Make a note in the comments field to indicate that the
exact configuration is not known.
231Z
gOMI
teasonable edit: connect new
vaterline to existing waterline
vith a 12" main and a 12" x 12"
ee.
Unreasonable edit: thejunction box
and combination Inlets on Farm Pond
Trl probably connect to a larger
system on Brier Creek Pkwy, but the
engineer has not prodded the data.
A closer inspection reveals this data
should come in with a later phase and
the updates should not be made at
this time.
19

When Should Pipes be Split?
If new infrastructure intersects existing pipes, the existing pipe feature may need to be split.
Examples that require Pipe Splitting:
- At point features
- New pipes that TEE off of existing pipes.
- When diameter changes somewhere along the length of a pipe (a swPipeJunction should be used at the split
to connect the two pipe features)
When a pipe has to be split for whatever reason the "FacilitylD" needs to be changed on one part of the
segment. The current "FacilitylD" is moved to the "LegacylD" and the new "FacilitylD" is <NULL>. If there
already exists a LegacylD, the new LegacylD replaces the old one. This is generally handled by Attribute
Assistant, but confirm that the information has been split properly.
*Note: Pipes are not split at lateral intersections such as at Saddles (Sewer) or Taps (Water). *
*Note2: Still determining how this process will continue forward through the CityWorks platfc
Editing Existing Infrastructure
Construction drawings and as-builts may provide clues about missing infrastructure or connectivity in
the existing utility systems. Existing infrastructure should be mapped if:
• New infrastructure that needs to be mapped connects to the existing system.
• Existing features in the GIS are not connected to the system and that connectivity is shown in the
construction drawing or as -built. (Examples: disconnected hydrants, disconnected water meters,
stormwater stubs where the construction drawing indicates the missing upstream or downstream
structure.)
If existing infrastructure is added, be sure to (1) indicate the source in the appropriate source fields and
(2) add the "dummy" ProjectlD (0000.00) to the ProjectlD field, and (3) add the ProjectlD of the source
where the missing infrastructure was found to the comments field.
Reasona
contructi
water mi
existing r
20

Unreasonable Case: in this situation the
existing hydrant could be connected to one of
three waterlines. The construction drawings
and as-builts were not helpful and even a site
visit did not clarify the issue. This hydrant
should not be connected.
Once utility edits are completed the editor should review their own edits by utilizing the QC/Review
process stated below. A personal review of your edits should be done prior to passing the project to a
second editor.
Reviewing Edits
All new project -related utility edits are reviewed by a second editor within a month of the data being
added. The purpose is two -fold: (1) catch attribution and utility configuration errors and (2) make
individual editors aware of any systematic errors they may be making as quickly as possible with the goal
of avoiding those problems going forward.
The steps use GIS, as-builts, and construction drawings. Whether the reviewer corrects the errors they
see or returns them to the editor for correction depends on the magnitude of the problem. For
example, the occasional missing sewer manhole invert or incorrect stormwater ownership can be
excused and corrected on the spot. A project that includes no invert data (when it was clearly included
on the as -built or in the data files) or where all the stormwater utilities on private property have been
coded as "City of Durham ROW" should definitely be returned to the editor because they reflect a larger
systemic problem. Even if the reviewer opts to correct the errors they see, they should still note what
problems they identified so that they can communicate that to the editor
1) Start by navigating to the project location in the GIS and opening the related as -built and
construction drawing.
2) Determine if there is a Demolition page in the construction drawing. If there is, review the plan
carefully and, with the utility infrastructure data turned on, determine if any existing infrastructure
that was supposed to be abandoned or removed is still in the active GIS utility layers. Return the
project to the editor immediately if infrastructure that should be abandoned or removed has not
been handled.
3) Turn on the Network Junction Errors layer within the QC layer group. A Network Junction Error is
created whenever a line is missing a coincident point feature on either end of the line segment.
Network Junction Errors are automatically removed when network connectivity is restored, by
21

snapping the appropriate point feature to the end of the line segment. "Orphaned" network
junction errors can be created and should be deleted if an attached line segment is deleted. Review
the Geometric Network write-up for more information about network junction errors.
4) Turn on the Error layers. Generally, it is best to review these errors by feature class. Review and
correct any errors. Details about these layers can be found in the Appendix.
5) Turn on the Ownership layers. Using the guidance about ownership, in the Appendix, review these
layers.
6) Zoom in close enough to the project so that individual features are visible and distinct from one
another. Turn on one utility and, while also referencing the as -built, "walk" the extent of the newly
added infrastructure. Look for 2 things: (1) utility configurations that fall outside of accepted design
expectations and (2) data missing from the GIS that is depicted on the as -built. Some of the
common instances of these types of errors are outlined below by utility. This error list should not be
considered comprehensive.
7) Select all features manually or by using the Select By Project ID tool and look for holes in the
attribute data.
8) Run the Data Reviewer tool. Details can be found in
F:\GIS\PROJECTS\ScriptingClub\Production\DRScriptToo1.
Common Stormwater Errors
a) swChannels features that have not been removed such that streams and creeks run through
houses and down roads.
b) Missing structures and pipes associated with SCMs.
c) Incorrectly coded ownership.
d) Entire blocks or legs of infrastructure that are missing from the GIS but are captured in the as -
built. (For example, one project we had a couple years ago left out all the infrastructure
associated with a cul-de-sac.)
e) Disconnected structures.
f) Network junction errors.
g) Location left as "0."
General QC Steps (can be done in the order of the QC'ers choosing)
1. Confirm that the following fields in the project polygon have been updated correctly: DateBuilt,
Storm Updated, Storm UpdatedWhen, StormUpdatedBy, SewerUpdated, SewerUpdatedWhen,
SewerUpdatedBy, WaterUpdated, WaterUpdatedWhen, WaterUpdatedBy, and PageCount,
2. Confirm that the as -built path and URL links work in the project polygon. Please refer to Project
Tracking SOP for more information.
3. Confirm that abandoned/removed features have been removed from the GIS.
4. Confirm there are no network junction errors associated with the Stormwater infrastructure.
22

5. Confirm that what is digitized matches what is shown on the as-builts' utility plan. Look for areas
included in the as -built, but not the GIS. Also look for disconnected point feature classes.
6. Confirm that flow direction is correct for storm.
7. Confirm that new utilities connect to existing utilities. This should always be true for sewer and
water, but only sometimes for stormwater. Stormwater infrastructure should terminate in an
end section or headwall.
8. Confirm that all point features are connected to the system (exceptions: drop inlets, hatches
and manholes associated with underground SCMs).
9. Confirm that pipe diameters "make sense." That is, smaller diameter pipes feed into larger
diameter pipes.
10. Confirm that the QC layers do not display any errors.
11. Confirm that the Ownership is attributed correctly using the Ownership layers.
12. Confirm that the Data Reviewer Final QC Script does not identify any errors.
13. Assess whether errors flagged by Data Reviewer that are adjacent to the project can be resolved
quickly and easily. If so, they can be passed back to the editor.
14. Confirm that all features associated with the Project have the correct projectlD. Scan the
attribute tables for the selected features looking for obviously erroneous values, such as
incorrect locations in the point feature classes.
15. Record all feedback to the mapper in a checklist on the project's Trello card.
16. Use the checklists below to catch utility -specific errors that are not caught by any of the
processes above.
QC Stormwater
SwChannels that need to be removed because they do not exist or have been piped. Look specifically
that streams that go through houses, down streets, etc.
SwPipes that are carrying streams that have not been given the Type "Culvert." Update the type.
End Sections / Headwalls with the incorrect assigned Task.
SCMs not mapped or connected to the system using virtual edges and points. SCMs data may not be
included in the digital data, but should be mapped based on the construction drawing and imagery.
23

Unique Stormwater Configurations
Stormwater configurations where there is a confirmed unknown structure:
• There are times where there is an unknown structure connecting two pipes that are CONFIRMED via
CD's, As -built, and field visits. With that being said, there are a couple of variations of this, which
would all be mapped using a PIPE JUNCTION.
• We occasionally receive PWGIS edits that states that there is a structure identified, but there is no
access to that structure to determine what type. This typically comes from CCTV practices. In this
case, the two pipes should be mapped connected by a PIPE JUNCITON.
• Another scenario is where we have one pipe entering another pipe where there is no physical
structure present. In this case, you would also connect the two pipes using a PIPE JUNCITON.
• The last scenario is where the is a verified pipe transition, whether it is a material change or pipe
size change, and there is no structure present.
• Below are two examples of these scenarios:
X
n
M\
Stormwater configurations where there isn't a confirmed structure:
• There is a scenario where there is possibly a structure present but it is NOT CONFIRMED via CD's,
As-builts, or field verified. In a situation like this, you would use the POSSIBLE JUNCTION feature to
connect the pipes.
• This scenario should be mapped using a POSSIBLE JUNCTION if the nature of the configuration
cannot be determined.
4 f.241
�1�
W24ff4ff
2409
24

III. Stormwater Attribution and Reference
Stormwater Infrastructure Ownership
We track ownership of utilities as a way to know who is responsible for maintaining it. In the case of the
stormwater system this involves assigning the appropriate code to the "OWNER" attribute on the
"swNodes" and "swPipes" feature classes (There is no OWNER assignment for the "swChannels" layer at
this time).
Unlike the water and sewer systems that have much more narrowly defined ownership/maintenance
responsibilities only selected portions of the stormwater system - primarily the portions that fall within
City maintained streets - are considered owned and maintained by the City. The remaining portions of
the system are considered either privately maintained or owned/maintained by another entity such as
NCDOT. And while the stormwater system does include the establishment of stormwater drainage
easements across privately owned property the maintenance of that infrastructure within the easement
is the responsibility of the property owner (and this is source of much mis-understanding when it comes
to maintenance responsibilities in the stormwater system).
New projects that involve new roads or large segments of stormwater infrastructure (such as a new
subdivision) are "accepted" when the City Council formally accepts the new infrastructure. This project
acceptance process occurs whether the infrastructure is constructed inside the existing city limits or is in
a newly -annexed area of the city.
Projects that include only small segments of public infrastructure (such as a leg of pipe and one or two
structures that tie the private infrastructure for a new apartment complex or strip mall into the public
system) are considered "accepted" when the mylars are delivered to us by Engineering Services.
Ownership of structures in the stormwater system is determined by the location of the structure while
ownership of pipes are determined by an examination of the upstream and downstream structures
connected to that pipe. Ownership of structures is more readily determined given that the structure is
essentially a single location and therefore can be assigned a definitive OWNER value. Ownership of
pipes is a bit ambiguous as the pipe itself can cross ownership boundaries. For this reason, the OWNER
values assigned to the structures at each end of the pipe are used in determining the final owner of the
stormwater pipe. In many cases the OWNER of a stormwater will be coded with the special value of
"SHARED" indicating the pipe itself crosses a ownership boundary.
The guidance below is considered to be true in an overwhelming number of cases, which is not to say
that these rules laid out below are never broken, just that it would be very unusual and noteworthy if
they were. Remember that the as -built is the document of record and trumps all general rules and
guidance.
25

"swNodes" OWNER Determination
"swNodes" Location/Situation
OWNER
The "swNode" feature is located WITHIN a PUBLIC RIGHT-OF-WAY:
The "swNode" feature is adjacent to a ROADS feature that has a "MAINT"
value of "LOCAL Pending" OR the "MAINT" value is "LOCAL" and the project
Pending City
has not yet completed the acceptance process (most new projects).
Acceptance
The "swNode" feature is adjacent to a ROADS feature that has a "MAINT"
value of "LOCAL" OR the value is "LOCAL Pending" and the project has
City of Durham
already been accepted.
The "swNode" feature is adjacent to a ROADS feature has a "MAINT" value
NCDOT
of "STATE".
The "swNode" feature is located WITHIN a PARCEL:
City OR Pending City
The parcel owner is "CITY OF DURHAM"
Acceptance (see
above)
The parcel owner is "DURHAM COUNTY"
County
The parcel owner is something other than the values above
Private
Exceptions: If a pipe starts and ends in a parcel and is rerouting a stream
under a road, the pipe and structures will receive a value of that matches
the owner of the road.
Value should match
owner of the road
Figure 2 below is a great example of this scenario.
26

"swPipe" OWNER Determination
"swPipe" Location/Situation
OWNER
"swNode" features on both ends of the pipe have identical OWNER values.
Use the same value
that is encoded on the
Note: Please review Exception section below
"swNode" feature
"swNode" features have an OWNER value of "City of Durham" at one end
Pending City
and "Pending City Acceptance" at the other end.
Acceptance
"swNode" features have an OWNER value that is a different value at each
end of the pipe.
If information is provided later by city personnel that the pipe's ownership
Shared
should be changed from `SHARED' this update should be made and a
note should be added to the SOURCE COMMENT field indicating who
provided this information about the ownership.
Exceptions: If a pipe starts and ends in a parcel and is rerouting a stream
under a road, the pipe and structures will receive a value that matches the
owner of the road.
Value should match
owner of the road
Figure 2 below is a great example of this scenario.
27

A couple of examples of pipe ownership assignment include the following:
Figure 1 : Ownership of structures are 'Pending' or'City
ROW', so this pipe will be coded as the same as the
structures.
Stormwater Structures ("swNodes")
Figure 2: Road ownership of the road is 'City ROW, so the pipe
and structures will receive a value of 'City ROW' for ownership.
Match the ownership value to the roads owner.
Feature Types
The swNodes layer contains all the types of discrete inlet and outlet structures that make up the
"closed" constructed stormwater system. These types are described below along with the typical
attribute values for new construction. Unless noted otherwise, nodes can be connected to 0 or more
upstream pipes and only 1 downstream pipe.
COMBINATION
INLET
An inlet built into the curb and gutter section of a street that
includes a both a drop inlet like grate and a curb inlet like throat
AKA.
opening in the face of the curb.
Catch Basin
Combo Box
CURB INLET
An inlet built into the curb face of a street. It does not include a
grate, but may have a very long throat.
W:

DROP INLET
AKA:
Grate Inlet
An inlet that is flush with the ground and consists of a large grate.
Roll Curb Grate
Yard Inlet
End sections represent the terminal end of a pipe or they may be a
specifically designed structure, such as a flared end section. These
END SECTION
locations represent points at which the "open" stormwater system
"closed"
(i.e. a stream or ditch) connects to the system.
Essentially a large curb inlet with a precast box which contains
engineered soil material to filter incoming stormwater. Filtered
water is piped to a nearby catch basin (the downstream catch basin
FILTERRA
also serves as an overflow device). An explanation of how a filterra
functions can be found here:
https://durhamnc.gov/DocumentCenter/View/3101/Filterra-
Presentation-November-29-2011-PDF?bid I d =
An access structure associated specifically with underground SCMs.
A hatch allows access to the SCM and is a large, metal door flush
HATCH
-_-_-_-_-
with the ground. The image below shows two hatches associated
with an underground storage SCM at the North Carolina State
AKA:
-----
Bilco Door
-_-_-_-_-
Employees Credit Union at 3872 Guess Road. Historically we have
used "Manhole" to capture this type of structure and will at some
point need to manually review manholes associated with SCMs to see
if they should be recoded as hatches.
Headwalls represent the terminal end of a pipe. These locations
HEADWALL
represent points at which the "open" stormwater system (i.e. a
stream or ditch) connects to the "closed" system. Headwalls come in
AKA:
several forms including the wing wall, vertical, and L-wall. Headwalls
End Wall
are often, but not always, associated with large culverts and SCMs.
Structure where two or more pipes meet. Junction boxes are not
accessible and new construction will not include any "true" junction
JUNCTION BOX
boxes. Any junction box that is accessible through a manhole should
be coded as a manhole.
29

Junction boxes that can be accessed through a manhole where two
or more pipes connect. If the digital submittal data indicates that
MANHOLE
they have installed 'junction boxes" check the imagery and the
construction drawing details if these are actually manholes and, if so,
set the Type to Manhole.
Minor drains will typically be connected to "minor pipes."
Attribution of minor drains is minimal and minor drains are only
included in the stormwater system if (a) the data is provided by the
MINOR DRAIN
engineer as part of the digital submittal or (b) there is a special
request within the Public Works Department to include this
infrastructure based existing drawings or field work.
This is an implied junction where two pipes are connected without a
standard structure. The three situation when pipe junctions should
be added are as follows:
1). When a pipe has a "tap -in" with another pipe (i.e. a 15" pipe
connects directly into a larger culvert without an actual structure).
2). When the pipe connects to a non-traditional structure that is not
PIPE JUNCTION
(or
co
represented in the swNodes layer (i.e. a pipe that connects into an
TRANSITION)
underground storage SCM).
3). When the diameter or material of a pipe changes without the
presence of a structure (i.e. an 18" RCP pipe is joined directly to an
18" HDPE pipe or an 18" RCP pipe is joined to a 24" RCP pipe).
If a pipe is extended by additional lengths of pipe consisting of
identical material, then no pipe junction would be added and instead
the existing length of pipe would just be extended in the GIS.
This type only used when the nature of the connection between two
pipes has not yet been determined. In other words, when even a
field visit to the site does not allow the editor to determine the
nature of the connection. Possible junctions should only be created
POSSIBLE
on occasions where the editor is conducting investigation regarding,
JUNCTION
■
or is otherwise notified by Public Works staff about, potential
unrecorded infrastructure that is not visible from the surface and
whose existence has not yet been verified by other means (such as a
CCTV inspection).
30

An inlet structure that is designed to remove water from a
stormwater control measure. Typically, a riser pipe has a small
diameter opening near the base so that during lower flows water
leaves the SCM slowly, but during higher volumes more water can
RISER PIPE
0
leave the SCM. Riser Pipes are typically connected to a 15- or 18-
inch reinforced concrete pipe that terminates with an end section.
Riser pipes can be found in dry ponds, wet ponds, constructed
wetlands, and bio-retention ponds.
This feature consists of a large inlet covered by a slab (typically
concrete) elevated above the surface by several inches. Stormwater
SLAB INLET
flows across the ground and enters the inlet through the gap, a.k.a.
throat, between the slab and the ground. Access into the slab inlet
AKA.
Open Throat
may be possible through a manhole set into the concrete top. The
Catch Basin
below -ground structure may be made of brick, concrete block, or
concrete and may be round or rectangular. A slab inlet may be at
the top of a system or it may have upstream pipes that carry
stormwater into the structure and then continues downstream.
A structure designed to control the rate at which stormwater is
released from the upstream portion of a site and is found in
conjunction with related SCM infrastructure such as an underground
wIER BOX
storage device or level spreader. These structures have an interior
wall (i.e. the "wier") which serves If the water level is lower than the
AKA:
Splitter Box
wall, then the stormwater exits slowly through a small opening at the
bottom of the wall. If the volume of water is in excess of the interior
wall, then the excess volume flows over the wall and exits the system
more rapidly.
31

Feature Attributes
General Stormwater Nodes Attribution
Date that infrastructure is accepted by
City Council for maintenance. For
Updated when mylars are delivered to PWGIS.
ACCEPTDATE
private infrastructure use date that
Left <NULL> when feature is created.
mylars are delivered to PWGIS.
Indicates whether the feature is inside
ADMINAREA
City Limits layer. County assets are not mapped.
or outside the city limits.
Unique ID for feature found on the as-
ASBUILTID
Plan -Profile sheet. See Figure 1.
built.
BOXDIM
Dimensions of the below -ground box.
Field work only. Otherwise <NULL> .
Not typically used. Comments should be
Text field to store notes about unusual
COMMENT
preceded by date and last name of editor
attributes or qualities.
(20190226-doig: note).
CONDITIONDAT
Date condition score was determined.
E
Part of asset management.
Leave <NULL> .
CONDITIONSCO
Condition score for individual feature.
RE
Part of asset management.
Leave <NULL> .
Date that the feature was created in
CREATEDATE
Automated (Attribute Assistant).
the GIS.
Username for editor who created the
CREATEDBY
Automated (Attribute Assistant).
feature.
Z (RIM) - Invert Elevation (INV OUT). If either
Difference between the z/elevation of
DEPTH
value is not available leave <NULL>. For end
the top of the structure and the invert.
sections and headwalls value can be 0 .
EDITDATE
Date that the feature was last edited.
Automated (Attribute Assistant).
Username for editor who last edited
EDITEDBY
Automated (Attribute Assistant).
the feature.
Indicates whether the feature
ENABLED
participates in the geometric network
True.
FACILITYID
Unique feature id used by Cityworks
Automated (Attribute Assistant).
Refer Appendix B for valid FORMS — these are
FORM
Shape of the structure or pipe.
dependent upon feature the feature TYPE.
Needed for replicated feature classes.
Globalid
Automated (SIDE).
Assigned by Database
Dimensions of the top of the structure
INLETDIM
Fieldwork only. Otherwise left <NULL> .
where the stormwater enters
The date should be pulled from the "DATEBUILT"
An estimate of when the structure was
field in the project tracking layer. This date is
INSTALLDATE
built.
derived from the date of the first as -built review
in the as -built database.
'INV OUT' on as -built Plan -Profile sheets. See
Figures 1 and 2 below. Can never be 0 . For end
Elevation of the bottom of the
INVERT
sections and headwalls value the INVERT may
structure.
match the Z if the structure was shot at the
bottom.
32

Previous FACILITYID. Allows users to
LEGACYID
find work orders and other records that
Left <NULL> when feature created.
are associated with feature
LOCATION
Nearest address
Site Address in Address Point or Parcel
layer .
Most new structures are made of precast
Type of material that the structure or
MATERIAL
concrete, but refer to the as -built construction
pipe is made from.
drawing details to confirm they are not brick.
OBJECTID
Unique id assigned by database
Automated (SDE)
OPERATIONALA
Indicates which watershed the feature
Name in sw5tormSewershed layer
REA
is in.
Structures in the right-of-way (ROW) will have
the same ownership as the road in the ROW,
Entity that is responsible for
OWNER
structures in a parcel will have an ownership of
maintaining the structure
PRIVATE, STATE, CITY, COUNTY, or FEDERAL,
depending on who owns the parcel.
UNC Path to the photo of the
Only structures added as part of the original
PHOTOPATH
infrastructure
inventory have photos.
Only structures added as part of the original
PHOTOURL
URL to the photo of the infrastructure
inventory have photos.
Proj ectID in Project polygon. Existing
Unique ID associated with the project
PROJECTID
features that are drawn in based on information
in the project polygon layer.
from a new as -built get a PROJECTID of 0000.00.
Risk of failure score for individual
RISKSCORE
feature. Part of asset management
Leave <NULL>.
Indicates the shape type by feature
SHAPE
Automated (SDE)
class.
Source used (digital submittal, as -built, field visit,
SOURCE
Primary source for the attributes.
construction drawing, etc.).
Not typically used. Comments should be
SOURCECOMMEN
Text field to store notes about unusual
preceded by date and last name of editor
T
attributes or qualities.
(20190226-doig: note).
If X,Y, and Z data provided, field should
Completed only if field -verified XYZ data
SOURCEXYZ
indicate source for these data.
available.
If X,Y, and Z data are collected by
SRCXYZDATE
PWGIS or another group, field indicates
Date that XYZ data collected.
collection date.
Indicates whether the feature is
STATUS
Editor sets value to Active.
currently in use.
Refer to values in Appendix B. TASK values are
The primary task of the TYPE of
TASK
dependent upon the TYPE and context of the
structure.
structure.
The dimensions of a curb or catch basin
THROATDIM
Field work only. Otherwise <NULL>.
opening.
Valid only for structures with throat openings
Distance from the GPS shot to the
THROATROD
such as COMBINATION INLETS, CURB INLETS, and
lowest elevation of the throat opening.
SLAB INLETS. Otherwise <NULL>.
Absolute elevation at the base of the
Calculate as Z—THROATROD and valid only for
THROATZ
throat of the structure.
certain types of structures. Otherwise <NULL> .
33

Specific structure or pipe within the
TYPE
larger feature class. Based on a domain
Refer to Feature Types above for valid types and
for the feature class.
Example Photos for visual identification.
The easting (X-coordinate) of the
Only completed if XY is provided from digital or
X
structure.
GPS data.
The northing (Y-coordinate) of the
Only completed if XY is provided from digital or
Y
structure.
GPS data.
AKA 'RIM' on Plan -Profile sheets. See Figures 1
Z
Elevation of the top of the structure.
and 2 below. Can never be 0 . For end sections
and headwalls value the INVERT may match the
Z if the structure was shot at the bottom .
More specific attribute information regarding appropriate FORM and TYPE values can be found in
%DDendix B: Valid Structure FORM and TASK Attributes.
Utility Importer Attribution
Stormwater Nodes
'ASBUILTID' Provided in DATA file
'TYPE' Provided in DATA file
'Z' Provided in DATA file
'INVERT' Provided in DATA file
'MATERIAL' Provided in DATA file
'PROJECTID' Selected in Importer, from 'PROJECT —ID' field
'INSTALLDATE' Set to 'INSTALLDATE' from provided ProjectlD
'SOURCE' Set to 'Digital Submittal'
'ENABLED' Set to 'True'
'TASK' Set to 'Inlet' for Combo, Curb, and Drop inlets.
Set to 'Junction' for Junction Box, and Manholes
Set to 'BMP' for Riser Pipe
Set to <NULL> otherwise
34

'DEPTH' Derived from 7 minus 'INVERT'
'X' 'Easting' value provided in DATA file
'Y' 'Northing' value provided in DATA file
'SHAPE@XY' Calculated from 'X' and 'Y' values provided in DATA file
Stormwater Pipes ("swPipes")
Stormwater pipes connect two stormwater structures. New pipes are typically of reinforced concrete,
although some may be HDPE or ductile iron. Pipe diameters vary greatly. Pipes at the top of a system
may be as small as 4-12" (like those that connect roof drains). As the drainage area increases, so do pipe
diameters and pipes of 15-36" are not uncommon. Only pipes 12" or greater in diameter must be
depicted in the GIS.
Feature Types
Pipes that are part of the stream network. That is, they transport
water in defined stream channels. Flow through these pipes is not
dependent on rain events. Culverts are typically found under roads
CULVERT
or other human -made structures. A culvert may consist of a single
pipe (or box, not all culverts are circular). Culvert diameters can be
quite large. The upstream and downstream nodes associated with a
culvert are almost always headwalls or end sections.
Driveway pipes are stormwater pipes that are located under
driveways. These pipes daylight on both ends. Unlike other types of
DRIVEWAY
pipes, driveway pipes begin and end with a swVirtualJunction
feature.
Pipes that are less than 12" in diameter; these are associated with
roof drains or SCMs. Trench drains should be captured as minor
pipes, if they are represented at all. These smaller pipes will only be
MINOR
represented in the GIS if there is a special request for their inclusion.
Existing minor pipes will not be removed at this time. Minor pipe
material is often PVC.
35

This type is used to represent underground storage Stormwater
Control Measures (SCMs) that consist of actual pipes, not large open
STORAGE
chambers. These pipes are used primarily to temporarily store
runoff from a site, rather than immediately conveying it
downstream.
STORMWATER
Most pipes in our stormwater utility network are classified with the
type STORMWATER. These pipes only carry water after a rain event.
Pipes about which there are uncertainties. 'STUB' should be used
when a pipe is known to exist, but its origin or terminal structure is
STUB
unknown. Pipe materials and diameters vary for stubs since they
really just serve to flag stormwater pipes that are missing attribution
and connectivity.
Feature Attributes
Date that infrastructure is accepted by
ACCEPTDATE City Council for maintenance. For
private infrastructure use date that
mylars are delivered to PWGIS.
ADMINAREA Indicates whether the feature is inside
or outside the city limits.
ASBUILTID Unique ID for feature found on the as -
built.
COMMENT
CONDITIONDATE
CONDITIONSCORE
CREATEDATE
Updated when mylars are delivered to
PWGIS. Left <NULL> when feature is
created.
City Limits layer. County assets are not
mapped.
Plan -Profile sheet. See Figure 3 below.
Text field to store notes about unusual Not typically used. Comments should be
attributes or qualities. preceded by date and last name of editor
(20190226-doig: note).
Date condition score was determined.
Part of asset management.
Condition score for individual feature.
Part of asset management.
Date that the feature was created in
the GIS.
Leave <NULL> .
Leave <NULL> .
Automated (Attribute Assistant)
W

Field Name
I .. I 2W
Username for editor who created
7
CREATEDBY
Automated (Attribute Assistant)
the feature.
DIAMETER
The diameter of a circular pipe.
Digital submittal, as -built, or field visit
Difference between the Z/elevation of Z (RIM) - Invert Elevation (INV IN). If either
DSDEPTH
the top of the structure and the pipe value is not available leave <NULL>. For
invert. end sections and headwalls value can be 0 .
Elevation at which pipe enters 'INV IN' on as -built Plan -Profile sheets. See
DSINVERT
downstream structure. Figure 3 below. Can never be 0 .
FACILITYID for the downstream
DSNODE
Automated (Python script)
swNodes structure.
Date that the feature was last
EDITDATE
Automated (Attribute Assistant)
edited.
Username for editor who last edited
EDITEDBY
Automated (Attribute Assistant)
the feature.
Indicates whether the feature
ENABLED
True
participates in the geometric network
FACILITYID
Unique feature id used by Cityworks
Automated (Python script)
FORM
Shape of the structure or pipe.
CIRCULAR unless noted on the as-builts.
Globalid Needed for replicated feature classes. Automated (SDE)
Assigned by Database
For non -circular pipes, the height of
HEIGHT the pipe in feet to the nearest tenth Typically based on a field visit
of a foot.
The date should be pulled from the
"DATEBUILT" field in the project tracking
INSTALLDATE An estimate of when the pipe was built. layer. This date is derived from the date of
the first as -built review in the as -built
database.
Previous FACILITYID. Allows users to Left <NULL> when feature created. If pipe
LEGACYID find work orders and other records that is split later then the FACILITYID of one
are associated with feature portion of the pipe is moved to the
LEGACYID field.
Nearest address to the centroid of the Site Address in Address Point or
LOCATION
pipe. Parcel layer
Type of material that the structure or Most new pipes are reinforced concrete
MATERIAL
pipe is made from. unless noted on the as -built.
OBJECTID
Unique id assigned by database.
Automated (SDE).
Indicates which watershed the feature
OPERATIONALAREA
Name in sw5torm5ewershed layer
is in.
Pipes share the ownership of their
Entity that is responsible for
upstream and downstream structures. If the
OWNER
maintaining the structure
ownership of the structures do not match
the pipe is coded as SHARED.
PROJECTID in Project polygon. Existing
Unique ID associated with the project in features that are drawn in based on
PROJECTID
the project polygon layer. information from a new as -built get a
PROJECTID of 0000.00.
37

Field Name
The slope of the pipe as expressed
PSLOPE
as a percentage to the nearest
hundredth.
Risk of failure score for individual
RISKSCORE
feature. Part of asset management
Indicates the shape type by feature
SHAPE
class.
Indicates shape length for lines and
SHAPE . stlength ()
polygons only. Calculated by
Database
Primary source for the attributes.
SOURCE
SOURCECOMMENT Text field to store notes about unusual
attributes or qualities.
STATUS Indicates whether the feature is
currently in use
Specific structure or pipe within the
TYPE larger feature class. Based on a domain
for the feature class.
ISource
Plan -Profile sheet. See Figure 3 below.
Leave <NULL> .
Automated (SDE)
Automated (SDE)
Source used (digital submittal, as -built, field
visit, construction drawing, etc.).
Not typically used. Comments should be
preceded by date and last name of editor
(20190226-doie: note)
Editor sets value to Active.
Refer to Feature Types table above.
Z (RIM) - Invert Elevation (INV OUT). If
USDEPTH
Difference between the z/elevation of
either value is not available leave <NULL>.
the top of the structure and the invert.
For end sections and headwalls value can be
Elevation of the bottom of the
0.
'INV OUT' on as -built Plan -Profile sheets.
USINVERT
structure.
FacilitylD for the upstream structure
See Figures 3 below. Can never be 0 .
Automated (Python script).
USNODE
VIDEOURL
URL for the video of the pipe.
Not typically completed. Leave <NULL>.
For non -circular pipes, the width of
WIDTH
the pipe in feet to the nearest tenth
Field work only. Otherwise <NULL> .
of a foot.
Utility Importer Attribution
Stormwater Pipes
Shape@ Upstream point set to'Shape@XY'value of
upstream 'ASBUILTID'from provided Manhole data.
Downstream point set to 'Shape@XY' value of
downstream'ASBUILTID'from provided Manhole
data.

ASBUILTID
Provided in DATA file
DIAMETER
Provided in DATA file
MATERIAL Provided in DATA file
USNODE Provided in DATA file
DSNODE Provided in DATA file
INVERTUS Provided in DATA file
INVERTDS Provided in DATA file
PROJECTID Selected in Importer, from 'PROJECT —ID' field
E Set to 'INSTALLDATE'from provided ProjectlD
Set to 'Digital Submittal'
iiii
ENABLED Set to 'True'
TYPE
Provided in DATA file
PSLOPE Calculated:
(Upstreaminvert—Downstreaminvert) * 100
RecordedLength
DEPTHDS Calculated:
Upstream Node Z— Upstream Node Invert
OEM
DEPTHDS Calculated:
Downstream Node Z — Downstream Node Invert
39

Splitting Pipes
In the majority of cases new stormwater infrastructure is connected to the existing system via some sort
of junction, typically a stormwater manhole or junction box. On the GIS side this is represented by
splitting and existing pipe, creating a new junction, and connecting the new pipe to this arrangement
(i.e. a three "swPipe" features with the a single "swNode" feature at the junction).
However, given the variety of pipe sizes and shapes in the stormwater system this scenario may not be
true in all cases. A typical situation is when a much smaller diameter pipe (such as a 15") connects to a
much larger pipe such as a box culvert. In many cases these "tap -in" type connections do not call for the
creation of a junction structure. In these cases the representative pipe feature can be directly
connected to the large pipe without splitting the existing feature.
SPLIT PIPE VIA JUNCTION CONNECTION
STEP
Procedure
Determine the point at which the existing "swPipe" feature will be split. This
1
will usually be the location of the "swNode" junction feature that serves to
form to the junction between the existing and new system.
2
Split the existing "swPipe" feature via the "Split" tool.
The splitting of the pipe will require the assignment of a new FACILITYID to one
of the new pipe segments. Copy the existing FACILITYID to the LEGACYID field
3
and assign the new pipe feature a new FACILITYID.
NOTE: This is handled automatically if the Attribute Assistant is active.
Connect all "swPipe" features in the intersection to the "swNode" feature that
4
serves as the junction.
TAP -IN CONNECTION PROCEDURE
STEP
Procedure
Find the approximate location where the smaller diameter pipe intersects the
1
larger diameter pipe.
40

Connect the smaller diameter pipe to the larger diameter pipe by snapping to
2
the larger diameter pipe feature. DO NOT split the larger diameter pipe as this
is not necessary.
Create a new "PIPE JUNCTION" feature at the intersection. This will
3
automatically replace the orphan junction at that location.
Curved Pipes
Curved pipe reaches are rare but they are present in the system. There should not be any curved
segments in new construction but they may be encountered in some older parts of the system. Typically
these "curved" pipes are formed during construction by slightly deflecting straight sections of pipe
gently around a large radius curve.
Curved pipe reaches should be represented by a single "swPipe" feature. The curve should be formed
by adding vertex elements to form the shape of the curve. Do not represent curved pipes as "true"
curves (i.e. do not use any of the "curve" or "arc" tools available on the editor toolbar in ArcMap), but
rather define the run of the curved pipe with multiple vertices.
Stormwater Channels
7
Pipes that are part of the stream network. That is, they transport
water in defined stream channels. Flow through these pipes is not
dependent on rain events. Culverts are typically found under roads
DITCH
or other human -made structures. A culvert may consist of a single
pipe (or box, not all culverts are circular). Culvert diameters can be
quite large. The upstream and downstream nodes associated with a
culvert are almost always headwalls or end sections.
FLUME
41

Driveway pipes are stormwater pipes that are located under
driveways. These pipes daylight on both ends. Unlike other types of
RIVER
pipes, driveway pipes begin and end with a swVirtuaUunction
feature.
Pipes that are less than 12" in diameter; these are associated with
roof drains or SCMs. Trench drains should be captured as minor
pipes, if they are represented at all. These smaller pipes will only be
STREAM
represented in the GIS if there is o special request for their inclusion.
Existing minor pipes will not be removed at this time. Minor pipe
material is often PVC.
Field Name
I
Source
Not typically used. Comments should
Text field to store notes about
COMMENT
be preceded by date and last name of
unusual attributes or qualities.
editor (20190226-doig: note).
Date that the feature was created in
CREATEDATE
Automated (Attribute Assistant)
the GIS.
Username for editor who created
CREATEDBY
Automated (Attribute Assistant)
the feature.
Date that the feature was last
EDITDATE
Automated
tomated (Attribute Assistant).
edited.
Username for editor who last edited
EDITEDBY
Automated (Attribute Assistant).
the feature.
Indicates whether the feature
ENABLED
participates in the geometric
True.
network
Unique feature id used by CityWorks
FACILITYID
Needed for replicated feature
Automated (Python script).
Globalid
Automated (SIDE).
classes. Assigned by Database.
Previous FACILITYID. Allows users to
Left <NULL> when feature created. If pipe
LEGACYID
find work orders and other records
is split later then the FACILITYID of one
portion of the pipe is moved to the
that are associated with feature
Nearest address to the centroid of
LEGACYID field.
site Address in Address Point or
LOCATION
the pipe.
Parcel layer
OBJECTID
Unique id assigned by database.
Automated (SDE).
Indicates which watershed the
OPERATIONALAREA
feature is in.
Name in swStormSewershed layer
42

Field Name
SHAPE.STLength()
TYPE
Indicates 1
class.
Indicates snape iengin Tor lines ana
polygons only. Calculated by
Database
Specific structure or pipe within the
larger feature class. Based on a
domain for the feature class.
WTRNM
WTRNMID
SCM (Stormwater Control Measures)
Automated (SIDE).
Refer to Feature Types table above.
Mapping Infrastructure Associated with Stormwater Control Measures (SCMs)
Almost all SCMs can be represented in some form, with the exception of "Low Impact Development"
and "Permeable Pavement". For those devices/practices there is nothing to be mapped into the GIS.
The intent is to indicate that stormwater flows through some structures that form elements of the SCM
device. At best this is a rough schematic of the device with the understanding that if someone needs full
details of the device they can consult the as -built drawings available from the links provided by the
"swSCMs" points.
SCM-related infrastructure should be mapped when the project is mapped. SCMs have as -built
requirements that are separate from our typical as -built review process and it is not uncommon that as -
built information will not be available at the time of the mapping of the project utilities.
The typical workflow should proceed as follows:
SCM Mapping Workflow
1'
Review the as -built to identify if there are any SCMs associated with the project. Use the
swSCMs layer as a secondary source to locate SCMs related to the project.
Gather and review SCM-related documentation. The SCM information can be located in the
2'
construction drawing or the SCM as -built. Typically, the as -built will not be available when
you are mapping the project. If it is available, a link to the SCM can be found on the swSCM
point feature.
3.
Map and attribute the SCM closed system and open system infrastructure according to the
guidelines in the following sections.
43

4.
If necessary, move the SCM point location stored in the SCMDB database to the center of
the SCM. Guidelines for Changing the Location of SCM Points can be found in Table 10
below.
Above Ground Structures
These SCMs include "Dry Pond", "Wet Pond", and other pond -like structures such as "Bioretention
Areas", "Constructed Wetlands", "Pocket Wetlands", and "Sand Filters".
Typical stormwater system components include the pipes and structures that terminate at the SCM
(usually provided on the project as -built), a riser or some other sort of device to control water flow out
of the SCM, and an outlet pipe that daylights the stormwater at an end section or head wall.
Many of these SCMs now also have an associated level spreader at the outlet pipe along with an
associated WEIR BOX that diverts stormwater to the level spreader.
Mapping Features Associated with Above Ground SCMs (see related figures below)
a). Add the RISER feature to the "swNodes" layer.
b). If present, also add the WEIR BOX that forms the bypass to a nearby level spreader
to "swNodes" layer.
c). Add headwall/end section where the stormwater from the device exits the closed
system.
1.
d). Add the pipes as necessary to the "swPipes" layer. Connect the pipe from the
RISER to the either outlet headwall/end section OR to the WEIR BOX. If the WEIR BOX
is present also add a pipe from the box to the outlet feature that directs stormwater
to the level spreader.
If there is an internal underdrain system within the device (such as within SAND
FILTERS, etc.), DO NOT map these features.
Add a feature to the swVirtualEdge layer connecting the outlet structure that enters
2'
the SCM to the RISER structure that allows stormwater to exit the device. Use straight
lines with limited vertices to connect the inlet pipes to the outlet pipe, taking into
account the design of the pond as can be seen in the imagery.
3.
44

Determine if you need to add another feature to the swVirtualEdge layer to connect
the outlet structure to the nearest open system feature. Refer to the section
Guidelines for Digitizing Flowlines.
Attribute the structures and pipes. Use as -built data if available. If not, use the
4.
imagery to estimate the location and form of the structures and use the construction
drawings to attribute pipe diameter and material.
If necessary, reposition the SCM point(s) to the correct location of the device. Please
5.
review how to move an SCM point by reviewing the swSCM Point section below the
Enclosure section in Table 10.
F qb'
:_x�•i'Y`.. �:. '9r Y'4`Q'!ad 1! �'.1f..'11'in R"�: FY y�. .4 �.
h'
.�4r9
;y Brier. Creek
S {
> - S
SEE INSET BELOW
,
77
N M�
3
Del Webb Carolina Arbors Phase 1B (1124.06) WP #8
45

1a
. _ r
1b
2
El
46
a. a
Del Webb Carolina Arbors Phase 1B WP #8 (INSET)
46

Underground Structures (swEnclosures)
The swEnclosure types include "Underground Sand Filter" - , "Underground Storage Chamber"
7, "Underground Storage Pipes"7, "Underground StormFilter Chamber" 0, and "Underground
Silva Cell- ."
Mapping Features Associated with Underground Structures
For large underground storage chambers, sand filters, and extensive systems
of underground pipe arrays, digitize a new polygon in the "swEnclosure"
feature class using the as -built to approximate the outer boundary of the
structure. Do this by either looking at the length and width that the as -built
provides, or measure the enclosure in the pdf provided. The corners of the
structure should meet at right angles.
2 Add the necessary inlet and outlet pipes that extend to the edge of the
device. Approximate the location of the entry/exit points and snap the ends
of the new pipe features to the edge of the "swEnclosure" polygon.
3 Add PIPE JUNCTION features at the entry/exit points of the structures where
the pipes connect to the Enclosure you have mapped. This will eliminate any
junction errors that you will have.
Add surface structures (Hatch/Manhole/Drop Inlet), using Construction
4 Drawing, As -built, and imagery, into the underground chamber by digitizing
the appropriate features in the "swNodes" layer. These features will not be
connected to the stormwater network but should be added as they are
features that are visible at the surface.
NOTE: Within the enclosure, you are only to map features that are visible
from the surface, such as Manholes, Hatches, or Drop inlets. Features inside
the enclosure such as weir boxes are to not be mapped.
5 Attribute the structures and pipes. Use as -built data if available. If not, use
the imagery to estimate the location and form of the structures and use the
construction drawings to attribute pipe diameter and material.
6
47

Add a FLOWLINE feature to the swVirtualEdge layer that represents the flow
of stormwater thru the structure, which will keep the geometric network
intact as well as flow direction.
NOTE: The virtual edge will go from the inlet of the enclosure to the outlet. If
there are more than one inlet, pick the farthest one away from outlet. The
additional inlets will then need to be connected to the initial virtual edge using
virtual edges and virtual junctions. Avoid drawing virtual edges and virtual
junctions on visible structures you've drawn in. For further guidance, review
Figure 4: SCM #13464 below. This is also a good example for if there are two
outlets in the enclosure.
If necessary, re -position the SCM points from the SCMDB database to the
center of "swEnclosures" polygon that represents device. Please review how
to move an SCM point by reviewing the swSCM Point section below this
7 section in Table 10.
Do not map any internal underdrain pipe system within the device (such as
Note within SAND FILTERS, etc). This is distinct from an underground storage
system that consists of large diameter pipes. Those kind of systems are
discussed below.
General swEnclosures Attribution
Field Name Description
Date that infrastructure is
accepted by City Council for
ACCEPTDATE maintenance. For private
infrastructure use date that
mylars are delivered to PWGIS.
Indicates whether the feature is
ADMINAREA inside or outside the city limits.
Area (sq. ft.) The size of the enclosure
underground.
Text field to store notes about
COMMENT unusual attributes or qualities.
Updated when mylars are delivered to PWGIS. Left
<NULL> when feature is created.
Automated (Attribute Assistant)
City Limits layer. County assets are not mapped.
Automatically calculated when you draw the
polygon.
Not typically used. Comments should be preceded
by date and last name of editor (20190226-doig:
note)
M.

Date that the feature was created
Automated (Attribute Assistant)
CREATEDATE
in the GIS.
Username for editor who created
Automated (Attribute Assistant)
CREATEDBY
the feature.
Date that the feature was last
Automated (Attribute Assistant)
EDITDATE
edited.
Username for editor who last
Automated (Attribute Assistant)
EDITEDBY
edited the feature.
Unique feature id used by
Use the SCM Number from the SCM Point and use
Cityworks
that number as the Facility ID for the enclosure you
are mapping.
FACILITYID
NOTE: If there are multiple enclosures with the same
SCM Number, please reach out to Cory to determine
how to handle attribution.
Needed for replicated feature
Automated (SIDE)
Globalid
classes. Assigned by Database
An estimate of when the
Date of the first as -built review in the as -built
INSTALLDATE
structure was built.
database.
Previous FACILITYID. Allows users
Left <NULL> when feature created.
to find work orders and other
LEGACYID
records that are associated with
feature
LOCATION
Nearest address
Automated (Attribute Assistant)
OBJECTID
Unique id assigned by database
Automated (SDE)
Unique ID associated with the
Proj ectlD in Project polygon. Existing features
PROJECTID
project in the project polygon
that are drawn in based on information from a new
layer.
as -built get a ProjectlD of 0000.00.
Risk of failure score for individual
Leave <NULL> .
RISKSCORE
feature. Part of asset
management
Indicates the shape type by
Automated (SIDE)
SHAPE
feature class.
49

Specific SCM that is given in the Refer to the SCMDB to confirm using the SCMID or
TYPE SCMDB or on the as -built/ project name.
construction drawing.
Indicates which watershed the Automated (Attribute Assistant)
Watershed feature is in.
Basin name in swStormSewerSheds layer.
swEnclosure Examples
Underground Sand Filter
Typical As -built:
5FMH-4
RIM= 313.66' �-
INV.302.03' SEE SHEET C-5.0 INV. gp.tii•1-yrM
FOR SAND FILTER, INV 30203• Ba 35gE1�-F
STRUCTURE
UNDER DRAfN PLAN 3p
AND SECTIONS 1NV.302.21'
S�
INV. 302.21'
A$ -BUILT
UNDERORAINRAIN� ,••pp�� - Y-
V�DEP�'- 1.
t�aet- . .
91� _ ,-' INV.302.51'
CO TOP QR� ��O SFMH-1 SD-4
304-26' �N RIM = 312.83" 15" RCP
a.B LF @ 4
`per o�•__ EUQi4 INV, 304.g3'
6" OQ
'.302.64' PQSEgI� �
�O
INV.302.T5' 00 TOP�'_ 6
304-14' FLOW SPUTTER
SF1AH-8 SO RIM 31 r-Do' (SEE DETAIL 01
-
THIS SHEET)
30 .10' FLOW SPLITTM=313.ER
304,10' nn g4 MH RIM=313.31'
sru+li a
,RIM - 316.49• GI RIMS=312.31'
WEIR�".Or
INV OUT (N)=W5.14'
YNV.302-ao , INV IN ^405.14'
INV IN [E]=305.03'
40,
1 SPO -
Figure 1: SCM #13445 1 Chick-Fil-A Westgate and 15-501 Underground Sand Filter as -built.
50

Mapping Depiction - Underground Sand Filter:
N5
1
Figure 2: SCM #13445 1 Chick-Fil-A Westgate and 15-501 Underground Sand Filter depicted in GIS.
51

Underground Storage Chamber
Typical As -built:
LF 1$'e 4-PINIR
HOPE �- J(I
r �1
OETEIIIL#41 r,O INUT � ls'NI {T � �
LF L9'P 4-R,NC HOP t
4a.44Y.
1 409.95 ' J
4-09,37
`Tj� Ana J
OET�
. O S 12"0 I
� t 12'A Fl7 �
STMMFlLTER
' UETENTM" SYSTEM n
p I iei� mrr 0y
� � + MV+46398i
� LF 12'0 O-RNG RCJK
409,42 111 LfH4PE 004pX �, j 4109f' 4i
1 J ,NNOTO Box
y4 I 12"4 IM Fx U. .to
24'0 W ELEV.-402.14) +a
O r 00 a".-1104 go t.
LF r2`e 6-RWROP
�x .
13 LF 24'4 4-F&C W11
i SI9S /
Figure 3: SCM #13464 1 Zaxby's S Miami Underground Detention as -built.
52

Mapping Depiction - Underground Storage Chamber:
I
Figure 4: SCM #13464 1 Zaxby's S Miami Underground Detention depiction in GIS.
53

Underground Storage Pipes
Typical As -built:
- ,, ---~
=.
s,
ACCESS LID
4;r DUAL WALL FABIRICATED
►M�
'WATER
L-
MANIFOLD
NIM"
fI
A
.�
1
OUT�L 7• =
INV IN 86&20 (360.14 -15" CPP) PIPE B7
,PRE T INLET STRUCTURE
3' B1L ACCESS HATCH
�` IG6Ef, ING PIPE D3
r �l
ST- itl
13.851
(3 UENt 1`ti;IiS .
. � \ �� 1`, 111 ls`
Il l 14J
\ Si=132 O Er TROL
O� STRUM {$DETAIL)
8" UNLIERD ROM FILTER
NV IN {Sr-0 35�]7s l
42-0 HDPE545 li it
(8 LENGTft
1,1 tsl
l
1
�1
l 1,11
TFALL 8'
I PEC1)
1
I PRECAST IINNL CTlll ,l'I
3' BILCO(D TCH
% l
lsst'il
Ill
l',I
Figure 5: SCM #00781 1 Voyager Academy Elementary School Underground Detention as -built.
54

Mapping Depiction - Underground Storage Pipes:
N
Figure 6: SCM #00781 1 Voyager Academy Elementary School Underground Detention depiction in GIS.
55

Underground StormFilter Chamber
As -built:
Figure 7: SCM #00690 1 Walmart #4369 Stormwater Filter — Proprietary Device as -built.
56

Mapping Depiction - Underground StormFilter Chamber:
Figure 8: SCM #00690 1 Walmart #4369 Stormwater Filter — Proprietary Device depicted in GIS.
57

Underground Silva Cell
Typical As -built:
E5
ti�z �_ II II
y _ MAST ARM I
MONAL POLE II STORMWATER II
5LF 12" PVC SCH SPUTTER BOx SEC
( , 9fi ROOF. DRAIN II STORMWATER S' PVC ` INV: 401.59 II DETAILS 1110� ROOF DRAINH
` PARKING ❑ 0 II LK VENT INV: 40+'W 40 9
:- OE
® o II o DECK VENT 10
PROPCSEO FINISHED"
GRADE: 4n6S6 " I� I
ZON PRUVI)6 +2 43 I
CELLSTRI E Slf0.0 SILVA --
S. SE DE AI F
I
/
EXISTING ELECTRIC
AND CABLE TV LINES
/ TO BE ROOTED
/ THROUGH SILVA CELLS
_E _T♦�
11�11
TF_--�
Figure 9: SCM #13325 1 City Center Silva Cell #1 as -built.
Mapping Depiction - Underground Silva Cell:
PIN: 0521-12-97-2257
PD.
102773
YNCT LLC
116 W MAIN ST
DB 2996 PG 453
DOWNTOWN TIER
DESIGN DISTRICT CORE (OD-C)
PROPOSED FINISHED
GRADE: 40455'
P:��JUNCTION
BOX
RIM: 404.70
INV IN: 901.50 (4"PVC)
INV. IN: 90F.3 401.50
INV OUT: 401-3 40145
�N` INN ­T.Tl— — --
N�
TIE TO EXISTING CURB
0 40439 1 AND GUTTER (TYP.)
OUT 401, 16I I
T _-
18" MINIMUM 0ryI��
Figure 9: SCM #13325 1 City Center Silva Cell #1 depicted in GIS.
58

Multiple SCMs in same Enclosure
Typical As -built:
~. v�
U wu.w
TOP ~A
,OP-4
nu^NHO=vPENwG
wE^NI> ODVER nrl
Figure ulS[IVI #00840-008411 Family Dollar Guess Road as -built.
59

Mapping Depiction — Sand Filter and Storage Chamber:
Figure 11: SCM #00840-00841 1 Family Dollar Guess Road depicted in GIS.
Filterras, Silva Cells, StormFilters, and Rain Harvest Systems
Table 9. SCM Mapping — Other SCM Devices
1). Add a new point to the "swNodes" layer and code it as TYPE of FILTERRA. Set the
TASK to "BMP"
FILTERRA
2). Add the connecting drain line to the "swPipes" feature class to the nearby catch
basin.
Silva Cell
Treat these features as an underground chamber storage system.
StormFilter
Treat these features as an underground chamber storage system.
.e

Rain Harvest Bookmarked for future update
System
swSCM Points
Table 10. SCM Mapping - Changing The Location of SCM Points
Make sure the "SCMDB (LIVE)" layer is loaded in your edit session. This layer is a Query
Layer that points directly to the SCMDB database.
1.
The "Stormwater Control Measures" layer (which points to the feature class called
"swSCMs") cannot be edited directly — the features within the "swSCMs" feature class are
overwritten nightly from the SCMDB database.
Open the SCM database. The startup file can be found here:
2.
F:\GIS\PUBLIC\SCMDB\BIN
In the SCMDB database, navigate to the SCM that will need to be moved.
To do this, you will then need to open the SCM tab J '` , click the Find SCM...
3•
button Find SCM ... at the top right, and then search the SCM project associated
with the project you are mapping via its SCM Number or SCM Name. The Number or
Name can be found by Identifying the SCM Point in ArcMap.
Once you find the project, click the Edit... button Edit... at the top right, and
then Map... button Map... in the SCM Physical (EDIT) window
that pops up. The PWGIS WebMap will come up and you will need to find the area
where the SCM is located. This will entail using the Search in the web map to find the
SCM Number of the SCM point.
4.
Once you find the location of the point, find where the SCM actually is located on the
parcel using the WebMap imagery. Once you do you will use the Q button by
clicking the button to activate it, which is the last button on the side panel, and then
click where the SCM actually is located in the map. You will see a white circle pop up
showing you where the point will be moved to.
5.
Lastly, you will click save on the map and then save on the SCM Physical (EDIT)
window. This will move the SCM point to the correct location.
61

NOTE: Use the SCMDB (LIVE) layer in your MXD to see your change to confirm it
worked. You will need to go to the View tab in your MXD located at the top left, and
then click Refresh. Once refreshed, you should see the SCM point move to the
location you picked.
62

Appendix
63

Appendix A: Classification of Stormwater Structures
Stormwater Structure Examples (Photos)
swNode TYPE
Example
COMBINATION INLET
A
CURB INLET
�.. _.�.
DROP INLET
j 4jr +..
SLAB INLET
YF -
l
64

swNode TYPE
Example
JUNCTION BOX
MANHOLE
+k
RISER PIPE
I
WIER BOX
(Internal Structure
Shown)
;,r.
M

End Section Examples
End Section FORM
Image
SOCKET.�
>aNil
� � � � �■■■■
BELL
V A%At
� �L�
CUT
r
FLARED
1.1.0

67

Appendix B: Valid Structure FORM and TASK Attributes
COMBINATION
INLET
CURB INLET INLET
DROP INLET
SLAB INLET
MANHOLE JUNCTION
JUNCTION BOX or
PIPE JUNCTION ACCESS
END SECTION INLET
HEADWALL or
OUTLET
WIER BOX
RISER BMP
FIL-TERRA
HATCH ACCESS
BELL
END SECTION CUT
SOCKET
FLARED
MITERED
VERTICAL
HEADWALL WING WALL
L-WALL
.:

Appendix C: Reserved FACILITYID Ranges
swNodes
swPipes
99

Appendix D: Geometric Network Parameters
Parameter
Value
Feature Dataset
StormWater
Geometric Network
StormWaterGN
Name
swChannels (Complex Edge)
swNodes
Feature Classes
swPipes (Complex Edge)
swVirtualEdge (Complex Edge)
swVirtualJunction
Snap Tolerance
Use the default tolerance value
Weights
Do no enter any weights
Z Snap Tolerance
Do not enter any Z snap tolerance
Preserve Enabled
YES
Values
70

Appendix E: Georeferencing the As -built [REMOVE]
1. Go through the as -built to identify sheets that show detailed infrastructure for the project. For
a small project the utility overview page may be sufficient.
331
--_,___� _i_�=== / E,X',�ATIINGC 341
345
`
x -IOB /•'II:I Ili l07 '•�...� •' 4 -
........;r" •'': 112 ll] ll6 (11_ .. I•
114 ]OE`'' •� 334
113 1d1 l litl l06 1M 1{14 E�1$T1dG.. .
L.'� PHa 5
336
y a
fi 116 11l7 ]18 119 120 12] l7= ]23x
J IL I I I N N 339 , 337i4 �v
,
•. ..... ..... ... ' ------ ---- - --- -- -- -_ - ter., .
-
-.,__- 27- 5 92
_ 1 I
�\ - - ... •-.. 129 EXISTI�G 11gT —
t 1 E%I$'`NG 130 1 ' PHASE 1A4 "' r 93
PHASE 1A31� 17l
155
_ I ' I
6� �t
161
1s1 > y l 20—
r%' 162
_ l50 ♦ 1 mL__
204
203i old'��0' P� 164
ASHTON HALL- PHASE 2 AS -BUILT UTILITY PLAN
For larger projects, the project may be broken into sections. It may be necessary for some projects to
use the individual plan -profile sheets.
Plan/Profile Sheets: The plan and profile sheet is a tool used in the workflow of Civil Engineers to
communicate between the Engineer designing the project and the Builder constructing the project.
Designers produce "plans and specifications", which include drawings of how to build the project (plans)
together with written instructions, design criteria, and other guidelines (specifications). Conversely,
builders typically provide the designers with "asbuilt" drawings that show how the project was actually
built, since field conditions not anticipated by the engineer could result in alterations to the original
design by the construction crew. Both types of products may include plan and profile sheets, as shown
below, which combine a plan view of the project area with a profile view of the project features within
the extents of the plan view. These sheets are especially useful on linear project features, such as roads,
sewer mains and stormwater mains. The plan view is a map of the project area with background
imagery, annotations, and the linear project feature. (Ref:
https://www.mvn.usace.army.mil/portals/56/docs/engineering/Geospatial/JAMPtech_esri2010.pdf)
71

From; F To; F of 4
© Delete Pages After Extracting
❑n�/ Extract Pages As Separate Files
4. Save each extracted page as a ".TIFF" file:
Edit View Window Help
a Open,..
Ctrl+O
� F6 LE-lJ fl
`tl� r�
Create
r
® Save Ctrl+S
PDF.,, Shift+Ctrl+S
Reduced Size PDF...
(ai Share Files Using Send Now Online,..
Attach to Email..,
Certified PDF...
Reader Extended PDF r
Optimaed PDF..,
JPEG
°❑--. Action Wizard
Revert
Close
Ctrl+W
Microsoft Word �
Spreadsheet r
More Options r
JPEG2606
TIFF '+
PNG'/ � •"
Properties... Ctrl+D
Print.., Ctrl+P
1CA..,W—k,ide at Bethpage-Ph2A 4.pdf
2 F:\.,,\Cr hide at Bethpage-Ph2A,pdf
•
3 F:\DocumentA,,h' \, \54St t nPh,,e1B,pdf
4 F:\DocumentA,,h' \, \54St t nPh,,el pdf
j/////,- �'
O� �+D
5\\durham_pw\,,.\Lak .wood R. dental.pdf
%%%///j//
T
Exit Ctrl+Q
5. Open the utility editing mxd and navigate to the general location of the project.
a. Find a project location by selecting the project from the Attribute Table of the Projects
Layer. The project will have the same name as the title of the As -Built. Once found,
right -click the left margin of the record and select 'Zoom To'.
163 00< „
Flash 11
Q Zoom To
11
Pan To 12
OR 12
6. Load the georeferencing toolbar.
Georeferencing- sto�ter for Proia
LAYER SELECTION
ADD CONTROL POINTS
VIEWER
Selects the RASTER
Allows you to select
Opens a viewer window
layer that is to be
control points from a
that only displays the
georeferenced.
layer and add them to
raster that you will be
the map.
georeferencing. This
window will allow you to
georeference a raster using
two windows.
73

7. Use the Add Data button to locate and add the TIFF into the mxd.
8. Select the correct Raster layer from within the Georeferencing Toolbar.
9. Open the Georeferencing Viewer window by selecting the VIEWER button.
10. Select the Add Control Points tool+ and add a point in the Viewer window to a landmark on
the drawing that is also identifiable in the GIS. Every pair of points begins with the Raster layer,
and ends with the corresponding feature in the data frame.
Good options include:
• Property corners
• Existing infrastructure that is visible on recent imagery and included on the as -built
11. After each pair control point pair is entered, select the 'Full Extent' button within the Viewer
window in order to reorient it to the Raster layer.
+ + + �..r L 1[ Ra +y
71 R Yi L
f
12. Every control point should increase the parity between the drawing and the GIS. To achieve
this, distribute the control points around the site and far apart from each other. Repeat this
process until 2 to 5 Control Point Pairs have been. Rasters with a high degree of geographic
accuracy will require fewer pairs of Control Points.
13. Once the TIFF is geo-referenced, open the as -built PDF for the project and continue to digitize
the utilities.
Appendix H: Easement Examples [REMOVE]
Encroachment Examples
• An example of an encroachment agreement is where the City wants to place a new water main
in NC-55 (aka Alston Ave.) where it passes under the Railroad. In this case, the City would need
two encroachment agreements, one from NC -DOT for the placement of the water main within
the ROW of NC-55, and a second encroachment agreement from NCRR for crossing the RR ROW
• Encroachment agreements may sometime have a set time limit (e.g. 99 years) and often have a
clause stating that under certain conditions the utility lines must be relocated or removed at the
utility owner's expense.
• Encroachment agreements do not have to have a defined width for the encroachment.
• Encroachment agreements typically have only a written description with no associated plat. The
exceptions are those granted by the U.S. Army Corps of Engineers.
• Developers are typically responsible for obtaining any necessary encroachment agreements as
part of their utility extension permit. These encroachment agreements are then turned over to
the City once utility construction is completed and accepted for maintenance by the City.
74

• Copies of encroachment agreements are maintained by the Public Works — Engineering
Development Review Group.
Utility Easement Examples
• An example of a utility easement is where the city proposes to remove a sewer pump station by
building a new sewer outfall. In this case the City acquires easements from every property
owner along the route of the proposed sewer outfall.
• Utility easements typically do not have a time limit attached to them.
• Utility easements typically have a defined width and length.
• Utility easements typically have both a written description and a survey plat.
• Utility easement deeds and plats are usually recorded in the Durham County Register of Deeds
office.
Historical Easement Practices
For sewer easements, past practices performed before the systems maps were converted to GIS
involved:
• Reception of the easement map or maps and assignment of an easement number, typically the
next available sequential number in the index database.
• Adding the easement record to the sewer easement index database
• After the particular sewer main(s) was constructed, as -built drawings approved and the mains
were added to the sewer system maps, the sewer mains were labeled with their easement
number.
During the time of the GIS conversion (2003-2006) the tracking of utility easements was discontinued by
public works as outlined above.
Both the sewer main and water main feature classes have a field for the placement of the easement
index numbers. This field is called "EasementNumber"
After the utility maps were converted to GIS (2006), existing sewer easement numbers were assigned to
those particular sewer mains in the GIS, but no new easement numbers have been created or assigned
for new easements and thus, no new numbers have been assigned to sewer mains in the GIS.
For Water line easements, index numbers were assigned, but no index database was ever created. With
few exceptions, water main easement index numbers have not been assigned to their corresponding
pipes in the GIS.
It is hoped that some future project will once again begin tracking and indexing utility easements and
make them readily identifiable from the GIS.
75

Appendix I: Document Format Standards
The following is a list of fonts and typefaces used to uniformly communicate groups of data or
references.
Referred material
Example
References to other sections or other SOPS are in bold
Introduction, Glossary of Text Formats, Database
Calibri font
Overview
References to Servers, GIS Databases, Feature
snFittings, DIAMETER
Datasets, Feature Classes, and Fields. Courier
font without quotes
References to Attributes within fields.
`Drop Manhole', `Ductile Iron', `City
`Courier with Single Quotes'
of Durham'
Here is a template for the tables in this document:
76

Appendix J: Adding Photos to Stormwater Structures
Most of the photos are named according the their LEGACYID. New structures and photos should be
name according the their FACILITYID. At some in the past we re -numbered all the structures with an
easy to generate FACILITYID but just kept the LEGACYIDs and the original names on the photo image
files.
Photos are stored in the following location:
\\durham_pw\Public Works\DocumentArchive\Photos\StormWater\inventory
There are several folders there, each begin with a "wz" followed by a number. This organization scheme
is held over from the original inventory work - here each folder represents a "work zone" (hence the
"wz" prefix). Work zones were used by the inventory contractor to divide up the City for the purposes of
planning field work. It is also handy to keep this scheme so a single folder does not contains thousands
and thousands of files (each folder currently holds about 3 to 4 thousand image files).
Links to photos are stored in two attribute fields: PHOTOPATH and PHOTOURL.
To associate the photo copy the image file to one of the "wz" folders, rename it to the FACILITYID, and
the add the correct PHOTOPATH and PHOTOURL links to the attribute fields for the structure as follows:
Find the most likely "wz" folder to use as the destination for the image file (any will do of course, but
1 picking a logical one would be helpful). Find a nearby structure with a photo and look at the
PHOTOPATH. Find out what "wz" folder the photo for the structure is stored within and use that as
the destination folder for the new photo.
2 Copy the image file to the folder you identified in the previous step. Rename the image file according
to the FACILITYID of the structure).
77

Add the links to the PHOTOURL and PHOTOPATH.
PHOTOPATH should use a UNC path (look at other structures for an example).
The path should look like this example:
//DURHAM_PW/PUBLIC_WORKS/DocumentArchive/Photos/StormWater/inventory/wz2/22D.108.jpg
Just replace the "wz2" you see in this example with the correct "wz" folder and the image file name
with the one you are using.
The PHOTOURL should look like this:
http://pwgis/photos/stormwater/inventory/wz2/22D.108.jpg
Again, replace the "wz" and image file name with the ones you are using.
Test the links with the IDENTIFY tool in ArcMap once your are done. If the testing does not work
notify your supervisor of this complete failure and your inability to follow written instructions.

Appendix K: Revision History
20210727-sarahsch: Copied sections over to a combined utility document and removed them from this
one, but saved a copy with today's date that has everything still.
20210715-sarahsch: Corrected ownership section, removed references to "Appendix ?", corrected
Operational Area source, removed duplicate table.
79