Print

Print


This numbering schema is very well thought out, but what happens when you need to add 2  inlets between IN-PRN-569-002 and IN-PRN-569-003?  Do the new inlets get numbered IN-PRN-569-002.1 & .2?  This is the biggest problem we’ve faced in a water utility.  We had very specific hydrant ID’s, but as the system grows the sequencing doesn’t work.   For new hydrants we now use whatever the last number is, regardless of location.  So, now if an employee needs to know the location of a particular asset, they don’t need to know a naming schema, they simply look at their iPad.

 

Justin D. Richardson, GISP

GIS Coordinator

Kennebunk, Kennebunkport

and Wells Water District

92 Main Street, P.O. Box 88

Kennebunk, Maine 04043

Tel:  207-985-3385

Fax: 207-985-3102

Cell:  207-604-8092

www.kkw.org

 

 

From: Northeast Arc Users Group [mailto:[log in to unmask]] On Behalf Of Bisacquino, Janel
Sent: Thursday, August 04, 2016 9:57 AM
To: [log in to unmask]
Subject: Re: Stormwater Feature Numbering

 

Our stormwater inlet numbering schema was driven by the roadway crews that maintain them.

 

Each grouping of inlets along a county route or local road is numbered in sequence beginning at the start of the road’s primary direction. Since the maintenance crews actually did the physical numbering the sequence meanders back and forth across the road as they found the inlets.  But this is how they most likely would work on them during a roadway paving project as well, so it works. The inlet number is then a concatenation of the route number/road name and the sequential number. To farther help the crews and for reporting purposes, we add the municipality abbreviation when marking the inlets. In the labels look like this: IN-PRN-569-002 but is read backwards: Second inlet along Route 569 in Princeton. For local roads, we have three letter abbreviations instead of route numbers.

 

If I had it to do over again, I might have assigned even numbers to the inlets along the primary direction of travel and odd numbers along the secondary travel direction or maybe just run the sequence from the start of the primary direction and then back along the secondary direction. The latter would help lead crews to stay along the shoulder of the road when servicing them for increased safety.

 

This numbering method works when extended it to off road inlets and other stormwater features by including additional attributes for an offset measurement to the feature from the closest road shoulder as well as a distance from the closest intersection to where the offset measurement is taken. These aren’t part to the feature label but are printed out in a list describing stormwater features to be maintained during a road paving project or other stormwater maintenance operation. This allows new inlets to be added as the next number in sequence associated with the route/road and the maintenance crews can still find the feature, especially if the list is organized by intersection and distance from intersection.

 

For stormwater features that can equally be assigned to any road making up an intersection, our assignment rule is to assign features to the county route with the lowest route number or, if only local roads are involve, the local road with the name closest to the start of the alphabet. However, you might also break the tie by assigning the feature to the road with the most important functional class. This is the call of your director, an engineer or GIS specialist creating/maintained/updating the numbering system. Just make sure that it is consistently applied.

 

Using the basic building blocks of a linear reference system to help navigate work crews to the stormwater features seems to keep everyone on the same page when talking about the stormwater system and is easy to add to and has real world relevance.

 

Good Luck,

 

Janel

 

Janel A. Bisacquino, GIS Specialist

Transportation Asset Management Information System (TAMIS)

Mercer County Department of Transportation and Infrastructure

300 Scotch Road - Building 1, Ewing, NJ 08628

[log in to unmask]  609-530-7500 ext. 101

 

Building better tools to communication the good work we do here every day

to foster a safe and effective transportation network

 

ü Think before you print

 

 

From: Northeast Arc Users Group [mailto:[log in to unmask]] On Behalf Of Gambrel, Sean
Sent: Wednesday, August 03, 2016 11:37 AM
To: [log in to unmask]
Subject: Stormwater Feature Numbering

 

Hello all,

Here in Bangor  we’ve had our stormwater infrastructure in GIS for some time, but currently use a grid-based numbering system which is not particularly useful for anyone.  We’re considering a switch, as we have not done a significant amount of asset management on stormwater yet and the current system is quite confusing for our field crews.  Looking ahead, toward more asset management work, we’d like to have a better system in place. 

  

Our sanitary sewer system is numbered like a branching tree, with a two letter prefix denoting subsection and a three number pipe id number, which are divided into branches by 100s / 10s as necessary.  So for instance AB123.  This system works well for us, but unfortunately can’t easily be replicated for our stormwater system because it is discontiguous in nature. 

 

Our current grid-based system is more-or-less arbitrary, but includes the complication of using a grid which is otherwise unreferenced elsewhere in the city.  This is creating many headaches and conflicts among staff.

Would you be willing to share what your community is using for stormwater numbering and what the pros and cons have been in using this numbering system?

Thank you very much,

Sean

 

 

Sean Gambrel, GISP

GIS Administrator

Addressing Officer

 

City of Bangor, Maine

207-992-4245

[log in to unmask]

 

 

Click here to report this email as spam.

------------------------------------------------------------------------- This list (NEARC-L) is an unmoderated discussion list for all NEARC Users.

If you no longer wish to receive e-mail from this list, you can remove yourself by going to http://s.uconn.edu/nearcsubscribe.

 

This message has been scanned for malware by Websense. www.websense.com

------------------------------------------------------------------------- This list (NEARC-L) is an unmoderated discussion list for all NEARC Users.

If you no longer wish to receive e-mail from this list, you can remove yourself by going to http://s.uconn.edu/nearcsubscribe.


The information contained in this e-mail is intended for the addressed recipient only. If you have received this e-mail in error, please contact us at (207) 985-3385. This e-mail does not reflect an intention by the sender to conduct a transaction or make any agreement by electronic means or provide an electronic signature unless otherwise directly stated herein. We assume no liability for any damage claimed to have been sustained as a result of transmittal of malware.
------------------------------------------------------------------------- This list (NEARC-L) is an unmoderated discussion list for all NEARC Users.

If you no longer wish to receive e-mail from this list, you can remove yourself by going to http://s.uconn.edu/nearcsubscribe.