top of page

Table of Contents

Why confirming road areas on 2D road ledger supplementary maps is important

Viewpoint 1: Distinguish the road area boundary line from the current road edge

Viewpoint 2: Cross-check information between the road ledger and the supplementary map

Viewpoint 3: Examine the relationship with boundary documents and land acquisition records

Viewpoint 4: Verify consistency with road width and the centerline

Viewpoint 5: Confirm the positions of structures and appurtenances

Viewpoint 6: Conduct on-site verification and check the update history

Common mistakes when verifying road areas

Summary


Why Confirming Road Areas on 2D Road Register Maps Is Important

The two-dimensional road ledger attached map is a road management document that organizes, in plan view, the location of roads, road areas, road centerlines, widths, lengths, intersection geometries, structures such as side ditches and bridges, and the relationship with surrounding features. Among these, confirmation of the road area is an important task directly linked to construction extent, occupation extent, maintenance and management responsibility, development consultations, boundary confirmation, and ledger updates. If the road area is not correctly understood, the locations that appear as roads on site and the areas treated as roads for management purposes will not align, making rework in later stages and misunderstandings among stakeholders more likely.


A road area is a concept that indicates the extent managed as a road. In general, it does not refer only to the paved portion used by vehicles. It may include sidewalks, shoulders, gutters, drainage facilities, slopes, retaining walls, planting strips, and other spaces necessary for management. Therefore, the pavement or gutter edges visible on site do not necessarily coincide with the road-area lines shown on the two-dimensional map attached to the road ledger.


What often confuses practitioners is that on drawings the road boundary line, pavement edge, gutter edge, public–private boundary, parcel boundary, structure lines, and reference lines are all depicted as lines. If you read a drawing without verifying the meaning of those lines, you may mistakenly interpret the road boundary line as the actual edge of the road on site, or treat the outside of a gutter as the public–private boundary. When confirming road boundaries, you need to interpret what the lines signify, rather than rely on how the lines look on the drawing.


Road boundaries may also need to be updated in response to changes in the roadway. When road widening, intersection improvements, sidewalk installation, gutter repairs, bridge maintenance, allocation of roads due to development, disaster recovery, or similar works are carried out, the on-site configuration and road management information may change. However, a change in the on-site shape does not necessarily mean that the road boundary has changed. Changes to existing structures resulting from construction and changes to the road boundary need to be checked separately.


When confirming the road area using a 2D road ledger supplementary map, it is important to examine the road ledger, the supplementary map, boundary documents, land acquisition documents, as‑built construction drawings, on‑site survey results, and on‑site verification results in combination. Rather than relying solely on the supplementary map, reconcile ledger information with actual site conditions to determine the extent of the area subject to road management.


In this article, we explain six perspectives to keep in mind when checking road areas on two-dimensional road register maps. If you check in the sequence of the difference between the road area boundary line and the existing road edge, verification with the register, the relationship with boundary documents, consistency with road width and the centerline, the positions of structures, and on-site verification and update history, you can more easily reduce judgment mistakes in practice.


Viewpoint 1: Read the road area boundary line and the current road edge separately

The first viewpoint for confirming the road area is to read the road area line and the current road edge separately. The road area line depicted on the two-dimensional road ledger map indicates the extent managed as a road. On the other hand, the current road edge often refers to visible on-site elements such as the pavement edge, gutter edge, curb, retaining wall, and slope edge, and does not have the same meaning as the road area line.


The position that appears to be the edge of the road on site is not necessarily the edge for road management purposes. There may be gutters or shoulders outside the paved surface that are included in the road area. Sidewalks, slopes, and drainage facilities may also be included in the road area. Conversely, places that visually appear to be used as roads may not be designated as road area in official records.


If you read the attached drawings without understanding this difference, you may perceive the road area as narrower or wider than it actually is. For example, if you treat the pavement edge as the road boundary line when deciding the construction extent, you may find that gutters or embankment slopes were actually included within the road area. Conversely, if you judge an area to be part of the road based only on how it is used on site, you may end up treating areas as road that have no administrative basis for such management.


