7 Essential Elements for Creating Plan Views of 2D Road Ledger-Attached Maps

Table of Contents

• Key considerations for creating plan views of 2D road ledger attached maps

• Element 1: Clearly define the purpose of creation and the scope of coverage

• Element 2: Establish the coordinate system, scale, and drawing accuracy

• Element 3: Correctly position the road boundary lines and road centerlines

• Element 4: Ensure consistency among width, length, and start/end points

• Element 5: Appropriately reflect structures and existing site features

• Element 6: Standardize line types, annotations, and legends

• Element 7: Preserve update history and source/reference materials

• Common mistakes that occur when creating plan views

• Summary

Key Considerations for Creating Plan Views of 2D Road Ledger Attached Maps

The plan view of a two-dimensional road ledger-attached map is road management material used to organize, in plan, the road’s location, road area, road centerline, width, length, intersection shapes, structures such as side gutters and bridges, and the relationships with surrounding features. Because it is referenced in various practical operations—road management, construction design, occupancy consultations, development consultations, boundary confirmation, maintenance and repair, disaster response, and ledger updates—it is required not merely to depict the road’s shape but to offer accuracy and clarity usable as management information.

When creating plan drawings, the important thing is not only to produce drawings that look tidy. It is necessary to comprehensively verify whether what basis the road boundary lines are drawn on, whether the road centerline is correctly connected at the start and end points, whether the definition of the width is consistent with the ledger and survey records, whether on-site structures and ancillary features are reflected to the necessary extent, and whether the assumptions about the coordinate system and scale are clear.

Two-dimensional road ledger maps, which represent roads as seen from above, make it easy to grasp the planar positional relationships of roads; however, they are documents that do not adequately convey vertical information such as height, gradients, level differences, or three-dimensional interference with underground buried objects. Therefore, it is important to clarify what will be represented on the plan view and what will be supplemented by separate documents or on-site verification. Trying to cram everything into the plan view makes it hard to read, but if necessary information is lacking, it becomes difficult to use in practice.

Roads also change over time. Road improvements, side ditch repairs, sidewalk construction, intersection upgrades, bridge maintenance, the attribution of roads due to development activities, disaster recovery, and the installation or relocation of objects occupying the road can change on-site conditions. If those changes are not reflected in the maps attached to the road ledger, the drawings will continue to show outdated information. When creating plan drawings, it is important not only to organize the information as of the time of creation but also to anticipate future updates and handovers.

In this article, we explain seven key elements important for creating plan views of 2D road ledger maps, aimed at practitioners. By organizing them in the order of purpose, coordinates and scale, road boundary lines and centerlines, widths and lengths, structures, line types and annotations, and revision history, it becomes easier to produce plan drawings that are user-friendly after delivery and less troublesome to update.

Element 1: Clarify the purpose of creation and the scope of applicability

When creating the plan view of a 2D road ledger supplementary map, the first things to confirm are the purpose of creation and the coverage scope. Depending on the purpose of the plan view, the required amount of information, the accuracy, the elements to be displayed, and the delivery format will vary. You need to clarify whether it will be used as a viewing/reference document for road management, as a base document for ledger updates, as a preliminary document for field surveys and construction consultations, or with an eye toward future digital management.

If you start drafting without a clear purpose, you are likely to run into information shortages or excessive detail later. For example, the work required for a plan that only needs to verify the road area and centerline is very different from that for a plan that must reflect width-change points, structures, boundary relationships, and on-site survey results. If you clarify the intended use cases up front, it becomes easier to decide how much to include in the drawing.

In the target scope, verify the route name, route number, starting point, end point, target section, intersection areas, connecting roads, branch lines, and connections with adjacent drawings. Maps attached to the road ledger are often organized by route, but actual roads on site are continuous through intersections and adjacent roads. If you extract and create only the target route, inconsistencies may arise at intersection areas and in connections with adjacent drawings.

Particular attention should be paid to intersections and corner cuts. While road areas and centerlines are easy to organize for straight sections alone, at intersections multiple roads connect and the road area expands. If you do not decide in advance the extent to include in the target route, the management divisions with connecting roads, and how to handle corner cuts, revisions are likely to occur later.

Also, it is important to clearly define the areas that are excluded. Adjacent roads managed by other entities, sections not confirmed on site, areas shown only for reference due to insufficient documentation, and structures managed on separate drawings should be arranged so they do not appear as definitive information on the plan. Delivering the work with excluded or unconfirmed information left ambiguous may cause users to mistakenly treat it as official information.

