nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Street maintenance

JoshWhite

I'm what others are doing to track street maintenance. I looked at some of the templates on here and they just simply don't quite meet my needs. What I want to be able to do is track the maintenance on each street. (I.e. chip sealing, brick repair, pothole repair, mill/overlay, etc.) I want to be able to have a history for each segment/block and easily show planned maintenance as well. I'm using what appears to be a template but I can't remember the source of it. I'm not sure it is the best for what I am doing and was wondering if others had done anything similar.

PROJECTLINE.XML.zip

Find more posts tagged with

Local

Accepted answers

RichardFairhurst

Josh:

Conveying information from overlapping features is always a challenge, whether it is points, lines or polygons. Some form of distribution process is typical for points and lines, like bus routes. LR is ideal for this because without redrawing anything or changing any actual geometry I can create side offsets of overlapping lines or points on my Centerlines through an offset distance value in another field. So I can assign different levels of side offset to create a distribution pattern that has a relationship to the date ranges of overlapping events. Because the geometry of the events is created at runtime in memory, it is very flexible, but the redraw time is somewhat slower than normal features, and a large number of features drawing at once will noticeably slow ArcMap down. However, once you have your event side offsets arranged you can export then to become actual features so they will display quickly.

Converting your existing overlapping lines to events is possible through the Locate Features Along Routes tool. You can save both datasets, since the features you currently have will be permanent to the original network, while the events are cartographically adjustable. Because changes can happen to the underlying network, the Roads and Highways extension is worth considering, because it helps create time stamped versions of your Centerline network as it changes over time and maintains event integrity in response to those changes according to the rules you set. The 10.2.2 version of the extension also lets you define segments without tracing using human readable relative limits, based on cross streets (or any other feature that crosses your road network, like City Boundaries) and offset distances along the road in a compass direction.

All comments

JoshWhite

This looks promising, however, I just discovered that they charge for this extension which is disappointing to me. I was looking for an option I could work with in house similar to the LGIM.

RichardFairhurst

Josh:

JoshWhite

Thanks for your response. Mine is also separate from the actual centerline for the same reason you pointed out. I used the centerlines to trace so that they match up but that is pretty much it. Some of your other concerns are also the reason I am looking for options. Right now, basically I have multiple lines stacked on top of each other, so you can't really identify the top feature only as this will cause you to miss the underlying layers. We used Cartegraph briefly but I was never familiar with it.

RichardFairhurst

We use Street Saver too track all of our Pavement Management data history. It is designed to deal with Pavement Management rankings and contains algorithms you won't find in any ArcMap application I have seen. I download it and geocode it from Segment Descriptions using LR event overlays. I do not encode it into the underlying Centerline and never will. Since segments can change frequently, I am considering the Roads and Highways extension for improvement history tracking, but our Pavement Management group will not change to ArcGIS as core of its data maintenance tracking at any time in the foreseeable future. GIS is not responsive enough and not good enough at handling one-to-many relationships for me to recommend it to anyone. ArcMap reporting is also not equal to the task of outputting the data reports our Pavement Management group needs, or any reporting application as far as I am concerned. These are ArcGIS's main deficiencies as a database in my view.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.