Clarifying the differences between 2D road ledger attached maps and road ledgers in 5 minutes

Table of Contents

• Understand the road ledger and the 2D road ledger map separately

• The road ledger is the basic document for organizing road management information

• The 2D road ledger map is a drawing that shows the positional relationships of roads

• Difference 1: grasp the roles of textual information and map information

• Difference 2: understand the difference between management items and spatial understanding

• Difference 3: look at the differences in update targets and verification methods

• Difference 4: clarify the differences in practical use cases

• Difference 5: understand the importance of cross-referencing the two

• Common points of confusion and practical precautions

• Summary

Understand the Road Ledger and the Two-Dimensional Road Ledger Attached Map Separately

In road management practice, the terms "road ledger" and "2D road ledger attached map" are often used side by side. Both are important documents for managing roads, but their roles are not the same. The road ledger is a document that organizes management information about roads, while the 2D road ledger attached map is a document that makes that information easier to confirm as a two-dimensional drawing. Simply put, the road ledger is a document for managing roads with text and numbers, and the 2D road ledger attached map is a document for understanding the location and shape of roads through drawings.

What often confuses practitioners is that both relate to a road's extent, width, length, structures, and route information. When the road register records the width and length and the attached drawing also shows the width and the centerline, it can be unclear which one to consult. However, the road register and the attached drawings are not complete on their own; they complement each other.

For example, even if you check the route name, starting point, end point, length, and width in the road ledger, it is difficult from text alone to determine where the road runs on a map, how far the road area extends, and the positional relationships with intersections, side ditches, and bridges. Therefore, you check the 2D map attached to the road ledger. Conversely, even if you look at the road’s shape on the attached map, you need to confirm the route’s official management information, length, width, service status, and update history in the ledger information.

If you don't understand this difference, you may mistakenly read the road area line as a boundary line, judge the roadway width solely by how it appears on the attached drawing, or treat an old drawing as the latest management information. The road ledger and the two-dimensional road ledger attachment are materials that may look similar but serve different roles. In practice, it is important first to grasp the differences between them and then to use each correctly according to your purpose.

The road ledger is the fundamental reference document for organizing road management information

A road ledger is a basic document used to organize the information necessary for roads managed by a road administrator. Generally, it organizes items such as route name, route number, starting point, end point, length, width, road classification, service status, road area, structures such as bridges and tunnels, road appurtenances, and information related to occupancy and management. It is a document used to confirm which roads are being managed, over what extent, and under what conditions.

The road ledger is used to capture the "attribute information" of roads. Attribute information refers to management-related information associated with the road itself. For example, it includes information such as the length of a given route, how the width is configured, where the start and end points are set, whether it is in service as a road, and whether bridges and ancillary structures are included in the scope of management.

In practice, consulting the road ledger allows you to understand a road's basic management conditions. It is used in situations such as checking the target route before planning construction, confirming the scope of an application for road occupancy, checking the conditions of roads to be connected in development consultations, organizing the sections subject to maintenance and repair, and responding to inquiries related to road management.

However, because road registers primarily consist of textual and numerical information, they have limitations when it comes to intuitively grasping spatial relationships. Even if you know the route name, width, and length, it is difficult to determine from register information alone how the road area corresponds to the actual on-site extent, how the area expands at intersections, or where gutters and retaining walls are located along the road.

Therefore, when consulting the road ledger, it is standard practice to verify it together with the two-dimensional road ledger attached maps and on-site documents. The road ledger is the central source of management information, and the attached maps are auxiliary materials for spatially understanding that information. Rather than determining the on-site boundaries based solely on the road ledger, cross-checking it with the attached maps and field survey results improves the accuracy of practical decision-making.

A two-dimensional road ledger map is a drawing that shows the positional relationships of roads.

A two-dimensional road ledger attached map is a planar drawing that organizes road information related to the road ledger. It presents, in a top-down view, the road alignment, road area, road centerline, changes in width, intersection geometry, bridges, side ditches, retaining walls, slopes, sidewalks, and positional relationships with surrounding features. Whereas the road ledger is a document that organizes roads using text and numerical data, the two-dimensional road ledger attached map is a document that visualizes the spatial relationships of roads.

