8 Practical Things to Know Before Preparing 2D Road Ledger Maps

Table of Contents

• Overview to grasp before creating a 2D road ledger map

• Practical knowledge 1: Understand the role of the road ledger map

• Practical knowledge 2: Distinguish between the road boundary line and the current road edge

• Practical knowledge 3: Confirm consistency among the centerline, start and end points, and extensions

• Practical knowledge 4: Organize the types of widths and their applicable sections

• Practical knowledge 5: Visualize deficiencies in existing documents and supporting materials

• Practical knowledge 6: Check the coordinate system, scale, and accuracy conditions

• Practical knowledge 7: Decide how to handle field surveys and surveying results

• Practical knowledge 8: Design the update history and operational rules

• Practical cautions that are easy to overlook before preparation

• Summary

The Overall Picture to Grasp Before Preparing 2D Road Ledger Attached Maps

Two-dimensional road ledger attached maps are road management materials that organize, in plan view, the relationships between road facilities—such as road location, road area, road centerlines, widths, lengths, intersection shapes, gutters and manholes, bridges, retaining walls, slopes, sidewalks—and surrounding features. In the practical work of municipalities and road managers, they are referenced in a wide range of situations, including road management, construction design, occupancy consultations, development consultations, boundary confirmation, maintenance and repairs, disaster response, and ledger updates.

When you think of maintaining 2D road ledger maps, you might imagine tasks like neatly redrawing old plans or digitizing paper drawings. However, in practice, that alone is not sufficient. It is necessary to verify which lines are road boundary lines and which lines are the current road edge, whether the centerline aligns with the start and end points in the ledger records, whether the width annotations indicate the road boundary width or the effective width, and whether structures such as gutters and manholes match the field conditions.

What you should know before maintenance is that the 2D road ledger attached maps are "drawings" and, at the same time, the "entry point" to road management information. Even if the lines and numbers on the drawing appear to be correct, if the source documents and update history are unknown, you may not be able to explain them later during construction consultations, occupancy verifications, or boundary confirmations. Conversely, if the meanings of lines and annotations, the source documents, field verification results, and the update history are organized, the road management materials will be easy to use even if the person in charge changes.

Before starting preparation, it is important to decide up front the purpose, scope of coverage, status of available materials, accuracy requirements, on-site verification, and post-delivery operations. If work begins with an unclear purpose, it becomes unclear whether a simple map for viewing is sufficient, whether formal documents for ledger updates are needed, or whether field survey results should be incorporated, causing rework midway. If the scope is also unclear, inconsistencies are likely to arise at intersections, connecting roads, and where the drawing interfaces with adjacent plans.

When preparing 2D road ledger maps, the organization done before drawing lines determines the quality of the final deliverable. It is important to check the road ledger, ledger survey records, as-built construction drawings, land acquisition materials, boundary documents, survey results, site photographs, and past update history, and to decide which information will be treated as the official basis, which will be displayed as reference, and which will be put on hold.

Practical Knowledge 1: Understand the Role of the Map Attached to the Road Ledger

Before preparing a 2D road ledger attached map, you first need to understand the role of the road ledger attached map. A road ledger attached map is not merely a plan view showing the shape of the road. It is a document to facilitate spatial confirmation of route information, road areas, widths, lengths, and information on structures recorded in the road ledger and ledger statements.

Road ledger maps are used in a wide range of practical situations. Road management personnel verify the route alignment and management boundaries. Construction staff check the scope of road improvements or repairs and the locations of features such as side gutters, manholes, bridges, and retaining walls. Occupancy/permit staff verify whether the proposed location lies within the road area and whether it interferes with existing structures or existing encroachments. In development consultations, they check the width of connecting roads, road areas, corner cut-offs, and relationships with drainage facilities. For boundary confirmation, these maps are referenced as preliminary materials for organizing the relationships among road area lines, public–private boundaries, parcel boundaries, and on-site structures.

In this way, 2D road ledger maps are materials viewed by multiple departments and stakeholders. Therefore, drawings that only the creator understands are insufficient. The meanings of road boundary lines, centerlines, existing site features, and reference lines must be clear, and it must be possible to trace them back to the ledger records and related documents. It is important not only that the drawings are easy to read, but also that they can be explained as road management materials.

Before preparing the material, clarify which task this attached drawing will be used for. Will it be organization for viewing, a formal ledger update, materials for construction consultation or occupation verification, or are you aiming ahead to future data maintenance and linkage with the management ledger? The necessary level of preparation will differ accordingly. If it is for viewing, clarity is prioritized, but if it is to be used for ledger updates or consultations, supporting documentation, accuracy, and update history will be required.

