7 Items to Check When Linking 2D Road Ledger Attached Maps with the Management Ledger

Table of Contents

• The purpose of linking the 2D road ledger attached map and the management ledger

• Basic policies to establish before linking

• Item 1: Verify the correspondence between route names and route numbers

• Item 2: Align the start point, end point, and length

• Item 3: Cross-check the road boundary lines and width information

• Item 4: Link management information for structures and appurtenances

• Item 5: Confirm the handling of coordinate systems and positional information

• Item 6: Record update histories and supporting documents in the management ledger

• Item 7: Leverage field verification results for the next update

• Common mistakes that often occur during management ledger linkage

• Summary

The Significance of Linking 2D Road Ledger Attached Maps and Management Ledgers

The 2D road ledger-attached map is a drawing used to organize, in plan view, the road location, road area, road centerline, road width, length, intersection configuration, structures such as side ditches and bridges, and the relationships with surrounding features. On the other hand, the management ledger is a document that organizes attribute information for managing roads, such as route name, route number, starting point, end point, length, width, structures, update history, inspection records, and repair history. By linking these two, it becomes easier to handle the positions on the drawings and the management information in the ledger under the same assumptions.

In road management practice, there is information that cannot be understood from drawings alone and information that is difficult to grasp from ledgers alone. By looking at two-dimensional road ledger supplementary maps, the positional relationships of road areas, centerlines, intersections, and structures become easier to understand. However, the official length of the route, width, management classification, update history, and management information for structures cannot always be fully confirmed from drawings alone. Conversely, even when the management ledger records length and width, it is difficult to determine which section on the ground they correspond to or which road area on the drawing they relate to without cross-referencing the supplementary maps.

When management ledger integration is not in place, differing information about the same road tends to remain between the drawings and the ledger. On the attached drawing the road boundary line may have been updated, while the road width in the management ledger remains outdated. The management ledger may show added structures whose positions are not reflected on the attached drawing. Even if the centerline has been corrected, the length and start/end point information may not have been updated. Such inconsistencies cause rework in construction coordination, occupancy confirmation, development consultation, maintenance and repair, and boundary verification.

The purpose of linking 2D road ledger maps and management ledgers is not to store drawings and ledgers separately, but to make the same road information verifiable in terms of both location and attributes. If you can organize so that route names and lengths are linked to centerlines on the drawings, update dates and source documents are linked to road boundary lines, and facility information and inspection histories are linked to the locations of structures, you can reduce the time spent verifying road management tasks and make it easier to prevent information omissions.

This article explains the seven items you should check when linking 2D road ledger maps with the management ledger. By sequentially confirming route information, start and end points, road area, road width, structures, coordinates, update history, and on-site inspection results, you can reduce inconsistencies between drawings and ledgers and make road management data easier to use in practice.

Fundamental Policies to Clarify Before Collaboration

Before linking the 2D road ledger maps with the management ledger, it is necessary to first clarify what will be linked. Attempting to fully synchronize all drawing information and all ledger information at once will make the scope of work too large. To start, it is easier to proceed by organizing the information that is frequently referenced in practice, such as route name, route number, starting point, end point, length, width, road area, structures, and update history.

The purpose of integration is also important. The required integration items vary depending on whether you simply want to improve readability, reduce rework when updating the management ledger, reflect on-site inspection results in the management ledger, or manage construction and inspection histories along the route. If you start work while the purpose is unclear, you are likely to end up in a half-finished state where information exists on drawings but cannot be searched from the ledger, or records exist in the ledger but their locations on the drawings cannot be identified.

Also, confirm which one will be used as the reference. The way to proceed will differ depending on whether you align the management register based on the 2D road ledger’s attached maps, update the attached maps based on the existing management register, or review both based on the field survey results. For information related to road areas and boundaries, you need to check not only the attached maps and registers but also land acquisition documents, boundary documents, as‑built drawings, and the field survey results together.

Before any coordination, confirming the latest versions is essential. If the official version of the attached drawings, the latest management ledger, work data currently being updated, and past versions are mixed together, it becomes unclear which information should be shared. Separate the official version and the working version, and make clear which point in time will be used as the reference. If this is left ambiguous, mistakes can occur, such as linking new ledger information to an old attached drawing or reflecting field survey results in a ledger that predates the update.