If you clarify the purpose and scope at the outset, the criteria for subsequent coordinate settings, line-type organization, annotations, layering, on-site verification, and pre-delivery checks will be established. The quality of floor plan production is largely determined by this initial organization.

Organize the coordinate system, scale, and drawing accuracy as Element 2

The second element involves organizing the coordinate system, scale, and drawing accuracy. Because the plan view of the two-dimensional road register map is a document that shows the positional relationships of roads, if the assumptions about the positional information are unclear, discrepancies will occur when it is overlaid with field survey results or related materials. Even if it looks well presented, if the coordinate system and scale conditions are unknown, you cannot determine how much it can be trusted in practice.

The first thing to confirm is which coordinate system you will use to create the plan drawing. When using existing attached drawings, field survey results, construction completion drawings, boundary documents, land acquisition materials, background maps, etc., each may not be managed in the same coordinate system. If the plane rectangular coordinate system, latitude/longitude, local coordinates, and drawing-specific coordinate systems are mixed, even if they are meant to indicate the same point, the positions may not align.

Even when using existing drawings, confirm the assumptions about coordinates. If past drawings are image data without coordinates, or are paper drawings scanned and aligned, they cannot be treated with the same accuracy as field survey results. When drafting based on old drawings, you need to understand the accuracy limits of the original source material.

Scale is also important. In paper drawings and image-based appendices, the scale, line thickness, distortion from scanning, and paper stretching affect positional accuracy. Even if you enlarge a small-scale drawing to read it in detail, you cannot achieve accuracy that exceeds the precision of the original drawing. When using them to check road areas or locations near boundaries, confirm that the scale and the method used to create them are appropriate for the intended purpose.

When incorporating field survey results, clarify the meaning and accuracy of the survey points. Having only coordinate values is insufficient; if you cannot tell whether a point is at the pavement edge, the outer edge of a gutter, a boundary marker, or on the road centerline, it cannot be correctly reflected on the plan view. Recording what was measured, the measurement date, the measurement method, the control points, and the coordinate system makes future updates easier.

When partially incorporating high-accuracy information, be aware that the overall accuracy of the drawing will not be uniform. If only certain sections reflect on-site survey results while surrounding areas retain older drawings, road boundary lines and centerlines may be misaligned at the connection points. It is important to clearly identify which areas are high-accuracy and which are provided for reference.

Organizing the coordinate system, scale, and drawing accuracy is the foundation that supports the reliability of plan drawings. Even if the lines on a plan appear correct, if the assumptions about positional information are ambiguous, problems can arise when verifying consistency with the site or other documents. If these conditions are recorded at the time of creation, successors and stakeholders can use them with confidence.

Correctly position the road boundary lines and the road centerline as Element 3

The third element is correctly placing the road boundary line and the road centerline. In the plan view of the 2D road ledger-attached map, the road boundary line and the road centerline form the framework of the drawing. The road boundary line indicates the area managed as a road, and the road centerline serves as the management axis connecting the route from its starting point to its endpoint. If these two remain ambiguous, it becomes difficult to organize road width, length, structures, construction scope, and areas of occupation.

The road boundary line does not necessarily coincide with the edge of pavement or the edge of the gutter visible on site. The road area may include the roadway, sidewalks, shoulders, gutters, drainage facilities, slopes, retaining walls, and planting strips. Therefore, simply tracing the pavement edge as the road boundary line may not correspond to the extent defined for road management. When placing the road boundary line, it is necessary to cross-check materials related to the road area, land acquisition documents, boundary documents, as-built drawings, and the results of on-site verification.

Do not treat the road area line as identical to the public–private boundary or the parcel boundary. They may coincide in some cases, but they are not always the same. Even when comparing cadastral maps or boundary documents with the maps attached to the road ledger, it is important to distinguish the meanings of the lines. A road area line indicates the extent for road management and may differ from land boundaries or the edges of existing structures.

The road centerline should not necessarily be drawn at the geometric center of the road area. In cases of widening on one side, a sidewalk on one side, at intersections, on curves, or immediately before and after bridges, the apparent center and the administratively defined centerline may differ. Because the centerline serves as an axis for organizing route length, survey stations, construction sections, inspection points, and structure locations, it should be placed while confirming consistency with the start and end points, existing records, and field survey results.

