07_NCS000250_NCDOT_FIP Procedures Manual

Highway
tarmw ter
Field Inventory Program Procedures Manual
Prepared by:
Dewberry Engineers Inc.
2610 Wycliff Road
Suite 410
Raleigh, NC 27607
919.881.9939
NC License No.: F-0929
Prepared for:
NC Department of Transportation
Hydraulics Unit
1590 Mail Service Center
Raleigh, NC 27699-1590
919.707.6700
[e-mail]
June 2016
(Update to ArcPad instructions — January 2018)

r~ c-
Hi1W
NOTICE OF PROPRIETARY INFORMATION
All rights reserved to Dewberry Engineers Inc.
This document was designed, prepared, and submitted by Dewberry Engineers Inc. to be used by the
North Carolina Department of Transportation Highway Stormwater Program and their authorized
representatives.
None of this material is permitted to be reproduced in any way or distributed to anyone other than
authorized representatives of the recipient.
REVISION HISTORY
This document was revised to reflect updates in hardware, operating system, and software utilized in the data collection
process in June 2016 (i.e. Windows 8.x tablets, Esri ArcPad 10.2, Trimble Positions 10.2.3.1).
The pervious version of the FIP Procedures manual was published in March 2014.

C:
Highway
Stormwater Field Inventory Procedures Manual
Contents
List of Common Acronyms, Terms, and Abbreviations................................................................................ i
I. Introduction...................................................................................................................................... 1
A.
Background.........................................................................................................................I
B.
Field Inventory Program (FIP) Objectives.........................................................................
1
C.
Determining Which Features to Collect.............................................................................
2
II. Tiered/Modular Inventory Program Design And Business Process........................................................
3
A.
Tier Structure.............................................................................................................................
3
B.
Stand -Alone Data Collection Modules.......................................................................................
4
C.
Overall Business Process...........................................................................................................
5
III. Role and Responsibilities........................................................................................................................
7
A.
Customer.............................................................................................................................7
B.
IP Manager..........................................................................................................................
7
NCDOT FIP Data Management Structure..........................................................................
7
Creatinga Job Work Area.................................................................................................
10
NCDOT — FIP Geodatabase Manager Data Work Flow Process — ArcGIS 10.1.............
16
Creating Field Data for ArcPad........................................................................................
21
Setting Up ArcPad for Field Data Collection...................................................................
32
Checking In and Correcting Field Data from ArcPad.......................................................
40
C.
Field Crew.........................................................................................................................
46
D.
HSP Geodatabase Manager...............................................................................................
46
IV. Feature Attribution and Sub -Meter Location........................................................................................
47
A.
What is a Stormwater System?.........................................................................................
47
B.
Feature Descriptions.........................................................................................................
48
C.
Feature Numbering System...............................................................................................
54
D.
Public Notification............................................................................................................
56
E.
Procedures for Entering Private Property.........................................................................
56
F.
Procedures for Inaccessible or Unverified Structures.......................................................
56
G.
Illicit Discharge or Hazardous Structure Procedures........................................................
58
H.
Encroachments and Right-of-Ways..................................................................................
58
I.
Attributing Stormwater Structures....................................................................................
59
V. Hardware
and Software Requirements...................................................................................................
70
A.
Data Collection Equipment......................................................................................................
70
B.
Data Collection Hardware and Software..................................................................................
71
C.
Quality Control and Accuracy Standards.................................................................................
71
VI. Safety and Traffic Control.................................................................................................................... 73
VII. Digital Pictures.................................................................................................................................... 75
VIII. System Connectivity .................
IX. Frequently Asked Questions ........
X. References .....................................
XI. Installation and Setup Procedures
76
77
79
80

Highway
Storjr,
o��
Field Inventory Procedures Manual
MobileClient Setup....................................................................................................................
InstallingArcPad 10.2...................................................................................................
Configure the NCDOT FIP Toolbar in ArcPad.............................................................
Installing Trimble Positions Extension for ArcPad.......................................................
GIS Workstation/Desktop Computer Setup................................................................................
Trimble Positions Desktop add -in Installation..............................................................
Setting Up the NCDOT folder location and associated project files on Desktop..........
Desktop GIS - NCDOT FIP AXF Forms Tool Setup ....................................................
XII. NCDOT Highway Stormwater Field Inventory Program Geodatabase Schema ................................. 96

Ncc13-
Highway
Field Inventory Procedures Manual
List of Common Acronyms, Terms, and Abbreviations
ArcGIS-Desktop software for GIS
ArcCatalog-Data manager for ArcGIS
ArcMap-Mapping application for ArcGIS
ArcPad-Mobile software for GIS
APM-ArcPad Map
AXF-ArcPad Exchange Format
BLOB -Binary Large Object
BMP-Best Management Practices
C#-C Sharp Programming Language
CAD -Computer Aided Drafting
CFR-Code of Federal Regulations
Cm -Centimeter
CORS-Continuously Operating Reference Stations
COTS -Commercial Off -The -Shelf
DWQ-Department of Water Quality
Dewberry -Dewberry Engineers Inc.
DMZ -Demilitarized Zone
EPA -Environmental Protection Agency
ESRI-Environmental Systems Research Institute
Extensions -Specialized tool in ArcGIS
Feature Classes -Collection of common features in
ArcGIS
FIP-Field Inventory Program
Gb-Gigabyte
GIS-Geographic Information Systems
GNSS-Global Navigation Satellite System
GPS-Global Positioning System
GPS Analyst -Trimble extension for ArcGIS
GPScorrect-Trimble extension for ArcPad
HSP-Highway Stormwater Program
ID -Identification
In -Inch or (")
IP-Inventory Program
IT -Information Technology
Kg -Kilogram
LAN -Local Area Network
L&S-Locations and Surveys Unit
Mb-Megabyte
MHz -Megahertz
MS4-Municipal Separate Storm Sewer
MXD-Map Document for ArcMap
NCDENR-North Carolina Department of Environment
and Natural Resources
NCDOT-North Carolina Department of
Transportation
NCGS-North Carolina Geological Survey
NHD-National Hydrologic Dataset
NPDES-National Pollutant Discharge Elimination
System
PC -Personal Computer/Desktop
PGDB-Personal Geodatabase
QA-Quality Assurance
QC -Quality Control
RDBMS-Relational Database Management System
ROW -Right -of -Way
SD -Secure Digital
SIDE -Spatial Database Engine
SDO-Stormwater Discharge Outfall
SQL -Structured Query Language
Stormwater Control -Preferred over BMP
Submeter-GPS accuracy under 1 meter
TMDL-Total Maximum Daily Load
UML-Unified Modeling Language
URS-URS, Corp.
USB-Universal Serial Bus
USGS-United States Geological Survey
WiFi-Wireless Fidelity
Revised i June 2016

�Cco-
Highway
Field Inventory Procedures Manual
Introduction
A. Background
The North Carolina Department of Transportation (NCDOT) Highway Stormwater Program (HSP) is a Department -
wide and Statewide initiative to protect and enhance stormwater quality while fulfilling the NCDOT's mission of
providing and supporting a safe and integrated transportation system. Guiding principles of the HSP are:
• Comply with NPDES Stormwater Permit requirements by managing, minimizing, and reducing stormwater
pollutants from roadway systems and industrial areas.
• Design sustainable programs that can be effectively managed, implemented and integrated into NCDOT.
• Develop solutions that improve program delivery that are proactive, form partnerships, have technical
merit, build institutional sustainability and are fiscally responsible.
The Field Inventory Program (FIP) is one such program developed by the HSP to facilitate the efficient collection
and storage of physical data about the existing NCDOT open and closed stormwater system.
URS oversees and administers activities in support of the FIP including the hosting and maintenance of GIS
stormwater data while Dewberry, a subconsultant to URS, provides the technical services needed for the
continued development and testing of the FIP.
As an initial step in the development of the FIP, Dewberry prepared a Needs Assessment Report and set forth
recommendations for development and implementation of the FIP. Through multiple phases of the project,
Dewberry developed a stormwater field inventory application and QA/QC tool utilizing ESRI's ArcPad 8 and ArcGIS
10. The purpose for this development approach was to utilize COTS or Commercial Off -The -Shelf software already
in use by NCDOT. The project was completed by providing training to HSP staff and the development of a
Procedures Manual and Field Guide to document office and field aspects of the FIP.
B. Field Inventory Program (FIP) Objectives
The NCDOT's second term NPDES permit, which became effective in April 2005, outlines four required
management measures associated with the identification and inventory of NCDOT stormwater outfalls. The first
three management measures are a continuation and expansion of requirements specified in the first term permit.
These requirements are detailed in Part II Section B Items 1(a), 1(b), and 1(c) of the 2005 permit and relate to the
implicit inventory of existing outfalls, procedures for updating this implicit inventory such that it includes implicit
outfalls from newly constructed roads, and outfall inventory of NCDOT industrial facilities, respectively. In addition
to these three requirements, a new management measure, Item 1(d), was added to the second term permit which
specifically requires the NCDOT to develop field outfall inventory procedures, and to prioritize areas for
cooperative field inventory projects.
Below is an outline of program objectives the FIP is designed to achieve, as well as a listing of subject areas the FIP
is not intended to address:
Revised 1 June 2016

�Cco-
Highway
Field Inventory Procedures Manual
Objectives of the FIP:
• Focused on supporting NPDES permit compliance
• Responsive to specific field information needs as identified and requested by HSP team members (see
Table 1 for supported HSP program areas)
• Employs a suite of inventory protocols so as to efficiently accommodate a variety of field inventory trip
objectives
• Data and procedures integrated into the HSP's GeoDatabase and Data Management Plan
• Implementation by NCDOT staff or consultants
The FIP is NOT intended to be a:
• Maintenance assessment program
• Asset management program
• Program to inventory newly constructed outfalls (these will be accounted for under a separate
program)
• Program to systematically inventory all NCDOT outfalls statewide irrespective of the current need for
that information
As noted above, implementation of the FIP will be on an as needed basis in response to permit compliance related
information needs identified by HSP team members.
C. Determining Which Features to Collect
As part of the initial Needs Assessment and Pilot Study (Final Pilot Study Report Dewberry & Davis, Inc. 2008),
determining the types of features and associated attributes to collect for a stormwater inventory was essential.
During the Pilot Study feature types and attributes were examined and reviewed by Dewberry and NCDOT to
determine the relevance to the FIP. A compilation of helpful reference documents supplied by various NCDOT
departments as well as interviews with NCDOT and URS staff guided the selection of the current list of feature
classes listed below and described in more detail later in this document.
After review of all referenced standards and discussions with HSP staff and URS, it was determined that attributes
for 17 feature classes would be collected. The list of feature classes and geometry includes:
1. BMPExisting (Point)
2. Channel (Polyline)
3. ChannelPoint (Point)
4. Culvert (Polyline)
S. DeckDrains (Point)
6. IllicitDischargePoint
(Point)
7.
Inlet (Point)
8.
JobWorkArea (Polygon)
9.
Junction (Point)
10.
LandPoint (Point)
11.
OverlandFlow (Point)
12.
Photo (Point)
13.
Pipes (Polyline)
14. PipelO (Point)
15. PipePoint (Point)
16. PollutionSource (Point)
17. Potential Retrofit (Point)
Revised 2 June 2016

�Cco-
Highway
Field Inventory Procedures Manual
II. Tiered/Modular Inventory Program Design And Business Process
The FIP is proposed to have a three tier structure. The term tiered inventory system refers to the hierarchical
design of the (FIP) and how it is implemented. Unlike most municipal inventory programs where the type of
information to be collected remains relatively static over the course of the program's life span, the HSP's FIP is
envisioned to support multiple data collection goals. This program structure allows for the type and quantity of
data collected to vary by inventory trip. This in turn facilitates optimization of the program by focusing data
collection only on the information required to address a predefined need at a predefined location.
A. Tier Structure
• Tier I — Discharge point identification
The primary data collection objective is to identify stormwater discharge points either within the ROW (Right -of -
Way) or in some rare cases outside of the ROW. The inventory includes some basic attribution, source, mapping
grade GPS, and photographs as appropriate. Tier I inventories are designed to minimally comply with NPDES
permit requirements as well as any applicable state stormwater rules requiring outfall identification. Tier I
inventories are subdivided into three categories tailored to meet the specific information need within a given
job work area.
o Tier I a — Identification of true outfalls to waters of the state at or within the ROW boundary (known as a
NCDOT outfall).
o Tier I b — Identification of points where concentrated stormwater is exiting the ROW (known as a ROW
discharge point) as well as any NCDOT outfalls present.
o Tier I c — Include the collection of Tier I b data plus the locations of outfalls to waters of the state outside
of the ROW extending from ROW discharge points.
• Tier II — Conveyance system connectivity within the ROW
The primary data collection objective is to identify where stormwater is coming from and where it is going within
the boundaries of the ROW for a specified job work area. Tier II inventories include detailed attribution of the
system, mapping grade GPS, and photographs as appropriate.
• Tier III —Total system connectivity within a work area.
In some instances it may be necessary to extend the inventory beyond the limits of the ROW. Tier III inventories
include detailed attribution of the system, mapping grade GPS, and photographs as appropriate to define the
connectivity of the entire drainage system within a study area. Tier II and III have the same level of attribution. The
difference between a Tier II and Tier III is the job work area definition (for example, Tier III includes inventory
outside the ROW).
It should be noted that extensive discussions were held with HSP staff to ascertain the FIP's need to acquire
elevation data as part of the system attribution. Based on the regulatory focus of the FIP it was determined that
Revised 3 June 2016

NCDO-
Higk;<way
I Field Inventory Procedures Manual
elevation data not be collected. This data would be collected via traditional survey if required for design related
activities. This reduces the complexity of the database design and minimizes field time required for data collection
and QA/QC processes.
Another important advantage of a tiered system is that it facilitates effective communication between the IP
Manager and the field crews. Associated with each tier is a pre -established suite of features and attributes (see
Appendix A). The IP Manager simply instructs the field crew to conduct a specific tier level inventory in a project
area and the types of information to be collected are known by all parties involved. This system will minimize the
need for the IP Manager to describe in detail the exact types of information the field crew is required to collect.
B. Stand -Alone Data Collection Modules
To maximize flexibility, supplemental drainage system attributes will be gathered through the use of stand-alone
data collection modules. Although these modules operate inside the same software environment they are stand-
alone in the sense that they are not dependent on the selected data tier for the level of attribution needed. These
modules are available at all times for each tier of inventory depending on the needs and priorities associated with
a given inventory trip request. If a module is activated (either in the office as part of the data request, or in the
field if the data request trip needs to be altered on -site) additional feature classes and attributes will be offered as
items to collect.
• Illicit Discharge Module — this module is used any time a suspected illicit discharge into the NCDOT's system is
encountered in the field. This data is used to support the HSP's Illicit Discharge Detection and Elimination
Program.
• Pollution Sources Module — this module is used as a means of identifying pollution sources both inside and
outside (in close proximity) of the ROW via an attributed point. This module was designed to primarily
support the HSP's TMDL Program.
• Retrofit Space Module — this module is used to record preliminary information pertinent to siting a retrofit
BMP. The module is limited to visual site attributes and does not include detailed engineering analysis or data
collection. It is anticipated that the types of data collected with this module will be restricted to information
related to available space for a BMP, photographs of the site, and any associated notes about the site and
watershed. This module is designed to support the HSP's BMP Retrofit Program. Connectivity may be helpful
here for identification of contributing area and thereby pollutant load. Therefore, the Retrofit Space Module
will be used in conjunction with a Tier II and Tier III inventory. The module provides special features and
attribution as an "add on" to the base inventory tier.
• Existing BMP Module —this module is used to record the presence of an existing NCDOT BMP within the ROW,
as well as collect basic attribution data and photographs as appropriate. This module is intended to primarily
support the BMP Inspection and Maintenance Program and possibly the TMDL program. The functionality of
this module could be extended to BMPs outside of the ROW if a need for such information is identified.
Revised 4 June 2016

�Cco-
Highway
ifigwlaiwom
­­.. Field Inventory Procedures Manual
• Photo Points Module — this is used as a "catch all" module for recording information about, and photographs
of, any point of interest in the field. This module can be used in those cases where it would be inappropriate
to use one of the above modules or the basic functionality included with the three inventory tier protocols.
The collection of photos should be considered for all Tiers and all modules by the IP Manager prior to
assignment of the project job work area to the field personnel.
• Overland Points Module —this module will help identify the high and low points on an overland drainage
system as well as flow direction and even help delineate catchment boundaries.
C. Overall Business Process
To maximize efficiency, a business process for data collection has been developed along with a work flow diagram
that outlines the data collection process (Figure 1). The purpose of the business process is to clearly define the
flow of information between the FIP participants and their relationship to one another. A Needs Assessment
performed in 2007 (NCDOT Field Inventory Program Needs Assessment Report
Dewberry & Davis, Inc. 2007) helped define the business process and the roles for each participant. These roles
include the Customer, IP Manager, Field Crew and/or Consultant and the HSP Geodatabase Manager discussed in
Section III: Roles and Responsibilities.
For some work requests, there may need to be special instructions or notes that document the details of the data
request or specific field notes regarding a particular job work area. The data collection process does not address
this step. There are two recommended methods that could be used to achieve this.
Geodatabase Method
The simplest method is in the form of two 255 character comment fields inside the digital "JobWorkArea" feature
class. These fields would store special instructions to the field crews and special collection notes from the field
crews. The NCDOT stormwater FIP geodatabase has been altered to include fields for special instructions and field
notes in anticipation of using this method. For very complex instructions, these fields would either summarize or
refer to the more complete special instructions that might be stored elsewhere.
Document Folder Method
Another easy way to store instructions is to make digital copies of emails, phone calls, memos, etc and place them
in the "Documents" folder with subfolders for each job work area. This is the easiest way to store the special work
area data instructions however it would not be as easy to retrieve and review as other methods.
Revised 5 June 2016

NCbT
Highway
Field Inventory Procedures Manual
NCDOT HSP
Caslnmer determines Field Inventory Program
i location and level of
mim-ationragwred Process Diagram
Customer Revised February 20, 2012
requests inventory
and
submits data
request form
dal. ehd exports to
Customer desired
IP Manager reviews
format
request, establishes
I
Job Work Area, and
assigns Job IC
Yes
Elb relevant '
IP Manager tags any
Gig stormwaterdala
Does extent O\
existing GI5 features
exist within Job Work Yes
► available Bzisling data> No
► requiring a higher tiered
Areas
satisfy request? -
inventory
♦
Po ezisling
IP Manager establishes
higher tiered Job
a rewsed Job Work Yes
Work Areas reduce the
Area
extent of the
request?
IP Manager
No
submits Jab Wark
Area data layer to
► Gaodatabasa
No
Manager
Geodatabasa
J
Manager checks
t�
F�Z7�-
out FIP
_
_
geodatab.illei
Georg bass Manager
delivers to IP
checks in Job Work Area
Manager
data layer into AmSQE
Master Geodalabase
IP Manager issues
work order and
delivers FIP
► geodatabase to
Field Crew
♦
Field Crow
Field Crow
delivers edited Fill
IP Manager post-
perfonnsfield
► geodatabase to IP
processes,
outfall
inventory
Manager
validates. and QAr
QGs field data
Yes
/7\
/ \ IP Manager
Is additional Are pass-
delivers data and
Held xrork required -' processing, validation.'
Na - Yes
Job ID Compleaon
/Gaoda[a4ase Manager
to satisfy QAIQG and QAIQG protocols -
Notice to
j Jhecks in past -processed _
protocols? satisfied?
Customer
j\\data into ArcSQE Master
Geodatabase
IP Manager
Geociatabase
delivers data to
Manager reviews
No IP Manager
field data
Geodatse aba
Past-poressed
a data
corrects
Manager
and resolves
gpnfl nts with
geodatabase
Figure 1: Field Inventory Program Data Collection Diagram
Revised 6 June 2016

�Cco-
Highway
Field Inventory Procedures Manual
III. Role and Responsibilities
A. Customer
The role of the customer is to determine the location and level of information needed. The customer could be any
NCDOT staff requesting stormwater conveyance data for a project or an HSP team member fulfilling a NPDES or
TMDL requirement.
Customers should begin the process by requesting and filling out a FIP Data Collection Request Form and providing
it to the IP Manager. The IP Manager can assist the customer in locating and defining the specific location or job
work area in GIS and provide additional guidance as needed.
B. IP Manager
Once the customer has completed the initial request, the IP Manager's role is to review the request and establish
the job work area in GIS. The IP Manager will discuss the appropriate resources to utilize for the project (for
example, HSP staff or consultant) and develop the schedule based upon the customers' needs.
Once the job work area is established, a current version of the FIP geodatabase will be requested from the HSP
Geodatabase Manager. The FIP geodatabase will be formatted for the FIP application, as detailed below, and
provided to the field crew. The IP Manager will QA/QC the data by using the FIP Validation tool in ArcMap as
explained below and ultimately either accept or reject the stormwater data from the field crew and provide the
data to the customer and the HSP Geodatabase Manager.
The IP Manager is also responsible for developing a Public Notification letter to be distributed to the public by field
crew personnel. If access to private property cannot be accessed safely, the IP Manager should be notified and a
determination will be made whether or not the data should be collected. The IP Manager will contact the
customer to determine if a revisit is required to obtain the stormwater data.
To further detail the IP Manager's role regarding the FIP geodatabase formatting and QA/QC, the technical
procedures are documented below.
The NCDOT FIP Desktop Toolbar is no longer required in ArcMap 10.1 Details about setting up a shortcut to run
the AXF Forms Tool can be found in section XI. Installation Procedures.
NCDOT FIP Data Management Structure
Data integrity is essential when managing any project, especially when data is transferred between office and field
activities. This section of the document will detail best practices for the IP Manager to follow when managing all
data types for a field inventory project.
Currently, the transfer of data between NCDOT's computer network and field collection devices is restricted due to
NCDOT network security settings. Once all relevant data for new field inventory project is obtained and field
activities are ready to commence, it's recommended that data structure be copied from the NCDOT network to the
Revised 7 June 2016

`CDO-
Highway
Field Inventory Procedures Manual
local hard drive of the IP Manager's personal computer. It's important to note that as the project progresses,
periodic updates to the NCDOT network should be performed in order to ensure data integrity.
The IP Manager will confirm the folder structure and naming conventions required for the integrity of the project.
• Each project is designated by a year and a
sequential identifier and project name (for
example, 12_00_CenturyCenter). To create a
new inventory project, copy and paste the
project folder template, "yr_id_template"
and correctly rename the new project folder.
• The new project folder contains three (3) sub -
folders: a "Documents" folder which holds
electronic documents related to the project
(for example, roadway plans and rights -of -
way agreements); a "Map" folder which
holds GIS data; and a "Photos" folder which
holds digital photos related to the project.
These folders are empty by default.
®C)�I . « My Documents P My F[P P it Seoxh My- .0
Organize - ',jj Open Sharewdh
Libraries
Dacuments
My Documents
My FIP
'. Computer
Q* Network
12111 Falls
Filefolder
F-mail Bum W—folder
H88 . ®I
Documents library
My FLIP
Arrangeby. Folder -
Name
Type
32_00_CenturyCenter
Filefolder
J� 12 01 Sovthca Whi cOak
Fil fclder
Ja 12 02 Falk
Filefolder
I yr-id template
Filefolder
l�lol��
®� My FIP a yr id template e
-N
Seorch yr id template p
Drganae - Share with . Bum
W—fokler
} Fa ordea
Documents library
yr id template
Arrange by Forcer -
Libraries
Name
Type
oe—erits
LU My Dccuments
Documents
Filefolder
My FIP
Map
Filefolder
My Temp
Photos
Filefolder
Public Documents
81016ico
Icon
�1 Music
j'�1034, ico
Icon
© Pictures
p� 1081,ico
Icon
® Videos
�'1084,ico
Icon
1088,ico
Icon
7 J Computer
1715,ico
Icon
f81 Camera,ico
Icon
CIF Network
_, defaultValuest t
Teat Document
j Hydrant,ico
Icon
ncDttTools.apa
APA File
_-NtTuuls.M
Teat Document
®ncD.tT,.1, ,
VBScript Script File
Tier.dbf
DBF File
1 lb items
Table 1: Required Files for FIP Application
File Name
Description
1016.ico
Image file format for computer icons.
1034.ico
Image file format for computer icons.
1081.ico
Image file format for computer icons.
1084.ico
Image file format for computer icons.
Revised 8 June 2016

NCDO-
Hig_Way
The new project folder also contains thirteen
small files necessary for the FIP application
software. These files are required for the
ArcPad application to function and include
the following:
Each of these thirteen (13) files are required
for the FIP application to function in ArcPad
8 and should remain under the main folder
structure. The only two files that may be
edited are the Default.Values.txtl and
Field Inventory Procedures Manual
1088.ico
Image file format for computer icons.
1715.ico
Image file format for computer icons.
Camera.ico
Image file format for computer icons.
Default.Values.txtl
ArcPad form required values.
Hydrant.ico
Image file format for computer icons.
ncDOTTools.apa
ArcPad applet.
ncDOTTools.txt
ArcPad applet code.
ncDOTTools.vbs
BScript for ArcPad application.
Tier.dbfl
Table of tier names/descriptions.
Tier.dbf2 files which should only be changed by the IP Manager. The Default.Values.txt file contains all the required
values or domains for each
feature class. The Tier.dbf contains
the tier level definitions.
Finally, to retain your personal settings such as toolbars, symbology, and base layers, copy the "ncdot.mxd" ArcGIS
map document and "NCDOT_HIP .mdb" personal geodatabase from the previous project folder and paste into the
"Map" folder of the new project folder. To maintain data integrety it's essential the IP Manager maintain consistent
folder structure and file names.
The NCDOT FIP Toolbar for ArcMap (ArcGIS Desktop 10.1) is no longer required. The setup process
includes creating a shortcut to run the AXF Forms Tool. See section XI. Installation Procedures for details.
Revised 9 June 2016

NCDO-
Higki<way
Field Inventory Procedures Manual
Creating a Job Work Area
Every new inventory project will require the creation of at least one job work area before requesting a new
personal geodatabase from the Field Inventory Program SIDE master geodatabase. This job work area will be
submitted to the Geodatabase Manager to ensure the appropriate data is obtained for the inventory project. The
general location of the project is initially defined by the project requestor through the Data Collection Request
Form seen below, but ultimately the creation of a polygon feature class of the job work area is generated by the IP
Manager.
Field Inventory Program
Data Collection Request Form
xrM'+iea me l�rn rrnn;a�rn
•rrcmo••vew. o comPkrcd bo•avPvlom. ran boa fir m: n�M�ew+wraoArel. rnWw�J�ra r�rc. ten urry e+nr+. p. xcm McN:rcrrte eertrcr. rtalepR+ee27evripm.
e Requestors Name:
e Contact InfonnatlonIphone and emall 1:
e Date:
Proiect Name or Num bar:
�. �..mn•. «�. �,.r �...e ,n-� rv.,.. r•�•nn. � ...v n...r rr-r.r d."crvpry�.l
Detailed Description of In ventury S—Wces Het ng Requested:
r.�..ri.... e..r ee .. kern.... re t.lrrd yror.n
. ....:..:....r .:..r...: r. ...��r�.. _ .. r r.�:1.:.. n,., ...,.ten,•.: r. r:�:.... r..r.......:..y ..-n... r. �.. _��l.pbe.eJ ..ev !Fowl- dw.. e.e.ro,..,e,.,P ;,,p..meemA e..
•� mrsn.or.�r.r..n.nr.�.o"o�mt of rna kc�wonwi. n. or.�yrKuostruuwrn eyn:ne rv-ge.ouon..enrrom eeowrn..wrk m.e
.....,,,e,..v fir,................n. m..,, .,, P m.n,. ,.T. ....,,.,... r.y m,..m,...M.... n.p...n.�r.,.,n � mr...� ../.,.,,,,
Please check applicable options:
Yes No
❑ ❑ should field collected GM points be "photo corrected" to match the c—ponding point wsl blt on an ae-
Hpl photo frwph7 If Yes—plwwte sp­tfy ebpvw the wwriwl photography to W used.
❑ ❑ Am the dimensions of catch basins and other Inlets requ rredle
❑ ❑ should drl"way cPlWrtS bo Inyantadad7
❑ ❑ Should channel IlnIrW he Identified?
❑ ❑ Should photographs br: twk— of wll structurpsi
❑ ❑ should field crews spend more than 10 min utas searching for dlfflcuIt to find structures/features?
If yes —pleas Specify w approwimwte Stanch LIMB limit,
U E:tlttlel aMP L tit. �e n�u h.,�g.. W orerltnd fie-
Applicable Modd—
LI Pollution Source L Photo U Repeat space WarkAreal D:
Once the IP Manager has the general location and has coordinated with the project requestor, the user is ready to
delineate the job work area. The graphic below represents a sample job work area, but the location and shape or
shapes will vary. Again, each project has to have at least one job work area but there may be multiple job work
areas for each project.
Revised 10 June 2016

NcCo-
Highway
ifigwlaimft
Delineating the Job Work Area in ArcGIS
Field Inventory Procedures Manual
The following steps will guide the user in the technical creation of the job work area in ArcGIS.
• Navigate to the "Map" folder and launch the map document Name •
called "ncdot.mxd" in ArcGIS. This folder is also where the ncdok,mxd
NCDOT HIP personal geodatabase will eventually be stored. NCDOT_FIP,mdb
It's important to note that this map document should be used
throughout the entire project lifecycle. Review the Data
Management Structure section of this document if you're uncertain of the "Map" folder location.
Once the map document is open, add additional NCDOT layers or imagery to locate the general location of the
project area. Recommended layers include roads, county boundaries, and aerial photography.
The link below will provide the user with the latest NCDOT road and boundary GIS data.
https://connect.ncdot. gov/resources/gis/pages/gis-data-layers. aspx
The latest aerial photography in North Carolina can be found at http://www.nconemap.com/.
Revised 11 June 2016

NCDO-
Higklway
Field Inventory Procedures Manual
• To start an edit session in ArcGIS 10.1, the recommended method is to
2 copy
right -click on the layer you wish to edit. In this case, the JobWorkArea
x Remove
feature class will be the layer delineating the work area for your
® Open Attribute Table
project.
loins and Relates
Zoom To Layer
Visible Scale Range
Use Symbol Levels
Selection
Label Features
Edit Features
V' Start Editing
Define New Types Of Features.
Organize Feature Templates..
• Select the JobWorkArea feature and the appropriate construction tool.
Typically, the "Polygon" tool would be appropriate for digitizing an
irregular shape.
As a note, the construction tool will change depending on the geometry
or shape of the feature, such as points and polylines.
I- Construction Tools
�3 Polygon
LJ Rectangle
O Circle
O Ellipse
'6- Freehand
M Auto Complete Polygon
:n Convert Features to Graphics...
Convert Symbology to Representation...
Data
O Save As Layer File...
p Create Layer Package...
L"e Properties...
DeckDrains
C. DeckDrains
IllicitDischarge Point
ID tlicitDischargePoint
Inlet
[ rnlet
07obworkArea
Junction
®]unction
LandPoint
6 LandPoint
OverlandFlow
OverlandFlow
Photo
+ Ph4t4
PipeIO
C PipeIO
Pi p ePo i nt
C PipePoint
Pipes
I. -Pipe
Pollutionsource
I/ Pollution5ource
PotentialRetrofit
Revised 12 June 2016

NcCo-
Highway
Field Inventory Procedures Manual
• Once the project area has been identified and using the best available data
such as aerial photography and roads, delineate the job work area. Double-
click to finish digitizing the polygon and save your edits. It's considered good
practice to save your edits throughout this process since ArcGIS does not
auto save.
Under the Editor toolbar, "Save Edits" allows the user to save while
continuing to edit.
• If you're satisfied with your delineated job work area and you've
saved your edits, right -click on the JobWorkArea feature class in
the Table of Contents and navigate to the "Open Attribute
Table".
Revised 13 June 2016

NCDO-
Higkiway
Field Inventory Procedures Manual
• Enter the project identifier under the "JobID" field for the new job work area. Due to the twelve (12) character
limitation of the JobID field, use a two (2) digit year and two (2) digit sequential number (e.g. for first job work
area in 2016: 16_01). Refer to the FIP Data Management Structure section of this document to determine the
appropriate naming convention.
Table
di
or riu
x
IMPRelrofftl
MPhutl
MoFlcl BufferSize
Tior
I Courmf
Division
I FieldCra
FirrnNaml RoqD,01
CreawOat I
JoblO
MaxF4atl
r -Nulls
<Nlil�
<Nul0
Tor II
Tw im
-Nulls
<Null�
<Null7
1Null�
EJH
EJH
_NCDOT
NCDOT
aNull7
Null,
�Null�
Null>
12_02
12 0e
0
0
,N01-
[Nulls
[Null? 0
KNull>
<Null>
<IN
<Nullr
-Nulls
<Null>
0
0
TlDr11
-Nulls
cNull>
-Nlflr
EJH
EJH
NCDOT
HCOOT
<HuP
<Hull>
<Null�
<Nulls
12 01
0
0
Tlerll <Nuls
12 02
4
I. ' 1 ' " ■7M l (l out of d Seleaed)
;lo at+ilorlr.4 •ea
• While not required, populating additional
attributes about the job work area and
inventory project may add value for the
field crew. The fields below reflect the
information found on the Data Collection
Request Form. Fields that are auto -
populated are not shown.
Remember to "Save Edits". It's important
to note that ArcGIS does not auto save and
therefore it's good practice to save edits
periodically.
Field Name
Description
Tier
Tier Level
MPolution
Pollution Module
MExBMP
Existing BMP Module
MIIIDischg
Illicit Discharge Module
MPRetrofit
Potential Retrofit Module
MPhoto
Photo Module
Instructns
Instructions for Field Crew
Field Notes
Notes from the Field Crew
RegDate
Requested Date
MOFlow
Overland Flow Module
BufferSize
Area of Study Extended by Field Crew
FieldCrew
Field Crew Name
FirmName
Consultant Name (if non-NCDOT)
Revised 14 June 2016

NCDO-
Higkiway
Field Inventory Procedures Manual
Right -click the "JobWorkArea" feature class in
navigate to "Data" and "Export Data". Rer
current job work area before exporting.
• Change the name of the output
file to reflect the project name and
save the feature class to the
project's "Documents" folder.
Refer to the FIP Data Management
Structure section of this
document to determine the
appropriate naming convention
(e.g. 16_01).
Click "OK", close ArcMap, and
send the feature class to the
Geodatabase Manager.
Export Data
Export: I Selected features
Use the same coordinate system as:
#this layer's source data
the data frame
the feature dataset you export the data into
(only applies if you export to a feature dataset in a geodatabase)
Output feature class:
ers\mqualls\Documents\My FIP\2012_003\Documents
OK Cancel
Revised 15 June 2016

'Cl
Higkiway
Field Inventory Procedures Manual
NCDOT —FIP Geodatabase Manager Data Work Flow Process — ArcGIS 10.1
Check Out
1. Create an .mxd containing all of the FIP layers. Ensure that the data is pointed to the correct ArcSDE
version
Fi,P csr Ykw lvPbw4 Fse! SyePpPn c�P�t 1 Cuge� W
Z��{'t0..:: aw >�%• �! � Tom' _ MrSa'.
ax
.,3 A 1"'r
. • �'y kcom rla.Dea.s o—er x n.m...
.mom
� NCDOijID.D80.PeMial ''ser� fin`
® HMT FIPZW. ,p .
®NCDOTjW.DiO.PiP�]
- IF HCDOf M.DW.P
14 KMT Im.OBO.LxWPomr
a � moa? Fm.maa,dau,.n..y,P�,r
GIx[Dorfm.osa.o. wr. r
- s8 xcmnt rm.oay.rrMw.�r
� xcooi�•m.oev.oFnpt„ama
- R NCDOf FIP.M.Rpc
2. Add the Distributed Geodatabase toolbar to ArcMap.
3D analyst
Advanced Editing
Animation
Arc Scan
COGO
Data given Pages
Data Framerools
Dimib tedGeodatabase
0
Draw
Edit Vertices
Editor
Effects
Feature Cache
Feature Construction
GPS
Geo coding
Geo database History
Geometric Network Editing
Georeferencing
Geostatistical Analyst
Graphics
Image Classification
Labeling
Layout
Revised 16 June 2016

L: _-
Highway
Stormwater
3. Click the Create Replica button on the Distributed Geodatabase toolbar.
Distributed Geodatabase-
4. Follow the screen shots below to perform the check out
Field Inventory Procedures Manual
Create Replica Wizard
g
Which geodatabam do you want to replicate data from?
dbo.DEFAULT-sde:sglserver:1672SR-M89009WEJ
Spatial Database Connection
hrr
These layers and tables will be available for replicabon,
NCDOT FIP.DEC.PotinntalRetrofit
NCDOT FIP.DEC.PollutonSourm
NCDOT FIP.DEC.%ePoint
NCDOT_FIP. DEC. PipeIO
NCO0T_FIP.06C.Photo
NCDOT FIP.DEO.OverlandFlow
NCDOT FIP.DEC.LandPoint
NCDOT FIP.DEC.]unction
NCDOT FIP.DEC.Inlet
NCDOTFIP. DEC. IIIicltDisdhargePoint
NCDOT _FIP. DEC.Oed Drains
NCDOT FIP.DEC.ChannelPoint
< ead< Next > 0
Create Rep Pica Wizard
This wizard lets you create a replica between this geodata6ase and another geodata6ase. By default, all
fatire classes and tables in the map that can be part of the replica are included, along with any related
data.
What type of Replica do you want to aeste?
Check—t
A dhecicbut allows you to edit the dam in the child geodatabase and then syndxonire the edits 1
with the parent geodatabase, Cncx the edits have been synchronized, you can no longer
syndmonize addit nal edits.
_j Two way replica
A two way replica allows you to edit the data in either replica geodatabase and periodically
synchronize the geodatabasesAll data must be versioned, have a global ID column and both
geodaiabases must be ArcSDE geodatabases.
_i One way replica
!?7 Parent to diild Child to parent
A one way replica allows you to send cianges in one direction, Choose to send Gam either a parent
ArcSDE geodata6ase to any type ofdi geodata6ase or from a child Ax SDE geodatabase to a
parent ArcSDE geodatabase, All data must have a global ID column.
About Creating Replicas
13adc Next
Revised 17 June 2016

NCDOT
Field Inventory Procedures Manual
Advanced C heck Out Options I. v II
What spatial extent do you want to apply to the diedcbut
# The current display extant
The full extent of the data
The boundary of the crrentiy selected graphic
_i The following extent:
Left: Top: �� Right:
Bottom:
rhooce whi h want to rfierk ont
Inclutl
Data
Target Name
Type
Check Out
Ilse Sperm
NCDOT_FIP.DDO.Sterm
Stormw ater
Featuire Dat—
;/
NCDOT_FIP.DHO.Putenti
Pot- ilRetrnFd
Featu re Cla
All Features
14
NCDOT_FIP.DHO.Polluti
Pollution Source
Feature Cla
All Features
rj
;/
NCDOT_FIP.D60.PipePo
PipePoint
Feature Cla
All Features
J
;f
NCDOT_FIP.D60.Pipes
Pipes
Featu re Cla
All Features
d
� � t
Iodide AY F�rdude AY Reset lJl i
❑J Extract related data
[&adc Next> Cancel
<&adc Next a
IIAdvanced Create Replica Options 1 0 l
Which geodatabase model should be used?
rug Full Model:
Assumes features are stored wiffi ffie same feahre type In both the parent replica geodatabase
and the d ild reply geodafabase.
j Simple Model:
The diild geodafabase will contain only simple features. Nonsimple features in the parent(e, g.
features in geometric networks and topologies) will he converted to simple feaures in the dhild
and vim versa during replication.
Use of archiving for 1 way replication
❑ Use archiving to track dhanges for 1 way replication
<Badc Next>
Revised 18 June 2016

NCDOi
Post Check Out Options
What do you want to do ohm the deck out has been completed,
i No further action
5. To confirm the process was
Replica Manager tool and verify
essential information.
_i Change the layers and tables to point to the dredced out data
Save a mpy of this map domment with the layers and tables pointing at
@ the dreck pt data:
:DOiStormwaterj14SSIPWIS_W ORKING1kitdeAJamanmVV tdeAlamanm. mxd
Summary,..
Field Inventory Procedures Manual
C back ® Cancel
Checking Out Data
Ed—ting S hema and Dab_.
Registering Checkout...
l5draciing Schema and Data: NCDOT_FIP. DBO.Fipes (111
Objeds)
Total Pmg—:
completed accurately click the
the timestamp, conflict and other
Revised 19 June 2016

High
Y4UGN:.,V.
Replica Manager
Replies types listed'.
rvame
Llttle-Namance FIP
Field Inventory Procedures Manual
Qistributed Geodatabase- �] I '4v
Synchronize Charges Wizard
The wizard allows you to synchronize changes between replicas
Geodatabase 1-7he oeodetabase that you have chosen to synchronize
NkCommon_Projed3)NCDOT5mrmwater l'-SSIP'GIS_WORMG�LittleAJamancc Ljtd
Replica To Synchronize: Little Alamance FIP
Geodatabase 2-7he gecdatabase centainting the relative replica
l�
Replica Type: Chedcaut
The Synchronize Direction: From Geodatabase 1 to Geodatabase 2
About getting replica dhanges
[ &ate Next >
"Using the same .mxd from the check-out process.
1. Click the Synchronize Changes button on the Distributed Geodatabase toolbar.
Distributed Geodatabase- 4 Qq -4,y
12:53:45 PM
Revised 20 June 2016

_r-
Highway
Stormwateri
Field Inventory Procedures Manual
Synchronize Changes Wizard , V I 1
❑ Remndle and post with the parent version
Spedfy how to promm mnflicts with non-versioned data or with versioned data when remnaling
and posting dianges,
Define conflicts
;A- By Cbject (by row)
6y Attribute (by column)
Resolve mnflicts
_i Resolve in favor of geodatabase 1
0 Resolve in favor of geodatabase 2
Resolve conflicts in versioned data manually at a later time.
® Conflicts with non-versisoned data will roll back the operation.
QYou will need to manually reconcile the syndironirabon version if there are
conflicts
back Finish Cancol
Creating Field Data for ArcPad
Revised 21 June 2016

NCDO-
Hig_Way
Field Inventory Procedures Manual
After the project job work area or areas have been delineated and provided to the Geodatabase Manager, the IP
Manager must create the field data used for the field inventory. The personal geodatabase (NCDOT_FIP.mdb)
provided back to the IP Manager will include the job work area feature class as well as any existing stormwater
data appropriate for the project. Utilizing ArcGIS the IP Manager will create the data that will eventually be loaded
into ArcPad.
For all functions in the NCDOT FIP tool to work, these layers need to be checked out as editable layers:
Points:
- BMPExisting
- ChannelPoint
- DeckDrains
- IllicitDischargePoint
- Inlet
- Junction
- LandPoint
- OverlandFlow
- Photo
- PipelO
- PipePoint
- PollutionSource
- Potential Retrofit
Polylines:
- Channel
- Culvert
- Pipes
Polygons:
- JobWorkArea
Some NCDOT FIP ArcPad data entry modules may fail to work properly if any of these data layers are not present.
Save the personal geodtabase (NCDOT _FIP.mdb) provided by the Geodatabase Manager to the "Map" folder
under the project directory. Review the Data Management Structure section of this document if you're uncertain
of the "Map" folder location.
• Before you can use the Trimble Positions Desktop add -in effectively, you must: 1) enable a geodatabase for
data collection. This must be done once for each geodatabase you are enabling. (See the Trimble Positions
Desktop add -in Administrator's Guide for configuration and administration information) 2) add a
TrimbleSessions feature class layer to each of your map documents, and 3) test the map against internal
validation criteria, to make sure that the map will create a mobile cache and project that will work in the field
to collect high -accuracy Trimble geometry.
• Start ArcGIS for Desktop, and open an existing Map document (MXD file).
Revised 22 June 2016