If you proceed with preparing the maps attached to the road ledger without understanding their role, necessary information may be missing, or conversely, too much unnecessary information may be crammed in. Clarifying the purpose of the drawings and sorting out who will use them and in what situations is the first step before preparation.

Practical Knowledge 2: Treat the road boundary line and the existing road edge separately

The second practical point is to distinguish between the road area line and the existing road edge. The most common source of misunderstanding in 2D road ledger maps is treating the road area line, pavement edge, gutter edge, and boundary-related lines on the drawing as if they were the same. Although all of these are represented as lines on the drawing, their practical meanings differ.

The road boundary line indicates the extent that is managed as a road. It may include not only the carriageway but also sidewalks, shoulders, gutters, drainage facilities, slopes, retaining walls, and spaces necessary for management. Therefore, the pavement edge or gutter edge visible on site does not necessarily coincide with the road boundary line. The road boundary may continue beyond the pavement edge, and gutters may be located within the road boundary.

On the other hand, the current road edge refers to the physical edge of the road that exists on site. Examples include the pavement edge, the outside of a gutter, the inside of a gutter, curbs, sidewalk edges, the front face of retaining walls, and slope edges. These are important pieces of information for field surveys and maintenance, but they are not the road boundary line itself. Even if a gutter has been relocated on site, that does not necessarily mean the road boundary line has been changed, so it is necessary to make separate determinations for updating the existing site features and for updating the management lines.

Before maintenance, confirm the basis for the road area boundary lines. Decide which documents—land acquisition materials, documents related to road areas, boundary documents, as‑built drawings, existing attached maps, field survey results, etc.—will be used as the basis for establishing the road area boundary lines. If the basis is insufficient, rather than fixing the boundary lines by conjecture, it is safer to manage them as pending items.

Also, when displaying the current road edge, clearly indicate which feature is being shown. Whether you show the outer side of the gutter, the inner side, or the pavement edge changes the meaning on the drawing. Using different line types, layers, and a legend to separate the road boundary line from existing features makes it less likely that a person reviewing the drawings later will misinterpret them.

Treating the road boundary line separately from the existing road edge affects the scope of construction, occupancy locations, boundary verification, and maintenance management. Understanding this difference before improvements enhances the reliability of 2D road ledger maps.

As Practical Knowledge 3, check the consistency of the centerline, the start and end points, and the extensions

The third piece of practical knowledge is to verify the consistency of the road centerline, starting point, end point, and length. The road centerline is the axis of route management in the two-dimensional map attached to the road ledger. It serves as the basis for organizing construction sections, inspection points, repair history, structure locations, and points of width change along the route.

The road centerline is not necessarily the simple midpoint of the road area. In cases of one-sided widening, one-sided sidewalks, intersections, curves, and bridges, the visually apparent center and the administratively defined centerline may differ. If the centerline is mechanically shifted to match the on-site road edge or pavement width, it may no longer align with the lengths in ledger records or with past inspection records.

Before maintenance, confirm the start and end points recorded in the ledger records and determine where they correspond on the attached drawing. Whether the start point is the center of an intersection, the edge of the road area, a management boundary, or the end of a bridge changes how the centerline should begin and how its extension is considered. The same applies to the end point. If the centerline is created while the start and end points are ambiguous, problems with reconciling later extensions and roadway widths will arise.

With respect to length, confirm whether the length in the ledger record and the centerline length on the attached drawing are consistent. If there is a discrepancy, check how the centerline was taken, the positions of the start and end points, the treatment of intersections, the representation of curved sections, the drawing accuracy, and the update history. Rather than simply matching the numbers, it is important to understand under what conditions the lengths are being managed.

For routes that span multiple drawings, we also check the connections with adjacent drawings. At drawing boundaries, we check whether the centerline is interrupted or duplicated, and whether the roadway boundary lines and width indications are continuous. Even if a single drawing is complete, inconsistencies across the entire route make it difficult to use as management documentation.

Confirming the centerline, the start and end points, and the extension before maintenance makes it easier to prevent major revisions after the drawings are created. The centerline should be treated not as an auxiliary line but as the backbone of the road ledger attached map.

Organize the types of roadway widths and their applicable sections as Practical Knowledge 4