At intersections, the handling of boundary lines and centerlines is particularly important. At intersections, the road area widens, involving corner cuts, sidewalks, gutters, cross drainage, and management divisions with connecting roads. It is necessary to clarify how far to extend the centerline of the subject route, how to treat the intersection with connecting roads, and how to express corner-cut areas as part of the road area.

Road boundary lines and centerlines should be clearly distinguished by line type and layer. If the two are drawn with similar line types, users may be misled. The road boundary line, as the line indicating the scope of management, and the centerline, as the axis for route management, should preferably be managed as separate systems both on drawings and in the data.

If you can position those two correctly, the overall reliability of the plan drawing increases. Conversely, on drawings where the road boundary lines or centerlines are ambiguous, no matter how well the annotations or structures are arranged, the drawing will have low practical value as a map attached to the road ledger.

Align width, length, and start/end points as Element 4

The fourth element is to reconcile the road width, length, and start and end points. In the plan view of the two-dimensional road ledger-attached map, even if the road boundary lines and center line are correctly placed, if the displayed width and length do not match the ledger records or the actual site, the document becomes difficult to use in practice. Road width, length, and start and end points are basic information for route management and are items that must always be confirmed when creating the plan view.

With respect to width, first make clear which width is being displayed. Road right-of-way width, effective width, carriageway width, and pavement width are not the same. Road right-of-way width indicates the width of the area managed as a road and may include side gutters, sidewalks, shoulders, and embankment slopes. Effective width may indicate the width that is practically available for passage or use. Pavement width and carriageway width have further different meanings. If these are recorded simply as “width” without distinguishing them, users will be misled.

Road widths may vary by segment. At intersections, bridges, sections with sidewalks, narrow sections, pullouts, and at the boundary between improved and unimproved road sections, the width is not constant. On plan views, place annotations so that it is clear which segment each width value corresponds to. If annotations overlap the road right-of-way lines or structures, or if the corresponding segment is unclear, mistakes can occur when reading the drawings.

Regarding length, confirm its relationship with the road centerline. Check whether the length recorded in the ledger agrees with the centerline length on the attached drawing. If there is a discrepancy, verify the positions of the start and end points, how the centerline was defined, the treatment of intersections, the depiction of curves, the drawing accuracy, and the timing of updates. If the centerline is revised, also confirm whether the length values are affected.

The start and end points must be clearly indicated on the plan. Whether the start point is the center of an intersection, the edge of the roadway area, an administrative boundary, or the end of a bridge changes how the length and centerline are handled. If the start and end points are ambiguous on the drawing, it becomes difficult to explain the section in question and the scope of the work.

Also, the width, length, and start/end points should be checked against the ledger records. If only the notations on the attached figure are updated while the ledger records remain outdated, inconsistencies will occur. Conversely, the ledger records may be updated while the width or centerline on the plan view still reflects old information. When creating plan drawings, it is important to reconcile the drawings and the ledger information as a single, consistent set.

By reconciling road width, length, and start/end points, the maps attached to the road register become more usable materials for route management. Not only recording numerical values but clarifying which route, which section, and which source document those values are based on enhances the quality of practical work.

Appropriately reflect structures and existing site features as Element 5

The fifth element is appropriately reflecting structures and existing site features. In the plan view of a two-dimensional road ledger map, not only road area lines and centerlines but also gutters, catch basins, transverse drainage, bridges, retaining walls, slopes, guardrails, signs, lighting, sidewalks, curbs, entrances and exits, adjacent waterways, and other elements related to on-site road management may be depicted. Because these serve as prerequisites for construction planning, maintenance management, occupancy consultations, and field surveys, it is important to organize them correctly to the necessary extent.

When depicting structures, clearly define which items will be shown. Depicting every existing feature in detail can make drawings hard to read, yet omitting facilities that are important for road management makes them impractical for use in the field. Decide, based on the purpose of the plan view, which structures to show on the drawing and which information to manage in separate documents or as attribute information.

Side gutters and catch basins are particularly important because they relate to road boundaries, drainage plans, and the scope of construction. When depicting a gutter, clarify whether you are showing the inside or the outside, or whether it is being shown as a centerline. Likewise, when depicting a basin, determine whether you are showing its center position or its outline. When reflecting surveying results, it is essential to record what each measurement point represents.

Bridges, retaining walls, and slopes are important when confirming their relationship to road areas and management limits. In bridge sections, the carriageway width, centerline, and road area may differ from those of adjacent roads. Retaining walls and slopes may be included within the road area or treated as structures on adjacent land. In plan views, they should be arranged so that the relationship between the road boundary lines and the structures can be read.