When reading road boundary lines, check the drawing's legend and line types. Look at how road boundary lines, road edge lines, gutter lines, structure lines, and reference lines are distinguished. In older attached drawings the legend may be insufficient. In such cases, confirm with the road ledger record, land acquisition documents, boundary materials, and as-built construction drawings, and adopt an approach of tracing the evidence rather than inferring the meaning of the lines.


Even when confirming the existing road edge, make clear which edge you are checking. Whether it is the inner or outer side for a gutter, the roadway side or the sidewalk side for a curb, or the front face or the top for a retaining wall will change the position shown on the drawings. Even when using field survey results, if the meaning of the measurement points is not understood, you cannot determine their relationship to the road area.


Reading the road area boundary line separately from the existing road edge is fundamental to verifying the road area. By not readily equating the lines on drawings with what is seen on site, and by clarifying the meaning of each, it becomes less likely to make errors when determining the construction extent, the extent of occupation, boundary verification, and the scope of maintenance and management.


Viewpoint 2: Cross-check the information in the road ledger with the attached map

The second perspective is to cross-check the information in the road ledger and the 2D road ledger attachment map. The road ledger organizes route name, starting point, end point, length, width, road classification, usage status, road area, structure information, and so on. The attachment map is a document that makes it easier to verify those pieces of information in plan view. When confirming the road area, it is necessary to check whether the textual information in the ledger and the drawing information in the attachment are consistent.


Even if the road register contains information on road areas and widths, it becomes difficult to use in practice if you cannot tell which parts of the attached map they correspond to. Conversely, even if boundary lines are drawn on the attached map, if they do not match the register’s information you cannot determine which should be used as the reference. In confirming road areas, it is fundamental to read the register and the attached map together as a set.


First, confirm the start and end points of the subject route. Check where the start and end points shown in the ledger records are indicated on the attached map. If you confirm the road area while the start and end points are unclear, the section in question may be shifted. At intersections, administrative boundaries, bridge sections, management boundaries, and similar locations, the way the start and end points are treated can affect the measurement of length and the confirmation of the area.


Next, cross-check the width recorded in the ledger with the road-area lines shown on the attached map. If the width listed in the ledger is intended to indicate the road-area width, verify that it does not substantially conflict with the distance between the road-area lines on the attached map. However, the term “width” can have multiple meanings—road-area width, effective width, carriageway width, pavement width, etc. Comparing the ledger’s width with the attached map or field survey measurements without first confirming what the ledger’s width denotes can lead to misunderstandings.


Also check the update history for road areas. If road areas have changed due to road improvements or development-related changes, the ledger records may have been updated while the attached maps remain outdated. Conversely, the boundary lines on the attached maps may have been revised while the ledger records’ width and length remain as old information. Rather than checking only one of the ledger or the attached maps, it is important to examine the update status of both.


Structural information is also subject to verification. When structures such as bridges, gutters, retaining walls, slopes, and sidewalks are related to the road area, confirm whether the facility information in the register matches the location on the attached map. By clarifying whether the road area boundary lies outside or inside a structure, and whether the structure is included within the road area, it becomes easier to determine maintenance responsibilities and the scope of construction work.


Verifying the road ledger against the attached maps is a process that enhances the reliability of road area confirmation. By checking whether the ledger's management information matches the spatial information on the attached maps, you can make it easier to explain road areas in practice.


Viewpoint 3: Examine the relationship with boundary documents and land records

The third perspective is to look at the relationship with boundary documents and land acquisition documents. When confirming the road area, it is risky to judge solely from the two-dimensional road ledger map. Because road area lines are deeply related to land acquisition, boundaries, and the history of road management, check, as necessary, boundary documents, land maps, materials related to the road area, past on-site inspection records, as-built drawings, and on-site boundary markers.


Road boundary lines, public-private boundaries, and cadastral boundaries may be located close to one another, but they do not always coincide. A road boundary line indicates the extent managed as a road, while a cadastral boundary is a line concerning land parcel divisions. The public-private boundary is often treated as indicating the border between public and private land, but it too does not necessarily match the road boundary line.


