10 Items to Check When Reviewing Deliverables of 2D Road Ledger Attached Maps

Table of Contents

• Why checking deliverables of 2D road register attached maps is important

• Check 1: Confirm the scope of the deliverables and the drawing composition

• Check 2: Prevent mixing the latest version with working copies

• Check 3: Confirm the road boundary lines and the existing road edges

• Check 4: Confirm the road centerline, start and end points, and extension

• Check 5: Confirm consistency between width annotations and the register records

• Check 6: Confirm that structures and ancillary features are reflected

• Check 7: Confirm the coordinate system, scale, and positional accuracy

• Check 8: Confirm the consistency of line types, layers, and legends

• Check 9: Confirm the supporting documents and the update history

• Check 10: Confirm the delivery format and future updatability

• Practical workflow for efficiently conducting deliverable checks

• Summary

Why It Is Important to Check Deliverables of 2D Road Ledger Attached Maps

The two-dimensional road ledger attachment map is a road management document that organizes, in plan view, the road location, road area, road centerline, widths, lengths, intersection geometries, structures such as side ditches and bridges, and the relationships with surrounding features. After delivery as a final product, it is referred to in a variety of practical tasks, including road management, construction design, occupancy consultations, development consultations, boundary confirmation, maintenance and repair, disaster response, and ledger updates. Therefore, in deliverable checks it is necessary to confirm not only the appearance of the drawings but also whether they are in a condition that can be used as road management information.

What is often overlooked during deliverable checks is that, even if the lines and text on the drawings are neat, the rationale or meaning may be ambiguous. If you do not check whether the road boundary line is being confused with the pavement edge or the gutter edge, whether the road centerline aligns with the start and end points in the ledger survey report, whether the width notation refers to the road boundary width or the effective width, whether the positions of structures match the actual site, and whether the coordinate system and scale are clearly specified, corrections or rechecks will be required after delivery.

Also, 2D road ledger maps are not materials that are completed once and for all. The field changes due to road improvements, side ditch repairs, sidewalk construction, intersection improvements, bridge repairs, road ownership changes resulting from development activities, disaster recovery, relocation of encroachments, and so on. At the stage of checking deliverables, it is also important to confirm whether the data structure can withstand future updates. If official versions and working versions are mixed, if the source documents cannot be traced, or if update histories are not retained, the next update will require a great deal of effort.

Deliverable checks are not merely tasks to hunt for errors in the submitted materials. They are a verification process to accept maps attached to the road ledger as management documents that can be used in practical operations. Below, we organize 10 items to check in the deliverable inspection of two-dimensional road ledger attached maps, arranged in the order that makes them easiest for practitioners to verify.

Check 1: Confirm the scope of the deliverables and the composition of the drawings

The first items to check are the scope of the deliverables and the drawing structure. The content of 2D road ledger attached drawings varies depending on the target routes, target sections, intersections, connecting roads, branch lines, and how the drawings are divided. No matter how neatly the drawings are produced, if the scope differs from the requested conditions, the deliverables are inadequate.

For the subject route, confirm that the route name, route number, starting point, and end point match the request and the road ledger. If a long route is divided into multiple drawings, it is also important that the drawing numbers and division ranges are consecutive. If the road centerline or road boundary line is interrupted or duplicated at drawing boundaries, the documents become difficult to use as management materials for the entire route.

Also confirm how intersection areas are handled. Even if only the subject route is depicted, if the intersection corner chamfers or the management classification with connecting roads are unclear, the deliverable will be difficult to use in construction or development consultations. Check that no locations that should be included in the scope are missing, such as connecting roads, sidewalks, gutters, cross drains, and the areas immediately before and after bridges.

When checking the composition of deliverables, verify that editable data, view-only data, a list of drawings, related documents, survey results, site photographs, revision history, and management tables are all included. If only the drawings are delivered and supporting documents or revision history are managed separately, it becomes difficult later to confirm the meaning of lines or numerical values. When checking deliverables, it is important to confirm not only the contents of the drawings but the overall composition of the entire submission.

As Check 2, prevent mixing the latest version and the working version

The second check is to prevent mixing the latest version with working copies. Deliverables of the 2D maps attached to the road ledger tend to contain a mix of official versions, review versions, working versions, previous versions, and revised versions. If multiple similar files are included among the deliverables and it is unclear which one is the official product, there is a risk of referring to the wrong drawing in actual work.

In deliverable checks, we confirm whether the data that should be used as the official version is clearly identified. We check whether the file name includes the update year and month or the version status, whether the title block in the drawing records the creation date and the update date, and whether the management table corresponds to the file name. Because it can sometimes be impossible to determine this from the file name alone, it is important to cross-check the information in the drawing with the delivery list.