Also decide the granularity of the linked information. Whether you link at the route level, the section level, or the structure level will change the data organization required. Associating route information only with the road centerline is relatively simple, but if you link information for width-change points or for each structure, you will need rules for managing sections and points.

To successfully implement management ledger integration, it is important to first organize the integration targets, reference materials, latest versions, data granularity, and update operations. If these prerequisites are in place, it becomes easier to move toward a practical, usable state of integration by checking the following seven items.

Verify the correspondence between route names and route numbers as Item 1

The first item to verify is the correspondence between route names and route numbers. When linking the two-dimensional road ledger attached maps and the management ledger, it must be clear which road on the drawing corresponds to which route in the management ledger. If this is misaligned, even if you later organize information on length, width, road areas, and structures, you may mistakenly associate those details with the wrong road.

In practice, the same road can have multiple names. When official route names, route numbers, locally used common names, construction project names, district names, and drawing numbers are mixed together, it becomes difficult to match attachments with the management ledger. For management ledger integration, it is convenient to use the official route name and route number as the standard, and, as needed, organize common or related names as search-assist information.

On 2D road ledger maps, a single drawing may include multiple routes. At intersections or where several branch lines connect, it is necessary to confirm which centerline corresponds to which route. Roads that appear connected on the drawing may be treated as separate routes in the management ledger. Conversely, even if a road is split across multiple drawings, it may be managed as a single route in the management ledger.

Be mindful of duplicate or missing route numbers. In older ledgers and past attached maps, route names and numbers may be recorded differently than they are now. Due to road reorganization, changes in designation, changes in management classification, or development ownership, route information may have been updated. Before integration, confirm that the route information officially used in the current management ledger matches the representation on the attached map.

Once the correspondence of route information is clarified, it becomes easier to link the management ledger's route information to the centerline on the drawings. If the centerline is associated with the route name, route number, start point, end point, and length, you can create a workflow to check ledger information from the drawings and to locate the target position from the ledger. Verifying the correspondence between route names and route numbers is the entry point for linking with the management ledger.

Item 2: Make the start point, end point, and length consistent

The second item is the consistency of the start point, end point, and length. In the road ledger, a route's start point, end point, and length are managed as basic information. In two-dimensional road ledger attached maps, these are represented as the road centerline and as segments on the drawings. To link the management ledger and the attached maps, it is necessary to clarify where the ledger's start and end points correspond on the maps.

The start and end points may be treated differently depending on the route, such as the center of an intersection, the edge of the road area, management boundaries, administrative boundaries, the ends of a bridge, or connection points with other routes. If the positions of the start and end points remain ambiguous, this can cause discrepancies between the centerline length and the length recorded in the management ledger. When indicating the start and end points on attached drawings, confirm that they are consistent with the descriptions in the ledger records.

Regarding length, confirm whether it refers to the length along the road centerline or the length as a management section, and how intersection areas are to be treated. If the centerline remains as shown on an old attachment map, the length may not match the length in the management ledger. Even if the centerline has been revised due to road or intersection improvements, it is necessary to check whether this affects the length recorded in the management ledger.

For routes that span multiple drawings, confirm whether the centerlines on each drawing are continuous. If a centerline is interrupted or duplicated at a drawing boundary, it will affect length management. If the management ledger treats the length as a single route while the attached drawings are divided into multiple lines so that continuity is unclear, the data becomes difficult to handle as linked data.

Aligning the start point, end point, and length clarifies the positional relationships in road management information. Construction sections, repair sections, inspection points, and structure locations can be more easily organized by distance or by section from the start point, making cross-checking between the management register and the accompanying drawings smoother.

As Item 3, cross-check road boundary lines and width information

The third item is the reconciliation of road boundary lines and width information. In the two-dimensional road ledger map, road boundary lines are shown as the management range on the plane. In the management ledger, information on widths and road areas is organized as numerical values and attributes. If the two are not consistent, confusion will arise in judgments regarding road areas and widths.