The fourth practical point is to clarify the types of width and the sections to which they apply. In two-dimensional road ledger maps, width is very important information, but the term “width” has multiple meanings. Confusing road area width, effective width, carriageway width, and pavement width leads to inconsistencies with ledger documents and field survey results.

The road area width indicates the width of the area managed as a road. It may include gutters, sidewalks, shoulders, slopes, and retaining walls. The effective width may indicate the width actually available for passage or use. The carriageway width is the width of the portion used by vehicles, and the paved width is the width of the paved area. Treating these as the same width can cause misunderstandings for personnel using the drawings.

Before maintenance, decide what the width displayed on the 2D road ledger attachment map is intended to indicate. If the width in the ledger record is the road area width, confirm its consistency with the road area line on the attachment map. When displaying pavement width or effective width measured on site, it must be expressed separately from the official ledger width. Clarify whether it will be shown as reference information or as management information.

The applicable sections are also important. Roads do not have the same width throughout. Widths can vary at intersections, bridge sections, sections where sidewalks are installed, narrow stretches, turnouts, and in improved and unimproved road sections. If it is not clear which section the width annotations on the attached drawing correspond to, incorrect values may be used in consultations or construction verifications.

When organizing width-change points, verify them by combining the centerline, road boundary line, structures, and field survey results. Also clarify measurement conditions, such as whether to use the outer edge of the gutter or the road boundary line as the reference, or whether to take measurements perpendicular to the centerline. In curved sections and at intersections, you may not be able to display widths using the same approach as in normal sections.

Road width is information that users of the road register's attached maps pay especially close attention to. By organizing the types of road widths and their applicable sections beforehand, you can significantly reduce verification and revisions after delivery.

Practical Knowledge 5: Visualize Insufficiencies in Existing Documentation and Supporting Evidence

The fifth practical knowledge is to make shortages of existing materials and supporting documents visible. When compiling 2D road ledger attached maps, we use existing attached maps, ledger records, as-built drawings, land acquisition materials, boundary documents, survey results, and site photographs, among other things. However, these are not always all available. If work proceeds while leaving material shortages ambiguous, lines and numerical values with weak supporting evidence will remain in the deliverables.

First, organize the materials you have on hand. Check whether there are existing road ledger maps, whether the ledger records are up to date, from what period the as-built drawings date, whether there are land acquisition documents or boundary records, whether the survey results record the coordinate system and the meaning of the survey points, and whether the site photographs show identifiable locations. It is important not only to confirm the existence of materials but also to assess what information those materials can serve as the basis for.

We will organize documentation shortfalls by categorizing them according to the type of information. We distinguish whether the basis for the road boundary line is lacking, whether the start and end points of the centerline are unknown, whether the definition of the road width is unclear, whether confirmation of the current status of structures is insufficient, or whether the coordinate system is unknown. Once the missing items are clarified, it becomes easier to prioritize field surveys and the review of additional documents.

Official evidentiary materials and reference materials should be distinguished. Old drawings, background maps, and on-site notes can be useful as references, but they are not necessarily usable as definitive evidence for determining road area lines or boundaries. As-built construction drawings are also effective for confirming the details of the work, but they may not always be documents that directly indicate road areas or boundaries. It is important to understand the nature of each material and use them appropriately.

It is important not to fill in missing information by guessing. Organize information that can be confirmed as confirmed information, mark information with weak supporting evidence as reference, and keep unverified information as pending items. This reduces the risk that users will over-rely on the drawings.

Visualizing gaps in documentation is an important step for maintaining the quality of maintenance. Rather than hiding what is missing, clarifying exactly what additional checks are required because of those gaps leads to two-dimensional road ledger maps that are usable in practice.

Confirm the coordinate system, scale, and accuracy requirements as Practical Knowledge 6

The sixth practical point is to verify the coordinate system, scale, and accuracy conditions. When preparing 2D road ledger attached maps, it is dangerous to assume that a drawing is high-precision just because it exists as digital data. If the source materials are paper drawings or scanned images, paper expansion and contraction, distortion during scanning, line thickness, and scale limitations will affect positional accuracy.

First, confirm the coordinate system of the existing attached drawings. Depending on the documents, the way positions are handled may differ — such as the plane rectangular coordinate system, latitude/longitude, local coordinates, or drawing-specific coordinates. When overlaying with field survey results, as-built drawings, or boundary documents, differences in coordinate systems can cause positional shifts. If the coordinate system is unknown, record/manage that it is unknown and avoid relying on it too much for high-precision positional determinations.