As the term "two-dimensional" suggests, the supplementary drawings essentially deal with plan information. They are suitable for confirming where the road runs, which section is the subject, what shape the road area takes, and how intersections and corner cuts are represented. On the other hand, heights, gradients, surface irregularities, retaining wall heights, drainage slopes, and three-dimensional interferences with underground buried utilities may not be fully captured by two-dimensional supplementary drawings alone.

There are many situations in practical work where two-dimensional maps attached to road ledgers are used. These include confirming road areas and widths before on-site surveys, identifying the scope of roadworks, confirming the positional relationships of encroachments, cross-checking documents concerning road boundaries and public–private boundaries, organizing locations for ledger updates, and examining the relationship with connecting roads during development consultations.

However, because 2D road ledger attached maps are drawings, attention must be paid to their creation date and accuracy. Attached maps based on old paper drawings can produce positional differences from the actual site due to line thickness, scale, or distortions introduced during scanning. Even digitized attached maps require caution: if the source material is old or the coordinate system is unclear, they should not be used uncritically as high-precision positional information.

The 2D road ledger attachment map is the entry point for linking the contents of the road ledger with on-site and spatial information. It is important not only to read the lines and symbols on the drawing, but also to confirm whether a line is a road boundary line, a centerline, the edge of a structure, or a reference line. Although the attachment map is visually easy to understand, you should not rely on appearance alone; it must be used in conjunction with the road ledger and related documents.

Difference 1: Understand the Roles of Textual Information and Drawing Information

The clearest difference between a road ledger and a 2D road ledger map is the way information is represented. A road ledger is primarily a document that organizes road information using text and numbers. Items such as route name, route number, starting point, end point, length, width, road type, operational status, and structure information are recorded as management items. On the other hand, a 2D road ledger map depicts the road’s location, shape, and relationship with the surrounding area as a drawing.

In the road ledger you can check how many meters long a route is and how the roadway width is organized. However, from the ledger’s textual information alone it is difficult to see how the road curves on the plan, where the width changes, or how the road area widens at intersections. By looking at the accompanying drawing, you can grasp the spatial situation of the road.

On the other hand, two-dimensional maps attached to the road ledger make it easy to visually confirm the shape of a road, but they do not necessarily allow you to read every official management item. Even if the attached map shows the route name and width, you cannot fully verify on the drawing the ledger’s recorded values, update history, service status, or facility management information. Map information is intuitive, but detailed management information must be checked in the road ledger.

Understanding this difference makes it easier to decide which to use in practice. When you want to check the official management information for a route, consult the road ledger. When you want to grasp the positional relationships of roads and the scope of on-site surveys, consult the 2D road ledger attached map. Rather than judging based on just one of them, the basic workflow is to confirm numerical values and attributes in the ledger and verify positions and ranges on the attached map.

Textual information and drawing information each have different strengths. The road register is suited to accurately organizing management information, while two-dimensional road register diagrams are suited to spatial understanding. By treating their roles separately, misunderstandings are less likely to occur when confirming road areas, widths, centerlines, and structures.

Difference 2: Understand the Difference Between Management Items and Spatial Awareness

The second difference is that the road ledger is a document that organizes management items, whereas the two-dimensional road ledger attached map is a document that supports spatial understanding. The road ledger systematically organizes the items that road managers need to manage roads. It is used to confirm management attributes such as the road’s name, number, length, width, structure, facilities, and service status.

On the other hand, the two-dimensional road register map is used to confirm how roads are positioned on the ground and on maps. It is reference material for understanding how far the road area extends, how roads connect at intersections, what the relationship is with adjacent waterways and private land, and where side ditches and bridges are located.

For example, even if "width" is recorded in the road ledger, it can be difficult to tell which part on-site that width refers to without looking at the accompanying map. To confirm whether it is the road area width, the effective width, the carriageway width, or the paved width, you need to cross-check the ledger information with the road area lines, road edges, and positions of structures on the map.