�Cco-
Highway
vwilliwft
• There are two (2) ArcGIS extensions required to
create the field data: ArcPad Data Manager and
Trimble Positions Desktop. Both extensions must
be activated in ArcMap to function. If loading
either of these two (2) extensions for the first
time, the order of installation matters.
Field Inventory Procedures Manual
Extensio�
Select the extensions you wank to use.
❑ 3D Analyst
❑ ArcPad Data Manager
❑ ArcScan
❑ G eostatistical Analyst
❑ Network Analyst
❑ Publisher
❑ Schematics
❑ Spatial Analyst
❑ Tracking Analyst
Description:
Trimble Positions Desktop add -in software v10.4.0.1
Copyright o 2012-2016 Trimble Navigation Limited
The Trimble Positions Desktop extension allows the incorporation
and use of high -accuracy 6 N S S positions and geometries into E S R I
ArcPad and ArcGIS Mobile workflows. G N S S positions may be
post -processed and their accuracy verified, and the feature
geometries uploaded to the GIS.
Close
• In ArcMap, if the Trimble Positions toolbar is not already turned on, then do so by right -
clicking on a blank portion of the toolbar in ArcMap and click to select the required toolbars.
The following toolbar should appear. Reposition it as desired.
• Click the Show Trimble Positions Desktop Administration Window toolbar button . The Trimble Positions
Desktop Administration window will appear.
• Create a project with Trimble Positions Desktop Administration using the Projects button. This step will enable
GNSS and Datum Transformations automatically, removing a number of steps from previous versions of the
Trimble software.
Revised 23 June 2016