This does not mean that past versions are unnecessary. Past versions can be useful for checking the history of changes to road areas, centerlines, road widths, and the positions of structures. However, past versions must be managed separately from the official versions. If past versions are mixed in the same hierarchy as the official versions, there is a risk that someone taking over will use an outdated drawing.

When working drafts or review data are included in deliverables, confirm that they are clearly distinguished from the official deliverable. Work-in-progress data may contain unverified lines, provisional annotations, reference displays, or structures prior to correction. If these are treated as the official version, errors can be introduced into road management information. In deliverable checks, identifying the latest version and clarifying version control are essential.

As Check 3, confirm the road boundary line and the current road edge

The third check is to confirm the road boundary line and the existing road edge. The road boundary line is an important line that indicates the extent managed as a road. The existing road edge corresponds to the edge of the road visible on site, such as the pavement edge, gutter edge, curb, retaining wall, or slope toe. The two may coincide, but they are not always the same.

In deliverables, confirm that road boundary lines are represented by distinct line types or layers. If they are represented the same way as pavement edges, gutter edges, boundary-related lines, or reference lines, users may misinterpret them. Road boundary lines indicate the administrative scope and have a different meaning from lines that denote the actual pavement extent or the edges of structures on site.

We also verify the basis for the road boundary lines. We check whether it is possible to trace which materials—land acquisition documents, documents relating to the road area, boundary records, as-built drawings, on-site survey results, etc.—were used to create the boundary lines. Boundary lines whose basis is unclear may look tidy on drawings but become difficult to explain during boundary confirmation or occupancy consultations.

For existing road edges as well, confirm which line indicates the pavement edge, which line indicates the gutter edge, and which line indicates the structure edge. In the case of a gutter, whether it is the inner side or the outer side changes the meaning of the location, and in the case of a curb, whether it is on the roadway side or the sidewalk side changes the meaning. If the deliverables include survey results, also verify that the meanings of the measured points correspond to the lines on the drawings.

For Check 4, verify the road centerline, the start and end points, and the length

The fourth check is to confirm the road centerline, the starting point, the end point, and the length. The road centerline is information that serves as the axis for route management. Because it serves as the reference for organizing length, survey stations, construction sections, inspection points, and the locations of structures, it is necessary to confirm in the deliverables that the centerline is correctly organized.

First, check whether the centerline is continuous for the subject route. Verify that it is not interrupted along the way, that it does not bend unnaturally at intersections, and that it connects to adjacent drawings at drawing boundaries. The centerline is not a simple geometric centerline of the roadway area. In cases of widening on one side, a sidewalk on one side, at intersections, or on bridges, the visually apparent center and the administratively defined centerline may differ.

Indicating the start and end points is also important. Confirm where the start and end points shown in the ledger records are indicated on the drawings. Whether they are at the intersection center, the road area boundary, the management boundary, or the end of a bridge affects how the centerline extension is treated. Deliverables with ambiguous start and end points make it difficult to reconcile with the ledger records and to explain the scope of the work.

Regarding lengths, confirm whether the centerline length and the length in the ledger records are consistent. If there are discrepancies, it is necessary to check how the centerline was defined, the positions of the start and end points, how curves and intersections are handled, and the timing of updates. Because the centerline may have been corrected while the length and attribute information remain outdated, review the drawings and ledger information together.

Check 5: Verify the consistency between the width display and the ledger records

The fifth check is the consistency between the width indication and the registry records. Width is information often referred to in road management, construction design, occupancy consultations, development consultations, and confirmation of road access. However, road zone width, effective width, carriageway width, and pavement width are not the same. When checking deliverables, it is necessary to confirm what the width indication on the accompanying figure represents.

If the width recorded in the road ledger register corresponds to the road area width, verify consistency with the road area lines on the attached map. It is also important to confirm whether the pavement width or effective carriageway width identified by the field survey has been recorded directly as the ledger width. When the measured survey values differ from those in the ledger register, it does not necessarily mean that either is incorrect. The types of width being measured may be different.

Also confirm the section to which the road width applies. A road does not have the same width throughout; the width changes at intersections, on bridges, in sections with sidewalks, at narrow portions, and in sections where the road has been improved. If it is not clear which section the width annotation on the deliverables refers to, users may apply the values to the wrong section.

We also check the placement of width annotations. We verify that the text does not overlap lines, that annotations are not positioned too far from their corresponding segments, and that multiple width values are not mixed together. When displaying both the official width and the reference width, it is necessary to distinguish which is the registry information and which is the on-site verification information.

Check 6: Confirm how structures and attachments are represented

The sixth check concerns how structures and road appurtenances are reflected. The 2D road ledger attachment map may show side drains, catch basins, cross drains, bridges, retaining walls, slopes, guardrails, signs, lighting, sidewalks, curbs, and other items. Because these relate to road management, construction planning, and maintenance and repair, it is necessary to check for omissions in the deliverables and for the persistence of outdated information.