The road area line indicates the boundary of the area managed as a road. It does not necessarily coincide with the pavement edge, the gutter edge, the public–private boundary, the parcel boundary, or the edge of structures. If the width recorded in the management ledger represents the road area width, check whether it is consistent with the road area line on the attached map. However, because "width" can refer to several concepts—road area width, effective width, carriageway width, pavement width, etc.—it is important to confirm what the width recorded in the management ledger actually means.

When widths vary by segment, organize which segment on the attached drawing corresponds to each width. Widths may change at intersections, bridge sections, sections with sidewalks, narrow sections, pullouts, and between improved and unimproved sections. If only a representative width is recorded in the management ledger, it is necessary to decide how to handle the detailed width variations shown on the attached drawing.

When reconciling road boundary lines and width information, land acquisition documents and boundary records are also relevant. If you link only the width information to the management ledger without any supporting evidence for the road boundary lines, it will be difficult to explain later during boundary confirmations or occupancy negotiations. If there are supporting documents for the road boundary lines, field verification results, or survey outcomes, tying those to the width information in the management ledger will be useful in practice.

Also, the difference between the current road edge and the road boundary line is important when linking with the management ledger. Even if the current condition of gutters or the pavement edge changes, the road area width does not necessarily change. By not confusing existing width, effective width, and road area width, and by clarifying which width should be treated as the official information in the management ledger, the reliability of the linked data is improved.

Associate management information for structures and appurtenances as Item 4

The fourth item is to link the management information of structures and road appurtenances to the two-dimensional road ledger maps. Roads contain various facilities such as side gutters, catch basins, transverse drainage, bridges, retaining walls, slopes, guardrails, signs, lighting, sidewalks, and curbs. Because these are directly tied to road function and maintenance, it is important to integrate their location information with the management ledger data.

Even if structures are shown on an attached map, if the management ledger does not have the facility name, type, management number, inspection history, and repair history organized, it becomes difficult to use for maintenance management. Conversely, even if the management ledger contains information about a structure, if you cannot tell where it is on the attached map, on-site verification and construction planning become time-consuming. By linking the two, you can confirm the location on the drawing and the management information in the ledger together.

When linking structures, clearly define how positions will be indicated. For side ditches, decide whether to manage them as lines or as segments; for manholes, whether to manage them as points; and for bridges, whether to manage them as segments or as facility extents. For retaining walls and slopes, you also need to organize which position to show on the drawings—such as the face, the top edge, or the extent.

Facility information becomes easier to manage when linked to route information and centerlines. If you can organize which route and which section a structure is on, and where it is located relative to the starting point, it becomes easier to find inspection and repair records. In disasters or emergency responses, being able to quickly confirm the location and management information of the facility is also a major advantage.

In coordinating structures and appurtenances, on-site verification results are also important. Inconsistencies can occur—for example, a facility may still be listed in the management ledger but have been removed on site, or it may not be shown on the attached map but have been newly installed on site. During coordination, it is necessary to cross-check as-built drawings, on-site photographs, survey results, and inspection records, and to update both the attached map and the management ledger.

Verify the handling of coordinate systems and location information as Item 5

The fifth item concerns the handling of coordinate systems and location information. When linking two-dimensional road ledger maps with management ledgers, it is necessary to confirm the assumptions regarding the coordinate system and how locations are represented so that the location information on the drawings is correctly linked to the attribute information in the ledger. If the coordinate system remains unclear, field survey results and the positions of structures cannot be managed correctly.

If existing road ledger maps are based on paper drawings or scanned images, they may not have accurate coordinates. Paper expansion and contraction, distortion during scanning, line thickness, and scale limitations can cause discrepancies with field survey results. Even when drawings have been digitized, if the source material is of low accuracy, caution is needed before treating them as high-precision positional information.

On the management ledger side, positions may be managed by route name, section, distance from the starting point, facility number, and so on. On the attached drawing side, they are managed by coordinates or positions on the drawing. To link these two, it is necessary to decide which positional representation will serve as the common reference. One approach is to manage by distance from an origin based on the road centerline, and another is to assign coordinates to each structure.

When handling coordinate systems, verify that plane rectangular coordinates, latitude/longitude, local coordinates, and drawing-specific coordinates are not mixed. When reflecting field survey results onto supplementary drawings, the meaning of the measured points is also important. If the meaning of the measurement targets—such as the outside of a side gutter, the pavement edge, a boundary marker, the center of a manhole, or the end of a bridge—is unclear, they cannot be correctly linked to the facility information in the management ledger.