Also, even if you verify the length in the road register, you need to confirm in the attached drawings which centerline that length was calculated along and where the start and end points are located on the plans. In particular, in curved sections, intersections, and bridge sections, the handling of the centerline and the start/end points affects practical judgment.

Spatial awareness becomes important in road construction and on-site inspections. Even if the relevant route is identified in the ledger, an attached map is necessary to grasp where to check on-site, what area should be targeted for construction, and how the road area relates to structures. In other words, the road ledger shows "what is being managed," and the two-dimensional road ledger attachment helps to understand "where and how it is being managed."

Grasping this difference clarifies the procedure for reviewing materials. Practically, the workflow is to first check the relevant route and management items in the road register, then confirm spatial relationships using the attached maps, and supplement with on-site surveys or related documents as necessary. Separating the consideration of management items from spatial understanding is an important perspective for understanding the difference between the road register and the attached maps.

Difference 3: Differences in update targets and verification methods

The road ledger and the two-dimensional road ledger map differ in what is updated and how they are checked. The road ledger’s update targets are management items such as route information, length, width, road classification, operational status, and structure information. In contrast, the two-dimensional road ledger map targets updates to the graphic representations on the drawing, such as road boundary lines, centerlines, road edges, intersection shapes, structure locations, width annotations, and relationships with surrounding features.

Considering a case where road improvements are carried out makes this difference easier to understand. When a road is widened, the road ledger may need updates to carriageway width, length, management sections, and information on structures. In the 2D road ledger map, the road boundary lines, centerline, width markings, locations of gutters and sidewalks, and the shapes of intersection areas must be updated. If only one of them is updated, inconsistencies will remain.

The methods for confirming updates also differ. The road ledger checks whether the values and items in the records have been correctly updated. The supplementary drawings check whether the lines and positional relationships on the drawings match the site, survey results, and as‑built drawings. It is easier to organize things if you think of the ledger as the material for confirming consistency of items and the supplementary drawings as the material for confirming spatial consistency.

However, the road ledger and the attached map should not be updated separately. If you update the width recorded in the ledger, you also need to review the width display and the road boundary lines on the attached map. If you update the centerline or the road boundary lines on the attached map, you need to confirm that they are consistent with the length and width recorded in the ledger. Even if the specific update targets differ, they must ultimately match as the same road management information.

A common mistake when updating is to revise only the supplementary drawings based on the as-built drawings, leaving the numerical values in the ledger records outdated. Conversely, there are cases where only the ledger records are updated while the supplementary drawings used on site remain in the old configuration. This leads to differing understandings of the road boundaries and widths among stakeholders depending on which documents they are looking at.

To understand the difference between the road ledger and the 2D road ledger attached map, it is important to consider the workflow of the update process. The road ledger updates management items, while the attached map updates positional relationships. Only by reconciling the two does the information become a complete set of road management information.

Difference 4: Organize the differences in practical use cases

There are differences in the situations in which the road ledger and the 2D road ledger maps are used in practice. The road ledger is used when you want to confirm the official management information of a road. This includes checking the route name, starting point, end point, length, width, management classification, operational status, and information on structures. It is often referenced for responding to inquiries, updating the ledger, basic verification for road management, and organizing information during the planning stage.

Two-dimensional road ledger maps are used when you want to check the positional relationships and extents of roads. They are used in situations such as viewing the road area and points where the road width changes before a field survey, confirming the positions of construction areas and structures, seeing where objects occupying the road area are located, checking the connection between development areas and existing roads, and understanding the relationship between boundary documents and on-site structures.

For example, when there is a consultation about road occupancy, the management information for the relevant route is checked in the road ledger, and the two-dimensional attached map of the road ledger is used to confirm the position of the planned occupancy within the road area. In construction design, basic information such as the route and width is confirmed in the road ledger, and the attached map is used to check the relationship with the road area, side ditches, intersections, and structures.

In development consultations, the management status of the road to be connected is checked in the road ledger, and the on-site connection point, road area, corner cuts, and width conditions are confirmed using the attached map. For boundary confirmation, not only the road ledger and attached map but also boundary documents, land acquisition documents, and on-site survey results are required; however, the attached map serves as the entry point for confirming the relationship between the road area and the actual site.