NCCQ-
Highw
Trimble Positions Desktop Administration
Field Inventory Procedures Manual
®1
Positions Desktop add -in version 10.3.0.2, Copyright ID 2012-2015 Trimble Navigation Limited
Current project: <not selected>
Connected to: TrimblePositions 1
Create, edit and delete projects. Export projects to field databases.
Projects
Manage field devices. Assign processing profiles with differential correction settings.
Devices
Manage processing profiles. Create and edit named profiles that specify base data sources and settings
Processing Profiles
for post -processing.
Create Projection File (PRJ) from Coordinate System (for Pathfinder Office)
Other Functions
Manage field configurations for ArcGIS for Windows Mobile workflows. Create and edit named
Field Configurations
configurations that specify real-time correction source hierarchies and settings.
• Click the Create button in the Projects Window.
TFiMble Positions Desktop Administration - Projects
Name Type MXD filename Compatible Workspace
t III �
Create... Edit... Remove Set Current Set M}{D OK
Revised 24 June 2016

NCDO-
Higkiway
Field Inventory Procedures Manual
• In the Create Project Window, select ArcPad from the drop down at the top of the window. Check the GNSS and
Datum Transformation settings. If everything is working fine then you should see a large green checkmark
symbol in the Map Document Compatibility area, as in the example below.
Create Project
Project Type: ArcPad
1. Project Type
Map Document Compatibility:
0 Map document can be used with Trimble Positions.
Datum Transformation for GNSS Data (in WGS84)
Map coordinate system: NAD_1983_StatePlane_North _Carolina _FIPS_3200_Feet (2264)
Map datum: D_North_American _1983 (6269)
Transformation to use: NAD_1983_To_WGS_1984_8 (1702)
[found in map] Chang,
Start Cancel
• Click the Start Button to proceed to the next window to set Layers for the project. Make sure that all the
available layers are checked in the listing.
Create Project - ArcPad
Workspace:
NCID 0T_FIP.mdb -I
1. Layers
Available layers:
2. Layer Settings
Layer
' Feature Class Alias Information '
0 BMPExisting
BMPExisting
3. Project Settings
0 Bridge Locations
NCDOTBridgel-ocations
Channel
Channel
ChannelPoint
ChannelPoint
Culvert
Culvert
® DeckDrains
DeckDrains
® Hydro line
hydromaLarc
® Hydro polygon
hydromaLpoly
® IllicitDischargePoint
IllicitDischargePoint
® Inlet
Inlet
FUT .I nhWnrkArea
.InhWnrkArea
1
III
® Hide incompatible layers
that cannot be used
C Next> Cancel
� � I I
Revised 25 June 2016

c_-
Highway
Stormwater
• Click the Next Button to go to the Layer Settings Window.
Create Project - ArcPad
1. Layers
2- Layer Settings
3. Project Settings
Workspace:
Selected layers
Layer
BMPExisting
Bridge Locations
Channel
ChannelPoint
Culvert
D eckD rains
Hydro line
Hydro polygon
I IlicitD ischargePoint
Inlet
JobWorkArea
Junction
Field Inventory Procedures Manual
NCDOT FIP.mdb
Metadata Transfer —
Feature Class
'for offrce-vde processing orajv
BMPExisting
Horizontal Estimated Accuracy:
N CD O T B ridgeLocations
Channel
ChannelPoint
=_ Vertical E stimated Accuracy:
Culvert
DeckDrains
Feature Height:
hydromaLarc
hydromaLpoly
I IlicitD ischargePoint
Inlet
JobWorkArea
Junction
Accuracy Threshold
• Click the Next Button to go to the Project Settings Window.
Create Project - ArcPad
1. Layers NCDOT_FIP
Map document:
2. Layer Settings NCDOT FIP
Accuracy reporting: 'for offrce-nde processing 0'*
3. Project Settings BB% Circular Error Probable (DEFAULT)
Feature heights:
* Use height above ellipsoid (HAE)
(E) Apply fixed geoid separation (m)
® Calculate geoid separation from file:
Horizontal (m):
® ext > Cancel
Set as the current project 0
< Back Finish Cancel
• You should see the following results window if the project was created successfully.
Trimble Posit oos Desktop add -in
i Successfully created new project [NCDOT_FIP].
Revised 26 June 2016

NCDO-
Higkiway
Field Inventory Procedures Manual
• Projects Window with newly created project. Click the OK button to return to the Administration Window.
Trimble Positions Desktop Ad mini strati on -Projects
Name Type MXD filename Compatible Workspace
NCDOT_FIP ArcPad NCDOT_FIP Yes
Edit... Remove Set Current SetMXD OK
Checking Out Data from ArcGIS Desktop for use in ArcPad
• On the Trimble Positions Toolbar in ArcMap, select the Trimble Positions Desktop Dockable Window Visibility
button 01 to open the Trimble Positions window.
• Click the Check Out/In button in the Trimble Positions window, then select Check Out to AXF to ArcPad from the
drop down menu.
Trimble Positions Desktop ❑
Sessions: Current project: NCDOT_VAtestl Display session outlines
Check 0,t/1nllllllllllllllll� Correct... View Features Update Features Remove Zoom To
FlCheck Out AXF to ArcPad
Check In AXF+SSF from AFcPad V
Revised 27 June 2016

NCDO-
Higkiway
• The Welcom screen will display, click the Next button
• The Select Data window will
display the available layers.
Check to make sure the desired
layers for the field data
collection project are set to
Checkout Data. See steps below
for setting background layers
and editable layers. When
complete, then click Next.
Field Inventory Procedures Manual
Gel Data For ArcP d - welcome ®P
The Get Data For ArcPad wizard allows you to get data for layers
represented in the active data frame and create the data in a Folder
that can be transferred into a mobile device for use with ArcPad.
Geodatabase layers and their related tables can be checked out for
editing in ArcPad. Any Feature or raster data in the active data
Frame can Le copied out, You can also copy out any graphics
present in the map, The wizard will guide you through the steps to
configure,
wWhich data layers represented in the active data Frame that you
uld like to copy out or check out.
• Which data layers (or related tables) will have pictures allocated
to it, and where those pictures will be put on check in.
• The extraction criteria and the output location.
Geodatebase data checked out From the Get Data For ArcPad
wizard can be checked in via the Get Data from ArcPad tool in
ArcMap or the ArcPad Check In geoprocessing tool.
I]oo not show. this welcome page again;
C Back ® Cancel
Get Data For ArcPad - Select Data
NW ®®
Choose the layers you wank
to get From the map.
Nate: Only layers that have
the map's spatial reference can be checked out.
Layer
'
Action
Folder
0
1[}13MPExisting
`
Checkout Data
C:INCDOTINCDOT_,,,
ChannelPoint
`
Checkout Data
C:INCDOTINCDOT_...
7
d DeckDrains
'
Checkout Data
C:INCDOTINCDOT_...
WO
QIllicitDischargePoint
`
Checkout Data
C:INCDOTINCDOT_,,,
R
O Inlet
`
Checkout Data
C:INCDOTINCDOT_...
WO
d ]unction
'
Checkout Data
C:INCDOTINCDOT_...
WO
QLandPoint
`
Checkout Data
C:INCDOTINCDOT_,,,
R
0 OverlandFlow
`
Checkout Data
C:INCDOTINCDOT_...
r
d Photo
'
Checkout Data
C:INCDOTINCDOT_...
F
QPipeIO
`
Checkout Data
C:INCDOTINCDOT_,,,
IW
dPipePoint
`
Checkout Data
C:INCDOTINCDOT_...
r
1pollution5ource
11111,
Checkout Data
C:lNCDOTlNCDOT
... W
C Back Next >
Cancel
Background data layers can be any data
that needs to be displayed for context.
You will need to edit the default ArcPad
map documents later to add these
background data layers into the ArcPad
mapping tools. Background data layers
should be exported to the ArcPad project
by selecting:
Export as background data (to AXF Layer)
—Make Read Only
Get [)at, For ArcPad - Salad Dales
Choose the layers you want to get From
Note: Only layers that have the map's
P7 A
the map,
spatial reference can be checked out.
0. a
Layer , Action Folder
OPIpeIO
'
Do not export
C:VNCDOT�NCDOT_..
■
PlpePoint
1
Do not export
C:VNCDOT�NCDOT_.,.
■
a
4�Pollution5oures
'
Do not export
C:)NCDOT�NCDOT_.,.
■
�PcrentialRetrofit
1
Do not expert
C:)NCDOT�NCDOT_.,.
■
e Channel
'
Do not export
C:)NCDOT�NCDOT_.,.
■
Culvert
,
Do not expert
eVNCDOT�NCDOT_.,.
■
e Pipes
'
Do not
O NCDOT NCDOT .,.
■
Do note port
®FFx_Countyschools
]obWorkArea
Export as background
data (to Shapefile)
Make Read Only
Export as background data (to AXF Layer)
Make Edltable
I 1
of
C Back
Next > Cancel
Display session outlines J
Revised 28 June 2016

NCDOT
pw--,
Editable data layers should be set to:
Check Out for disconnected editing in
ArcPad — Data based on defined
extent
Field Inventory Procedures Manual
Get Data For ArcPad -Select Data
®®
Choose the layers you want to gat from the map,
Note, Only layers that have
the —', spatial referen an
be checked out,
o� C
Layer
, Action
Folder
06MPE%Isting
' checkout Data
C:(NCDOT(NCDOT...
r
t]
QChanne1—t
' Checkout Data
I DOT(NCDOT
... r
a
QD,Mralns
' Checkout Data
C NCDOT NCDOT
... [
=
m
DonotaP-
Qlnlet
/
0lwctlon
Check Out for d—
... eded edging in ArcPad
Data based on defied a -t
QLdndPOlnt
,
import as background data (to Shapefile)
I
Schema 6nlv(start with bla nk data set}
Q^OverlandFlow
Expon w background data (m AXF layer)
J Photo
,
QPipe10
Do not export
C:yNCDOTyNCDOT_...
r
�PioePoint
/ Do not export
C:INCDOTINCDOT
❑ X
c Back Next > Cancel Display session oullinw 0
NOTE: The Check Out tool will use the visible extent from
your ArcMap map window by default. Your map should be
set so that you can see the entire JobWorkArea extent for
the current project area or else the data will not export the
proper area of interest. You can check that the extent used
for the project is set to the Current Visible Extent in the Data
Frame Properties dialog box. See example on right.
Revised 29 June 2016

NCDO-
Higk;<way
• Use the Select Picture Options to determine which
fields are used to store photo links. With the
upgrade to ArcPad version 10.2, the FIP database
and tools have been updated to support 3 photo
linking fields, as specified in the example below.
Once you have verified the Picture Fields, click
Next.
• The Select Output Options allows to specify
the name of the folder that will be created to
store the data. The tool will automatically
increment the number at the end of the file
name from the previous data folder name.
You can type in a different name, if desired, as
well as change the storage location. Make
sure the Create an ArcPad map (.apm file) for
the data checkbox is selected, and that it has
a Map name. Click the Next button to
continue.
NOTE: The location of the MXD, Data Folder,
and APM file must not change until the data is
checked back in, or else Check In might fail.
Field Inventory Procedures Manual
Get Data For ArcPad - Select Picture Options ®®
Layer
Picture Field(s)
Q BMPEAi Ling
, Photol, Photo2, Photo3
0 ChannelPoint
, Photol, Photo2, Photo3
0 DeckDrains
, Photol, Photo2, Photo3
Q IllicitDischargePoint
Photol, Photo2, Photo3
Q Inlet
Photol, Photo2, Photo3
0 ]unction
Photol, Photo2, Photo3
Q LandPoint
Photol, Photo2, Photo3
Q OverlandFlow
' Photol, Photo2, Photo3
Q Photo
' Photol, Photo2, Photo3
!
III
r
Copy pictures to this folder when checking in data. (e.g ��yourpc�pictures)
41
❑r' Keep path of existing pictures in data.
C Back Next 7 Cancel
Get Data For Arc Pad -Select Output Options
[=®1
What data do you want?
Spatial extent: The current display extent 0
] Only get selected Features
l� Only get features specified in layer's definition query
❑J Only get fields specified as visible in layer's properties
Specify a name for the folder that will be created to store the data:
DataForArcPad9
Where do you want this folder to be stored?:
C: �NCDOT�ArcPa d_Data
[0 Create an ArcPad map (•apm file) for the data Map name: NCDOT_FIP apm
© Encrypt checked out data Password:
Q Validate feature classes before checking out
• In the Select Deployment Options Window, make
sure the Create the ArcPad data on this computer
now option is checked. Click the Finish button to
complete the process.
Back Next > I I Cancel
Get Data For AICPad - Seled Deployment Optiom I®
Data deployment options
After the data is created:
❑ Create .ZIP file containing the ArcPad data
❑ Create ready to deploy .CAB File containing the ArcPad data
•d• Create the ArcPad data on this computer now
Save this configuration for now and create ArcPad data another time
[ Back Finish Cancel
Revised 30 June 2016

NCDO-
Higkiway
•
You should see a status window like the one on the right
display if the data was successfully created.
Field Inventory Procedures Manual
Get Data For ArcPad ®®
Operation successful
Report:
Output Folder: C:�NCDOT�ArcPad_DatalDataForArcPad9 1
Map Name: NCDOT_FIP.apm
Projection: NAD_1983_StatePlane_North_Carolina_FIPS_3200_F
Total Layers: 17
Total Feature Layers: 17 (17 succeeded)
Total Image Layers: 0 (0 succeeded)
Graphics Layer Exported: No (not attempted)
Check in photo Folder will be: Not set
Keep photo paths in AXF File: No
Zip File created: No (not attempted)
Deployable CAB file created: No (not attempted)
rrr r
OK
The "DataForArcPad" folder should now contain newly created files.
Open the log file named NCDOT FIP mdb.axf.1og using NotePad or a similar text editor to confirm there were
no errors. See example on the right.
Name i
t1DataForArcPad.axf.xml
L�J� ExistingBMP.apm
1` LJIllidtDischarge.apm
141 ncdot.apm
ncdot.apm.bmp
NCDOT_FIP_mdb.axF
I illL�JOverlandFlow.apm
140 PhotoPoints.apm
14'1 pollution5ource.apm
L��J� Retrofit5pace.apm
L�`�J� tieria.apm
�4�1� tierib.apm
L��J� tieric.apm
L�`�J� tierii,apm
141 tieriii.apm
- I 01J
File Edit Format View Help
2012-03-16 18:22:10
Logging started
2012-03-16 18:22:10
MEMORYSTATOS
Load: 72%
Physical: Total-2096452
kb Avail-574824
kb
virtual: Total=2097024
kb Avail=1369404
kb
Page: Total=4194303
kb Avail=4194303
kb
?012-03-16 18:22:10 »
Loading schema
?012-03-16 18:22:10 >>
Loading tables
?012-03-16 18:22:10 »
Elapsed time Oms (TO)
?012-03-16 18:22:10 s>
Loading layers
1012-03-16 18:22:10 >>
Elapsed time Oms (TO)
?012-03-16 18:22:10 »
schema loaded : 15ms (T1)
2012-03-16 18:22:10 >>
Loading schema
1012-03-16 18:22:10 a>
Loading tables
?012-03-16 18:22:10 »
Elapsed time Oms (TO)
?012-03-16 18:22:10 >>
Loading layers
?012-03-16 18:22:10 »
Elapsed time Oms (TO)
?012-03-16 18:22:10 s>
schema loaded : Oms (T1)
2012-03-16 18:22:10
Logging Ended
2012-03-16 18:22:10
MEMORYSTAT05
Load: 72%
Physical: Total=2096452
kb Avail=575152
kb
virtual: Total=2097024
kb Avail=1368876
kb
Page: Total=4194343
kb Avail=4194303
kb
J
Update ArcPad Project Data Collection Forms for Tablet Screen Size
• By default the Trimble Positions software configures the data collection forms in the APM file for use on small
screen mobile devices. In order to reformat the forms to be viewed and used on larger screens such as Windows
tablets, the NCDOT AXF Forms Tool must be run on the project file.
• After completing the Check Out process using the Trimble Positions tool, update the tier and module project
files (APM) by running the "Update Axf File" tool. This tool was previously part of an ArcMap custom toolbar
called NCDOT FIP toolbar. Now it functions as a standalone application.
Revised 31 June 2016

NCDO-
Hig_Way
- Field Inventory Procedures Manual
• Run the tool by double-clicking on the Name Date modiFied size
AXFTooI_NCDOT.exe file, which should be
located in the c:\NCDOT\ folder of the GIS data 6f 1J2016 3:36 PM
Workstation, or alternatively, follow instructions AXFTool_NCDOT.exe 5f27f2015 4:58 PM 13 KB
in section XI. Installation Procedures to add a
shortcut to the AXF Forms Tool and use the shortcut to run the application. Browse to the folder where the
saved NCDOT_FIP_mdb.axf file that was just created in the previous steps is located and click the Update AXF
button.
ao AXF Tool For NCDQ_ E3
ArcPadAXF File : CANCDOTWcPad_DatalDataForArcPad101%CDOT_VA WE!!!
Revised 32 June 2016

NCDO-
Higki<way
Field Inventory Procedures Manual
Setting Up ArcPad for Field Data Collection
Important!
The result of the prior step will be a compressed database file in .axf format. This .axf file MUST be placed into a
specific directory for the application to work successfully. Additionally, the ArcPad application is "hard -coded" to
expect a particular file name for the .axf file ("NCDOT_FIP_mdb.axf").
For a root application path of "C:\NCDOT_FIP", the processed .axf file will be found in
"C:\N CDOT_F I P\AX FToo I\data".
Copy the just created NCDOT_FIP_mdb.axf file (together with the .axf.log, and .log files) from the "AXFTool\data"
directory. Paste these files into this directory: "C:\NCDOT FIP\ArcPad_applet\DataForArcPad".
1 nese data layers need to be present In the oUtpl
f4 NCDaT_FIP_mdb.axf IEI0®
El-0 I��r*IfS"i
p...� Feature Layers
E7 �% BMPExisting
p g Channel
p...�% ChannelPoint
❑+-<i�> Culvert
p <�% DeckDrains
E ­� IllicitDischargePoint
p a Inlet
❑+... JobworkArea
p...d Junction
E7 �% LandPoint
p...d 4verlandFlow
17...�% Photo
p...d PipeIC
p <�% PipePoint
E7...<i�> Pipes
PollutionSource
❑+ � PotentialRetrofit
p...� Feature Tables
❑+.-J Data Tables
kj, Files
El t& Properties
Ei Spatial Information Schema Tables
rrr
t .axf file for all functionality in ArcPad to work:
Revised 33 June 2016

NCC0-
Highway
Field Inventory Procedures Manual
Procedure to configure ArcPad HP settings:
Launch ArcPad to configure the required settings. ArcPad stores specific configurations in a file
called an applet (.apa). The NCDOT FIP application requires the applet called ncDotTool.apa that's
stored under the project directory. Perform the following:
When ArcPad launches, you may be prompted to open a default map or create a new map. Do not open
the default map. If you see this interface, click the' ' in the upper right corner:
Welcome to ArcPad I 11 II
Please select ho-n- you wish to start
NeN map
Create a QuidkProject
r Choose map to open
® Open last map used
F- Set as default and don't ask again
Revised 34 June 2016

_c
Highway
Stormwater
2. If you see this interface. click the red 'Y'.
Field Inventory Procedures Manual
J Open Map
x
4
►
Name
Folder
Date
IllidtDischarge.apm
C:iNCDOT_FIP)ArcPad_appletWataForArcPad 2017-12-2713:28
NCDOT_FIP.apm
C:V4CDOT_FIP�ArcPad_applet�DataForArcPad 2017-12-271:28
NCDOTTIP Testl.apm
C:3NCDOT_FIP�CHECKO"CDOT Testl 2017-12-2711:03
OverlandFlow.apm
C:�NCDOT_FIPOrdDad_applet3DataForArcPad 2017-12-2713:28
PhotoPoints.apm
C:3NCDOT_FIPOrd}ad_applet}DataForArcPad 2017-12-271:28
pollutionSource.apm
C:1P4CDOT_FIIDOrcPad_applettipataForArcPad 2017-12-2713:28
Retrofit5pace.apm
C:1P4CD0T_FIPOrcPad_appletipataForArcPad 2017-12-2713:28
tieria.apm
C:1r4CD0T_FIPOrcPad_appletlpataForArcPad 2017-12-2714:02
tierib.apm
C:iNCDOT_FIP'ArcPad_applet3pataForArcPad 2017-12-271:28
tieric.apm
C:iNCDOT_FIP�ArcPad_applet3pataForArcPad 2017-12-271:28
tierii.apm
C:�NCDOT_FIP)ArcPad_applet3pataForArcPad 2017-12-271:28
tieriii.apm
C:}NCDOT_FIP)ArcPad_appletlpataForArcPad 2017-12-2713:28
< c�3
c5o)
+
Revised 35 June 2016

NCDO-
Higk;<way
Field Inventory Procedures Manual
Once a blank ArcPad session starts, click "Options" under the main ArcPad toolbar and select the "Paths"
to b.
Urditied - A rcP ad
jX
Under Other "Additional Paths", browse to the location for the new applets ("ArcPad_applet") and click
"OK".
4:= ArcPad Options
Display [] Camera CT Paths General
Default Maps & Data Path
Navigation Server ►
C:`..NCDOT_FIP
Public Files Path
C:INCDOT_FIP
Other Additional Paths lApplets
C:`..NCDOT_FIP`._"rcPad_applet
00
5. A message will pop up stating "Some preferences may have changed that require a restart to take effect".
Click "OK" and exit ArcPad.
Revised 36 June 2016

NCDO-
Higk;<way
Field Inventory Procedures Manual
6. Re -open ArcPad and again cancel the default map interface that appears. Under the NCDOT Toolbar select
the "Setup" button. This allows the selection of the current job work area, field crew, firm name and type
of study.
Untitled - ArcPad
— V /
-0
f k J
10
T T T T
Study Info
7.1 Setup
Job ID:
Iobl
Field Crews: Firm Name:
crewl firml
Sel&zt type of study:
.........................�
Identification of true outfalls to
waters of the state at or within the
RO'V-, boundary (known as a
NCDOT outfall)
00
Using this tool to select the type of data entry will open a pre -configured ArcPad map document (.apm) for the
selected data layers. This will also have the effect of closing any other open ArcPad map documents that you
might have had open. These pre -configured .apm files are located at this path ("DataForArcPad") within the
ArcPad_applet directory.
The pre -configured .apm files are named:
ExistingBMP.apm
I IlicitDischarge.apm
OverlandFlow.apm
Revised 37 June 2016

�Cco-
Highway
PhotoPoints.apm
pollutionSource.apm
RetrofitSpace.apm
tieria.apm
tierib.apm
tieric.apm
tierii.apm
tieriii.apm
Field Inventory Procedures Manual
There is also a "master" .apm named: NCDOT_FIP.apm which could potentially be used to reconstruct the
other .apm files.
Procedure to add new default background data layers:
It is possible to edit these .apm files (to add default background data layers for example), but be extremely careful
when altering these files that you don't change any existing layer names, as this may break the application
functions. If you do want to alter these pre -configured .apm files, please make sure that you have a backup copy of
the directory first, make your changes, and then test ArcPad with the modified .apm files.
To add background data layers, perhaps from your previously created .axf data file, follow this procedure:
1. Within ArcPad, open the .apm files that you want to edit. For example, open the "tierla.apm" file from
the "DataForArcPad" directory.
Open the map file browser dialog:
Revised 38 June 2016

NCDOr
--
Open Map
Field Inventory Procedures Manual
C
_ Name
Folder
W Dath
ExistingBMP.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
IllidtDischarge.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
NCDOT_FIP.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
NCDOT_FIP Testl.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2711:03
OverlandFlow.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
PhotoPoints.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
pollutionSource.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
Retrofit5pace.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
tieria.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2714:02
tierib.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
tieric.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
tierii.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
tieriii.apm
C:lprojects)NCDOT_ArcPadWCOM_testingyj ...
2017-12-2713:28
0.J, .+z
2. Next, add the desired background layers from .axf files (or even from shapefiles, potentially):
In�X
In this case we are adding "Bridge Locations":
+ Add Layer(s)
PathC:1ProjectslJdCDOT_ArcPad%AECOM_testing%NCDOT_FIP +
�aui��•x.�w.aim_u.acu.•s3�iu�s�.n.in�iw.ai�r�a �
ArcPad_applet
i$ DataForArcPad
AXFToal
CHECKOUT
jo NCDOT Testl
J ]<�} Bridge Locations
3. Make sure to save your changes to each edited .apm file.
Revised 39 June 2016

NCDD'
Y'.UL: Al
Field Inventory Procedures Manual
Close ArcPad and reopen. Then access the modified map files using the FIP toolbar settings tool, as discussed
earlier.
Background on scripting and code files:
Other internally used files include the .apa file (ArcPad Application) which points to a .vbs (Visual Basic Script) file.
This .vbs file contains all of the application logic for the FIP tool. The .apa file links the ArcPad tool buttons to the
proper code functions in the .vbs file. These files are located in the "ArcPad_applet" directory. At this location
there are also default data values files (.txt and .dbf format files) as well as several icon files (.ico) used in the
ArcPad application. Don't modify any of these application specific files without having a back up of the entire
directory. In the "Data ForArcPad" directory, you will find the .apm map files that are pre -configured to reference
data in an .axf data file named: "NCDOT_FIP_mxd.axf'. If this file does not exist, the application will fail to launch
and there will be various error messages. Within each custom ArcPad map (.apm) file, there are also references
from specific layers and data columns to code functions within the .vbs code logic file. These script functions are
typically used to perform "validation" to require certain columns to be filled out before allowing a new feature to
be added successfully.
Checking In and Correcting Field Data from ArcPad
When the field inventory has been completed, the data should be post -processed using the FIP recommended
method. The FIP recommeds using the Trimble Positions extension for ArcMap. This method allows for a seamless
check -in and differential correction process within ArcMap. For detailed information regarding the Trimble
Positions extension refer to the Trimble support site:
http://www.trimble. com/mappin,izGIS/trimblepositions. aspx?tab=Technical_ Support
Data Check In
The step-by-step process below describes the check -in process using the Trimble Positions extension in ArcMap.
• Copy the data from the data collection device to a location accessible on the GIS workstation where the project
was orginally created. Open the Map Document File (MXD) used to create the data collection project
(NCDOT FIP.MXD). Turn on the Trimble Positions desktop extension, if is not already on. If the Trimble Positions
Desktop Dockable window is not open, then open it by selecting the 0� button on the Trimble Positions toolbar.
Click on the Check Out/In button, and select Check In AXF+SSF from ArcPad.
Revised 40 June 2016