When a drawing partially reflects high-precision survey results, note that the overall accuracy of the drawing is not uniform. If only certain structures have high coordinate accuracy while surrounding road boundary lines are derived from older drawings, measures must be taken so users do not mistakenly assume the entire drawing has the same level of accuracy. It is important to record the accuracy and the supporting evidence for positional information in the management ledger.

Organizing coordinate systems and the handling of location information makes it easier to find information during on-site verification, construction coordination, inspections, repairs, and disaster response. When linking two-dimensional road ledger maps with the management ledger, establishing rules for location information is indispensable.

Add the update history and supporting documents to the management ledger as Item 6

The sixth item is to record update histories and supporting documents in the management ledger. Even if the two-dimensional road ledger attached maps and the management ledger are linked, if update histories are not retained, it becomes impossible to know when, why, and what information was changed. The road ledger attached maps are documents used for a long time and are continuously updated to reflect changes in the roads, so history management is extremely important.

In the update history, organize the update date, the affected route, the affected section, the update details, the reason for the update, the supporting references, whether on-site verification was performed, the verifier, and any pending items. Record separately whether the road boundary line was updated, the centerline was corrected, the roadway width was changed, structures were added, or only existing site features were updated.

Supporting documents include as-built drawings, field survey results, land acquisition documents, boundary records, ledger records, site photographs, and inspection records. If you keep the lines on drawings and the figures in ledgers traceable to their source documents, it will be easier to explain later if inquiries arise. Information that has been updated without a clear basis tends to require reconfirmation at the next update.

Recording information that was not incorporated and items put on hold in the management ledger is useful. For example, if the location of a side gutter has changed on site but the evidentiary materials for the road boundary line have not been confirmed, so the boundary line was not updated, or if a structure was confirmed but whether it is subject to management remains undetermined, recording the rationale for those decisions can streamline the next verification work.

Recording update histories in the management ledger makes it easier to determine whether the attached drawings or the ledger contain the most recent information. If only the attached drawings are updated and there is no history in the management ledger, successors cannot trace the basis for the updates. If the management ledger is used as the entry point for information, organizing update histories and supporting documentation is indispensable.

Incorporate the on-site verification results as Item 7 into the next update

The seventh item is to manage on-site verification results in a form that can be utilized for the next update. The value of linking the 2D road ledger attachment maps and the management ledger lies not only in connecting drawings and ledgers, but in enabling information verified on site to be continuously reflected. If on-site verification results remain only in personal notes or photo folders, they will be difficult to utilize for the next update.

On-site inspections check pavement edges, gutters, curbs, boundary markers, manholes, retaining walls, slopes, bridges, signs, guardrails, points of roadway width change, and intersection geometries. When recording these in the management ledger, organize the inspection date, inspector, inspected item, location information, photo numbers, details of any discrepancies, and the status of whether they have been reflected. It is important to make clear which information has been reflected in the supplementary drawings and which information is on hold.

Linking field inspection results to routes and sections makes it easier to identify what should be updated next. For example, if a discrepancy in the location of a side ditch is confirmed in a certain section but its relationship to the road boundary line has not yet been verified, leaving that information in the management ledger as a pending item will allow it to be prioritized for verification during the next update.

Photos and survey points are also organized and managed by their location and meaning. Even if only photos are stored, they cannot be used if it is unclear which location they show. Survey points, too, must be recorded—whether they are the outside of a gutter, the pavement edge, a boundary marker, or the center of a manhole—because without that information it is difficult to reflect them in the map attached to the road ledger.

If on-site inspection results are incorporated into the management ledger, the basis for updating drawings can be accumulated. By recording on-site information each time a road is improved or maintained and establishing procedures to reflect it in both the supplementary drawings and the ledger, road management information will gradually become more accurate. A mechanism that leverages on-site inspection results for the next update greatly enhances the practical benefits of linking with the management ledger.

Common mistakes that often occur when integrating with management ledgers

Linking two-dimensional road ledger attached maps with management ledgers tends to produce several errors. The most common is a mismatch between route names and route numbers. If official route names, common names, construction names, and drawing numbers are mixed together, the road on the attached map can be incorrectly linked to a route in the management ledger. It is important to organize route information before linking.