First, verify that the objects to be displayed match the requested conditions. It is not always necessary to show every structure in detail, but if primary assets under management are missing it becomes difficult to use in practice. Side ditches, manholes, bridges, and retaining walls are also related to road areas, widths, and drainage plans, so cross-check them with the site and related documents.

Verify whether the locations of structures are consistent with the as-built drawings, field survey results, and site photographs. Deliverables based on old attached drawings may still show side gutters that have already been removed or old manholes. Conversely, structures newly installed on site may not be reflected. It is important to confirm the extent to which current conditions are reflected.

We also check the meaning of points and lines that indicate structures. Whether they refer to the inside or the outside of a side ditch, the center or the outer edge of a manhole, the face or the top of a retaining wall, the end of a bridge or the boundary of the approach road changes the meaning of the positions on the drawing. If the deliverables include survey points, confirm whether there is an explanation of the measurement targets.

Check 7: Verify the coordinate system, scale, and positional accuracy

The seventh check is the coordinate system, scale, and positional accuracy. The deliverables of the two-dimensional map attached to the road ledger may be used by overlaying them with field survey results, as-built drawings, boundary documents, and background maps. Therefore, it is important to confirm which coordinate system they were created in and what scale and accuracy are assumed.

With respect to coordinate systems, check whether the coordinate system assumed by the deliverables is clearly specified, such as the plane rectangular coordinate system, latitude/longitude, local coordinates, or coordinates unique to the drawing. Data with an unknown coordinate system can cause positional discrepancies when overlaid with field survey results. If existing materials originate from paper drawings or scanned drawings, also confirm that there are limitations to coordinate accuracy.

Regarding scale, verify that the notation in the drawing border and title block is consistent with the scale of the actual data. For materials created by scanning paper drawings, paper expansion or contraction, distortions during scanning, and line thickness have an impact. Even if the deliverable has been digitized, it cannot achieve accuracy greater than that of the original source material.

When field survey results are reflected, verify the extent to which they are reflected. If only certain sections are based on high-precision survey results while the surrounding areas are derived from existing drawings, the entire drawing cannot be treated as having the same precision. If there are areas with different precision, check whether this is indicated in notes or in the management table.

Check 8: Verify consistency of line types, layers, and the legend

The eighth check is the standardization of line types, layers, and the legend. In 2D road register attached drawings, many lines are displayed, such as road boundary lines, road centerlines, existing road edges, pavement edges, gutter edges, boundary-related lines, structure lines, and reference lines. If these are not organized, people reading the drawings will misinterpret the meaning of the lines.

In the deliverables, verify that the road boundary line and the centerline are clearly distinguished. The road boundary line is the line indicating the extent of management, and the centerline is the axis for route management. They need to be represented separately from existing on-site features such as the pavement edge and the gutter edge. It is desirable that the meaning of each line can be understood from the layer names or the legend.

Check whether layer names are set so they are understandable to the person who will update them later. If abbreviations or working names that only the creator understands remain, they will cause confusion during handover. Verify that the layers are organized by role, such as road boundary lines, centerlines, existing site features, structures, annotations, and reference information.

Whether the legend matches the drawing display is also important. If a line type shown in the legend is not used in the drawing, if a line type used in the drawing is not included in the legend, or if the same line type is used to convey multiple meanings, the reliability of the deliverable is diminished. For deliverables consisting of multiple drawings, also check that line types and legends do not change from drawing to drawing.

Check 9: Verify reference materials and revision history

The ninth check concerns the supporting documents and the revision history. A two-dimensional road ledger map will be difficult to use in practice if it is delivered with only lines and numbers and its supporting basis is not clear. In deliverable checks, verify which documents the road boundary lines, centerlines, widths, and structure locations are based on.

Supporting documents include the road register, ledger survey records, existing appended maps, as-built drawings, land maps, boundary documents, survey results, site photographs, and structure documents. We check whether the deliverables are in a state that allows them to be traced back to these documents. Having a list of supporting documents or a management table makes later verification easier.

It is desirable that the revision history records the creation year/month, update year/month, affected route, affected section, update contents, materials used, whether on-site verification was performed, and any pending items. Distinguishing and recording whether the road area boundary lines were updated, only the existing road edge was updated, the centerline was corrected, or structures were added will be helpful for the next update.

We also verify information that was not incorporated and any unconfirmed items. For example, if a discrepancy was found on site but was put on hold because supporting documentation for the road boundary line was insufficient, and that decision was not recorded, the successor will end up repeating the same check. In the deliverable check, we look not only at the updated information but also at how information on hold is organized.

Check 10: Confirm the delivery format and future updatability

The tenth item to check is the delivery format and its future updatability. Two-dimensional road ledger drawings are documents that will continue to be updated after delivery in response to road improvements and field verifications. You need to confirm not only that the deliverables are easy to read but also that they are in a format that can accommodate future updates.