Distinguishing between existing on-site features and management information is also important. The edge of pavement and the edge of a gutter are lines visible in the field, but they may have a different meaning from the road boundary line. Reflecting existing on-site features does not necessarily mean changing the road boundary line. If existing on-site features and the road boundary line are treated with the same line type or on the same layer, users can be easily misled.

When incorporating the results of on-site verification, it is also important to record what point in time the information on the drawings represents. Because roads change, if the date of on-site verification or the update history is unknown, future personnel cannot judge how much they can rely on that information. Structures and existing site features are important elements that link the maps attached to the road ledger to the field, but they are also information prone to missed updates and incorrect reflection.

Standardize line types, annotations, and legends as Element 6

The sixth element is to standardize line types, annotations, and legends. In the plan view of a 2D road registry map, many pieces of information overlap, such as road area lines, centerlines, road edges, structure lines, boundary-related lines, reference lines, annotations, and background features. If these representations are not standardized, users may misread the drawings even if the content is correct.

When organizing line types, the meanings of lines are separated according to their roles in road management. The road area line indicates the management scope, the road centerline is the axis for route management, pavement edges and gutter edges are existing site features, boundary-related lines convey information related to land boundaries, and reference lines are treated as auxiliary information. Drawing these with the same line type will confuse readers of the drawings.

Notes should be placed so that the corresponding lines and sections are clearly identifiable. If it is unclear which section a width annotation applies to, where the start and end points are, or which facility a structure name refers to, reviewers are likely to request corrections. Overlapping text, or text that overlaps road boundary lines or structure lines, reduces legibility.

The legend is a set of conventions for reading drawings. Confirm that the line types and symbols used on a drawing correspond to the legend. Situations such as line types appearing on the drawing that are not in the legend, or a line type that the legend designates as a road-area boundary being used to mean something else, should be avoided. When producing multiple drawings, standardize them so that the legend and line types do not vary from drawing to drawing.

Also separate the presentation of confirmed information and reference information. If definitive road boundary lines based on land acquisition documents and survey results are displayed with the same visual weight as reference features incorporated as background, users may mistakenly treat the reference lines as official information. It is important to make unconfirmed sections and reference displays identifiable by notes and line types.

Standardizing line types, notes, and legends not only improves the readability of drawings but also directly prevents misunderstandings in practice. A plan drawing should not be something only the creator can understand. It needs to be organized so that even someone seeing it for the first time can understand the meaning of the lines and the priority of the information.

Retain the revision history and supporting documentation as Element 7

The seventh element is to retain update histories and supporting documentation. The plan views in the 2D road ledger's attached maps are not something you create and finish; they are documents that are updated to reflect changes in the road. If update histories and supporting documentation are not retained, you will not be able to explain why a line or a value is what it is during the next update or when responding to inquiries.

Update history records the date of creation (year and month), date of update (year and month), target route, target section, details of the update, materials used, whether on-site verification was performed, the scope of survey results reflected, and any pending items. It should be made clear whether the road area boundary was updated, the current road edge was updated, the centerline was corrected, width annotations were changed, or structures were added.

Source documents include the road ledger, ledger records, existing attached maps, as‑built drawings, land acquisition maps, boundary documents, field survey results, site photographs, and structural documentation. If you make it clear which document was used as the basis for which piece of information, it will be easier to verify later. If only lines remain on the drawings and the source documents are unknown, the reliability of the materials as road management records decreases.

Recording information that was not reflected can also be useful in practice. For example, if the pavement edge on site had changed but there are no supporting documents for the road boundary line so the boundary line was left unchanged, or if there is a structure on site but it is unclear whether it is subject to management so it was put on hold, record those decisions. Such information is important for the next update or during handover.

Management of official versions, working versions, and past versions is also related to the revision history. If a floor plan that is still being worked on is used as the official version, unverified information may be used in practical decisions. Manage drawings confirmed as the official version, drawings under review, and past versions separately, and record their status within the drawings and in the management sheet.

Keeping records of revision history and supporting documents is work that enhances the future value of plan drawings. By not only producing accurate drawings at the current time but also keeping them in a state that makes the decision-making process understandable later, the 2D road ledger attached drawings can serve as management documents that remain useful for a long time.

Common mistakes that occur when creating floor plans