Next, there are mistakes where only the attached drawings are updated and the management ledger is not. Even if road boundary lines or centerlines are corrected, inconsistencies remain if the ledger's length, width, and update history are left outdated. Conversely, there are cases where only the management ledger is updated while the attached drawings retain old information. Drawings and ledgers need to be checked together.

There are also errors caused by confusing definitions of width. If the width recorded in the management ledger is linked to the attached drawings without confirming whether it refers to the road area width, the effective width, or the pavement width, it may appear not to match the results of on-site surveys. Width should be managed not only by its numerical value but also together with its definition and the applicable section.

Mistakes can also occur when the locations of structure information are unknown. Even if the management ledger contains structure names and inspection histories, if their positions cannot be identified on the attached maps, they become difficult to use for on‑site responses. It is necessary to decide whether to manage structures as points, lines, or segments, and to align the attached maps with the ledger.

There are also mistakes where the assumptions about coordinate systems and positional information are not checked. If an existing attached drawing originates from a scanned plan but is treated as high-precision positional information, discrepancies with on-site survey results become problematic. It is necessary to record the coordinate system, survey accuracy, and the meaning of the survey points.

Finally, there is a mistake of not keeping an update history. If you cannot tell which document served as the basis, when an update was made, and what information was updated, it will cause problems for the next update or handover. In management ledger integration, it is important to manage not only the current information but also the history of updates.

Summary

By linking 2D road ledger maps with management ledgers, it becomes easier to view positional information on the drawings together with the management information in the ledgers. By linking road areas, centerlines, widths, lengths, structures, on-site inspection results, and update histories, you can streamline verification tasks for road management, construction coordination, occupancy confirmation, development consultations, maintenance and repairs, and disaster response.

The first thing to check is the correspondence between route names and route numbers. Unless it is made clear which road on the attached drawing corresponds to which route in the management ledger, lengths, widths, and structure information cannot be correctly linked. Organizing the official route names, route numbers, drawing numbers, and common names is the starting point.

The second item is to ensure consistency among the starting point, ending point, and length. Confirm where the start and end points on the management ledger are located on the attached drawing, and whether the centerline length and the ledger length are consistent. For intersection areas and routes that span multiple drawings, continuity of the centerline is also important.

The third point is the reconciliation of the road boundary line and width information. The road boundary line does not necessarily coincide with the pavement edge or the gutter edge. You need to confirm whether the width recorded in the management ledger refers to the road area width, the effective width, or the carriageway width, and align it with the sections shown on the attached map.

The fourth is to link management information for structures and their appurtenances. By linking the locations of drainage gutters, manholes, bridges, retaining walls, guardrails, signs, and lighting with their management numbers, inspection records, and repair histories, maintenance and on-site inspections become easier.

The fifth issue is the handling of coordinate systems and location information. To link existing attached maps, field survey results, structure locations, and section information in the management ledger, it is necessary to organize the coordinate systems, reference points, the meanings of measurement points, and the rules for position representation.

The sixth is to record the update history and supporting documents in the management ledger. If you can see when an update was made, which document served as the basis, and what information was updated, future updates and responses to inquiries become easier. Leaving records of information that was not reflected and items on hold also prevents repeating the same checks.

The seventh is to apply on-site inspection results to the next update. If you record the information on side ditches, boundary markers, structures, and points where width changes that were confirmed on site—together with photos and location data—in the management ledger, you can use them as the basis for updating the attached maps. It is important not to leave on-site inspection results as personal notes, but to manage them as part of ledger integration.

To more reliably advance the linkage between the 2D road ledger map and the management ledger, it is effective to accurately preserve position information acquired on site and link it to the road area boundary lines, centerlines, structures, and width sections on the drawings. LRTK, a GNSS high-precision positioning device that can be attached to and used with an iPhone, is a suitable option for verifying on site the locations of features such as side gutters, manholes, boundary markers, road edges, points related to the centerline, and structure locations, and recording them as high-precision position information. If you want to link the management ledger and the 2D road ledger map including on-site information, considering the use of LRTK can help improve the accuracy of road management information and facilitate more efficient update work.