Confirm the scale as well. Enlarging a paper drawing will not provide accuracy beyond the original scale. There are limits to extracting detailed road areas or positions near boundaries from small-scale drawings. Even the thickness of lines can make a significant difference on site. Before any work, it is important to determine which information will be used at which level of accuracy.

When reflecting field survey results, confirm the control points, measurement methods, measurement targets, and measurement dates. Coordinates alone are not sufficient; you must record whether the point is on the outer side of a gutter, the pavement edge, a boundary marker, or the center of a manhole. If the meaning of the measurement target is unclear, it will be difficult to reflect it in road boundary lines or the locations of structures.

When high-precision information is reflected only partially, clearly indicate that the overall accuracy of the drawing is not uniform. If some sections are based on field survey results while surrounding areas inherit older attached drawings, it is necessary to prevent users from misunderstanding that everything has the same accuracy. Record the scope of reflection and the accuracy conditions in the revision history or management table.

If you confirm the coordinate system, scale, and accuracy conditions before preparation, you can reduce inconsistencies between drawings and the field, drawings and the ledger, and drawings and survey results. Organizing the assumptions underlying location information is the foundation that supports the quality of two-dimensional road ledger maps.

Decide how to handle on-site investigations and surveying results as Practical Knowledge 7

The seventh piece of practical knowledge is deciding how to handle field surveys and survey results. When preparing two-dimensional attached maps for the road ledger, existing materials alone may not reveal the current conditions. In such cases, by utilizing on-site surveys and survey results, you can confirm road edges, side ditches, manholes, boundary markers, points where the roadway width changes, and the locations of structures.

In an on-site survey, decide in advance what you will confirm. Depending on whether the purpose is to verify the road boundary line, to check the existing road edge, to inspect structures such as side ditches and manholes, or to identify points where the roadway width changes, the items to observe on site will differ. If you go to the site with an unclear purpose, photographs and measurement points may be difficult to use later.

When obtaining survey results, always record what each measured point represents. Note what was measured — for example, the outside edge of a gutter, the pavement edge, a boundary marker, the center of a manhole, the front face of a retaining wall, the top of a slope, the end of a bridge, etc. Even if you only have coordinate values, they cannot be used to update drawings if the measured feature is unknown. It is also important to link field photographs to the measured points.

When reflecting the results of a field survey, separate existing site features from management information. If it can be confirmed on site that the position of a side gutter has changed, the gutter line as an existing site feature may be updated. However, that does not necessarily imply a change to the road boundary line. To update the road boundary line, comparison with land acquisition documents and road boundary records is necessary.

Also, information that could not be confirmed during the site survey will be left as pending items. Details such as boundary markers not being found, the management classification of structures being unclear, insufficient supporting documentation for road area boundary lines, or inconsistencies with existing drawings whose coordinate system is unknown are clues needed for verification on the next visit. Recording what is unknown will make post-maintenance operations easier.

If you decide how to handle field surveys and survey results in advance, the work to maintain 2D road ledger attached maps can be streamlined. Leaving the information obtained on site in a form that can be used directly in drawings leads to improved quality and reduced rework.

Design update history and operational rules as Practical Knowledge 8

The eighth piece of practical knowledge is to design the update history and operational rules. A two-dimensional road ledger map is not a document that is finished once and for all. If there are road improvements, side ditch repairs, sidewalk improvements, intersection upgrades, bridge repairs, changes in development ownership, disaster recovery, or relocation of encroachments, it needs to be continuously updated.

The update history records the update date, the relevant route, the relevant section, the content of the update, the materials used, whether an on-site inspection was conducted, the extent to which survey results were reflected, the verifier, and any pending items. These are categorized separately to show whether the road boundary line was updated, the centerline was corrected, width annotations were changed, side ditches or manholes were added, or only the current road edge was updated.

Linking to supporting documents is also important. Make it clear which materials were used as the basis for updates—such as as-built drawings, ledger records, land acquisition documents, boundary documents, survey results, site photographs, and inspection records. If the lines and attributes on the drawings can be traced back to the supporting documents, responding to inquiries and handing over will be easier.

Decide management rules for official versions, working versions, and past versions. If a drawing that is still being worked on is used as the official version, unverified information may be used for practical decision-making. Past versions are necessary for checking history, but if they are mixed with the official version they can cause misuse. Make the status of versions clear in file names, folder structures, the title block within drawings, and in management sheets.