For the delivery format, we check whether viewing data, editable data, print-ready data, management tables, attribute information, survey results, site photographs, and a list of supporting documents are provided in accordance with the request conditions. It can be difficult to perform updates with viewing data alone. For projects that require editable data, we also confirm whether layers and attributes are organized.

For future maintainability, we will check whether the official version, the working version, and past versions can be managed separately. If it is not clear which data should be used as the reference when updating, there is a risk of modifying an old drawing. If the file structure, drawing numbers, revision history, and management table are organized, future updates and handovers will be easier.

We also evaluate the reusability of the data. We check whether it is possible to extract only the road boundary lines, whether centerlines can be linked to route attributes, whether structure locations can be connected with management ledgers, and whether field survey results can be used for the next update. If deliverables can only be handled as mere images or a single drawing, they may be unsuitable for future updates.

Delivery format and updatability are items that are unlikely to cause problems immediately after receiving the deliverables, but they can make a significant difference at the time of the next update. During the deliverables check, it is important to confirm whether the data will be usable in the long term.

Practical Workflow for Efficiently Reviewing Deliverables

To conduct deliverable checks efficiently, first review the overall composition of the deliverables, then proceed in the order of drawing contents, ledger reconciliation, on-site reconciliation, and data structure. If you jump straight into the details of the drawings, confirmation of the scope and the finalized version may be delayed, which can lead to unnecessary checks.

First, check the list of deliverables to confirm that the target routes, drawing numbers, data formats, and related documents are all present. Next, identify the data to be used as the official version. Then, verify the road boundary lines, centerlines, widths, structures, notes, coordinate system, and legend. Finally, check for consistency with ledger records, supporting documents, field survey results, and the update history.

It is important to record the inspection results. If you organize items with no issues, items requiring correction, and items to be put on hold, it will make it easier to confirm with the creator and to compare upon resubmission. In particular, items that affect practical judgment—such as road boundary lines, road widths, and centerlines—should have the reasons for correction and supporting documentation clearly stated.

Deliverable checks may not be completed in a single pass. Anticipating a recheck after revisions and preserving the initial inspection findings can reduce the effort of repeatedly checking the same items. It is important to treat deliverable checks not merely as an acceptance procedure but as a process of preparing documentation that can be used for future road management.

Summary

When checking deliverables of 2D road ledger attached maps, it is important to comprehensively verify not only the appearance of the drawings but also the scope, latest version, road boundary lines, centerlines, widths, structures, coordinate system, line types, supporting documents, revision history, and delivery format. Because these deliverables are used after delivery for road management, construction design, occupancy consultations, development consultations, boundary confirmation, maintenance, and repair, identifying inconsistencies during the checking stage reduces rework later.

First, confirm the scope and the composition of the drawings. Check that the subject route, start point, end point, intersection sections, drawing numbers, and related documents match the request conditions. Next, verify that the latest version and working versions are not mixed, and clarify which deliverable should be used as the official version.

Confirmation of the road boundary line and the existing road edge is also indispensable. Because the road boundary line is not necessarily the same as the pavement edge or the gutter edge, confirm the meaning and basis of the line. For the road centerline, the start and end points, and the extension, check that they are consistent with the ledger records and not interrupted at the drawing boundaries.

For width indications, verify that road area width, effective width, carriageway width, and pavement width are not being confused, and confirm which segment each width value corresponds to. For structures and appurtenances, check whether gutters, manholes, bridges, retaining walls, guardrails, signs, and the like are consistent with on-site conditions and related documents.

Coordinate systems, scale, and positional accuracy are also important. When overlaying on-site survey results and related materials, if the coordinate system, control points, and the meaning of measurement points are not clarified, positional discrepancies will occur. For line types, layers, and legends, verify whether road boundary lines, centerlines, existing site features, and reference information can be distinguished.

If supporting documents and update histories are organized, future updates and handling of inquiries will be easier. Regarding delivery formats, confirm whether editable data, management spreadsheets, and attribute information are needed in addition to view-only files, and determine whether the configuration can withstand future updates.

To make deliverable checks of two-dimensional road ledger maps more reliable, it is effective to keep the position information acquired on-site in a state that can be compared with the lines and points in the deliverables. LRTK, a GNSS high-precision positioning device that can be attached to and used with an iPhone, is a suitable option for confirming on-site points related to side ditches, manholes, boundary markers, road edges, centerlines, points of width change, and structure locations, and recording them as high-accuracy position information. If you want to verify discrepancies between the drawings and the field during deliverable checks and look ahead to post-delivery updates and integration with management ledgers, considering the use of LRTK can more easily lead to improved quality of two-dimensional road ledger maps and greater efficiency in road management operations.