A common mistake in practice is to treat structures such as side ditches and retaining walls as boundaries. On site, the outside of a side ditch may be taken as an indication of the boundary, but in reality the side ditch may be installed within the road area. The same applies to retaining walls and embankment slopes: they may be managed as road facilities or may be structures on the adjacent land. It is important not to judge the road area or boundary solely by the position of structures.


When checking boundary documents and land acquisition documents, also look at when they were created and the scope they cover. Older documents may not match current on-site conditions. If there have been road improvements, land acquisitions, reassignment of road ownership due to development activities, or additions of corner cuts, each document may reflect these changes at different times. Rather than simply comparing the latest on-site conditions with past documents, it is necessary to trace the sequence of events.


When updating road area boundary lines, supporting documentation is especially important. Even if the locations of pavement or side ditches on site have changed, if there is no basis for changing the road area itself, there may be cases where the boundary lines should not be altered. Updates to the existing road edge and updates to road area boundary lines should be judged separately. When changing road area boundary lines, it is desirable to record supporting evidence such as land acquisition documents, documents related to the area, and boundary documents.


By examining the relationship with boundary documents and land acquisition documents, the road boundary lines on the two-dimensional map attached to the road ledger gain explanatory power. If you can understand what the lines on the drawing are based on, it becomes easier to explain them to stakeholders during construction consultations, occupancy verifications, and boundary confirmations.


As viewpoint 4, check alignment with the width and centerline

The fourth perspective is to check the road area in relation to the road width and the centerline. Viewing the road area boundary alone does not reveal whether the entire attached drawing is consistent. By verifying that the road area boundary, road centerline, width, length, starting point, and end point do not contradict one another, it becomes easier to prevent misinterpretation of the road area.


The road centerline is the line that serves as the axis for route management. It may run through the middle of the road area, but in cases of one-sided widening, a one-sided sidewalk, intersections, curves, or bridges, the centerline may not coincide with the geometric center. Check the left and right distances from the road boundary line to the centerline, and if there is an unnatural bias to one side, confirm the reason. It is necessary to ascertain whether this is due to one-sided widening, a displacement of the boundary line, or the centerline remaining outdated.


Consistency with the width is also important. If the attached drawing shows the road zone width, verify that the road zone lines and the width annotations do not contradict each other. Also check which sections the width values apply to and where the width change points are. Roads are not the same width over their entire length; widths may change at intersections, on bridges, in sections with sidewalks, in narrow stretches, and at lay-bys.


When confirming the road area, distinguish between the road area width, effective width, carriageway width, and pavement width. The width enclosed by the road area boundary lines is not the same as the width that vehicles can actually use on site. Where side ditches, sidewalks, shoulders, slopes, structures, or encroachments are present, the actual usable width within the road area may be reduced. It is important not to confuse confirmation of the road area with confirmation of the passable width.


Also check the relationship with the length. If the road boundary line is updated, it can affect the centerline, the starting and ending points, and the length. When intersections are improved or a road is realigned, it may be necessary to review not only the boundary line but also the centerline and its length. If you only revise the road boundary line while the length and centerline remain based on old information, inconsistencies will remain in the map attached to the road ledger.


By verifying alignment with the width and the centerline, the road area can be treated as management information for the entire route. Not only checking whether the position of the road area line is correct, but also confirming consistency with the centerline, width, length, and ledger records contributes to improving the quality of the 2D road ledger-attached map.


As Viewpoint 5, confirm the positions of structures and attached elements

The fifth viewpoint is to check the positional relationships between the road area and structures and road appurtenances. The road area may include not only carriageways and sidewalks but also facilities such as gutters, catch basins, cross drains, bridges, retaining walls, slopes, guardrails, signs, lighting, and curbs. Confirming the locations of these elements makes it easier to grasp the actual conditions of the road area.


Gutters and curbs are particularly important when confirming road boundaries. In the field, gutters and curbs are sometimes regarded as indicators of the road edge. However, the outside edge of a gutter does not necessarily indicate the road boundary line or the public–private boundary. Gutters may be installed within the road area. In two-dimensional road ledger maps, the road boundary line and the gutter line need to be read as separate lines.