It is necessary to use them differently even for disaster response and emergency inspections. The road ledger is used to identify the relevant routes and management sections, while the supplementary maps are used to confirm the locations of damaged sites, their relationship to surrounding roads, and the positions of bridges and drainage facilities. In recovery planning, decisions are made by combining ledger information, supplementary map information, and the results of on-site inspections.

Thus, the road register is strong for verifying management information, while the two-dimensional road register attached map is a document well suited to verifying on-site conditions and spatial aspects. In practice, there are situations where viewing only one of them is sufficient, but for important decisions it is safer to check both. In particular, when matters involve road areas, boundaries, widths, or construction extents, it is standard practice to use the road register together with its attached map.

Understand the importance of cross-checking the two as Difference 5

After understanding the differences between the road ledger and the 2D road ledger attached map, the most important thing is to cross-check them. The road ledger and the attached map have different roles, but they are ultimately documents for managing the same road. Therefore, if the ledger's numerical values and items conflict with the lines or positional relationships on the attached map, they become difficult to use in practice.

Typical items to be verified include route name, start point, end point, length, width, roadway area, centerline, and structure information. Confirm that the start and end points of the route recorded in the ledger are correctly shown on the attached map. If there is a large discrepancy between the ledger’s length and the centerline length on the attached map, it is necessary to check how the centerline was defined or measured, the positions of the start and end points, and the timing of updates.

Verifying widths is also important. Confirm whether the width recorded in the register matches the road area width shown on the attached drawing, and whether it has been confused with the effective width or the pavement width. Road area width, carriageway width, and pavement width are not the same. If it is unclear which width is being displayed on the attached drawing, the figures in the register may appear not to match the actual on-site width.

Also for road areas, confirm whether the boundary lines in the ledger information and the attached map are consistent. When road improvements, land acquisition, or development attribution have occurred, the ledger may have been updated while the attached map remains outdated. Conversely, the boundary lines on the attached map may have been corrected while the ledger records and supporting documents have not been updated.

Structural asset information is also subject to verification. When items such as bridges, side ditches, retaining walls, drainage facilities, and road appurtenances are managed in the ledger, check whether their locations and extents can be confirmed on the attached map. It is not necessary to display all detailed information on the attached map, but for facilities that are important for management, it is desirable to enable moving back and forth between the ledger and the attached map.

When a discrepancy is found during reconciliation, rather than immediately deciding that one or the other is incorrect, check the creation date, update history, supporting documents, and the on-site conditions. If the ledger is up to date but the attached drawing is outdated, the attached drawing needs to be updated. If the attached drawing reflects the as-built drawings but the ledger records contain old information, the ledger needs to be updated. If both are outdated, on-site inspection or confirmation using surveying results will be necessary.

The road ledger and the two-dimensional road ledger map become more valuable when used in cross-checking after you understand their differences. Rather than relying on only one, confirming that both sets of information are consistent is fundamental to preventing rework and misunderstandings in practice.

Common Points of Confusion and Practical Considerations

There are several points where the road register and the two-dimensional road register attached maps are easily confused. The most common mistake is to treat the lines on the attached map as formal boundary lines or road-area lines as they appear. The attached map may show road-area lines, centerlines, structure lines, reference lines, background features, and so on, but they do not all carry the same meaning. Road-area lines must be distinguished from public–private boundaries, parcel boundaries, pavement edges, and gutter edges.

Next, the width recorded in the road ledger can be confused with the apparent width on the attached map. When the width listed in the ledger indicates the width of the road area, it may differ from the on-site carriageway width or the paved width. Even if a road looks wide on the attached map, you must confirm whether that widening represents the road area, a corner cut at an intersection, or merely a background depiction.

Care must also be taken in handling the start and end points. In the road ledger, the start and end points are organized as management information, but it can be difficult to determine where they correspond on the attached drawings. In particular, at intersections, administrative boundaries, and bridge sections, the location of the start and end points affects length and centerline management. It is important to cross-check the ledger records with the attached drawings to confirm the positions of the start and end points.