r:ccr.
Highway
Trimble Positions Desktop i
Sessions: Current project: NCD O T_VAtest
Device Start Time ' End Time Notes
:heck Out/In J L Correct.
Check out AXF to ArcPad
Check In AXF+SSF from ArcPad
Field Inventory Procedures Manual
❑ x
Display session outlines J
Status
View Features Update Features Remove Zoom To
• In the Check In ArcPad AXF files window, click
the Browse button and find and select the
project AXF file (typically located at
c:\NCDOT\ArcPad_Data\DataForArcPadXX, the
AXF file will typically be named
NCDOT_FIP_mdb.axf).
• Select the Geographic Coordinate System,
which should be: GCS North American 1983
• Click the Check Contents button to view the
data available in the AXF to verify that the
correct project is selected.
• Click the Check In button if everything looks
correct.
Check in ArcPad AXF files
KX
Current project: NCDOT_VAtest
Select AXF file:
C:INCDOTIArcPad_DatMDataForArcPad1%NCDOT_VAtest_mdh.axf Browse..
Coordinate system for real-time corrections (if applicable):
GCS —North _American _1983, NAD_1983_To_WGS_1984_8
—Select...
AXF file password:
Check Contents
Layer name New Edited
Deleted '
0 BMPExisting 1
O 0
t"❑ ChannelPoint 0
0 0
© DeckDrains 0
0 0
t"❑ IllicitDischargePoint 0
0 0
rIl Inlet 0
f rrr
0 0
r
Check In
• You should see a dialog box similar to the one below, with the number of features reflecting the
numbers from your project.
Trimble Positions Desktop add -in
Checked -in 4 feature(s) out of 4 new and modified features in the AXF
file.1 feature(s) were added to Trimble Position session(s). Please see
log file for more information.
0K
• If you select the current project in the Trimble Positions Desktop Dockable window, then click the
Correct... button.
Revised 41 June 2016

lCco-
Highway
PRO " ..ice
Field Inventory Procedures Manual
Trimble Positions Desktop
Sessions:
Current project: NCDOT_VAtest
❑ X
Display session outlines
Dra to group by t
Device Start Time
End Time Notes
Status
Device 1 612120161.0.35AM
612120161.0:39AM
Waiting For Correction
Check Outlln... Correct...
View Features Update Features Remove
Zoom To
• If you see the dialog box warning on
the right then you will need to setup
a Processing Profile. See section
below specific instructions.
Trimble Positions Desktopaddkin
Please set-up a profile in the Trimble Positions Desktop Administration
form.
4K
Setting Up a Processing Profile for Correction of GPS data using Trimble Positions
• Open the Trimble Positions Desktop
Administration window using the 01
button on the Trimble Positions
toolbar.
• Select the Processing Profiles button.
• Click the Create button in the
resulting window.
Trimble PosRVOns Desktop Administrati on
Positions Desktop add in version 10.3. 0.2, Copyright o 2012 2015 Trimble Navigation Limited
Current oroiect. NCDOr vntect
Connected[,: Tri.blePosmons_1
Projects Create, edit and delete projects. Export projects to field databases.
Manage field devices Assign processing profiles with differential mnecticn settings.
Processing Profile' Manage processing profiles. Create and edit named profiles that specify hale data sources and settings
for post -processing.
Other Functions Deate Proi-t,cn File (PRJ] from Coordinate System (for Pathfinder Office]
Field Configurations Manage field configurations for ArcGIS for Windoms Mobile workflows. Create and edit named
configurahons Mat specify real-time coinecti,n sou,oc hieraichies and settings.
Trimble Positions Desktop Ad ministration - Processing Profiles
Fickle Name Description
Create__ Edlf_ Remove OK
Revised 42 June 2016

`CCo-
Highway
• Enter a Profile Name, typically
this should reflect the name of
the data collection project or
project area.
• A Base Provider must be created
by clicking the Select button.
Field Inventory Procedures Manual
Edit Profile
Profile Name: Little Alamance
Search for Base Data:
;oUsing a single base station
North Carolina Geodetic Survey, Raleigh Select._
® Using a folder or specific base files
Cancel OK
• The base stations files are downloaded from Continuously Operating Reference Stations or CORS sites
stored on ftp sites and automatically retrieved as needed by the Trimble Positions software. In the
Select Base Station window, in order to display a current list of available Base Stations, select The city
and search for a city nearest the data collection site, or select the Current map center option, which
ever works better on a case -by -case basis. See example below.
• If needed, select the Update List button to refresh the list of CORS sites and select the appropriate
base provider. Click "OK" to accept the selection.
• If your base provider is within 50 miles (80km) of your job work area it is recommended to use only a
single base provider. If your base provider is outside 50 miles (80km) of your job work area it is
recommended that you use three base stations to process vour data.
Select Base Station
Show Base Stations Closest to:
The city:
Current map center
Show Base Stations within:
1 1000 km
W9
Base Station
Distance
o
North Carolina Geodetic Survey, Raleigh
COPS, RALEIGH DOT (NCRD), NORTH CAROLINA (ITRFOO (19971-Derived from IGS...
0 cm
6 km
COOP _CORS, Durham, NC
33 km
COPS, DURHAM COOP (DURH), NORTH CAROLINA (ITRFOO (1997)-Derived from I...
33 km
COPS, JORDAN LAKE (NCJL), NORTH CAROLINA (ITRFOO (1997)-Derived from IGS...
36 km
COPS, SMITHFIELD (NCSF), NORTH CAROLINA (ITRFOO (1997)-Derived from IGS08...
37 km
CORS, LILLINGT0N 2004 (NCLI), NORTH CAR 0LINA (ITRFOO (1997)-Derived from I...
44 km
COR5, SANFORD (SNFD), NORTH CAR 0LINA (ITRFOO (1 997)-D erived from I6508 (...
58 km
CORS, NASHVILLE (NCNA), NORTH CAR 0LINA (ITRFOO (1 997)-D erived from IGS08...
59 km
COPS, WILSON (NC L), NORTH CAROLINA (ITRFOO (1997)-Derived from IGS08 (N...
64 km
Show Base Stations of Type: All types
] Only show base stations supporting GLONASS
Base Station
New... Copy... Properties... Delete...
Update List
OK Cancel
Revised 43 June 2016

_c -
Highway
Stormwater
• Click OK to Accept the new
Processing Profile.
Field Inventory Procedures Manual
Tnmbl e P ositi ore Desktop Ad ministration - Processing Profiles
Profile Name Description
Little Al—arrice Single base station [North Carolina Geodetic Survey, Raleigh]
Geale... Edit... Remove DK
Revised 44 June 2016

`CDO-
Higkiway
Field Inventory Procedures Manual
Data Check In — Continued
• Continue through the wizard once the Processing Profile has been created. Click "Start" to begin the
differential correction process. Select the Correct... button to begin the GPS correction process.
Trimble Positions Desktop
❑ x
Sessions:
Current project: NCDOT_VAtest
Display session outlines 0
Drag a column header
here to group by that colu
Device
Start Time
End Time Notes
Status
Device 1
U2120161 0:35AM
U21201610:39AM
Waiting For Correction
Zoom To
Check Out/In...
Correct...
View Features Update Features Remove
• In the Correct Sessions dialog
window (example at right), select the
Sessions to Correct and pick the
Processing Profile to Use for this
session. Then select the Correct
button.
0
Processing Profile to Use:
0 Delete previous downloads
Correct
• As the differential process completes, the summary will indicate the number of corrected features
and the estimated accuracy for the corrected positions. Close the interface.
Revised 45 June 2016

�Cco-
Highway
ifigwlaiwo1 Field Inventory Procedures Manual
C. Field Crew
The IP Manager will provide a version of the FIP geodatabase to the field crew to use with the FIP application.
Field crew will follow procedures described in this document and perform field QC to confirm their methods of
collection are accurate.
The IP Manager will provide the field crew with Public Notification letters to be distributed to property owners. If
access to private property is denied, the field crew is responsible for notifying the IP Manager immediately. The IP
Manager will provide guidance to the field crew.
The field crew will notify NCDOT of any illicit discharge or hazardous structure conditions immediately and provide
photos of the issue. The IP Manager will notify the appropriate personnel immediately and provide guidance.
The field crew is responsible for attending a NCDOT Safety Training class and for adhering to NCDOT safety and
traffic control policies. See Section VI: SAFETY & TRAFFIC CONTROL.
Once the field crew has reviewed the FIP geodatabase for any potential errors, the geodatabase is provided back
to the IP Manager for review and validation.
D. HSP Geodatabase Manager
The role of the HSP Geodatabase Manager is to provide a version of the FIP geodatabase to the IP Manager, review
the FIP geodatabase provided by the IP Manager and resolve any conflicts with the Master FIP geodatabase.
Although the HSP Geodatabase Manager does not perform a review for accuracy or completeness, internal checks
must be performed before incorporating data into the Master FIP geodatabase.
http://surveying-mapping.duncan-parnell.com/GPS-Mapping-Support.html
1. ArcPad 8 Settings with Trimble GPScorrect
2. Configuring and collecting features with a TruPulse Laser in ArcPad
http://www.trimble.com/mappingGIS/yuma rugged tablet.aspx?dtlD=technical support
3. GPS Pathfinder ProXH and ProXT Receivers: Setting up a Bluetooth Connection through a Yuma Rugged
Table Computer
4. Trimble Yuma Tablet Computer: Connecting to the Internal GPS Using Mapping & GIS Field Software
http://www.trimble.com/mappingGIS/gpsanalyst.aspx?dtlD=technical support
5. Trimble support site for GPS Analyst extension for ESRI ArcGIS software
http://www.trimble.com/mappingGis/pathfinderproxrt.aspx?dtlD=technical support
6. GPS Pathfinder ProXRT Receiver: Bluetooth Connection
Revised 46 June 2016

NCDO-
Higkiway
Iftw-., Field Inventory Procedures Manual
IV. Feature Attribution and Sub -Meter Location
A. What is a Stormwater System?
A stormwater system is a series of inlets, manholes/junction boxes, interconnected pipes, outlets and open
channels that form a network of conveyance systems for the collection, transmission, and treatment of
stormwater discharges from developed areas (for example, NCDOT roadways). These features, described in more
detail below, are captured with the FIP on an as needed basis.
Stormwater inlets typically are placed at low points in the terrain allowing stormwater to collect and flow by
gravity into the inlet. Inlets may also be located on continuous grades of roadways to periodically collect runoff
and limit the spread of water to acceptable widths for the transportation facility.
Unlike inlets, manholes/junction boxes are not designed to allow stormwater to enter the stormwater conveyance
system. Manholes/junction boxes are useful in many ways in a stormwater conveyance system. These structures
can be used to change flow direction, provide a box to junction two or more pipe systems into one system, and/or
to provide points of access to a stormwater conveyance system for maintenance. Stormwater structures, such as
inlets and junctions, will be collected as point features in the FIP.
Most stormwater pipes typically drain by gravity but in rare instances may flow under pressure. Pipes in a
stormwater system are typically constructed of reinforced concrete (RCP) but can be made from corrugated metal
pipe, vitrified clay, ductile iron, PVC, corrugated polyethylene (hard plastic), etc. Pipes will be collected as linear
features in the FIP.
While stormwater pipes can exist in a variety of geometries, most stormwater pipes are circular and are described
by diameter (expressed in inches). By convention, most pipes are made to standard sizes. Stormwater pipes sizes
beginning at 12" typically increase by a three inch (3") increment until the pipe size reaches eighteen inches (18").
Pipes larger than 18" typically increment larger by six inches (6"). Commonly encountered pipes sizes include 12,
15, 18, 24, 30, 36, 42, 48, 54, 60, 66, and 72 inches. Pipes larger than 72" in diameter or equivalent size are
typically located at stream crossings under roadways (culverts).
Other pipe/culvert geometries may be encountered in the field. The most common other geometries are elliptical,
rectangular (box), arch (w/natural bottom), arch pipe, or other. Pipes that match these geometries will be
dimensioned by rise (height) and span (width) and will be expressed in feet.
The point at which an enclosed pipe system enters from or is released to an open channel is known as a pipe
inlet/outlet. The PipelO feature may be found discharging to either a natural waterbody such as a lake, river, or
stream, or to a manmade channel or Best Management Practice (BMP) such as a detention basin. In some cases
the PipelO may actually be an outfall to waters of the State.
Often a stormwater system contains open conveyances such as roadside swales, rip rap lined channels etc. Open
channels can have varying geometric shapes and also can be MP's captureing and infiltrating stormwater via
natural soils or underdrains.
Revised 47 June 2016

NCDO-
Higk;<way
Field Inventory Procedures Manual
NCDOT has a NCDENR Permit No. NCS000250 that defines an outfall to mean a point source at the point where a
municipal separate storm sewer (MS4) discharges to waters of the United States and does not include open
conveyances connecting two municipal separate storm sewer, or pipes, tunnels or other conveyances which
connect segments of the same stream or other waters of the United States and are used to convey waters of the
United States (40 CFR 122.26 (b) (9)).
Under the same NCDENR permit, a stormwater discharge outfall (SDO) is defined as a point of stormwater
discharge to waters of the State (streams, wetlands, open water). An outfall is not restricted to pipes and includes
any type of conveyance or any discharge from a BMP that discharges to waters of the State.
Identification of waters of the State and outfalls for the FIP are discussed in detail in the Technical Memorandum
"NPDES MS4 Outfall Identifications Guidelines".
The purpose of a BMP or stormwater control is to provide flood quality and quantity control. A BMP facility is
typically designed to allow for the removal of pollutants prior to flow discharge to a lake, river, or stream. To
decrease erosion potential and/or improve aesthetics in developed areas, a PipelO may be submerged below the
water surface elevation and may not be visible.
In summary, a stormwater system is the system of collection inlets, outlets, pipes, waterbodies, and open
channel reaches that stormwater travels through a watershed. For example
• Inlets that collect stormwater
• Pipes that carry stormwater (underground system)
• Outfalls that discharge stormwater into waters of the State
• Open channels that convey stormwater
• Culverts and bridges that convey open channels under roadways
• Water quality ponds and dry detention ponds that detain stormwater
B. Feature Descriptions
Attribute information will be collected for any feature that conveys stormwater inside and/or outside of the
NCDOT right-of-way depending upon the tier level. The following table includes descriptions and sample photos
for most of the feature types included in the FIP. Not all feature types are displayed below (e.g. job work area)
but will be describe later in this section.
Revised 48 June 2016

r:ccr.
Highway
-'twblw
Field Inventory Procedures Manual
Table 2: Sample Feature Descriptions
Feature Type
Description
Sample Photo
Combination Inlet
Combination inlets (combo inlets) are usually found
along streets and parking lots. These structures►
collect stormwater through a "combination" of a
grate and an open throat. Any structure that
collects stormwater with a grate and throat is
considered a combination inlet.
Curb Inlet
Curb inlets usually are located along the curb line
on roads and parking lots. This structure typically
has one throat to collect runoff; however some curb
inlets have two inlets. For a structure to be a curb
inlet, it has to be located along a curb or in a parking
lot etc.
Funnel Inlet
Funnel drains typically direct the flow of
F
stormwater runoff using the curb line on roads into
a corrugated steel or aluminum pipe. There may be
1_
varying designs and limited access to funnel drains.
`
Grate Inlet
Grate inlets can be found in parking lots, yards,
bridges, along roads and roadway medians. These
structures are typically located in depressions in the
-
pavement or ground.
Yard Inlet
Yard inlets usually have 1-4 openings for
stormwater to enter the structure. They are
typically located in localized depressions in open,
..ram
grassy areas to collect stormwater. These
- G•.."'q
structures usually have manholes for access.
M:
Structures without manholes are consideredq
..
L:.
;':` `'^•
concrete "slab top" structures and should be
declared inaccessible.
Revised 49 June 2016

r:ccr.
Highway
-'twblw
Field Inventory Procedures Manual
Table 2: Sample Feature Descriptions
Feature Type
Description
Sample Photo
Junction/Manhole
Junctions and manholes are not designed to allow
additional flow into the stormwater system.
Manholes are placed in a stormwater system for
system maintenance, to join two or more
stormwater systems, to change the flow direction
'
of a stormwater system, or to increase pipe size(s).
Pipe Inlet / Outlet
Pipe inlets and outlets of storm drain systems are
(PipelO)
where the stormwater enters or exits a pipe system,
respectively. The example to the right is a pipe
i*
outfall, projecting from fill, flowing into a riprap
V -,
r.
lined channel.
Channel - Open
Channels typically are larger, water carrying
Channels
drainage ways and have a well defined geometry.
Open channels will be included to provide
connectivity between stormwater systems and
natural waterbodies and rivers.
€y�`"
Channel Point
Channel points can be a blind end, junction, curb
cut, high point, outfall or other. These points will
represent the general location and type of channel
intersections, end points and starting points. This
example shows an arched wall allowing water to
flow into a swale. Definitions are provided in
Section I attributing stormwater structure located
on page 48.
Revised 50 June 2016