On roads with retaining walls or slopes, the paved surface alone cannot determine the extent of the road area. There may be slopes or retaining walls outside the paved surface that are managed as road facilities. If the positions of slopes or retaining walls are shown on the attached map, confirm their relationship to the road area boundary line. During field inspections, it is important to clarify which position is being recorded: the top of the slope, the toe of the slope, the front face of the retaining wall, or the top of the retaining wall.


Bridge sections and watercourse crossings also require attention. The bridge width and the right-of-way of the approach road may differ from those in adjacent sections. Verify how the road right-of-way lines connect before and after the bridge, and whether their relationship with the centerline and width appears natural. For roads along waterways, the relationship between the road right-of-way and the watercourse bed can become complex, so cross-checking with related documents is necessary.


The locations of roadside appurtenances are also related to verification of the road area. By confirming whether signs, guardrails, lighting, wheel stops, and similar fixtures are inside or outside the road area, it becomes easier to organize the scope of maintenance and management and the premises for occupancy consultations. However, do not determine the road area based solely on the existence of appurtenances; confirm them together with the road area boundary lines and supporting documents.


By checking the locations of structures and appurtenances, you can relate the road area to the on-site facilities. Rather than just looking at the road area boundary lines, confirming the relationship with the facilities that make up the road leads to a road-area verification that is useful in practice.


Viewpoint 6: conduct on-site verification and check the update history

The sixth point is to verify the on-site situation and the update history. Even if you confirm the road area using two-dimensional road ledger attached maps, if they do not match the on-site conditions or the update history, there will be concerns about using them in practice. When confirming road areas, it is important to review not only drawings and documents but also the results of on-site verification together with the past update history.


On-site verification checks field elements that may be related to road area boundary lines. We inspect pavement edges, gutters, curbs, retaining walls, slopes, boundary markers, catch basins, bridges, sidewalks, entrances and exits, encroachments, and other items, and reconcile differences between the existing attached drawings and the field. If discrepancies are found on site, we distinguish whether they are due to changes in the existing structures, changes to the road area, or insufficient accuracy of the existing attached drawings.


On-site inspection results are recorded together with photographs, location information, measured values, the inspection date, the inspector, and the meaning of the measurement targets. Coordinates alone may not make clear whether a point refers to the outside of a gutter, the pavement edge, or a boundary marker. When using the data to confirm road areas, it is necessary to clearly record the meaning of each measured point.


I will also check the update history. If you can confirm when the road boundary lines were updated and which documents they were based on, it will be easier to determine what point in time the current attached map represents in terms of road information. If there were road improvements or development attribution but no update history remains, it becomes difficult to identify the cause of discrepancies between the site and the attached map.


Even if discrepancies are found during on-site verification, the road boundary lines are not necessarily corrected immediately. Changes to road boundaries require supporting documentation. Even if the on-site pavement edge or the position of gutters has changed, if the basis for the road boundary cannot be confirmed, only the current on-site features may be updated while the boundary line is left on hold. What is important is to record both the information that was updated and the information that was put on hold.


If you check on-site verification and the update history, you can avoid relying on a drawing from a single point in time when determining road areas. To make the maps attached to the road ledger usable as continuous management documents, it is essential to manage on-site verification, update history, and supporting documents together as an integrated set.


Common Mistakes in Road Area Confirmation

When verifying road areas on two-dimensional road ledger maps, there are several common mistakes. The most frequent is confusing the road-area boundary line with the current road edge. Treating the pavement edge or the edge of a gutter as the road-area boundary can lead to incorrect judgments about the scope of road management. Road-area boundary lines must be confirmed based on administrative grounds, not on their appearance on site.


Next, there is a mistake of treating the road area line as identical to cadastral boundaries or public‑private boundaries. The road area line and the land boundary may coincide in some cases, but they are not always the same. When cross-checking with cadastral maps and boundary materials, it is important to interpret the lines according to their different meanings. Do not assume they are the same just because the lines are close to each other on the drawing.


