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; } } }

Pavement Management System (PMS) implementation into GIS

RichardTruong

I've being asked to implement a Pavement Management System (PMS) into GIS and maintained through GIS. There are several issues I encountered during the implement process. First, the PMS system which were being recorded over the years is in Excel spreadsheet. The pavement of the recorded information is usually started at one intersection and ended at the next intersection. Secondly, this Excel data does not contain any unique value to each pavement record, just road names description of the beginning and end of the road intersections. Yes, there is a field indicating the total linear length of pavement. Now from the GIS point of view, GIS road segment some time has many breaks between two intersections. There are unique id number being assigned to each segment within GIS feature road data. At this point, I really have no idea where to begin regards the implementation. Any assistance is greatly appreciated.

PS. I have little knowledge in programming.

Najděte více příspěvků označených jako

Accepted answers

All comments

SepheFox

Hi Richard, is it possible to post a screenshot of your excel table? Does it have any x/y location fields, such as lat/long or other coordinates? How about your road layer? Does it contain intersection information?

If possible, can you post a zipped file of both the excel table, and the road data?

RichardTruong

Hi Sephe,

Thank you so much for taking the time to review my enquiry. The Excel table is too extensive for snap shot, therefore, I zipped the table along with our road centerline polyline feature for your review. A quick glance at the Excel table, the only information which require to join with the road centerline feature are hi-lite in 'yellow-color' fields. As you can see, there are no coordinate systems on either Excel or line feature, however, line feature can be modified to add the x/y coordinates. In addition, the line feature does not have intersection info.

Thank you,

Richard

RTruong.zip

JoeBorgione

Your street feature class has the 'ExternalStreetKey' field which appears to be a unique id which is a start.

With a name like External, one would think that someone was thinking of a relationship with (drum roll) some external data source I don't see that field defined in the spreadsheet, but if you were to comb through any other data sources you may find it attached to a table (spreadsheet) somewhere. If you can, that pretty much will allow you to relate the centerline features to the appropriate pavement record.

RichardFairhurst

Pavement management is dealing with the same basic problem as this post about Street Matching. Linear Referencing (LR) is the solution and was probably developed specifically because of pavement management requirements. LR can create any point or line segment using any portion of a linear feature without having to break that feature up. My solution is to maintian a segmented Centerline layer in a standard polyline feature class with a topology that ensures I create segment breaks at every intersection that fully snap together.

Then I have a script that derives 3 things from the Centerlines: 1) an LR Route network that merges all segments for each road into a single route with measures, 2) an intersection point feature class, and 3) an event table containing the route ID and measure of every pair of names in all orders that meet at each intersection. The event table contains fields I can join to other tables (like a PM table) based on a concatenated pair of street names so that I can convert other tables to LR event tables. Based on this derivative data I also have been able to build an application that walks a user through creating human readable limits that the application will convert into the route and measures required to define that segment.

You also should develop some kind of ID system for you PM segments. My jurisdiction uses our maintained road number billing numbers and a numerical segment ID for our PM IDs. It looks like M12345A 01000, where the first part is the billing number and the last part is the segment number. The use of a 5 digit segment number starting at 01000 lets us change the segmentation of the roads and maintain a unique sequential (south to north or west to east) numbering of each set of route limits, so that each set of limits over time is defined by a unique number.

RichardTruong

Hi Joe,

Thank you for the respond. Unfortunately, there is no unique id to Excel data, just Road Centerline feature.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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