Differences in creation dates can also cause confusion. In situations where the road ledger has been updated but the supplementary maps are outdated, where the supplementary maps reflect post-construction conditions but the ledger records still contain the old figures, or where past supplementary maps remain as reference materials, you must verify which information is the most recent. If management of the latest versions is inadequate, multiple pieces of information about the same road may be used simultaneously.

Be aware of differences in coordinate systems and accuracy. Just because two-dimensional road ledger maps have been digitized does not necessarily mean they are based on high-precision survey results. Some materials are merely scanned paper drawings, some are based on schematic maps, and some drawings have unknown coordinate systems. When making judgments about road areas or locations near boundaries, it is safer to verify the accuracy of the drawings and, if necessary, carry out an on-site survey.

In practice, it is important not to make judgments based solely on either the road ledger or the 2D road ledger map, but to cross-check multiple sources according to the purpose. Confirm road management information in the ledger, verify positional relationships on the map, and when boundaries or on-site accuracy are important, check boundary documents and on-site survey results. By making this workflow a habit, you can reduce mistakes caused by confusing the road ledger and the map.

Summary

The road ledger and the 2D road ledger map are both indispensable materials for road management, but their roles differ. A road ledger is a management record that organizes information such as route name, starting point, end point, length, width, road classification, operational status, and structure information in text and numerical form. A 2D road ledger map is a drawing used to confirm, in plan view, the road area, centerline, changes in width, intersection shapes, structures, and the relationships with surrounding features.

The road ledger is a document that organizes "what is being managed," and the two-dimensional road ledger supplementary map is a document for understanding "where and how it is being managed." The road ledger alone can make spatial relationships difficult to understand, and the supplementary map alone can make the official management items and update history hard to discern. The two are not opposing documents but are complementary to each other.

To summarize the differences, the road ledger is strong in textual and numerical information, while the 2D road ledger attached map is a resource strong in drawing information and spatial understanding. In the road ledger, you confirm management items such as route, width, and length; in the attached map, you confirm the road area, centerline, and the positional relationships of structures. In practice, it is clear and easy to follow the workflow of confirming the basic information of the target road in the road ledger and then grasping its relationship to the actual site with the attached map.

There are differences even in update operations. In the road ledger, management items such as road width, length, service status, and structure information are updated. In the 2D road ledger attached map, road boundary lines, centerlines, road edges, intersection shapes, structure positions, and width annotations are updated. However, if only one of the two is updated, inconsistencies will remain, so they must always be cross-checked after updating.

The situations in which they are used in practice are slightly different. For checking official route information or the figures on the register, consult the road register. For confirming field surveys, construction extents, road sections, occupancy locations, and the relationships with intersections and structures, consult the 2D road register maps. For boundary confirmation and detailed design, it is important to combine boundary records, as-built drawings, and on-site survey results.

Pay particular attention not to judge the lines on the supplementary map by appearance alone. Road area lines, public–private boundaries, parcel boundaries, pavement edges, gutter edges, and structure edges have different meanings. Also, the width recorded in the register does not necessarily match the width visible on site. It is important to understand the differences between road area width, effective width, carriageway width, and pavement width, and to cross-check the register with the supplementary map.

If you correctly understand the difference between the 2D attached map of the road ledger and the road ledger, it becomes easier to carry out road management verification tasks. Confirm management information in the ledger, check positional relationships on the attached map, and, as necessary, supplement with field surveys and related documents. By grasping this basic approach, you can reduce discrepancies in understanding during construction, road occupancy, development consultations, boundary confirmation, and update management.

To more practically link the road register and the two-dimensional road register attached maps, a system that connects position information collected on site to register updates and map verification is important. LRTK, a high-precision GNSS positioning device that can be attached to an iPhone, is a suitable option for verifying on site and recording high-precision position information for items such as road areas, centerlines, width-change points, drainage gutters, manholes, boundary markers, and structure locations. If you want to more accurately connect the management information in the road register with the positional information in the two-dimensional road register attached maps through field verification, considering the use of LRTK can help improve the accuracy of road management operations and streamline verification tasks.