A common mistake is failing to confirm the definition of the width. If you compare field measurements with the width shown in the registry without checking whether that registry width refers to the road right-of-way, the effective width, or the paved width, the results can appear inconsistent. Clarifying the meaning of the width and the section to which it applies can reduce misunderstandings.


Checking only the road area without looking at the centerline is also dangerous. If the centerline, start and end points, length, and road area line are not consistent, the attached map will be difficult to use for route management. Even if the road area line alone is shown correctly, if the centerline and length remain based on outdated information, the register as a whole is incomplete.


Not recording the results of on-site checks is also a problem. If information confirmed on site—such as side ditches, boundary markers, structures, and points of width change—is only kept as photos and notes, it cannot later be reflected in the drawings. It is important to keep a record of the facts confirmed on site and of what was incorporated into the drawings.


To prevent mistakes when confirming road area boundaries, it is necessary to verify the road area boundary line, the existing road edge, boundary records, the roadway width, the centerline, structures, and the results of on-site inspections together as an integrated whole. Rather than viewing drawing lines in isolation, linking multiple sources and the on-site conditions to make judgments is a practical safety measure in professional practice.


Summary

To confirm the road area on a 2D road ledger attachment map, it is important not to look only at the road area lines on the drawing but to comprehensively check the existing road edge, the road ledger, boundary documents, land acquisition documents, road width, centerline, structures, on-site inspection results, and the update history. The road area is information indicating the extent managed as a road and is closely related to construction limits, occupancy scope, maintenance responsibilities, development consultations, and boundary confirmation.


The first perspective is to read the road boundary line and the existing road edge separately. The pavement edge, gutter edge, curb, retaining wall, and slope edge are the edges of the road visible on site, but they do not necessarily coincide with the road boundary line. It is important not to judge the road boundary solely by how it appears on site.


The second is to reconcile the information in the road ledger with the attached drawings. Confirm that the route name, starting point, end point, length, width, and road area information in the ledger records are consistent with the boundary lines and centerlines on the attached drawings. If you make a judgment based on only one of them, you may overlook inconsistencies.


The third is to examine the relationship with boundary documents and land-acquisition documents. The road area boundary line, the public–private boundary, the parcel boundary, and the land-acquisition boundary are not necessarily the same. It is necessary to check land maps, boundary documents, materials related to the road area, and on-site boundary markers, and to organize the basis for the road area boundary line.


The fourth item is to verify consistency with the roadway width and the centerline. Road area boundary lines relate to width, the centerline, the start and end points, and length. Distinguish between road area width, effective width, carriageway width, and pavement width, and check whether the relationship from the centerline to the boundary lines on both sides does not appear unnatural.


The fifth is to confirm the locations of structures and appurtenances. Side ditches, catch basins, bridges, retaining walls, slopes, guardrails, signs, and lighting are related to the road area and the scope of maintenance and management. Because the location of a structure does not necessarily indicate a boundary or zone line, verify by comparing the attached drawings, the on-site conditions, and the supporting documents.


The sixth point is to perform on-site verification and check the update history. Record the pavement edges, gutters, boundary markers, and structure locations confirmed on-site together with photos and location information, and keep a history of which information was reflected in the drawings. Even if the road boundary line is not updated, recording the reason as a pending item will be helpful at the next inspection.


To more reliably carry out confirmation of road areas on 2D road ledger maps, it is effective to link position information acquired on site with the road area boundary lines and structural information on the drawings. LRTK, a GNSS high-precision positioning device that can be attached to and used with an iPhone, is a good option for tasks that involve confirming features related to road areas—such as gutters, boundary markers, points of width change, centerlines, and structure locations—on site and recording them as high-precision position information. By reducing omissions in road area confirmations and positional mismatches with drawings, and by making the 2D road ledger maps usable as management materials that reflect actual site conditions, considering the use of LRTK can help improve the accuracy and efficiency of road management operations.


Next Steps:
Explore LRTK Products & Workflows

LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.

LRTK supercharges field accuracy and efficiency

The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.

bottom of page