r:ccr.
Highway
-'twblw
Field Inventory Procedures Manual
Table 2: Sample Feature Descriptions
Feature Type
Description
Sample Photo
Culvert
Culverts can have various geometries or shapes.
Shapes may include arch, box, circular or even
;z
elliptical. Culverts are used to convey open
channels under roadways. This example shows a
`� I
double box culvert.
1 _
Swale/Ditch
Swales usually carry stormwater from pipe outlets
into channels. Swales are generally conveyances
that are typically dry. Swales can also be BMP's
which are discussed in more detail below and in
',. •=:
Appendix B.
Deck Drain (Scuppers)
Deck drains are inlets that transport stormwater
away from bridge and over passes into surrounding
conveyance systems. In the case of bridges, the
conveyance system may be a stream or river. For
►+
an overpass, deck drains may be located at either
_
end so runoff doesn't drop onto oncoming traffic
below.
Bioretention: Basin or
A bioretention facility consists of a depression in the
Swale
ground filled with a soil media mixture that
supports various types of watertolerant vegetation.
Common locations are median strips, ramp loops,
traffic circles and parking lot islands. Typical
applications treat runoff from less than 1 acre. This
photo example was taken at a rest stop off
Interstate 40.�'�
Y i y
qq
Revised 51 June 2016

r:ccr.
Highway
Field Inventory Procedures Manual
Table 2: Sample Feature Descriptions
Feature Type I Description
Infiltration: Basin or Infiltration basins are normally dry basins, much like
Swale extended dry detention basins, with the exception
that the stormwater does not flow out into a
receiving stream. Rather, the stormwater is
allowed to infiltrate. Infiltration devices are used
frequently to infiltrate runoff from adjacent
impervious surfaces, such as parking lots. This
photo example was taken near the coast on NC-24.
BMPExisting
Sample Photo
These points represent the general location and identify the type of existing BMPs. BMP types include:
Bioretention:Basin, Bioretention:Swale, Dry Detention: Basin, Dry Detention:Swale, Filtration:Basin,
Filtration:Swale, Hazardous Spill Basin, Infiltration:Basin, Infiltration:Swale, Level Spreader, Preformed Scour Hole,
Proprietary Catch Basin Insert, Proprietary Water Quality Inlet, Stormwater Wetland, Wet Detention Pond, and
Other which would be described in a comment field.
Please review Appendix B for stormwater control names used in all NCDOT manuals as well as DWQ's Stormwater
BMP Manual for a complete description of all existing BMP types (http://portal.ncdenr.org/web/wq/ws/su/bmp-
manual). Existing BMPs are included in the features that will function as a stormwater flow network.
Channel
These linear features represent the general centerline of open channels, swales, and ditches. Sheet flow and curb
flow are included as types of flow that could be collected where needed for flow connectivity with other collected
features. Channels are included in the features that will function as a stormwater flow network.
ChannelPoint
These points represent the general location and identify the type of Channel intersections, end points and
beginning points. Current types include: Blind End, Channel Junction, Curb Cut, High Point, Outfall, and Other.
Channel points are included in the features that will function as a stormwater flow network.
Culvert
These linear features represent the centerline of conduits used to convey open channels under roadways. Culvert
material, geometry (Circular, Elliptical, Rectangular, Arch, Box, Other), Diameter (or Height and Width), as well as
upstream and downstream depths are also attributed. Culverts are included in the features that will function as a
stormwater flow network.
DeckDrains
This point feature represents multiple small drains along a bridge deck. A single point will normally be taken to
indicate the presence of numerous deck drains. This is typically the most downstream drain unless specifically
Revised 52 June 2016

NCDO-
Higki<way
w-., Field Inventory Procedures Manual
defined by the customer. A grated deck drain (scupper) connected to a closed conveyance system would be
differentiated from a grated drop inlet based on the number of drains (multiple verses 1 or 2) along the deck and
the size of the connecting pipe (6" verses >15").
IllicitDischargePoint
This point feature type is used to locate the point at which a suspected illicit discharge is entering the ROW. In
addition, the reporter's name, reporter type, type of conveyance feature the illicit discharge was observed
in/coming from, type of dump or discharge, weather active flow is observed, odor, color,
appearance, vegetation condition, land use, and discharge source will be attributed.
Inlet
This point feature type is used to locate drainage inlets. Inlet types collected include: Combination, Curb, Funnel,
Grate, Yard, Unverified, and Other. In addition the following conditions will be noted, number of grates,
percentage of blockage, structure depth, presence and condition of steps, description of the immediate
surroundings adjacent to the structure, accessibility, a determination of and description of maintenance needs,
number of small pipe connections (if any), diameter of largest tie-in (Inches), whether active flow is observed from
tie-ins, any comments needed to further describe tie-ins, a determination if any tie-in could be considered an illicit
connection or evidence is present (for example, odor, colored flow, etc) within the structure that an illicit
discharge somewhere in the system may be conveyed through the structure. Inlets are included in the features
that will function as a stormwater flow network.
JobWorkArea
Each FIP project will start with a request for GIS based stormwater features in a particular area and each project
may have one or more job work areas. These polygon feature classes show the extents of a stormwater collection
effort and will be based on the tier level requested. Feature and attribute collection is based on rules associated
with a specific module or tier level selected and will be stored in the FIP geodatabase.
Junction
This point feature type is used to locate drainage manholes and junctions boxes that typically have no inlet and
provide for a pipe size, slope, or directional change. In addition the following conditions will be noted, structure
depth, presence and condition of steps, accessibility, a determination of and description of maintenance needs,
number of small pipe connections (if any), diameter of largest tie-in (inches), whether active flow is observed from
tie-ins, any comments needed to further describe tie-ins, a determination if any tie-in could be considered an illicit
connection or evidence is present (for example, odor, colored flow, etc) within the structure that an illicit
discharge somewhere in the system may be conveyed through the structure. Manholes are included in the features
that will function as a stormwater flow network.
LandPoint
This point feature type is used to locate the high and low points on an overland drainage system as well as flow
direction and even help delineate catchment boundaries.
OverlandFlow
This point feature type is used to identify how stormwater flows over a land area such as sheet flow, concrete curb
flow or concrete divider flow. A channel would be drawn connecting the overland flow points to indicate flow
direction.
Revised 53 June 2016

�Cco-
Highway
Field Inventory Procedures Manual
Photo
This point feature type is used to show where a photo unattached to other collected stormwater features was
taken. This feature can also used to collect and describe unusual stormwater features that field crews may be
unable to properly identify in the field. Photo points are included in the features that will function as a stormwater
flow network. However connectivity rules will not apply.
PipelO
This point feature type is used to locate and describe the ends of confined stormwater drainage systems. PipelO
types collected are either a pipe inlet or a pipe outlet. In addition the following conditions will be noted, is the
PipelO an existing NPDES outfall, is follow-up investigation needed to verify whether or not the feature is a true
outfall to Waters of the State (Yes/No), is the PipelO an encroachment, evidence of significant scour, a
determination and description of maintenance needs. PipelOs are included in the features that will function as a
stormwater flow network.
PipePoint
This point feature type is used to locate a point along a pipe that leaves or enters the ROW. In addition, the general
type of off -ROW continuing downstream conveyance should be determined as: Channel, Pipe, Sheet Flow, or
Unknown. PipePoint's are included in the features that will function as a stormwater flow network.
Pipes
This linear feature represents the centerline of all confined stormwater flow. Pipe material, pipe geometry
(Circular, Elliptical, Rectangular, Arch, Box, Other), diameter (or height and width), as well
upstream and downstream depths will also be noted. Pipes are included in the features that will function as a
stormwater flow network.
PollutionSource
Collected as part of the Pollution Sources Module —these points are used as a means of identifying pollution
sources both inside and outside (in close proximity) of the ROW.
PotentialRetrofit
Collected as part of the Retrofit Space Module —these points record preliminary information pertinent to siting a
retrofit BMP.
Features that will participate in the stormwater flow network will require connectivity with other collected
stormwater features. Each participating feature will be flagged if not connected, or if no outlet to an appropriately
coded PipePoint, DeckDrain or ChannelPoint exist as part of the validation process.
C. Feature Numbering System
The FIP application does not assign a unique structure identification number for each structure in the field. This
unique identification number will be automatically assigned once the field data has been validated and imported
back to the Master FIP geodatabase by the HSP Geodatabase Manager.
Revised 54 June 2016

NCDOT
pw--,
Field Inventory Procedures Manual
Table 3: Feature Numbering System
Feature Layer
BMPFxisting
Feature ID
Joi)ID_BMP##
Channel
ChannelPoint
JobID_CHP##
Culvert
J ob I D_CVT##
DeckDrains
JoblD
DKD##
I I I i c i t D i s c h a rge P o i n t
Inlet
Junction
JobID_IDP##
JobID_INT##
JoblD JNC##
LandPoint
Overland Flow
JobID
LDP##
JobID_OLF##
Photo
JobID_PHO##
Pipes
JoblD_PIP##
PipePoint
JobID
PPT##
PipelO
JobID
PPT##
PollutionSource
JoblD_POS##
Potential Retrofit
JobID_PRT##
Revised 55 June 2016

�Cco-
Highway
Field Inventory Procedures Manual
D. Public Notification
Each field crew will carry a letter from NCDOT to provide to concerned citizens when approached. This letter will
explain the project and list the FIP phone number for further questions. Field crews will wear identifiable shirts
and USDOT safety vests at all times.
E. Procedures for Entering Private Property
There likely will be cases where stormwater structures will be located on private property. In these cases field
crews should attempt to contact the owner for permission to enter the property. For cases where a stormwater
structure is on private property AND the field crew team cannot make contact with the property owner and the
property is not secured or fenced in, the team will enter the property, provided that the field crew team will be
covered under the protection of the NCDOT.
If the field crew encounters a secured or fenced private property, without the permission of the property owner,
the field crew will classify the structure as "inaccessible".
If the field crew enters on private property and/or is requesting permission to access a stormwater structure on
the property and the owner instructs the field crew to leave, the field crew must leave immediately. Any
structures located on the property should be deemed as inaccessible with a comment stating that property access
was denied by the owner.
F. Procedures for Inaccessible or Unverified Structures
It is anticipated that a small percentage of all encountered stormwater structures may present special problems
for the field crews. Structures with special problems hindering access to a structure should be coded as
inaccessible in the database "Comment" field. Problems existing at the structure should be explained in the
"Problem" field. In order for a structure to be considered inaccessible, crews must be able to physically locate the
structure and determine the structure type. It's recommended that the field crew take a photo for the HSP staff to
review (for example, structure welded shut, debris, flooding). However, if a car is parked on the structure or a
dangerous animal is present, no photo is needed.
Alternatively, an inlet defined as unverified is designed to store a location for a structure that cannot be seen and
can only be assumed present based on the alignment of upstream and downstream pipes. The actual structure
type does not need to be determined for unverified structures and location is approximated based on perceived
direction of pipes.
The following procedures are established for location of inaccessible or unverified structures:
Revised 56 June 2016

r:ccr.
Highway
Field Inventory Procedures Manual
Table 4: Inaccessible\Unverified Structures Procedures
Problem Standard Procedure
Structure is buried
If structure is buried and cannot be found within five (5) minutes of searching, the pipes
leaving the upstream and/or downstream structure will be stubbed in the general
direction of the missing structure. If the field crew can determine by intuition (based on
the alignment of upstream and downstream pipes) the approximate location of the
buried structure, the field crew should place an "unverified" structure point and connect
the pipes perceived to be conveyed through the structure.
Cannot remove top — metal hood
If the top cannot be removed from a structure after five (5) minutes of trying, the
or concrete slab top
structure will be marked inaccessible. Photo requested.
Structure is in restricted area
If the structure is in a restricted area such as a power company substation and access is
not allowed, then the crew should hand place the structure with the best available data
and accuracy. Make sure to note why the structure was inaccessible in the comment
field.
Property owner will not allow
Give the property owner the form letter from the NCDOT explaining the project. If the
access
property owner still will not allow access, then hand- place the structure with the best
available data and accuracy. Make sure to note why the structure was inaccessible in the
"Comment" or "Problem" field.
Structure is paved over
If the field crew can determine by intuition (based on the alignment of upstream and
downstream pipes) the approximate location of the paved over structure, the field crew
should identify the inlet as "unverified" and connect the pipes perceived to be conveyed
through the structure. If the structure is visible but cannot be is physically occupied, then
the appropriate structure type should be placed and declared inaccessible, with a
comment stating the situation.
Area under construction
In areas of new construction, structures should only be attributed if the structures are
completed with structure tops set at a permanent elevation. Structures should not be
attributed if the structures could be further modified, changing the survey control point,
or other attributes. If an area of new construction is encountered, the field crew should
speak to the construction supervisor and get permission to locate any "final" structures.
Pipes should be stubbed in the direction of flow to any incomplete structures, and a
comment should be added to the pipes "Comment" field indicating new construction in
the direction of flow. If there is any doubt about new construction do not survey and
note this in the "Comment" or "Problem" field. Photo requested.
Revised 57 June 2016

NCDO-
Higktway
Field Inventory Procedures Manual
Attempts to survey structures along heavily traveled roadways should be made during
Heavy traffic or unsafe acess off peak hours. NCDOT and USDOT roadway safety procedures shall be followed at all
times.
If the structure cannot be located safely, then offset the structure by standing
perpendicular to the structure at the roads edge and hand place the structure or use a
laser range finder. In the "Comment" field, note that the structure could not be
attributed due to heavy traffic. Photo requested.
Vehicle parked on structure If the structure cannot be located and attributed because of a vehicle parked on the
structure, the field crew should make up to two more visits to the structure to attempt
to locate the structure. Judgment should be used in determining the appropriate days
and times for the 2nd and 3rd attempts. For example, if the structure is in a business
parking lot, then perhaps the next attempt should be before 8 a.m.
If the structure remains inaccessible, the field crew should hand -place using offset
method from the GPS or by using best available planimetrics. A note should be added to
the "Comment" field explaining why the structure was declared inaccessible. Photo
requested.
G. Illicit Discharge or Hazardous Structure Procedures
Field crews will flag and photo document any illicit discharge or hazardous structure conditions immediately. The
IP Manager will then coordinate the appropriate response in conjunction with the IDDEP Manager. According to
the EPA, illicit discharges of concern include:
• Sanitary wastewater
• Effluent from septic tanks
Car wash wastewaters
• Improper oil disposal
• Radiator flushing disposal
• Laundry wastewaters
Spills from roadway accidents
• Improper disposal of auto and household toxics
If the illicit discharge does not present an immediate risk of health or safety of others, the field crew should notify
the IP Manager within twenty-four hours.
Hazardous structures will include any structure that pose an immediate risk to the health or safety of others.
Structures with missing grates and failing supports are examples of hazardous structures that would warrant
NCDOT notification. Field crews should notify the IP Manager of hazardous structures at their earliest safe
opportunity.
H. Encroachments and Right -of -Ways
NCDOT does not maintain a common layer for ROWS so field crews should use their best judgment along with
physical characteristics to determine the ROW boundaries. Right-of-way boundaries can utilize fence lines, power
Revised 58 June 2016

NCC0-
Highway
dalalawwft
Field Inventory Procedures Manual
poles, ditches or maintained grass shoulders. The IP Manager will use current NCDOT aerial photographs to
determine the job work area, but the field crew can modify the job work area to match conditions on the ground.
Encroachments along NCDOT roadways require right-of-way encroachment agreements. In most cases, if not all,
the encroachments are utilities of some sort and may or may not connect with NCDOT stormwater features.
In cases where channels or pipe inlet/outlets intersect and connect to NCDOT stormwater features, the
ChannelPoint and PipelO feature classes have an "Encroach" field the field crew can attribute with "Yes' or "No".
If a pipe entered and exited the ROW without ever connecting with the NCDOT stormwater conveyance system,
the FIP would not consider this an encroachment.
I. Attributing Stormwater Structures
Stormwater structures are collected as point features in the FIP geodatabase and have attributes attached to the
corresponding spatial depiction of the structure. Many of the stormwater structures (point features) will have
common attributes, such as structure depth, pipe invert measurements, steps and scour.
Depth measurements should be made from a common yet consistent survey control point to the deepest point in
the structure. Each structure type has a unique survey control point. Figure 2 shows depth measurements for
various structure types. Typically the depth should be approximately equal to the pipe invert leaving the structure.
In some cases the structure may be designed with a stilling basin, allowing the structure to attenuate flows and
reduce velocities in the stormwater system. A structure with a stilling basin will have the pipe invert leaving the
structure raised above the structure invert. A comment should be included in the geodatabase for any structure
that has a stilling basin.
Revised 59 June 2016

lcco-
Highway
survey
Control Point
Yard Inlet
Survey
Control Point
C�
Plow
Combination Inlet
y
, trol Point
Manhole/junction BoA
Survey Survey Cc
Control Point Point
Structure with Stilling Bas! r
p
now
Field Inventory Procedures Manual
Grate Inlet
Curb Inlet with Manhole Curb Inlet with Metal Hood
Figure 2: Depth Measurement for Various Structure Types
Revised 60 June 2016

�Cco-
Highway
ifigwlawwft
ow ­­.. Field Inventory Procedures Manual
Each attributed stormwater structure, except pipe inlets/outlets, will have a pipe leaving the structure and may
have one or more pipes entering the structure. For each pipe in the stormwater structure, the pipe invert
measurement from the survey control point (drop -down measurement) will need to be obtained. It is important
that this measurement be made as the vertical distance to the pipe invert, not as a diagonal measurement. The
diameter of each pipe in the stormwater structure will also need to be obtained. This measurement should be
taken as the diameter of the pipe opening, not including the thickness of the pipe walls. Figure 3 shows an
example how pipe invert measurements should be taken and an example of a pipe diameter measurement.
Figure 3: Pipe Invert Measurements
Many structures will have steps for structure maintenance. Steps can be made of brick or metal. Steps will
typically be found on structures with depths greater than 3 feet. The "Step" attribute will identify whether the
structure has steps and if they are safely passable.
Tie-in's may also be present in a stormwater structure. Tie-in's are typically small PVC pipes that feed stormwater
from commercial or residential buildings. The total number of tie-in's should be attributed.
Scour is defined as erosion caused by runoff either leaving the structure, as is the typical case with a PipelO, or
flowing around the structure as is the case with bridge piers. Only the presence of scour is required.
Combination Inlets ("Combo Inlets")
Combination inlets are typically found along the curbs of roads and parking lots. Their primary purpose is to collect
runoff from adjacent gutter sections. A combination inlet has both a throat opening and a grate. Typically these
structures have a metal hood with no manhole cover (lid). Measurements can typically be made through the grate
openings.
The structure depth is measured from the control point to the maximum depth of the structure. The maximum
depth of the structure is defined as the lowest elevation of the structure floor. This will typically be very close to
Revised 61 June 2016

NCDO-
Higkiway
w-.. Field Inventory Procedures Manual
the elevation of the pipe leaving the structure. The survey control point for a combination inlet will be located at
the curbside edge of grate, centered.
Figure 4: Combination Inlet.
(Survey control point shown by red dot).
Curb Inlets
Curb inlets are typically found along residential streets and along both major and secondary roads. The purpose of
curb inlets is to collect runoff water from adjacent gutters, minimizing flow spread on the roadway.
The structure depth is measured from the control point to the maximum depth of the structure. The control point
is located at the center of the flow line at the road level of the throat. The depth of the structure is defined as the
lowest elevation of the structure floor. This will typically be equal to the elevation of the pipe leaving the
structure. A comment should be provided if the structure depth is significantly higher (< 0.5 ft) than the pipe
invert leaving the structure, indicating the presence of a stilling basin.
In some cases, curb inlets covers/tops may be constructed with a concrete slab and manhole. In cases where there
is a manhole, the manhole rim should serve as the survey control point.
Revised 62 June 2016

NCDO-
�Iigkiway
Field Inventory Procedures Manual
. - hz S•'y Z.
Figure 5: Curb Inlet with Manhole Lid.
(Survey control point shown by red dot).
Funnel Inlets
Funnel inlets or funnel drains will typically be found along gutter sections. Typically, the funnel inlet will be used to
direct stormwater runoff into an inaccessible catch basin attached to a corrugated pipe. See Table 2 for a sample
photo.
Grate Inlets
Grates inlets will typically be found in parking lots, yards, and occasionally along gutter sections. Typically the
grate will be on grade with surrounding ground and are often located in low spots of the terrain
A grate inlet can have one or multiple grates. If a grate inlet has one grate, the survey control point will be the
center of the grate. In the case of multiple grates, the control point will typically be centered at the center grate
for odd number of grates and between the two grates for even number of grates. The structure depth is measured
from the control point to the maximum depth of the structure which is defined as the lowest elevation of the
structure floor. This will typically be the elevation of the pipe leaving the structure. Error! Reference source not
found. shows the typical location for the control point of structures containing different numbers of grates.
Revised 63 June 2016

NCDOT
1�--
A
If
rk
Figure 6: Grate with Various Survey Control Points
Yard Inlets
Field Inventory Procedures Manual
Grate #&�
Yard inlets are typically found in front or back yards or highway medians and typically located in low areas of the
terrain. Yard inlets often have multiple throat openings to allow water to enter from all sides.
A typical yard with a manhole access will have the control point located at the center of the manhole cover (lid).
Some yard inlets may not have a manhole access, only a concrete slab for cover. For structure with only a concrete
slab and no manhole, the structure should be called inaccessible. If no manhole exists, the control point should be
placed in a location that will remain at the same elevation after the lid is removed and replaced, such as the
bottom of the throat. Crews should make a comment in the FIP geodatabase describing alternate control point
placement.
A typical yard inlet will consist of a 4.5-5.0 foot square concrete slab with or without manhole access. If no
manhole exists and the throat is not large enough to take measurements through, the structure should be
designated inaccessible.
Revised 64 June 2016

NCDO-
Hig_Way
Field Inventory Procedures Manual
The structure depth is measured from the control point to the maximum depth of the structure. The maximum
depth of the structure is defined as the lowest elevation of the structure floor. This will typically be very close to
the elevation of the pipe leaving the structure.
Figure 7: Yard Inlet with Survey Control Point.
Pipe Inlets / Outlets
Pipe inlets/outlets or Pipe10's are locations where stormwater enters or leaves an open channel conveyance
feature. There are several types of end sections with which pipe inlets/outlets can be designed, see Figure .
The survey control point used for inlet/outlets depends on which end section type is used. Typically the survey
control point will be the top of pipe. Survey control points for structures with a headwall will be on the top of
headwall centered over the flow opening. The pipe measure -down should be taken from the survey control point
to the invert of the pipe (sediment should be removed to make measurement).
Revised 65 June 2016

NCDOT
PYGGRfN
F-�-e W"'!
Projecting from fill
Headwall
Field Inventory Procedures Manual
Mitered End Section
Flared End Section
Figure 8. Examples of Pipe Inlets/Outlets End Sections and Survey Control Points
(Pipe end treatments reduce flow velocities and help prevent scour associated with high velocity flows. Examples include
riprap, concrete, and level spreaders. Other treatments should be described in the comment field. See Figure for
examples of pipe end treatments.
Level Spreader
Figure 9: Pipe Outfall End Treatments
Riprap
Revised 66 June 2016

�Cco-
Highway
ifigwlaiwoow 1 Field Inventory Procedures Manual
Manholes/Junction Boxes
Unlike inlets, manholes/junction boxes are not designed to collect stormwater runoff from the ground surface.
Their primary purpose is to join two or more stormwater systems and/or change flow direction. They are typically
found in street intersections and between structures that are more than 300 feet apart.
The survey control point for the typical manhole/junction box will be located at the center of the manhole lid. The
box of a manhole is round, while the box of a junction box is rectangular.
The structure depth is measured from the control point to the maximum depth of the structure. The maximum
depth of the structure is defined as the lowest elevation of the structure floor. This will typically be very close to
the elevation of the pipe leaving the structure, see Figure 2 for examples.
Pipes and Pipe Points
Pipes will be collected as linear features in the FIP geodatabase. All linear structures will be drawn by the user in
the field, thus establishing pipe connectivity in the field. The ability to establish pipe connectivity in the field
allows for increased quality control because the office staff will be able to instantly see the schematic of the
stormwater system the crew is attributing.
Pipes must be directly connected to at least one structure in the FIP geodatabase. If one end of the pipe is not
connected to a structure in the FIP geodatabase, the end without a structure is referred to as a "STUB". It is
impossible to have a pipe "stubbed" at both ends. Also, there are no intermediate vertices/nodes in the linear
feature representation of the pipe except where a pipe enters or leaves the ROW which is called a Pipe Point.
A Pipe Point is not a true stormwater structure but is used by the FIP to help define the point at which a ROW
discharge occurs. Although not a true stormwater structure, Pipe Points will participate in the stromwater flow
network. The two descriptions for a Pipe Point are flow into the ROW or flow out of the ROW.
Linear representations of a pipe are direction dependent. Therefore the user must take special notice of the
direction in which the pipes are digitized. Most municipal stormwater inventories start collecting data
downstream and working upstream to a source structure. For the FIP, the field crews will be locating structures
within the NCDOT right-of-way and working their way downstream to an outfall. Depending on the project job
work area, a full inventory may be required (Tier III). In this case a municipal style of field collection may make
more sense. The standard methodology for digitizing flow direction using ArcPad, as with any ESRI product, is that
the starting vertex will be the upstream end of the pipe and the ending vertex will be the downstream end of the
pipe. This digitizing methodology applies to all linear features, including channels and culverts.
The upstream and downstream ends of each pipe will have a drop down measurement (except for stubs). The drop
down can be used to calculate the invert elevation at a later date. If LiDAR data is available, this enables the slope
of the pipes to be calculated and evaluated.
The physical attributes for a pipe are its geometry, opening dimensions (diameter, height or width), material, and
invert measurements. There are six possible pipe shapes. (see
Table 5: List of Pipe Shapes
Revised 67 June 2016

�Cco-
Highway
ifigwlaiwom
ow ­­.. Field Inventory Procedures Manual
Table 5: List of Pipe Shapes
Pipe Shapes
Circular
Elliptical
Rectangular
Arch
Arch Pipe
Other
The majority of pipes will be circular. For these pipe shapes, diameters will be measured and entered in the
database in inches. If the pipe is not round, then a rise and span measurement are to be collected in feet. The
"rise" measurement is taken to be the vertical distance from the top of pipe to the pipe invert, taken as the tallest
dimension. The "span" measurement is taken to be the horizontal measurement, taken at the widest dimension.
Channels and Channel Points
Channels will be delineated and attributed in the field and revised later in the office using aerial photography or
topographic data. Channel points should be used at the downstream cross section of the waterway segment. A
waterway segment is defined as a stretch of channel that has nearly similar physical and dimensional attributes.
For example, a swale/ditch is any open channel conveyance feature lacking a defined geometry. Typically swales
only carry flows during storm events, and are often V-shaped in geometry with fairly flat side slopes. Channels are
open channel conveyance systems with a well-defined geometry, typically trapezoid. All channels will be
attributed with a top width, bottom width, and height. For rectangular channels, the top width and bottom width
should be equal but since most natural lined channels will not have a constant geometry, representative
measurements of these dimensions should be made for the channel reach.
Each time the channel changes any attributes, such as shape or lining, a new channel point should be located and
attributed at the downstream end of the channel reach. Channels should be attributed at every pipe outlet
location and along any channel when the overall attributes of the channel change. Current channel point types
and descriptions include:
• Blind End -channel that does not flow into any other stormwater structure or water body.
• Channel Junction -identifies the intersections, start and end points.
• Curb Cut -funnels runoff to swales that channel the stormwater to some sort of stormwater control or BMP.
• High Point -the highest elevation of a continuous stormwater channel.
• Outfall-the location at which stormwater discharges to waters of the State. Waters of the State is defined
in Chapter IV, Section A.
• Other -channel point that is not described above.
Revised 68 June 2016

Field Inventory Procedures Manual
Figure 10: Channel Attribution and Channel Dimensioning
Revised 69 June 2016

NCDO-
Higki<way
Field Inventory Procedures Manual
V. Hardware and Software Requirements
A. Data Collection Equipment
Table 5 below lists the typical equipment / tools that each inventory crew should have in the field:
Table 6: Typical Field Crew Equipment
Equipment
Description / Use
Tablet Computer and ArcPad
Data Collection
GPS Antena/Receiver
Data Collection
Pick Axe
Opening manholes
Safety Toe Boots
Safety
Safety Gloves
Safety
Manhole Pry Bar
Opening manholes
Field Notebook
Making brief notes/sketches of systems
Digital Camera
Digital pictures
25' Tape Measure and 6' Stick
Depth measurements / pipe drop -down measurements
Bubble Level
Slobe angle measurements
Shovel
Uncovering manholes, removing minor silt and sediment from structures in order to
collect data.
High Powered Flashlight
Viewing dark, deep manholes to determine condition estimates
Power Inverter
Charging batteries, cell phone, pen -computer from car battery
Orange Reflective Vests
Safety (wear at all times!)
Orange Hat/Cap
Safety
Traffic Cones (36")
Minor Traffic Control
Airhorn
Safety
Survey Road Signs
Traffic Notification
Safety Goggles
Wear when needed
Rain Ponchos
Wet weather
Hip Waders
Channel attribution
Machete
Clearing brush from around pipe outfalls
100 Foot tape with anchor system
(calibrated)
Used for deep structures that depths and inverts unreachable by the 25' tape. The
100' tape is also helpful for attributing large channels.
Revised 70 June 2016

r:ccr.
Highway
Field Inventory Procedures Manual
Table 6: Typical Field Crew Equipment
Equipment
Description / Use
Cell Phone
Safety / Communications
First Aid Kit
Safety
B. Data Collection Hardware and Software
Hand held GPS units, tablets and laser range finders are becoming more and more prevalent in the GIS industry
causing a dramatic reduction in cost of these devices and better integration with other software and hardware.
Today, GIS data can be loaded onto a field computer with a Window's OS and collect new data or edit existing data
with mapping grade accuracy ('/- 3"). These advantages in technology are what prompted the NCDOT FIP to create
a customized field application utilizing ESRI's mobile mapping software, ArcPad.
While the FIP originally chose to use Trimble's Yuma'" GPS tablet
running Windows 7 OS, the upgrade of the FIP application to
support ArcGIS 10.1 enables the use of additional handheld
devices such as Windows 8.x tablets and laptops. When Esri
updated their geodatabase with the release of ArcGIS 10.1,
Trimble updated its software architecture to match the new Esri
configuration by creating it s Positions software, replacing the
GPS Analyst extension for ArcGIS Desktop and Trimble
GPScorrect extension for ArcPad 8. In addition, Esri has updated
its ArcPad mobile collection software to version 10.2 from the
previous version 8. In order to take advantage of the newest
iteration of the NCDOT FIP Application, ArcGIS 10.1, ArcPad 10.2,
and Trimble Positions software are required. The customized
A typical Windows 8.1 Tablet
ArcPad 10.2 FIP application guides the field crews through the collection and attribution process using custom
forms based on predetermined values or domains. The FIP application allows the user to establish pipe and
channel networks in the field with mapping grade accuracy. The FIP application was developed and tested to run
on Windows 7 and 8.x tablets with data input forms sized to fit on 10" tablet screens.
The FIP also utilizes laser range finders for collecting data in potentially high risk areas, such as highways. ArcPad
10.2 is entirely compatible with laser range finders and there's no additional customization to the FIP Application
required.
C. Quality Control and Accuracy Standards
The IP Manager and field crews are ultimately responsible for following proven QA/QC processes to verify the
quality of the field data and to enhance overall quality of the Master FIP geodatabase. Field QA/QC processes are
limited due to the storage space and processor speeds of some handheld devices. A more detailed QA/QC process
will be performed in the office using the FIP Validation Tool in ArcMap.
Revised 71 June 2016

NCDO-
Hig_Way
Field Inventory Procedures Manual
The FIP Validation Tool incorporates quality control processes designed to efficiently uncover data discrepancies
through an automated approach. Feature codes, attributes, geometry, connectivity and business rules of each
feature class are evaluated for consistency and accuracy. The output of these discrepancies will be displayed in a
summary table, viewable in ArcMap, which can be reviewed by the IP Manager to determine if any action is
necessary.
Based on past experience with stormwater inventories, some of the QA/QC steps and required training may be
fairly technical if highest quality results are to be achieved. GPS accuracy cannot be guaranteed and is therefore
the responsibility of both the IP Manager and field crew to identify errors. Some of the steps that improve final
results are not obvious to end users if omitted.
When the field inventory has been completed, the data should be post -processed by the IP Manager using the FIP
recommended method. The FIP recommends using the Trimble Positions extension for ArcMap. This method
allows for a seamless check -in and differential correction process within ArcMap. For detailed information
regarding the Trimble Positions extension refer to Trimble Positions Extension Getting Started Guide.
(http://www.trimble.com/mappingGIS/gpsanaiVst.aspx?dtlD=technical support).
During the development of the FIP geodatabase design, specific domain values were assigned for appropriate
feature types to eliminate the possibility of incorrect data being entered by the field crew. Validation of field
collected data is an important process that should take place in the field to limit revisits. The IP Manager however
will play the role of QC Manager and perform the a separate review and validation in the office. Based on the IP
Managers QC results, a field revisit may or may not be required.
Submitting the FIP geodatabase to the HSP Geodatabase Manager, should be considered the final step in any
QA/QC and accuracy standards process. The HSP Geodatabase Manager will apply internal rules and procedures
to ensure the validity of the data before incorporating it back into the Master FIP geodatabase.
Revised 72 June 2016

NCDO-
Higki<way
Field Inventory Procedures Manual
VI. Safety and Traffic Control
Safety is a top priority for NCDOT and the FIP. Due to the FIP field crews close proximity to traffic, it's highly
recommended that all field personnel attend a NCDOT Work Zone Safety for Location and Surveys Training course.
This safety course can provide a strong foundation for field crews operating in the field.
Occasionally, some traffic control will be necessary in order to obtain attribute information on structures. Traffic
control shall be consistent with North Carolina Supplemental to the Manual on Uniform Traffic Control Devices
(http://mutcd.fhwa.dot.gov/resources/state info/north carolina/nc.htm) and the USDOT "Manual on Uniform
Traffic Control Devices" (MUTCD, 2003 Edition, Part 6: Temporary Traffic Control,
http://mutcd.fhwa.dot.gov/htm/2003r1/part6/part6-toc.htm). In addition to the NCDOT and USDOT guidelines,
the procedures used by consultants for survey safety are to be followed.
In general, field crews should operate with at least two members, of which one member is designated the crew
leader. Orange shirts or vests will be worn at all times for maximum visibility. Orange cones and vehicles with
flashing lights will also be used when working in roadways to alert oncoming vehicles.
Each crew will be also equipped with a cellular phone. The cellular phone shall be used for communication
between project members and in times of emergency situations.
Personal Safety Equipment should include
a. Orange safety vests must be NCDOT certified as Class 2, Level 2. Old and worn out vests should
not be used.
b. Orange hats are used by NCDOT for added visibility.
c. Safety toe shoes, not steel toe, are used by NCDOT. No requirement on height of shoe/boot.
d. Airhorn instead of radio used in high traffic zones by spotters. NCDOT recommended the airhorn
from past experiences working along 1-40.
Signs and Other Safety Equipment should include
a. The most commonly used devices by NCDOT for traffic control are cones, signs and strobe lights.
b. Cones should be 28" to 36" depending on the location. Major highways should use 36' cones
whereas rural areas can use 28' cones.
c. Signs should typically be anywhere from 1' to 7' tall (MUTD), dependent upon the situation. Two
lane roads should be 5' tall whereas rural roads can be 1'-5' tall. The edge of the traveled road is
what the sign height is based on. (for example, a 5' sign should be 5' above the edge of
pavement, not the shoulder. If there is a sloping shoulder the sign should be higher).
d. A rule of thumb for signs is that if the public is distracted by the field crews activities, put up a
sign. However, if it takes longer to put signs up than it does to collect the data, you may want to
evaluate the situation.
e. The USDOT Manual on Uniform Traffic Control Devices: Part 6 Temporary Traffic Control provides
USDOT recommended distances for signs based on posted speed limits and length of work area.
Revised 73 June 2016

NCDO-
Higki<way
Field Inventory Procedures Manual
Some work areas may only need a "Start" and "End" sign if the collection process is fluid. Also, if
a motorist can see the "Start" and "End" signs, no other signs are required (for example, Work
Zone Next 4 Miles).
f. Signs should be laid down or taken up if the field crew plans to leave a work zone for more than
30 minutes.
g. Signs mounted on the back bumper of the shadow truck are useful along shoulders.
h. Strobe lights on trucks can be used instead of signs if the collection process is short term.
Figure 12: Field Crew Sign
�ra
Revised 74 June 2016

NCCO-
Highway
Field Inventory Procedures Manual
VII. Digital Pictures
Digital pictures may be required during a field visit if requested or to show issues with a specific stormwater
structure (for example, illicit discharge, damaged structure). The FIP has a stand-alone module specifically for
collecting photo points in the field. The Photo Points Module will be used as a "catch all" module for recording
information about, and photos of, any point of interest in the field. This module can be used in those cases where
it would be inappropriate to use one of the other modules or the basic functionality included with the three
inventory tier protocols. The collection of photos should be considered for all Tiers and all modules by the IP
Manager prior to assignment of the work area to the field personnel.
The digital pictures should capture the structure and immediate structure surroundings (see figure14 ). The
pictures will likely be used in generating maintenance work order requests and for formal NPDES permit
submittals. For the digital picture to be useful to the FIP, proper photo orientation standards must be followed.
Photos must be taken such that they capture not only the structure, but the surrounding area as well.
Photo Extent Too Close
Figure 13: Example of Correct Photo Extent
Photo Extent Correct
Revised 75 June 2016

NCDO-
Higki<way
Field Inventory Procedures Manual
VIII. System Connectivity
The goal of the FIP is not to provide 100% connectivity between stormwater features. Unlike most municipal
inventory programs where the type of information to be collected remains relatively static over the course of the
program's life span, the FIP is envisioned to support multiple data collection goals. The three tiered structure
allows for the type and quantity of data collected to vary by inventory trip. This in turn facilitates optimization of
the program by focusing data collection only on the information required to address a predefined need at a
predefined location.
Reasonable efforts are to be made by the field crew to resolve pipe connectivity issues in order to avoid
subsequent site visits. However, in some cases, pipes will be encountered during the inventory whose source or
destination cannot be determined. Significant efforts (greater than five minutes) should be made to locate the
source or destination of the stubs. If the end structure for a pipe cannot be located, the pipe is to be stubbed in
the perceived direction of flow. The length of the stub will indicate how far upstream along the perceived pipe
path the field crew looked for the structure. In general anytime a pipe is stubbed in the FIP geodatabase, the field
crew should comment on the circumstances from which the stub resulted. The pipe will be attributed based on
the observed end of the pipe (geometry, diameter, material, and invert).
In certain situations pipe stub orientation will indicate the approximate location of an unidentifiable structure. In
these situations the field crew may place an inlet point and attribute the feature type as "Unverified" and connect
the pipe system. If pipe connectivity is not intuitive, the field crew should not use the "Unverified" inlet point to
establish connectivity.
Revised 76 June 2016

NCDO-
Higki<way
Field Inventory Procedures Manual
IX. Frequently Asked Questions
The following is a list of frequently asked questions.
What if a pipe has no known destination?
Add pipe indicating the approximate alignment. The field crew should enter a comment indicating the
circumstances of the connectivity problem. The type of pipe would be called a "stub".
What do we do if we encounter an illicit discharge (e.g. oil being directly discharged into the
storm sewer)?
If any illicit discharge is encountered by the field crews, you should immediately contact the IP Manger
within twenty-four hours and take a digital photo of the site.
How do we handle concerned property owners?
Property owners with questions or concerns should be given the standard form letter provided by the FIP
explaining the purpose of the project and any contact information with the NCDOT. If any property owner
asks you not to enter his/her property or to leave the property, the field crew must leave immediately. A
comment should be made for any pipes stubbed to the property where access was denied.
What happens if we break a manhole cover?
The IP Manger should be contacted immediately. If the open manhole is in the line of traffic, then the
City Police should be called immediately to assist in traffic control while the NCDOT maintenance
responds to the call.
In general, if a manhole appears cracked and weak, DO NOT attempt to gain access. Code the structure as
inaccessible, record the comment, and contact the IP Manager.
What should I do if I drop a grate into a structure?
First, safely secure the area with cones as appropriate. If the grate cannot be raised, secure the area and
contact the IP Manger for assistance.
How do we handle inaccessible structures (e.g. manhole welded shut)?
If a structure is visible but for whatever reason cannot be accessed or opened for attribution the field
crew should locate the structure and mark the structure inaccessible and comment why the structure was
inaccessible. Pipes should be connected to this feature if the connectivity is intuitive to the field crew. If
the structure is not visible or otherwise not physically determined to exist, then the field crew should not
place a structure.
It's recommended that the field crew take a photo for the HSP staff to review (for example, structure
welded shut, debris, flooding). However, if a car is parked on the structure or a dangerous animal is
present, no photo is needed.
Revised 77 June 2016

�Cco-
Highway
Field Inventory Procedures Manual
How is connectivity defined when a pipe outlet flows into an undefined ditch (for example,
open field)?
Connectivity needs to be provided in these areas. It's recommended the field crew delineate a channel to
show flow direction but attribute the channel as sheet flow. Land points may also be used to delineate
peaks and sags. The field crew may need to rely on available topography layers for help determining the
direction of flow.
What if there is an area of new construction, do we collect attributes?
Structures should be attributed in areas of new construction only if structure tops are placed at the
finished grade. The field crew may need to talk with the construction site manager to discuss which
structures are at finished elevations. If there is any doubt whether a structure is at finished grade or not,
do not attribute the structure. The field crew should place a comment in the pipe feature class explaining
that the property is under construction.
What if an unmapped stream is being conveyed under a road via a culvert?
The Pipe feature class should be used to indicate a situation as mentioned above. If one or more outfalls
are discharging to the unmapped stream then a basic amount of locational information about that stream
should be collected. This might include PipeIC's, Pipe's, and a Channel (i.e. stream channel). This
provides a positive affirmation that the outfalls indentified are correct.
When would you attribute a PipelO as an NPDES outfall if there was a very short channel
located between the PipelO and Waters of the State?
If the PipelO is actually the Outfall, then the channel isn't significant. The procedure would be to digitize a
small channel from the Outfall to the WOS for connectivity purposes only and identify it as a "Connector"
in the comment field. By definition there should not be any inventory features "downstream" of the
Outfall.
How would you draw a connector to an unmapped stream?
Generate connectors only on an as needed basis and through a process outside of the standard FIP
procedures.
When to use feet versus inches?
All dimensions for data collection will be in feet except for pipe diameters which are in inches.
Revised 78 June 2016

�Cro-
Highway
Field Inventory Procedures Manual
X. References
NCDOT Field Inventory Program Needs Assessment Report
Dewberry & Davis, Inc. 2007
Final Pilot Study Report
Dewberry & Davis, Inc. 2008
Stormwater Controls Naming Convention Memorandum
NCDOT Roadside Environmental and Hydraulics Units
URS Corporation, January 2008
DWQStormwater BMP Manual (7/07)
North Carolina Division of Water Quality
Stormwater Best Management Practices Manual, July 2007
http://portal.ncdenr.org/web/wq/ws/su/bmp-manual
USDOT Manual on Uniform Traffic Control Devices: Part 6 Temporary Traffic Control
http://mutcd.fhwa.dot.gov/htm/2003rl/part6/part6-toc.htm
NC Supplemental to the Manual on Uniform Traffic Control Devices
http://mutcd.fhwa.dot.gov/resources/state info/north carolina/nc.htm
Trimble Positions Extension Getting Started Guide
http://www.trimble.com/mappingGIS/gpsanalyst.aspx?dtlD=technical support
Revised 79 June 2016

_r-
Highway
Stormwater
XI. Installation and Setup Procedures
Mobile Client Setup
Field Inventory Procedures Manual
Installing ArcPad 10.2
ArcPad 10.2 is required for the NCDOT FIP application and Trimble Positions software to function. As
of the update of this document, ArcPad version 10.2.3 is the current version and should be used to ensure
compatibility with Trimble software and GPS devices. You can download the ArcPad software from the
following webpage if your Esri account ha s the proper permissions to access:
htlp://www.esri.com/gpps/Troducts/download/index.cftn#ArcPad
Download and run the ArcPad 10.2.3 installer.
On the initial screen accept the default folder and
click the Next button.
Once the installation files have extracted, make
sure the check box next to the Launch the setup
program is checked, then click the Close button.
The setup routine will begin.
Destination Folder For Files
Please select the destination Folder where the package should extract the Files:
11MIMMOMM NMI
C:�Users�rdelach�Cocuments`ArcPad 10.2.3
Browse
Archive C Back I Next > I Cancel
J
Revised 80 June 2016