Operational rules should specify who updates, who reviews, and in what state a version is made official. Deciding in advance when to carry out post-construction updates, reflect inspection results, organize on-site verification findings, and reconfirm outstanding items makes it easier to keep the supplementary drawings up to date.

By designing an update history and operational rules, a 2D road ledger map becomes a management document that can be used over the long term. In practice, it is extremely important to consider not only the level of completeness at the time of creation but also how easy it will be to update in the future.

Practical precautions easily overlooked before maintenance

What is easily overlooked before preparing 2D road ledger annex maps is that the appearance of the drawings and their practical accuracy are not the same. Even if lines are neatly drawn, they are insufficient as road management documents if it is unclear what those lines represent and which sources they are based on. Before preparation, you need to verify the meaning and the basis of the lines rather than their appearance.

Also, pay attention to timing discrepancies among materials. Ledger records, as-built drawings, site photographs, survey results, and existing attached diagrams do not necessarily represent information from the same point in time. There may be cases where an as-built drawing reflecting road improvements exists while the attached diagram still contains old information, where further repairs were carried out after a site survey, or where only the ledger records have been updated. It is important to check the materials' creation dates and the scope of what they reflect.

The method of recording on-site inspections is another item that is easy to overlook. Simply taking photos is not enough; unless you record where and what was photographed and what each measurement point indicates, you will not be able to reflect them on the drawings later. It is important to keep the on-site inspection results in a form that can be used for the next update.

Furthermore, it is necessary not to try to finalize everything at once. Sections with insufficient documentation or locations that are difficult to verify on site should be managed as pending items. If road area boundary lines or boundary-related lines are presented as confirmed information without justification, later corrections may become substantial. Distinguishing confirmed information, reference information, and pending information is an important consideration before undertaking work.

Summary

Before compiling two-dimensional road ledger maps, it is important to understand the purpose of the drawings, the difference between road area boundary lines and the actual road edge, the centerline, start and end points and extensions, the types of width measurements, the lack of reference materials, coordinate systems and accuracy, field surveys, and update history and operational rules. If you begin work without organizing these items, even drawings that look tidy will require rechecking and corrections every time they are used in practice.

First, understand the role of the road ledger map. Since it is a document used for road management, construction design, occupancy consultations, development consultations, boundary confirmation, maintenance and repair, and disaster response, it must be interpretable in the same way by multiple responsible staff, not just its creator.

Next, consider the road area boundary line and the current road edge separately. The pavement edge or the edge of a gutter are lines visible on site, but they are not necessarily the road area boundary line. By separating updates to existing site features from updates to management lines, it becomes easier to prevent incorrect determinations of the area boundary.

Third, verify the consistency of the centerline, the start point, the end point, and the extension. The centerline is the axis of route management and is related to the extension recorded in ledger records, survey points, and the locations of structures. It is important not to treat it as a visual centerline.

Fourth, organize the types of widths and their applicable sections. Distinguish between road right-of-way width, effective width, carriageway width, and pavement width, and clarify which section each width annotation corresponds to.

Fifth, we visualize deficiencies in existing documents and supporting materials. We organize where the lack of supporting evidence occurs among road boundary lines, centerlines, road widths, structures, and coordinate systems, and classify information into confirmed information, reference information, and items on hold.

Sixth, check the coordinate system, scale, and accuracy conditions. Paper drawings and scanned drawings have limits to their accuracy, and to overlay them with surveying results it is necessary to confirm the coordinate system and the meaning of the measurement points.

Seventh, decide how to handle on-site inspections and survey results. If you organize in advance what to check, what to measure, and how to record photos and location information, it will be easier to apply the on-site findings when preparing drawings.

Eighth, design the revision history and operational rules. Separate official, working, and past versions, and record the update date, reference materials used, changes applied, and items on hold so that future updates and handovers proceed smoothly.

To more reliably advance the preparation of two-dimensional road ledger maps, it is effective to link position information obtained on site to road boundary lines, centerlines, width-change points, and structure information. LRTK, a GNSS high-precision positioning device that can be attached to and used with an iPhone, is a well-suited option for verifying on-site points such as side ditches, manholes, boundary markers, road edges, points related to the centerline, width-change points, and structure locations, and recording them as high-precision position information. If you want to compensate for insufficient pre-preparation materials and discrepancies with field conditions and prepare two-dimensional road ledger maps as practical management documents, considering the use of LRTK can help improve the accuracy of road management operations and increase the efficiency of update work.