 |
 |
Hi All, I am with Jason on this one. Making a unique ID that includes some location description just adds another element to manage in your database one feature at a time. I think it is useful to have another field with something like the basin ID, but I wouldn't rely on it as part of the unique ID. That way you can just apply the basin ID to all the points within that basin all at once. If you have to change it on individual features it just gets messy when you have to edit a catchment boundary or something. If you have 1000 DMHs and CBs spread across 10 basins, I would recommend numbering them 1-1000, and keeping the basin ID separate. Then you can still quickly query basins by the other field (or symbolize), but your labels are shorter because you don't need to have the prefix representing the basin. And if you DO want to label with the basin, your labeling expression can be: [basin]&"_"&[ID] I also stay away from the prefixes CB, DMH, SMH for the same reason: you can symbolize your maps to indicate whether something is a manhole or a catch basin, so adding the prefix "SMH_" or "CB_" before every number doesn't really help, it just makes your labels longer. Jeff On Wed, Aug 3, 2016 at 4:03 PM, Brett R. Horr <[log in to unmask]> wrote: > > +2. > > We use a meaningful hydro feature name that is adjacent to or a part of > the system like Long Beach (LB) or Bridges Swamp (BS) as the prefix and > then start increasing the numbers as one moves away from the outfall. > > Brett Horr, GISP > Director of GIS and Technology > Town of York > 186 York Street > York, Maine 03909-1314 > (207) 363-1007x243 > http://www.yorkmaine.org/ > > From: Northeast Arc Users Group [mailto:[log in to unmask]] On > Behalf Of Lynne Fielding > Sent: Wednesday, August 03, 2016 3:57 PM > To: [log in to unmask]<mailto:[log in to unmask]> > Subject: Re: Stormwater Feature Numbering > > Hi All > > For what it’s worth I advocate for a numbering schema that means something > (ie DCB_xxx, SMH_xxx) and here in Westwood the numbering itself relates to > the location in town they are…..sewer mini-systems or catchments, which > really helps when you’re trying to find it/them. I’ve worked with the other > way and those numbers are illogical and get really big and then just try to > label your map! Having a layer that shows where the ‘catchments’ are helps > too. > > My two cents before I retire ☺…………………… > > Lynne W Fielding GISP > GIS Specialist > IT Dept > Town of Westwood > 781-320-1082 > > From: Northeast Arc Users Group [mailto:[log in to unmask]] On > Behalf Of Jason Wise > Sent: Wednesday, August 03, 2016 3:48 PM > To: [log in to unmask]<mailto:[log in to unmask]> > Subject: Re: Stormwater Feature Numbering > > I'm a big fan of unique IDs that don't mean anything. If you have 1,000 > catchbasins, call the next one 1001, regardless of where it is. If it's in > a GIS, the number doesn't need to tell you where it is. > > Your boss will hate this idea, so of course you'll have to come up with > some kind of watershed-based system. > ________________________________ > From: Gambrel, Sean<mailto:[log in to unmask]> > Sent: 8/3/2016 11:36 AM > To: [log in to unmask]<mailto:[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]<mailto:[log in to unmask]> > > ------------------------------------------------------------------------- > 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 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 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. > > CONFIDENTIALITY: The information contained in this electronic mail message > and any electronic files attached to it may be confidential information, > and may also be the subject of legal professional privilege and/or public > interest immunity. If you are not the intended recipient you are required > to delete it. Any use, disclosure or copying of this message and any > attachments is unauthorized. If you have received this electronic message > in error, please inform the sender or contact [log in to unmask] This > footnote also confirms that this email message has been checked for the > presence of computer viruses. > > ------------------------------------------------------------------------- > 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 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.