NCDOT
1�--
Click the Next button on the ArcPad 10.2
InstallShield Wizard.
Accept the license agreement and click the Next
button.
Click the Install button when the following
window appears.
Field Inventory Procedures Manual
Welcome to the Arcload 10.2 Setup program
It is strongly recommended that you uninstall any previous
versions of ArcPad and exit all Windows applications before
running this setup program.
Click Cancel to quit setup and close any programs you have
running. Click Next to continue the installation.
WARNING: This program is protected by copyright law and
international treaties.
Unauthorized reproduction or distribution of this program, or
any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent
possible under law.
i
C Back Next Cancel
License Agreement
You must agree with the licence agreement below to proceed.
1MP OK1 ANI-REAL) CA1*1 ULLY
Unless superseded by a signed license agreement between you and Esri, Esri is
will i g to license Products to you only ifyou accept all terms and conditions
contained in this License Agreement. Please read the terms and conditions
carefully. You may not use the Products until you have agreed to the terms and
conditions ofthe License Agreement. Ifyou do not agree to the terms and conditions
as stated, click "I do not accept the license agreement" below; you may then request
a refund ofapplicable fees paid.
LICENSE AGREEl13EC]T
R j accept the terms in the license agreement Print
..............................................................:
k[30o not accept the terms in the license agreement
Back Next 7 Cancel
Ready to Install the Program
The wizard is ready to begin installation.
IF you want to review or change any of your installation settings, dick Back. Click Cancel to
exit the wizard.
Current Settings:
letup Type:
Typical
Destination Folder:
C:�Program Files (x86)�ArcGIS�ArcPad10.2�
Jser Information:
Name: Employee
Company: Dewberry
Back Install Cancel
X
X
Revised 81 June 2016

NCDOT
moo --
Click the Finish button to complete the
installation.
The installation should have put 2 ArcPad shortcuts on your desktop,
examples on right.
There should also be a new folder in the Start Menu under ArcGIS
similar to the example on the right.
Configure the NCDOT FIP Toolbar in ArcPad
Field Inventory Procedures Manual
J
InstallShield Wizard Completed
The Install5hield Wizard has successfully installed ArcPad 10.2.
Click Finish to exit the wizard.
C Back Finish Cancel
In order to install the NCDOT FIP Toolbar in ArcPad you will need to have copied over the
ArcPad_applet folder from the GIS workstation/desktop computer. For consistency, the folder should be
located on the c-drive of the at: c:\NCDOT\ArcPad_applet\
The contents of the ArcPad_applet folder should look
like the example on the right.
Name '
Type
Size
.i DataForArcPad
6j112016 5:00 PM
File folder
1016.110
1j14j20097:32AM
Icon
6KB
1034.ico
1J14j20097:32 AM
Icon
6KB
gk 1081.ico
1J14j2009 7:32 AM
Icon
6 KB
P 1084.im
1j14j2009 7:32 AM
Icon
6 KB
1088.ico
1J14j20097:32 AM
Icon
6KB
1715.ico
1J14j20097:32 AM
Icon
6KB
�1 Camera.im
2j13j2007 6:12 PM
Icon
1 KB
defaultValues.txt
5j17j2012 1:52 PM
TXT File
3 KB
Hydrant, im
2J13j20078:10 PM
Icon
1KB
2 n,DotTools apa
5J27j2015 1:27 PM
APA File
4 KB
® ncDotToolsv6s
6j512015 3:43 PM
VBScript Script ..
51 KB
Tier.d6f
12123j2009 224 PM
DBF File
7 KB
Revised 82 June 2016

NCDOT
0M.-,
Once the ArcPad_applet folder is
in place, start ArcPad. Once loaded
select Options from the Options
Menu in ArcPad.
Field Inventory Procedures Manual
OAdvanced Settings...
In the ArcPad Options window (see
M"'a°
Navlgatnr
below), select the Paths tab, then
®Scale
Bar
select "Applets" in the Other
Panning Frame
Additional Paths dropdown list.
Then click the folder on the line
iarttatus
Bar
below to browse to the
North Arrow
ArcPad_applet folder which should
Extension Tools
be located at
c:\NCDOT\ArcPad_applet.
Once you have selected the applet folder path, then click the OK button on the Directory Browser
window, then OK again to accept the option changes in ArcPad.
J
VDisplay Camera 4 Paths I ,% General o+ 4
Default Maps & Data Path
erslydelachlDocuments,C:4Users{ PubliclDocuments4ArcPad J
Public Files Path
IC:%UsersTublicTocumentslArcPad J
Other Additional Paths lApplets 11
ES Directory Browser X
o...k1 LANDeskSoftware950
Idprovisioning
MSOCache
p NCDOT
0 ArcPad Data
p AXFToaI
L �j
p OpenRefine
ArcPad may require a reboot for the changes to take
effect. Some preferences may have changed that require a restart to
take effect
When restarted, the FIP Toolbar should be visible, see example below.
EFIP Toolbar
Revised 83 June 2016

NCDO-
Higktway
Field Inventory Procedures Manual
Installing Trimble Positions Extension for ArcPad
In order to ensure that you are running the proper versions of Trimble software, reference the
compatibility chart below. The current release of Trimble Positions as of the update of this document is
dated February 2016. The associated Trimble Positions for ArcPad extension version is 10.2.3.1. This
version is required for Trimble Positions to function in Windows 8.x OS. Compatibility with Windows 10
is unknown at the time of update of this document.
Trimble Positions ArcPad extension
The following tables list the compatibility between the Trimble Positions ArePad extension, field computers, and GNSS receivers. The
Trimble Positions ArcPad extension requires the Windows Mobile operating system version 6.0 or later.
T_,ble 15 Trimble Positions .Arc Pad extension- Wincio°,h,s operating sys*em — desk'oo and "ablet computers
1
Trimble Positions ArcPad extension version 10.2.1.1 is only supported on Windows Mobile and Windows Embedded Handheld devises.
2
The Windows? operating system, 32-bit and64-bit are both supported.
3
The Windows? Professional operating system, 32-hit version, is the only version supported by the Trimble Yuma andYurrra 2 rugged tabletcomputers.
The full Trimble compatibility document can be found at:
http://trl.trimble.com/docushare/dsweb/Get/Document-160913/
The Trimble Positions software and documentation can be downloaded from the following website:
http://www.trimble.com/globaITRLTAB.asp?Nav=Collection-89086
Download and run the Trimble Positions Extension J
for ArcPad installer. Click OK on the initial window.
Thank you For downloading Trimble Positions ArcPad extension v10.2.3.1.
You will now be redirected to the installer.
Before you can use the software, you will need to register the Proof of
Purchase Number (POPN) you received when you ordered the software, and
use the Installation Code to activate the installation,
■ Now readying the Trimble Positions ArcPad extension
v10.2.3.1 installation package.
Cancel
0-2-3_1 About
Revised 84 June 2016

_r-
Highway
Stormwater
Click "English" when you see the window to the right.
Click Install
Select Install Trimble Positions ArcPad extension
for Windows (English).
Field Inventory Procedures Manual
Trimble Posit -ions AncPad exlenwn — - 9061-WI
Revised 85 June 2016

NCDOT
OW--,
Select English (United States) and press the Next
button.
Select the Next button.
Make sure ArcPad is not running and click the
Next button.
Field Inventory Procedures Manual
Welcome
Welcome to the Trimble Positions ArcPad extension for
Windows Setup program. This program will install Trimble
Positions ArcPad extension for Windows on your Desktop
Computer.
<Back Next> Cancel
Information
Before continuing with the installation, please ensure that Arct is not running on Desktop
Computer. Select the Exit option from the drop -down menu on the main ArcPad toolbar.
<Back Next> Cancel
X1
Revised 86 June 2016

NCDOT
1�--
Accept the terms of the software license, and click
the Next button.
Click the Next button to start copying the program
files.
Click the Finish button to complete the installation.
Field Inventory Procedures Manual
License Agreement
Please read the following license agreement carefully.
User License Agreement
Tble Positions ArcPad extension
HVIPORTANT, READ CAREFULLY. THIS END USER
LICENSE AGREEMENT (AGREEMEN7") IS A LEGAL
AGREEMENT BETWEEN YOU (either an individual or a single
entity) AND TRIMBLE NAVIGATION L]2,=D and its affiliates
(collectively, "Trimble") and applies to the Trimble Positions ArcPad J
f• Laccept the terms. of the license. agreement Print
I do not accept the terms of the license agreement
<Back Next> Cancel
InstallShield Wizard Complete
The Installs hield Wizard has successfully installed Trimhle
Positions AicPad extension for Windows. Click Finish to exit
the wizard.
<Back Finish ',
X1
Revised 87 June 2016

NCDOT
ow--,
Trimble Positions Software License Activation
Field Inventory Procedures Manual
Once Trimble Positions software is installated on the Windows tablet, licensing for the software must be
Activated.
For the Trimble Positions Extension for ArcPad on the Windows Tablet, you must run the Trimble
Positions ArcPad extension for Windows Activator from the Start Menu, and enter the extension
Installation Code. See the example below on the right.
Enter an Installation Code
Fa- ace r— "dw—. C�
Revised 88 June 2016

_r-
Highway
Stormwater Field Inventory Procedures Manual
GIS Workstation/Desktop Computer Setup
In order to create field data collection projects and correct GPS data Esri ArcGIS Desktop GIS software is
required. The tables below specify that for compatibility with Trimble Positions software version
10.2.3.1, ArcGIS for Desktop Standard or Advanced is required and Trimble Positions extension for
ArcGIS Desktop version 10.4.0.1 must be installed.
Table 11 Trimble Positions Desktop add -in: Esri ArcGIS for Desktop software
101,10�
MAL
an 10.2.D.1
Trimble Positions
10.2.2.1
Desktop add
-in
10a0.1,10.3.0.2
10.4.0.1
Esri An G15 far Desktop
1
10.2.xM
1
See table below.
-Cannot enable or synchronize attachments. -Limited or no support for enterprise
-Cannot add GloballD fields through the User Interface geodatabases and ArcSDE services.
to allow synchronization. refer to Esri documentation.
-Degraded performance when collecting session data in
the field.
Trimble Positions Desktop add -in Installation
As of the update of this document, the required version of Trimble Positions Desktop extension is
v10.4.0.1. You can download the software from this location:
http://www.trimble.com/globalTRLTAB.asp?Nav--Collection-89086
Once Trimble Positions extension for ArcGIS
Desktop version 10.4.0.1 is downloaded, run the
executable file. Click the OK button on the license
warning dialog.
The window on the right will popup and
extract the files.
'Trimble Pvsi[iarx Desktop add - in v10.4.0.1
Tha nk you for downloading Trimble Positions Desktop add - in v10.4.0.1
You will now be redirected to the installer.
Before you can use the software, you will need to register the Proof of Purchase
Number [P 6P N] you received when you ordered the software, and use the
Installation Code to activate the installation.
WinZip Self -Extractor -Trimble Positions Desktop add -in.exe
} Now readying the Trimble Positions Desktop add -in Setup
v10.4.0.1 installation package.
Cancel
Unzipping TrimblePositionsDes
Revised 89 June 2016

NCDO-
Higkiway
Click English on when you see the window on
the right.
Click Install in the resulting window on the
right.
Click on Install Trimble Positions Desktop add -
in. See example window on right.
Field Inventory Procedures Manual
�.04 Trimble Prt,c oaskt.p Ad -in I-1 Ei "I
p�'Ti1111bI@. Trimble Positionsa
Version 104.0.1
� Go aecN
Meln Menu a
Install
Install Trimble Positions
Install Tnmhle Positions
nnslall Trimble Positions
- Install SgLite OBDO
J
and inhmetionel colpgipM.
'F tlocume�tion.
Desktop
Desktop add -in
License Manager
PathAnder Office
Driver
tretlemeA.aM pehn[leee
add -in
Tools
eetlasnhed in qua pmtlucl
by n6
Revised 90 June 2016

NCDOT
PkGGRfN
Click the OK button on the InstallShield Window
The installation may require additional updates to be
installed. If so, you will see a window like the
example on the right. Click the Install button.
NOTE: Installing additional required software may
require one or more system reboots before the
installation can continue.
Click the Next button on the InstallShield
Wizard dialog box.
Field Inventory Procedures Manual
Trimble Positions Desktop add -in -InstallShield Wizard
aSelect the language for the installation From the choices below.
English (United States)
41C Cancel
Trimble Positions Desktop add -in - InstallShield Wizard
®Trimble Positions Desktop add -in requires the following items to be installed on your
computer. Click Install to begin installing these requirements.
Status Requirement
Pending Microsoft Visual C++ 2013 Redistributable Package (x64)
Pending Microsoft Visual C++ 2012 Update 4 Redistributable Package (x86)
Pending Microsoft Visual C++ 2012 Update 4 Redistributable Package (x64)
Pending Microsoft Visual C++ 2013 Redistributable Package (x86)
Install Cancel
Trimble Positions Desktop add -in - InstallShield Wizard
kWelcome to the InstallShield Wizard For Trimble
Positions Desktop add -in
The InstallShield Wizard will install Trimble Positions
Desktop add -in on your computer. To continue, click
Next.
<Back Next> Cancel
Revised 91 June 2016

_c -
Highway
Stormwater Field Inventory Procedures Manual
Accept the terms of the license agreement
and click the Next button.
Enter your name and your company/organization
name when you see the dialog box on the right.
Select Complete setup types and click the Next
button.
Trimble Positions Desktop add -in - InstallShield Wizard
License Agreement
Please read the following license agreement carefully.
End User License Agreement
Trimble Positions Desktop add -in —
EVIPORTANT, READ CAREFULLY. THIS END USER
LICENSE AGREEMENT ("AGREEMENT—) IS A LEGAL
AGREEMENT BETWEEN YOU (either an individual or a single
entity) AND TRIMBLE NAVIGATION LII=D and its affiliates
(collectively, "Trimble") and applies to the Trimble Positions
S l t Accept heterm
s ms. of. the. licensee . agrement Print
i I do not accept the terms of the license agreement
InstallShield
<Back Next> Cancel
Trimble Positions Desktop add -in - InstallShield Wizard
Customer Information
Please enter your information.
Please enter your name and the name of the company for which you work.
I lacer Name
Company Name:
Company{
<Back Next> Cancel
Trimble Positions Desktop add -in - InstallShield Wizard
Setup Type
Select the setup type to install.
Please select a setup type.
.......................
;u• Complete
All program features will be installed. [Requires the most disk space.]
Custom
Select which program featuresyou want installed. Recommended for
advanced users.
InstallShield
<Back Next> Cancel
Revised 92 June 2016

NCDOT
OW--,
Click the Next button to accept the download of
the latest coordinate system definitions.
Click the Install button to contintue the
installation.
When the installation completes, click the Finish
button, and close the installation window.
Field Inventory Procedures Manual
Trimble Positions Desktop add -in - InstallShield Wizard u
Upgrade Coordinate Systems '
A
You can choose to upgrade your coordinate system zones and sites.
0 lJ rade coordinate s ster
zones and sites
�Pg........................................y.................................................:
hield
You should upgrade in order to get the latest coordinate system
definitions. Any user -defined coordinate system zones and sites
are retained during the upgrade.
<Back Next> Cancel
Trimble Positions Desktop add -in - InstallShield Wizard
Ready to Install the Program
The wizard is ready to begin installation.
Click Install to begin the installation.
If you want to review or change any of your installation settings, click Back. Click Cancel to exit
the wizard.
InstallShield
< Back Install _ Cancel
Trimble Positions Desktop
InstallShield Wizard Complete
The InstallShield Wizard has successfully installed Trimble
Positions Desktop add -in. Click Finish to exit the wizard.
< Back Finish Cancel
Revised 93 June 2016

NCDOT
pw__
Trimble Positions Software License Activation
Field Inventory Procedures Manual
Once Trimble Positions software is installated on the desktop and also on the Windows tablet, licensing
for the software must be Activated. On the desktop computer this is accomplished by running the Trimble
Positions License Administrator from the Window State menu, and entering the license Installation Code.
See example below on the left.
+'I Trimble Positions Desktop add -in License Administrator 0=®
The License Administrator allows you to view and choose the source of your license. Choose 'Single
Use to use or activate an installation code for this machine only. Choose 'Floating'to select a network
location where a Trimble Positions License Manager is installed.
r Single Use
Trimble Positions Desktop add -in is using the single use license below. If you wish to install or
update the license, click on 'Activate, enter the Installation Code, and follow the instructions.
Installation Code: Activate
r Floating
Trimble Positions Desktop add -in is using the Trimble Positions License Manager on the machine
Shown below. To change the server for the License Manager, click on'Change'. To test the
connection, click on'Test ,.
Server Address: Change...
Borrow License... I Test
OK Cancel
girPrq iOr'. VJi rd•
® Enter an Instillation Code
� w....wrcv.�rarwe+[oe.
Setting Up the NCDOT folder location and associated project files on Desktop
Find the folder displayed in the image on the right in NCDOT (folder to copy to GIS workstation c-drive)
the deliverable provided under task WA58B.
Copy the folder in its entirety (including all contents) to the c-drive of the GIS workstation that will be
configured for data Check Out, Check In, and Post Processing. Once copied to the local c-drive, rename
the folder to simply "NCDOT". The resulting path to the folder should now be: c:\NCDOT\
The c:\NCDOT\ folder will contain the
following folders and files:
name -
I Date modified
W ArcPad_applek 61212016 4;22 PM
Wi ArcPad_Data 611J2016 3:39 PM
AXFTool 612J2016 4:22 PM
ncdok,apo 61312015 9:47 AM
NCDOT_FIP,apo 61412015 2:17 PM
Q NCDOT_FIP,mdb 612J2016 2:28 PM
J NCDOT_FIP,mxd 614J2015 10:06 AM
177 KB
177 KB
239,804 KB
807 KB
Revised 94 June 2016

NCDOT
1�__
Desktop GIS - NCDOT HP AXF Forms Tool Setup
Field Inventory Procedures Manual
The NCDOT FIP Toolbar was originally developed for ESRI's ArcGIS Desktop 10 environment and is
no longer required when using ArcGIS 10.1. Instead, the executable file is run to update the forms in the
ArcPad data collection project to property fit the screen of a Windows 10" tablet or larger screen size.
The NCDOT FIP Toolbar was developed to support the NCDOT Highway Stormwater Program's
functional specifications for a field collection and desktop validation tool in ESRI's ArcGIS and ArcPad.
For this project the development environment was as follows:
o Visual Studio 2010
o C# programming language
o ArcGIS 10.1
o ArcPad 10.2
The NCDOT FIP AXF Forms Tool (see folder Name Date modified size
structure in image on right), can be run directly
from its stored location on the GIS workstation, data 6JIJ2016 3:36 PM
by double clicking on the • ' AXFTooI_NCDOT,exe 5J27J2015 4:58 PM 13 KB
AXFTool NCDOT.exe file. i
The recommended location to store the tool is: c:\NCDOT\AXFTool\
You may create a shortcut that can be stored in a
convenient location on the GIS workstation such
as on the desktop, by right -clicking on the
AXFToo1 NCDOT.exe file and selecting Create
Shortcut from the context menu. You can then
rename the shortcut to AXF Forms Tool and drag
and drop it to the desktop or other convenient
folder location for future use.
Name Date modified Size
,r data 1011512015 1:00 AM
him Open
Send to
Cut
Copy
Delete
Rename
Properties
Revised 95 June 2016

_r-
Highway
Stormwater
Field Inventory Procedures Manual
XII. NCDOT Highway Stormwater Field Inventory Program
Geodatabase Schema
Geodatabase: NCDOT FIP Geodatabase schema revised under Task Order
WA58B in 2015-16
Geodatabase Summary Graphics
Revised 96 June 2016

_r-
Highway
Stormwater
Geodatabase Detail Graphics
Field Inventory Procedures Manual
■ Simple feature class
Geometry Point
■
' Potential Retrofit
Contains M values No
Contains Z values No
D.. type
Allow
n L, HIS Default value
Prec-
Domain
OBJECTID
Object ID
-�
Shape
Geometry
Yes
-'
SiteName
String
Yes
50
SiteDesc
String
Yes
iL 50
SiteOwner
String
Yes
HSPDomainSiteOwner _� 7
AvailSpace
Double
Yes
0 0
DArea
Double
Yes
0 0
DALULC
String
Yes
HSPDomainLand Use __ 50
RetroType
String
Yes
HSPDomainBMPType __ 30
TMDLID
String
Yes
__ 50
RuleslD
String
Yes
__ 50
EngAssess
String
Yes
__ 50
KeepActive
String
Yes
__ 3
Constr
String
Yes
__ 50
Comments
String
Yes
__ 255
PhotoYN
String
Yes No
HSPDomainYesNo __ 3
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
__ 255
XYSource
String
Yes GPS
HSPDomainXYSource __ 9
AttDate
Date
Yes
0 0 8
FeaturelD
String
Yes
__ 20
JoblD
String
Yes
__ 12
Problem
String
Yes
__ 50
Reason
String
Yes
__ 50
Photol
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
255
■ Simple feature class
Geometry Point
' PollutionSource
Contains M values No
Contains Z values No
- • name
D.. type
Allow
nulls Default value
Prec-
Domain isioength
OBJECTID
Object ID
'
Shape
Geometry
Yes'
_
SiteName
String
Yes
50
SiteAdd
String
Yes
50
PolSorType
String
Yes
HSPDomainPollutionSo
� 12
DOTSource
String
Yes
HSPDol f5th5 (? NoUnkn_I 3
DrainsROW
String
Yes
HSPDom2YPYtsNoUnkn_L 3
HotSpotCon
String
Yes
HSPDomaMTbsNoUnkn3
PrimPoll
String
Yes
__ 20
SecdryPoll
String
Yes
__ 20
TertPoll
String
Yes
__ 20
Comments
String
Yes
__ 255
PhotoYN
String
Yes No
HSPDomainYesNo __ 3
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
__ 255
IllicitFlg
String
Yes
HSPDomainYesNo __ 3
XYSource
String
Yes GPS
HSPDomainXYSource __ 9
AttDate
Date
Yes
0 0 8
FeaturelD
String
Yes
__ 20
JoblD
String
Yes
__ 12
Problem
String
Yes
__ 50
Reason
String
Yes
__ 50
Photol
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
255
SiteName
SiteDesc
SiteOwner
Acreage
Drainage
Landuse
RetroType
TMDLID
RuleslD
Assessment
KeepActive
Constraints
Comments
PhotoYN
PhotolDs
Photol-ink
XYSource
AttDate
FeaturelD
JoblD
Problem
Reason
Photol
Photo2
Photo3
SiteName
SiteAdd
Source
DOTSource
DrainsROW
HotSpot
Prime
Secondary
Tertiary
Comments
PhotoYN
PhotolDs
Photol-ink
I IlicitFllag
XYSource
AttDate
FeaturelD
JoblD
Problem
Reason
Photol
Photo2
Photo3
Revised 97
June 2016

NCDOT
pw"-
aSimple feature class
Pipes
OBJECTID
Object ID
Shape
Geometry
Yes
Geometry
String
Yes
Diameter
Double
Yes
Height
Double
Yes
Width
Double
Yes
Material
String
Yes
USFeatureTy
String
Yes
DSFeatureTy
String
Yes
USDD
Double
Yes
DSDD
Double
Yes
USEIevEst
Double
Yes
DSEIevEst
Double
Yes
Comments
String
Yes
PhotolDs
String
Yes
PhotoYN
String
Yes
Photol-ink
String
Yes
Owner
String
Yes
AttDate
Date
Yes
FeaturelD
String
Yes
USID
String
Yes
DSID
String
Yes
JoblD
String
Yes
Problem
String
Yes
Reason
String
Yes
MaxTier
String
Yes
DomainEnabled
Short integer
Yes
Length
Double
Yes
Shape_Length
Double
Yes
Photo1
String
Yes
Photo2
String
Yes
Photo3
String
Yes
Field Inventory Procedures Manual
Geometry Polyline
Contains M values No
Contains Z values No
HSPDomainGeometry __ 12
0 0
0 0
0 0
Concrete HSPDomainPipp Material__ 8
H DomainUSD Feature__ 20
HSDomairTGSDSFeature__ 20
r., o
0 0 0
0 0 0
0 0
0 0
255
255
No HSPDomainYesNo __ 3
255
NCDOT HSPDomainOwner __ 7
0 0 8
20
15
15
12
50
50
HSPDomainTiers __ 3
1 EnabledDomain 0 _
0 0
0 0
255
255
255
■ Simple feature class
Geometry Point
Pi ePoint
p
Contains M values No
Contains Z values No
Data type
Allow
nulls Default value
Prec-
Domain ision- Length
OBJECTID
Object ID
ME
' ,_
Shape
Geometry
Yes
,- ' ,_
FeatureTy
String
Yes
HSPDomainPipePtType 20
Comments
String
Yes
__ 255
PhotoYN
String
Yes No
HSPDomainYesNo __ 3
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
__ 255
Incoming
Short integer
Yes
0
Sh gef
0
MEing
ROWDs
tring
Yes No
HSPDomainYkn_
ContConvey
String
Yes
HSPDomfilHOhanneIhannelDS
r•.....,o.,r.,.,o __ 10
ApproxElev
Double
Yes
0 0
XYSource
String
Yes GPS
HSPDomainXYSource __ 9
AttDate
Date
No
0 0 8
FeaturelD
String
Yes
__ 20
JobID
String
Yes
__ 12
Problem
String
Yes
__ 50
Reason
String
Yes
__ 50
MaxTier
String
Yes
HSPDomainTiers 3
DomainEnabled
Short integer
Yes 1
EnabledDomain 0 _
Photo1
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
255
Geometry
Diameter
Height
Width
Material
USFeatureTy
DSFeatureTy
USDD
DSDD
USEIevEst
DSEIevEst
Comments
PhotolDs
PhotoYN
Photol-ink
Owner
AttDate
FeaturelD
USID
DSID
JoblD
Problem
Reason
MaxTier
DomainEnabled
Length
Photo1
Photo2
Photo3
FeatureTy
Comments
PhotoYN
PhotolDs
Photol-ink
Number of Pipes In
Number of Pipes Out
ROWDischPt
ContConvey
ApproxElev
XYSource
AttDate
FeaturelD
JobID
Problem
Reason
MaxTier
DomainEnabled
Photo1
Photo2
Photo3
Revised 98 June 2016

_c -
Highway
Storrnwater Field Inventory Procedures Manual
Simple feature class
Geometry Point
PI el0
P
Contains M values No
Contains Z values No
Data •
Allow
Default value
Prec-
Domain
OBJECTID
Object ID
�
�� _
Shape
Geometry
Yes
FeatureTy
String
Yes
HSPDomainPipelOType__ 6
Scour
String
Yes
No
HSPDomainYesNo __ 3
Comments
String
Yes
__ 255
MaintNeed
String
Yes
No
HSPDomainYesNo __ 3
MaintCom
String
Yes
__ 255
PhotoYN
String
Yes
No
HSPDomainYesNo __ 3
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
__ 255
Incoming
Short integer
Yes
0 _
Outgoing
Short integer
Yes
0
OutfaIIWOS
String
Yes
No
HSPDomainYesNoUnkn __ 7
ConfirmOF
String
Yes
No
HSPDomainYesNo __ 3
ROWDischPt
String
Yes
No
HSPDomainYesNoUnkn7
ContConvey
String
Yes
HSPDomdlHOhannelDS __ 15
Encroach
String
Yes
No
HSPDomainYesNo 3
Obstructed
String
Yes
0
HSP omainObstruction
oo��onf��o __ 6
ApproxElev
Double
Yes
0 0
Owner
String
Yes
NCDOT
HSPDomainOwner __ 7
XYSource
String
Yes
GPS
HSPDomainXYSource __ 9
AttDate
Date
Yes
0 0 8
Reason
String
Yes
__ 50
FeaturelD
String
Yes
__ 20
JobID
String
Yes
__ 12
Problem
String
Yes
__ 50
MaxTier
String
Yes
HSPDomainTiers __ 3
DomainEnabled
Short integer
Yes
1
EnabledDomain 0 _
Photol
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
255
Simple feature class
Geometry Point
Photo
Contains M values No
Contains Z values No
Field name
Data type
Allow
nulls Default value
Prec-
Domain ision Scale Length
OBJECTID
Object ID
Shape
Geometry
Yes
Comments
String
Yes
__ 255
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
__ 255
Incoming
Short integer
Yes
0 _
Outgoing
Short integer
Yes
0 _
ApproxElev
Double
Yes
0 0
XYSource
String
Yes GPS
HSPDomainXYSource __ 9
AttDate
Date
Yes
0 0 8
FeaturelD
String
Yes
__ 20
JobID
String
Yes
__ 12
Problem
String
Yes
50
Reason
String
Yes
�_ 50
DomainEnabled
Short integer
Yes 1
EnabledDomain 0 _
Photol
String
Yes
�_ 255
Photo2
String
Yes
�_ 255
Photo3
String
Yes
255
FeatureTy
Scour
Comments
MaintNeed
MaintCom
PhotoYN
PhotolDs
Photol-ink
Number of Pipes In
Number of Pipes Out
OutfalIWOS
ConfirmOF
ROWDischPt
ContConvey
Encroach
Obstructed
ApproxElev
Owner
XYSource
AttDate
Reason
FeaturelD
JobID
Problem
MaxTier
DomainEnabled
Photol
Photo2
Photo3
Comments
PhotolDs
Photol-ink
Number of Pipes In
Number of Pipes Out
ApproxElev
XYSource
AttDate
FeaturelD
JobID
Problem
Reason
DomainEnabled
Photol
Photo2
Photo3
Revised 99 June 2016

_r-
Highway
Storrnwater Field Inventory Procedures Manual
■ Simple feature class
L'J OverlandFlow
OBJECTID
Object ID
Shape
Geometry
Yes
FeatureTy
String
Yes
Comments
String
Yes
PhotoYN
String
Yes
PhotolDs
String
Yes
Photol-ink
String
Yes
XYSource
String
Yes
AttDate
Date
Yes
FeaturelD
String
Yes
JoblD
String
Yes
Problem
String
Yes
Reason
String
Yes
MaxTier
String
Yes
DomainEnabled
Short integer
Yes
Photol
String
Yes
Photol
String
Yes
Photo3
String
Yes
■ Simple feature class
LandPoint
OBJECTID
Object ID
=
Shape
Geometry
Yes
FeatureTy
String
Yes
Comments
String
Yes
PhotoYN
String
Yes
PhotolDs
String
Yes
Photol-ink
String
Yes
XYSource
String
Yes
AttDate
Date
Yes
FeaturelD
String
Yes
JoblD
String
Yes
Problem
String
Yes
Reason
String
Yes
MaxTier
String
Yes
DomainEnabled
Short integer Yes
Photol
String
Yes
Photo2
String
Yes
Photo3
String
Yes
Geometry Point
Contains M values No
Contains Z values No
HSPDomainOverlandFlo 9
-i 255
No HSPDomainYesNo __ 3
255
255
GPS HSPDomainXYSource __ 9
0 0 8
__ 20
12
50
50
HSPDomainTiers __ 3
1 EnabledDomain 0 _
255
255
255
Geometry Point
Contains M values No
Contains Z values No
HSPDomainPeakSag __ 9
255
No HSPDomainYesNo __ 3
255
255
GPS HSPDomainXYSource __ 9
0 0 8
20
12
50
50
HSPDomainTiers __ 3
1 EnabledDomain 0 _
255
255
255
FeatureTy
Comments
PhotoYN
PhotolDs
Photol-ink
XYSource
AttDate
FeaturelD
JoblD
Problem
Reason
MaxTier
DomainEnabled
Photol
Photol
Photo3
FeatureTy
Comments
PhotoYN
PhotolDs
Photol-ink
XYSource
AttDate
FeaturelD
JoblD
Problem
Reason
MaxTier
DomainEnabled
Photol
Photo2
Photo3
Revised 100 June 2016

_c -
Highway
Storrnwater Field Inventory Procedures Manual
Simple feature class
Geometry Point
Junction
Contains M values No
Contains Z values No
Field name
D.. type
Allow
nulls
Default value
Prec-
Domain
OBJECTID
Object ID
Shape
Geometry
Yes
,_
FeatureTy
String
Yes
HSPDomai QJunctionTyp ,_ 8
Numinflo
Short integer Yes
0
0 _
Depth
Double
Yes
0 0
Steps
String
Yes
HSPDomainSteps __ 11
Accessible
String
Yes
HSPDomainAccessible __ 11
Comments
String
Yes
__ 255
MaintNeed
String
Yes
No
HSPDomainYesNo __ 3
MaintCom
String
Yes
__ 255
PhotoYN
String
Yes
No
HSPDomainYesNo __ 3
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
__ 255
Incoming
Short integer Yes
0 _
Outgoing
Short integer Yes
_
OutfaIIWOS
String
Yes
No
_0
HSPDomainYesNoUnkn
_ 7
ConfirmOF
String
Yes
No
HSPDomainYesNo __ 3
Tielns
Short integer Yes
HSPDomainTielns 0 _
TieSize
Double
Yes
0
HSPDomainTieSize 0
String
Yes
No
ioTielnFlow
HSPDomainYesNo _3
TieComment
String
Yes
_255
i
IllicitFlg
String
Yes
No
HSPDomainYesNo __ 3
ApproxElev,
Double
Yes
0 0
Owner
String
Yes
NCDOT
HSPDomainOwner __ 7
XYSource
String
Yes
GPS
HSPDomainXYSource __ 9
AttDate
Date
Yes
0 0 8
FeaturelD
String
Yes
__ 20
JobID
String
Yes
__ 12
Problem
String
Yes
__ 50
Reason
String
Yes
__ 50
MaxTier
String
Yes
HSPDomainTiers 3
DomainEnabled
Short integer Yes
1
EnabledDomain 0 _
Photol
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
255
Simple feature class
Geometry Polygon
JobWorkArea
Contains M values No
Contains Z values No
• name
D.. type
Allow
nulls Default value
Prec-
Domain
OBJECTID
Object ID
��
-__
Shape
Geometry
Yes
i__
Instructns
String
Yes
__ 255
FieldNotes
String
Yes
__ 255
MPolution
String
Yes
HSPDomainYesNo __ 3
MExBMP
String
Yes
HSPDomainYesNo __ 3
MIIIDischg
String
Yes
HSPDomainYesNo __ 3
MPRetrofit
String
Yes
HSPDomainYesNo __ 3
MPhoto
String
Yes
HSPDomainYesNo __ 3
MOFlow
String
Yes
HSPDomainYesNo __ 3
BufferSize
Double
Yes 0
0 0
Tier
String
Yes
HSPDomainTiers __ 6
County
String
Yes
__ 15
Division
String
Yes
__ 15
FieldCrew
String
Yes
__ 6
FirmName
String
Yes
__ 30
RegDate
Date
Yes
0 0 8
CreateDate
Date
Yes
0 0 8
JobID
String
Yes
__ 12
MaxFeatlD
Long integer
Yes 0
0 _
Shape_Length
Double
Yes
0 0
Shape_Area
Double
Yes
0 0
Photol
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
255
FeatureTy
NumPipes
Depth
Steps
Accessible
Comments
MaintNeed
MaintCom
PhotoYN
PhotolDs
Photol-ink
Number of Pipes In
Number of Pipes Out
OutfalIWOS
ConfirmOF
Tielns
TieSize
TielnFlow
TieComment
I IlicitFlg
ApproxElev
Owner
XYSource
AttDate
FeaturelD
JobID
Problem
Reason
MaxTier
DomainEnabled
Photol
Photo2
Photo3
Instructns
FieldNotes
MPolution
MExBMP
MIIIDischg
MPRetrofit
MPhoto
MOFlow
BufferSize
Tier
County
Division
FieldCrew
FirmName
RegDate
CreateDate
JobID
MaxFeatlD
Photol
Photo2
Photo3
Revised 101
June 2016

NCDOT
Ww'.— Field Inventory Procedures Manual
■ Simple feature class Geometry Point I
' Inlet Contains M values No
Contains Z values No
OBJECTID
Object ID
,MkL—
Shape
Geometry
Yes
FeatureTy
String
Yes
HSPDomainlnletType __ 8
FeatureTy
NumGrate
Short integer Yes
0 _
Numerate
Depth
Double
Yes
0 0
Depth
Steps
String
Yes
HSPDomainSteps __ 11
Steps
Surround
String
Yes
HSPDomainSurrounding __ 35
Surround
Accessible
String
Yes
HSPDomainAccessible __ 11
Accessible
Comments
String
Yes
__ 255
Comments
MaintNeed
String
Yes
No
HSPDomainYesNo __ 3
MaintNeed
MaintCom
String
Yes
__ 255
MaintCom
PhotoYN
String
Yes
No
HSPDomainYesNo __ 3
PhotoYN
PhotolDs
String
Yes
__ 255
PhotolDs
Photol-ink
String
Yes
__ 255
Photol-ink
Incoming
Short integer Yes
0
Number of Pipes In
Outgoing
Short integer Yes
0
Number of Pipes Out
Outt
String
Yes
No
__ 7
HSPDomainYesNoUnknaIIWOS
OutfallWOS
ConfirmOF
String
Yes
HSPDomainYesNo __ 3
ConfirmOF
Obstructed
String
Yes
0
H S P Domai nobstru ction
oe—M.tee 1 __ 6
Obstructed
Tielns
Short integer Yes
HSPDomainTielns 0
Tielns
TieSize
Double
Yes
0
HSPDomainTieSize 0 ZE
TieSize
TielnFlow
String
Yes
No
HSPDomainYesNo _3
TielnFlow
TieComment
String
Yes
__ 255
TieComment
IllicitFlg
String
Yes
No
HSPDomainYesNo __ 3
IllicitFlg
ApproxElev
Double
Yes
0 0 =
ApproxElev
Owner
String
Yes
NCDOT
HSPDomainOwner __ 7
Owner
XYSource
String
Yes
GPS
HSPDomainXYSource __ 9
XYSource
AttDate
Date
Yes
0 0 8
AttDate
FeaturelD
String
Yes
__ 20
FeaturelD
JoblD
String
Yes
__ 12
JobID
Problem
String
Yes
__ 50
Problem
Reason
String
Yes
__ 50
Reason
MaxTier
String
Yes
HSPDomainTiers __ 3
MaxTier
DomainEnabled
Short integer Yes
1
EnabledDomain 0
DomainEnabled
Photol
String
Yes
__ 255
Photol
Photo2
String
Yes
__ 255
Photol
Photo3
Strinq
Yes
�� 255
Photo3
■ Simple feature class
Geometry Point
•
• IllicitDischargePoint
Contains M values No
ContainsZvalues No
OBJECTID
Object ID
9r ,
Shape
Geometry
_M-
Yes -
StructType
String
Yes
HSPDomainDischargeF
10
PhysicalOb
String
Yes
-A
HSPDBRtttrfi[31S hargeT __ 9
ActiveFlow
String
Yes Yes
HSPDomainYesNo __ 3
Odor
String
Yes
HSPDomainDischarge0__ 10
Color
String
Yes
HSPDomaftischargeC 6
HSPDomif7ischargeA__
Appearance
String
Yes
9
VegCond
String
Yes
HSPD61 MMD%I&argeV
9
LandUse
String
Yes
HSPDomainLandUse __ 20
Source
String
Yes
H S PPDoma i n Disch argeS
8
Comments
String
Yes
-.— __ 255
PhotoYN
String
Yes No
HSPDomainYesNo __ 3
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
__ 255
Reporter
String
Yes
30
ReporterTy
String
Yes NCDOT
HSPDomat--hargeR
10
XYSource
String
Yes GPS
o��NTno
HSPDomainXYSource __ 9
AttDate
Date
Yes
0 0 8
FeaturelD
String
Yes
__ 20
JobID
String
Yes
__ 12
Problem
String
Yes
__ 50
Reason
String
Yes
__ 50
Photol
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
__ 255
OutfalllllicitDischarge
String
Yes
HSPDomainOuttalllllicitD 50
StructType
PhysicalOb
ActiveFlow
Odor
Color
Appearance
VegCond
LandUse
Source
Comments
PhotoYN
PhotolDs
Photol-ink
Reporter
ReporterTy
XYSource
AttDate
FeaturelD
JoblD
Problem
Reason
Photol
Photo2
Photo3
Outfall I I IicitD ischa rge
Revised 102
June 2016

NCDOT
pw--,
Field Inventory Procedures Manual
Simple feature class Geometry Point
• ■ DeckDrains Contains M values No
Contains Z values No
OBJECTID
Object ID
Shape
Geometry
Yes
SysClosed
String
Yes
No
HSPDomainYesNo
3
NumDrains
Short integer
Yes
0 _
Comments
String
Yes
__ 255
MaintNeed
String
Yes
No
HSPDomainYesNo
__ 3
MaintCom
String
Yes
__ 255
PhotoYN
String
Yes
No
HSPDomainYesNo
__ 3
PhotolDs
String
Yes
__ 255
Photol-ink
String
Yes
255
Incoming
Short integer
Yes
0 i
Outgoing
Short integer
Yes
0 -
OutfaIIWOS
String
Yes
No
HSPDomainYesNoUnkn
_M 7
ConfirmOF
String
Yes
HSPDomainYesNo
__ 3
ApproxElev
Double
Yes
0 0
AttDate
Date
No
0 0 8
Owner
String
Yes
NCDOT
HSPDomainOwner
__ 7
XYSource
String
Yes
GPS
HSPDomainXYSource
__ 9
FeaturelD
String
Yes
__ 20
JobID
String
Yes
__ 12
Problem
String
Yes
__ 50
Reason
String
Yes
__ 50
MaxTier
String
Yes
HSPDomainTiers
__ 3
DomainEnabled
Short integer
Yes
1
EnabledDomain
0 _
Photol
String
Yes
__ 255
Photo2
String
Yes
__ 255
Photo3
String
Yes
255
tiSimple feature class
r Culvert
OBJECTID
Object ID
i
Shape
Geometry
Yes
Geometry
String
Yes
Diameter
Double
Yes
Height
Double
Yes
Width
Double
Yes
Material
String
Yes
USFeatureTy
String
Yes
DSFeatureTy
String
Yes
USDD
Double
Yes
DSDD
Double
Yes
USEIevEst
Double
Yes
DSEIevEst
Double
Yes
Comments
String
Yes
PhotoYN
String
Yes
PhotolDs
String
Yes
Photol-ink
String
Yes
Owner
String
Yes
AttDate
Date
Yes
FeaturelD
String
Yes
USID
String
Yes
DSID
String
Yes
JobID
String
Yes
Problem
String
Yes
Reason
String
Yes
MaxTier
String
Yes
DomainEnabled
Short integer Yes
Length
Double
Yes
Shape_Length
Double
Yes
Photol
String
Yes
Photo2
String
Yes
Photo3
String
Yes
Geometry Polyline
Contains M values No
Contains Z values No
Im '__
Cir HSPDomainGeometry __
12
0 0
0 0
0 0
Concrete HSPDomainPivpeMaterial_w
HSDomainUSDSFeature_r
H SDom ai rTUS90S Featu renwI
8
20
Tvnc
20
0 0
0 0
0 0
0 0
`
255
No HSPDomainYesNo
3
255
255
NCDOT HSPDomainowner __
7
0 0
8
MM
20
__
15
MM
15
12
50
50
HSPDomainTiers __
3
1 EnabledDomain 0 _
0 0
0 0
255
255
255
SysClosed
NumDrains
Comments
MaintNeed
MaintCom
PhotoYN
PhotolDs
Photol-ink
Number of Pipes In
Number of Pipes Out
OutfaIIWOS
ConfirmOF
ApproxElev
AttDate
Owner
XYSource
FeaturelD
JobID
Problem
Reason
MaxTier
DomainEnabled
Photol
Photo2
Photo3
Geometry
Diameter
Height
Width
Material
USFeatureTy
DSFeatureTy
USDD
DSDD
USEIevEst
DSEIevEst
Comments
PhotoYN
PhotolDs
Photol-ink
Owner
AttDate
FeaturelD
USID
DSID
JobID
Problem
Reason
MaxTier
DomainEnabled
Length
Photol
Photo2
Photo3
Revised 103 June 2016

NCDOT
PROGRAM
❑Simple feature class
ChannelPoint
OBJECTID
Object ID
1
Shape
Geometry
Yes
FeatureTy
String
Yes
Comments
String
Yes
PhotoYN
String
Yes
PhotolDs
String
Yes
Photol-ink
String
Yes
OutfallWOS
String
Yes
ConfirmOF
String
Yes
ROWDischPt
String
Yes
ContConvey
String
Yes
Encroach
String
Yes
Obstructed
String
Yes
ApproxElev
Double
Yes
Owner
String
Yes
XYSource
String
Yes
AttDate
Date
Yes
FeaturelD
String
Yes
JoblD
String
Yes
Problem
String
Yes
Reason
String
Yes
MaxTier
String
Yes
DomainEnabled
Short integer
Yes
Photol
String
Yes
Photo2
String
Yes
Photo3
String
Yes
❑+ Simple feature class
Channel
OBJECTID
Object ID
Shape
Geometry
Yes
FeatureTy
String
Yes
TopWidth
Double
Yes
BotWidth
Double
Yes
Depth
Double
Yes
LiningType
String
Yes
StandH2O
String
Yes
USFeatureTy
String
Yes
DSFeatureTy
String
Yes
USEIevEst
Double
Yes
DSEIevEst
Double
Yes
IllicitFlg
String
Yes
Scour
String
Yes
Comments
String
Yes
MaintNeed
String
Yes
MaintCom
String
Yes
PhotoYN
String
Yes
PhotolDs
String
Yes
Photol-ink
String
Yes
Owner
String
Yes
AttDate
Date
Yes
FeaturelD
String
Yes
USID
String
Yes
DSID
String
Yes
JoblD
String
Yes
Problem
String
Yes
Reason
String
Yes
MaxTier
String
Yes
DomainEnabled
Short integer
Yes
Length
Double
Yes
Shape_Length
Double
Yes
Photol
String
Yes
Photo2
String
Yes
Photo3
String
Yes
Revised
Field Inventory Procedures Manual
Geometry Point
Contains M values No
Contains Z values No
..yV"nhT.mo4""V" ..111111111111_ g
255
No
HSPDomainYesNo __ 3
255
No
HSPDomainYesNoUnkn=� 275
No
HSPDomainYesNo _� 3
HSPDomainYesNoUnkn_
No
7
HSPDomd1liChannelDS
15
HSPDZft1RY1 VftUnkn=�
No
7
HSPDomdlHObstruction
0
6
Pcrncn4nnc 1
0 0
NCDOT
HSPDomainowner 7
GPS
HSPDomainXYSource __ 9
0 0 8
20
12
_- 50
_i 50
HSPDomainTiers __ 3
1
EnabledDomain 0 _
255
255
255
Geometry Pol
Contains M values No
Contains Z values No
Channel HSPDomainChannelTyp g
0 0
0 0
0 0
HSPDomainChannelLini__ 10
—T—
No
T—.
No HSPDomainYesNo
HSPDomainYesNo
No HSPDomainYesNo
No HSPDomainYesNo
NCDOT HSPDomainOwner
HSPDomainTiers
1 EnabledDomain
104
7_ 3
._ 20
._ 20
0 0
0 0
._ 3
._ 3
._ 255
._ 3
._ 255
._ 3
._ 255
._ 255
._ 7
0 0 8
._ 20
._ 15
._ 15
._ 12
._ 50
._ 50
._ 3
0 _
0 0
0 0
._ 255
._ 255
255
FeatureTy
Comments
PhotoYN
PhotolDs
Photol-ink
OutfallWOS
ConfirmOF
ROWDischPt
ContConvey
Encroach
Obstructed
ApproxElev
Owner
XYSource
AttDate
FeaturelD
JoblD
Problem
Reason
MaxTier
DomainEnabled
Photol
Photo2
Photo3
FeatureTy
TopWidth
BotWidth
Depth
LiningType
StandH2O
USFeatureTy
DSFeatureTy
USEIevEst
DSEIevEst
I IlicitFlg
Scour
Comments
MaintNeed
MaintCom
PhotoYN
PhotolDs
Photol-ink
Owner
AttDate
FeaturelD
USID
DSID
JoblD
Problem
Reason
MaxTier
DomainEnabled
Length
Photol
Photo2
Photo3
June 2016

Highway
Storrnwater Field Inventory Procedures Manual
■ Simple feature class
BMPExisting
OBJECTID
Object ID
Shape
Geometry
Yes
BMPType
String
Yes
SiteDesc
String
Yes
Comments
String
Yes
MaintNeed
String
Yes
MaintCom
String
Yes
PhotoYN
String
Yes
PhotolDs
String
Yes
Photol-ink
String
Yes
Incoming
Short integer
Yes
Outgoing
Short integer
Yes
ApproxElev
Double
Yes
Owner
String
Yes
XYSource
String
Yes
AttDate
Date
Yes
FeaturelD
String
Yes
BMPID
Long integer
Yes
JobID
String
Yes
Problem
String
Yes
Reason
String
Yes
DomainEnabled
Short integer
Yes
Photol
String
Yes
Photol
String
Yes
Photo3
String
Yes
Geometry Point
Contains M values No
Contains Z values No
■mil. -J===
HSPDomainBMPType __ 12
255
255
No HSPDomainYesNo __ 3
255
No HSPDomainYesNo __ 3
255
255
0 _!
0
0 0
NCDOT HSPDomainowner 7
GPS HSPDomainXYSource 9
0 0 8
20
0
12
50
50
1 EnabledDomain 0 _
__ 255
__ 255
MM 255
BMPType
SiteDesc
Comments
MaintNeed
MaintCom
PhotoYN
PhotolDs
Photol-ink
Number of Pipes In
Number of Pipes Out
ApproxElev
Owner
XYSource
AttDate
FeaturelD
BMPID
JobID
Problem
Reason
DomainEnabled
Photol
Photol
Photo3
Revised 105 June 2016

r _-
Highway
Stormwater
Geodatabase Domain Listings
Coded value domain
HSPDomainChannelPointType
Description
Field type String
Split policy Default value
Merge policy Default value
Code
HighPoint
Description
High Point
ChanJunct Channel Junction
Blind End
Blind End
Curb Cut
Curb Cut
Outfall
Outfall
Other
Other
Coded value domain
HSPDomainChannelType
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code
Description
Channel
Ditch
Ditch
Swale
Swale
SheetFlow
SheetFlow
Curb
Curb
Barrier
Traffic Barrier Flow
Coded value domain
HSPDomainDischargeColor
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
Black
Black
Brown
Brown
Yellow
Yellow
Green
Green
Gray
Gray
White
White
Clear
Clear
Other
Other
Coded value domain
HSPDomainDischargeFeatureType
Description
Field type String
Split policy Default value
Merge policy Default value
Pipe
DescriptionCode
Pipe
Ditch
Ditch
CatchBasin
Catch Basin
Gratelnlet
Grated Inlet
Manhole
Manhole
Other
Other
Field Inventory Procedures Manual
Coded value domain
HSPDomainDischargeAppearance
Description
Field type String
Split policy Default value
Merge policy Default value
Code Description
Oilysheen Oily sheen
Sewage Sewage
Chemical Chemical
Detergent Detergent
Other Other
Coded value domain
HSPDomainOutfall I IlicitDischarge
Description
Field type String
Split policy Default value
Merge policy Default value
Code Description Found Not Found
Found Found
Inconclusive Inconclusive
Coded value domain
HSPDomainChannelDSConveyType
Description
Field type String
Split policy Default value
Merge policy Default value
Code
Description Channel
Pipe
Pipe
Sheet Flow
Sheet Flow
Unknown
Unknown
Coded value domain
HSPDomainDischargeSource
Description
Field type String
Split policy Default value
Merge policy Default value
Code
Description Residential
SanSewer
Sanitary Sewer
SpillRel
Spill Release
Coml/Ind Commercial/Industrial
Other
Other
Revised 106 June 2016

NCDOT
ow-c-,
Coded value domain
HSP Domain Poll utionSou rceType
Description
Field type String
Split policy Default value
Merge policy Default value
Code
ErosConst
Description
Erosion-ConstructionSite
ErosNonConst
Erosion-nonConstructionSite
ImpactBuffer
Impacted Buffer
TrashDmpng
Trash Dumping
SanWaste
Sanitary Waste
OutdMatStor
Outdoor Material Storage
GasStation
Gas Station
VehRepairMnt
Vehicle Repair/Maint
Junkyard
Junk Yard
Restaurant
Restaurant
DumpMngmt
Dumpster Management
Ag-Animals
Ag-Animals
Ag-Crops
Ag-Crops
Golf Course
Golf Course
TurfLandscap
Turf/Landscaping
Coded value domain
HSPDomainlnletType
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
Grate
Grate
Curb
Curb
Combo
Combination
Funnel
Funnel
Yard
Yard
Unverify
Unverified
Other
Other
Coded value domain
HSPDomainAccessible
Description
Field type String
Split policy Default value
Merge policy Default value
Code Description
Open able Accessible -Open
NotOpenable Accessible -Not Openable
NoAccess Inaccessible
Coded value domain
HSPDomainTiers
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
Is
Tier la
lb
Tier lb
Ic
Tier Ic
II
Tier II
III
Tier III
Field Inventory Procedures Manual
Coded value domain
HSPDomainPipeMaterial
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code
Description
Concrete
Concrete
CMP
Corrugated Metal
CPP
Corrugated Plastic
PVC
PVC
Iron
Iron
VCP
Vitrified Clay
Stone
Stone
Brick
Brick
Other
Other
Coded value domain
HSPDomainTielns
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
10
Tie -In 10
11
Tie -In 11
12
Tie -In 12
01
Tie -In 01
02
Tie -In 02
03
Tie -In 03
04
Tie -In 04
05
Tie -In 05
06
Tie -In 06
07
Tie -In 07
08
Tie -In 08
09
Tie -In 09
0
not collected
Coded value domain
HSPDomainObstruction Percentage_1
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code
0
Description
0
1-25
1 to 25
51-75
51 to 75
76-100
76 to 100
26-50
26 to 50
NTR
Non Tier Required
Coded value domain
HSPDomainSiteOwner
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code
Description
NCDOT
NCDOT
City
City
Private
Private
Unknown
Unknown
Revised 107 June 2016

NCDOT
pw--,
Coded value domain
HSPDomainSurroundings
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code
Description Expressway Gutter
ShldBermGutr
Shoulder Berm Gutter
CurbGutter
Curb and Gutter
TraffBarrier
Traffic Barrier
VegShoulder
Vegetated Shoulder Section
Other
Other
NC4T
Not Collected for Tier
Coded value domain
HSPDomainOwner
Description
Field type String
Split policy Default value
Merge policy Default value
Code
Description
NCDOT
NCDOT
Public
Public
Private
Private
Unknown
Unknown
Coded value domain
HSPDomainDischargeReporterType
Description
Field type String
Split policy Default value
Merge policy Default value
..-
NCDOT
Description
NCDOT Personal
Contractor
NCDOT Contractor
AdoptHwy
Adopt -A -Highway
GenPublic
General Public
Other
Other
Coded value domain
HSPDomainPeakSag
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
Peak Peak
Field Inventory Procedures Manual
Coded value domain
HSDomainUSDSFeatureType
Description Up/Dn structure type
Field type String
Split policy Default value
Merge policy Default value
..-
Description
BlindEnd
Blind End
BuriJunc
Buried Junction
ChanJunct
Channel Junction
ChanPt
Channel Point
Comb
Combination
Curb
Curb
CurbCut
Curb Cut
Funnel
Funnel
Grate
Grate
HighPt
High Point
JuncBox
Junction Box
LowPIROW
Low Point ROW
Manhole
Manhole
Other
Other
Peak
Peak
Inlet
Pipe Inlet
Outlet
Pipe Outlet
Sag
Sag
STUB
STUB
Unverify
Unverified
Yard
Yard
Coded value domain
HSPDomainYesNoUnknown
Description
Field type String
Split policy Default value
Merge policy Default value
Code Description
Yes Yes
No No
Unk Unknown
Coded value domain
HSPDomainYesNo
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
Yes Yes
No No
Coded value domain
HSPDomainPipePtType
Description
Field type String
Split policy Default value
Merge policy Default value
Code Description
Flowln Flow into ROW
FlowOut Flow out of ROW
Revised 108 June 2016

NCDOT
tea__
Coded value domain
HSPDomainLand Use
Description
Field type String
Split policy Default value
Merge policy Default value
Code
Description
Residential
Residential
Commercial
Commercial
Industrial
Industrial
Rural
Rural
Coded value domain
HSPDomainDischargeVegCond
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
None None
Normal Normal Growth
Excessive Excessive Growth
Inhibited Inhibited Growth
Coded value domain
HSPDomainTieSize
Description
Field type Double
Split policy Default value
Merge policy Default value
DescriptionCode
2.25
2.25
2.5
2.5
3
3
4
4
6
6
8
8
12
12
2
2
0.75
0.75
1
1
1.25
1.25
1.5
1.5
0
not collected
10
10
Coded value domain
HSPDomainSteps
Description
Field type String
Split policy Default value
Merge policy Default value
Code
Description
Pass able
Present -Passable
NotPassable
Present -Not Passable
NotPresent
Not Present
Field Inventory Procedures Manual
Coded value domain
HSPDomainChannelLiningType
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code
Clay/Silt
Description
Clay/Silt
Sandy
Sandy
Cobbles
Cobblestone
GrassVeg
GrassNegetative
Riprap
Riprap
FabricForm
Fabric Form
Other
Other
NC4T
Not Collected for Teir
ConcAsphlt
Concrete / Asphalt
Coded value domain
HSPDomainXYSource
Description
Field type String
Split policy Duplicate
Merge policy Default value
DescriptionCode
GPS
GPS
HandPlace
Hand Placed
GPSOffset
GPS-Offset
Survey
Survey
Asbuilt
Asbuilt
Other
Other
Coded value domain
HSPDomainGeometry
Description
Field type String
Split policy Duplicate
Merge policy Default value
DescriptionCode
Cir
Circular
Rect
Rectangular
Arch
Arch
Ellipt
Elliptical
Box
Box
Other
Other
NC4T
Not Collected for Tier
Coded value domain
HSPDomainDischargeOdor
Description
Field type String
Split policy Default value
Merge policy Default value
Code
Description
Sewage
Sewage
RottenEggs
Rotten Eggs
Fishy
Fishy
Skunk
Skunk
Petroleum
Petroleum
None
None
Other
Other
Revised 109 June 2016

NCDOT
Coded value domain
HSPDomainPipelOType
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code Description
Inlet Pipe Inlet
Outlet Pipe Outlet
Coded value domain
HSPDomainBMPType
Description
Field type String
Split policy Default value
Merge policy Default value
DescriptionCode
BioretBasin
BioretentiorrBasin
BioretSwale
Bioretention:Swale
DryDetBasin
Dry Detention:Basin
DryDetSwale
Dry Detention:Swale
WetDetPond
Wet Detention Pond
LevSpread
Level Spreader
FiltBasn
Filtration:Basin
FiltSwale
Filtration:Swale
InfiltBasin
in Filtration: Basin
InfiltSwale
inFiltration:Swale
SWWetland
Stormwater Wetland
HazSplBasin
Hazardous Spill Basin
PrefScourHol
Preformed Scour Hole
PropCBlnlet
Proprietary Catch Basin Inlet
PropWQlnlet
Proprietary Water Quality Inlet
Other
Other -Describe
Coded value domain
HSPDomainOverland Flow
Description
Field type String
Split policy Default value
Merge policy Default value
Code
Description
SheetFlo
Sheet Flow
CurbFlo
Concrete Curb Flow
DivideFlo
Concrete Divider Flow
Coded value domain
EnabledDomain
Description
Field type Short integer
Split policy Default value
Merge policv Default value
False
True
Field Inventory Procedures Manual
Coded value domain
HSPDomainDischargeType
Description
Field type String
Split policy Default value
Merge policy Default value
Code Description
Dump Dump
Discharge Discharge
Other Other
Coded value domain
HSPDomainJunctionType
Description
Field type String
Split policy Duplicate
Merge policy Default value
Code Description
Manhole Manhole
JunctBox JunctionBox
Revised 110 June 2016