When creating plan views of 2D road ledger-attached maps, several typical mistakes occur. The most common is confusing the road boundary line with the existing road edge. Treating the pavement edge or the gutter edge as the road boundary line can result in drawings that do not correspond to the scope used for road management. Road boundary lines require supporting evidence concerning land acquisition and the road area.

Next, there is a mistake of drawing the centerline simply at the visual center. The road centerline is the axis for route management and is related to the starting point, end point, length, and stationing. In cases of one‑side widening or at intersections, the center of the road area and the management centerline may not coincide. When creating the centerline, confirm consistency with ledger records and existing documents.

Not verifying the definition of width is also a common mistake. If width is recorded without distinguishing road area width, effective width, carriageway width, and paved width, users will be misled. It is also problematic when it is unclear which section a width value corresponds to. Widths must clearly state not only numerical values but also their definitions and the sections to which they apply.

Mistakes are sometimes made by drafting without checking the coordinate system or scale. When old paper drawings or scanned drawings are traced to create a plan, they may not match field survey results or related documents. It is important to check the coordinate system, survey results, control points, and the accuracy of the source materials, and, when necessary, to record notes about accuracy.

Omitting updates to structures is another common mistake. Even when road boundary lines and center lines have been updated, side ditches, manholes, bridges, retaining walls, and guardrails may remain with outdated information. Conduct field verification and compare with as-built drawings to properly reflect the necessary structures.

Finally, failing to keep a revision history is also a major mistake. Even if the drawings themselves are well organized, if it is unclear when and on which documents they were based, future updates or handovers will be difficult. When creating floor plans, it is essential to retain not only the finalized drawings but also the basis for their creation and the revision history.

Summary

When creating plan views for 2D road register maps, it is important not only to draw the shape of the road but also to organize information that can be used as road management documentation. By reviewing the intended purpose, coordinate system, road area lines, road centerline, width, length, structures, line types, annotations, and update history together, you can produce a plan view that is practical to use and easy to update.

First, clearly define the purpose and scope. Whether it is for viewing, ledger updating, construction consultations, or on-site verification will change the required level of accuracy and the items to be displayed. It is important to organize the target route, starting point, end point, intersections, connecting roads, and any excluded areas.

Next, clarify the coordinate system, scale, and drawing accuracy. When overlaying existing drawings, field survey results, as‑built drawings, and boundary records, confirm the coordinate system and the accuracy of the source materials. When working from paper drawings or scanned drawings, you need to understand and account for distortions and the limitations of scale.

Road boundary lines and road centerlines form the framework of plan views. Road boundary lines do not always coincide with the existing road edge or parcel boundaries. The centerline is not simply the geometric center of the road area; it is organized as the axis for route management. At intersections and on curves, attention must also be paid to the relationship with connecting roads and corner cuts.

Width, length, and start/end points should be aligned with the ledger records. Distinguish the road right-of-way width, effective width, carriageway width, and pavement width, and clarify which section each width corresponds to. Because length relates to how the centerline and the start/end points are handled, it is important to verify it against the ledger records.

Structures and existing site features are also properly reflected. Side ditches, manholes, bridges, retaining walls, slopes, guardrails, signs, and lighting are related to road management and construction planning. However, because existing site features and management information such as road boundary lines do not have the same meaning, they are represented with separate line types and layers.

Standardizing line types, annotations, and the legend is also indispensable. Ensure road boundary lines, centerlines, existing road edges, structure lines, boundary-related lines, and reference lines can be distinguished, and arrange annotations so that the sections they correspond to are clear. It is important to use wording that can be understood even by personnel viewing the drawings for the first time.

Finally, record the update history and reference materials. If you keep it in a state where it is clear which materials were used as the basis, when, and which sections were created or updated, future updates and handovers will be easier. Recording information that was not incorporated and any pending items is also useful in practice.

To more reliably advance the creation of plan views for the 2D maps attached to road ledgers, it is effective to link position information obtained on-site with roadway boundary lines, centerlines, width-change points, and structure information on the drawings. LRTK, a GNSS high-precision positioning device that can be attached to an iPhone, is a suitable option for verifying on-site points related to gutters, manholes, boundary markers, road edges, centerline points, and structure locations and recording them as high-precision positional information. If you want to integrate on-site verification with plan creation rather than rely solely on existing materials, considering the use of LRTK can more easily lead to improved accuracy of the 2D maps attached to road ledgers and increased efficiency in road management operations.