top of page

Table of Contents

Reasons why managing drawings attached to 2D road ledgers tends to be problematic

Method 1: Establish rules for managing current and past versions

Method 2: Create a system that allows searching by route name or drawing number

Method 3: Record the basis for creation and the update history

Method 4: Link drawings to ledger records and related documents

Method 5: Manage accuracy information such as coordinate systems and scale

Method 6: Reflect on-site verification results in drawing updates

Operational points for maintaining ongoing drawing management

Summary


Why it's difficult to manage drawings of 2D road ledger attached maps

Two-dimensional road ledger attached maps are important road management documents that organize, in plan view, the location of roads, road areas, centerlines, widths, lengths, intersection configurations, structures such as gutters and bridges, and the relationships with surrounding features. Because they are referenced in a variety of situations—roadworks, occupancy consultations, development consultations, boundary confirmations, maintenance and repairs, disaster recovery, ledger updates, and so on—not only the content of the drawings themselves but also how they are stored, searched for, updated, and shared becomes a major practical challenge.


The reason drawing management often becomes problematic is that the two-dimensional road ledger attached drawings are not documents that are finished once they are created. Roads change due to pavement repairs, side ditch rehabilitation, sidewalk improvements, intersection upgrades, road widening, relocation of encroachments, disaster recovery, and transfer of road ownership resulting from development activities. Each time, information that should be reflected in the attached drawings is generated. With each update the number of drawing files increases, and when past versions, working versions, review copies, and official versions coexist, it becomes unclear which one to use.


A particularly common problem is not knowing which version is the latest. If there are multiple drawings with similar names in a shared folder and they are managed only by date or the name of the person responsible, stakeholders can end up discussing while looking at different drawings. When one person is looking at the updated road boundary line but another is referring to the pre-update attachment, perceptions of width, boundaries, construction scope, and occupancy scope become misaligned.


Also, the fact that drawings are separated from related documents is problematic. Even when looking only at the map attached to the road ledger, you may not be able to determine which document the road boundary line is based on, whether the road width figures match those in the ledger survey records, whether as‑built drawings have been incorporated, or whether they are based on field survey results. If drawings exist but their basis cannot be traced, it becomes difficult to explain later.


Drawings are sometimes stored without information about their coordinate system, scale, or creation accuracy. When images that are simply scans of paper drawings, digital drawings with coordinates, drawings that reflect on-site survey results, and reference diagrams indicating approximate positions are stored together in the same place, users cannot judge the differences in accuracy among them. The more polished a drawing looks, the more likely people are to overestimate its actual positional accuracy.


Simply saving drawing files is not enough to avoid problems when managing 2D road ledger attached drawings. You need to consider managing the latest version, organizing files for easy searching, maintaining update histories, linking to supporting documents, recording accuracy information, and reflecting field verification results as an integrated whole.


This article explains six methods, aligned with the operation of road ledger attached drawings, to help practitioners avoid confusion in drawing management.


Method 1: Establish management rules for the latest and previous versions

The first thing to put in order when managing drawings for 2D road ledger attachment maps is the rules for handling the latest and past versions. The most dangerous situation in drawing management is not knowing which drawing is the official latest version. If an old drawing is referenced in road construction or occupancy consultations, judgments about road limits, road width, centerline, and structure locations will be misaligned, causing rework during on-site verification and stakeholder meetings.


To clearly identify the latest version, first distinguish among the official version, the working version, the review version, and the past version. The official version is the drawing used for operational decisions and consultations. The working version is a drawing that is being updated and should not yet be treated as finalized information. The review version is an interim drawing used for stakeholder review and requests for corrections. The past version is a drawing retained for record verification. If these are stored at the same level with similar names, misuse is likely to occur.


How drawings are named is also important. Using a name that makes the route name, drawing number, applicable section, creation year and month, and update status clear will make them easier to find. However, relying too much on the file name can lead to confusion later due to renaming or duplication. It is safer to also record the creation year and month, update year and month, version status, and details of updates in the title block and management table within the drawing.


It is also important to keep past versions. If you only retain the latest version and delete all older drawings, you will no longer be able to track how road right-of-way or widths have changed. Past versions become important reference materials when comparing before-and-after road improvements, tracing the history of boundary confirmations, or reviewing past discussions. However, because mixing past versions with the latest version can lead to misuse, you need to separate their storage locations and display methods.


We will establish rules for drawings that are being updated as well. Drawings provisionally revised after site verification, drawings currently being updated to reflect as-built drawings, and drawings awaiting confirmation from related departments are not official versions. When sharing drawings that are in progress, it is important to include a name or note that clearly indicates they are not yet official documents. If unverified lines are used for operational decisions, corrections will be required later.


When managing the latest version, it is also necessary to decide who will finalize the official version. If drawings individually revised by staff are treated as the latest version as-is, information that has not yet been approved may become mixed in. Establish a process to review updates and, after confirming consistency with ledger records and related materials, store them as the official version.


Two-dimensional maps attached to the road ledger are materials used by many personnel over long periods. When rules for the current and past versions are in place, stakeholders can discuss matters based on the same drawings. The first step to preventing problems in drawing management is to ensure that anyone can determine which drawing represents the current official information.


Method 2: Implement a system that allows searching by route name or drawing number

The second method is to set up a system that lets you quickly find the required drawing by route name or drawing number. Two-dimensional road ledger attachment maps become more complicated to manage as the number of target roads increases. If drawings are saved only under the district name, the responsible person's name, or the work date, it takes time to find the required drawing and there is a risk of opening the wrong drawing.


Maps attached to the road ledger are often organized by route unit, drawing number unit, district unit, or management-section unit. Which unit to use as the basis depends on the management method, but it is important to ensure that at least the route name, route number, drawing number, applicable section, and creation date are identifiable. If the drawing's storage location, file name, title block within the drawing, and the information in the management ledger match, searching and cross-referencing will be easier.


A frequent practical problem is when the same road is known by multiple names. If official route names, common names, district names, construction project names, and locally used names are mixed together, you may not be able to find the drawing you need even after searching. For drawing management, it’s convenient to center on the official route name and drawing number while also allowing searches by common names and related keywords as needed.


The rules for drawing numbers are also important. If drawing numbers are not standardized, it becomes difficult to understand the relationships with adjacent drawings or with different sections of the same route. Long routes may be divided into multiple drawings, requiring confirmation of the connections with adjacent drawings. If drawing numbers reflect the relationships between routes and sections, it becomes easier to check connection points and carry out updates.


Organizing where documents are stored must not be overlooked. Even when the road ledger maps, as-built drawings, field survey results, ledger records, and site photographs are stored in different locations, there needs to be a system that lets you trace from the route in question to the related materials. You may be able to find drawing files, but if you cannot locate the supporting documents, you will not be able to verify the meaning of the road boundary lines or the widths.


Also, when paper drawings remain, we map the paper storage number to the digital data management number. Historical road register maps and boundary records are sometimes kept on paper, and the background may not be clear from the digitized attachments alone. If paper and electronic records are managed separately, they cannot be cross-referenced when needed.


A system that makes searching easy does more than just reduce working hours. Being able to correctly find the necessary drawings also serves as risk management to avoid using incorrect materials. Two-dimensional road ledger attached maps are documents used for operationally important decisions such as road areas, boundaries, and widths. By creating a state where drawings can be found without hesitation by route name or drawing number, the stability of drawing management is greatly enhanced.


Method 3: Record the rationale for creation and the update history

The third method is to always retain the basis for creation and the update history. Two-dimensional road ledger maps are insufficient if they only have lines and numbers drawn on the drawing. It must be possible to later verify which sources the road boundary lines are based on, under what measurement conditions the widths were compiled, which start and end points the centerline is based on, and whether the locations of structures are based on field surveys or on as-built drawings.


Drawings whose basis for creation is no longer documented become difficult to explain, even if they look tidy. For example, when there is an inquiry about a road area line, if it is not clear whether it was based on a land map, on boundary records, or simply carried over from a past appendix map, it becomes difficult to use for practical decision-making. For information concerning boundaries and road areas, being able to trace the basis is extremely important.


The update history is the same. When a supplementary drawing is updated due to road widening, culvert renovation, intersection improvement, development attribution, disaster recovery, etc., record when, which section, and based on which documents it was revised. Without an update history, the next person responsible for using the drawings cannot determine how up-to-date the current drawings are.


It is useful to record in the revision history not only what was changed but also the reasons why something was not changed. For example, if the paved area on site has expanded but supporting documentation for a change in the road boundary cannot be confirmed, and therefore the boundary lines were left unchanged, recording that judgment prevents repeating the same verification later. Including in the management scope not only the information reflected on the drawings but also information that is under review or on hold is helpful in practice.


The basis for creation and update history can be managed solely by notes within the drawings, but when the amount of information increases the drawings become difficult to read. Therefore, it is practical to prepare a separate management table and organize the drawing number, route name, update date, update contents, supporting documents, verifier, and whether on-site verification was performed. Necessary information should be shown concisely on the drawing, with details available in the management table or related documents.


Also include relationships to previous versions in the history. Knowing from which version to which version an update was made makes it easier to track changes in road areas, road widths, and the locations of structures. In particular, when you need to explain past conditions for boundary verification or construction coordination, the revision history can be a great help.


2D road ledger maps are documents that continue to be used even when personnel change. If only the original creator understands them, they are not suitable for long-term road management. By recording the basis for their creation and the history of updates, you can preserve the reliability of the drawings and turn them into management documents that enable the next person in charge to make decisions without hesitation.


Method 4: Link to ledger records and related materials

The fourth method is to manage two-dimensional road ledger maps by linking them with ledger records and related documents. Road ledger maps can be used on their own, but ideally they should be read together with ledger records, as-built drawings, survey results, boundary documents, land acquisition documents, structure documents, occupancy documents, site photographs, and the like, which clarifies their practical significance.


The ledger records organize route names, starting points, ending points, length, width, road type, operational status, structure information, and other items. The centerlines, width markings, and road boundary lines on the supplementary map must be consistent with the information in the ledger records. If only the supplementary map is updated while the ledger remains with outdated information, multiple differing values or ranges will exist for the same road, causing confusion in practice.


Linking to the as‑built drawings is also important. When works such as road widening, side ditch repair, sidewalk construction, intersection improvements, or bridge repairs are carried out, those as‑built drawings serve as the basis for updating the supplementary drawings. If lines on the supplementary drawings were updated based on the as‑built drawings, it is necessary to keep them in a state that allows tracing which construction documents were reflected.


Linking boundary records and land acquisition records is indispensable when explaining road boundary lines. Road boundary lines do not necessarily coincide with the public-private boundary, the cadastral boundary, the pavement edge, or the gutter edge. Therefore, if the road boundary line can be traced back to the land maps and boundary documents that serve as its basis, it will be easier to explain during boundary confirmation and occupancy consultations.


Linking field survey results and photographs is also effective. When features confirmed on site—such as road edges, boundary markers, gutters, inspection chambers, retaining walls, and points where the road width changes—are incorporated into drawing updates, manage which locations those survey results and photographs correspond to. It is important to record not only the coordinates of points but also what each measured point represents and which photograph shows which on-site condition.


Even if related documents are stored in different locations, managing them using drawing numbers or route numbers as common keys makes it easier to find the necessary materials. By keeping them in a state where you can trace from supplementary drawings to ledger records, from ledger records to as‑built drawings, and from as‑built drawings to field survey results, checking road management information becomes smoother.


Two-dimensional road ledger attached drawings are not materials that are complete on their own. Only when linked with related materials do the meanings of the lines and numerical values become clear. To avoid problems in managing drawings, it is important to manage the attached drawings, ledger records, and supporting materials together as an integrated set.


Method 5: Manage accuracy information such as coordinate systems and scale

The fifth method is to manage accuracy information such as coordinate systems and scale. Even if a two-dimensional road ledger map looks well presented, if you do not know what level of positional accuracy the drawing has, you may misuse it in practical work. In particular, when overlaying it with on-site survey results or other spatial information, information on the coordinate system and scale is indispensable.


Paper and scanned drawings can be useful for visual checks, but they do not necessarily contain accurate coordinate information. Expansion and contraction of paper, distortions during scanning, image tilt, line thickness, and limitations of scale can cause positions on the drawing to differ from field survey results. Treating such drawings as high-precision positional information may lead to incorrect determinations of roadway areas or boundaries.


Even with digital drawings, you must exercise caution if the coordinate system is not clearly defined. If the plane rectangular coordinate system, latitude/longitude, local coordinates, proprietary drawing coordinates, etc. are mixed, positions will not align when overlaid with other materials. When combining road ledger maps, field survey results, construction drawings, documents related to parcel numbers, aerial photographs, and point cloud data, confirming the consistency of coordinate systems is important.


We also manage scale information. On small-scale drawings, road configurations may be simplified, and slight differences on the drawing can become large differences in the field. Even with large-scale drawings, depending on how they were produced and the accuracy of the source materials, they may be unsuitable for making judgments near boundaries. It is important to understand, for each drawing, what level of precision is appropriate for which uses.


In drawings where alignment has been performed, record which point was used as the reference and how consistent the alignment is across the entire drawing. When old paper drawings are digitized and coordinates are assigned, they may match near some control points but show large discrepancies in more distant areas. Leave notes on accuracy so that the entire drawing is not assumed to be accurate based on only a part of it.


Accuracy information is useful in practice when recorded in the drawing management table or as annotations within the drawing. If the coordinate system, scale, creation method, survey results used, whether position alignment was performed, and any accuracy-related cautions are known, users can judge how much they can rely on the drawing. It becomes easier to distinguish appropriate uses—for example, it may be suitable for rough checks of roads but an on-site survey is required for boundary determinations.


In managing drawings for 2D road ledger attached maps, it is important to manage not only whether drawings exist but also their accuracy. If accuracy information is organized, you can avoid over-relying on the attached maps and make judgments to combine on-site verification and surveying where necessary.


Method 6: Incorporate On-Site Verification Results into Drawing Updates

The sixth method is to put in place a workflow that ensures on-site verification results are reflected in drawing updates. Two-dimensional road ledger attached drawings are only useful for practical work if they match the actual road conditions on site. Even if discrepancies are identified in the field, if that information is not incorporated into drawing management, the next person responsible will again make decisions based on the outdated attached drawings.


During on-site verification, we check roadway boundaries, pavement edges, side ditches, curbs, retaining walls, slopes, boundary markers, points where the carriageway width changes, points related to the centerline, structures, and encroachments. We verify whether items shown on the attached drawings exist on-site and whether items present on-site are reflected on the attached drawings. In particular, after road improvements, after development handover, after disaster recovery, and after occupancy works, discrepancies between the drawings and the site are likely to occur.


The results of on-site checks are recorded together with photos, location information, measurements, the date of the check, the person who checked, and the details of the check. Photos alone can sometimes make it unclear which location is being shown. For measurement points, it is also necessary to record whether the point is outside the gutter, at the pavement edge, at a boundary marker, or at the center of a manhole. If the meaning of a point is unclear, it cannot be determined when reflecting it on the drawings.


If discrepancies are found, do not immediately revise the drawings; instead, verify them against the supporting documents. Even if the pavement edge on site has changed, the road area line has not necessarily been altered. Even if a side gutter has been relocated, it may have a meaning separate from the boundary line. When reflecting on-site verification results in the ledger update, it is necessary to determine which information—road area, boundaries, width, or structures—should be updated.


Once the decision to update has been made, update the drawings, ledgers and records, and related materials together. If you only correct the supplementary drawings while the records remain outdated, inconsistencies will arise. Even if you only update the records while the drawings remain outdated, incorrect supplementary drawings will be used on site. When reflecting the results of field verification, it is important to manage the supplementary drawings and ledger information together as a single, integrated set.


An approval workflow is also required to reflect on-site verification results. If drawings provisionally revised by workers are used as the official version, there is a risk of including unverified information. Separate the states of under review, under revision, and approved, and perform the necessary verification before storing them as the official version.


Management of 2D road ledger attached drawings is not completed by merely storing the drawings. Only when there is a process of verifying them on-site, recording discrepancies, confirming the supporting evidence, and reflecting them in formal updates do the attached drawings become management materials that reflect actual field conditions.


Operational points for continuing drawing management

To avoid problems managing drawings in a 2D road ledger, it is important to establish a system that can be operated continuously rather than organizing them only once. Because roads are constantly changing, drawing management should be designed on the assumption that it will require ongoing updates. Even if you organize them neatly at first, without rules for subsequent updates and sharing, the drawings will become mixed again after a few years.


For ongoing operations, it is important to clearly define the scope of responsibility for drawing management. Decide who will update drawings, who will confirm the official version, and who will verify consistency with related documents. If the responsible parties remain unclear, discrepancies found on site may not lead to updates of the drawings.


Also organize the timing for updates. Deciding in advance when to review the attached drawings—such as when road construction is completed, when occupancy works affect structures or the road edge, when a road is vested due to development, when boundary confirmations are carried out, or when disaster recovery is completed—makes it easier to prevent overlooking updates.


Sharing information with related departments is also important. Road ledger maps are used not only for road management but also for construction, occupancy, land acquisition, development consultations, disaster prevention, maintenance and repairs, and other operations. If each department holds separate documents, different information about the same road can remain. By sharing rules for drawing management and standardizing the location of the official version and the update procedures, you can reduce discrepancies in understanding.


It's helpful to prepare a standardized record format for capturing field checks and survey results. If you record the inspection date, inspector, location information, photos, the meaning of measurement points, the nature of any discrepancies, and update decisions in a consistent format, it will be easier to use later when updating drawings. If records vary by person, organizing them at the stage of reflecting them in the drawings will take time.


Also, trying to make all drawings high-precision at once creates a substantial burden. It is more realistic to improve management accuracy sequentially, starting with locations that have higher operational priority—such as planned construction sites, sections with many boundary verifications, sections with many occupancy consultations, sections where old drawings remain, and sections with high disaster risk.


Drawing management is not just a method of storage but the workflow itself. By continuously managing the latest versions, searchability, update history, related documents, accuracy information, and the incorporation of on-site verification results, 2D road ledger attached maps become road management materials that can be used over the long term.


Summary

To avoid problems managing drawings of 2D road ledger attached maps, it is important not only to save the drawings but to manage the latest version, searchability, supporting documents, update history, accuracy information, and field verification results together. Road ledger attached maps are practical documents that show the road area, centerline, width, length, structures, and relationships with surrounding features, and they are used in many situations such as road construction, occupancy consultations, development consultations, boundary confirmation, and maintenance and repairs. Therefore, insufficient drawing management can lead to misalignments of understanding among stakeholders and rework.


The first method is to establish rules for managing the latest and past versions. Distinguish between official, working, review, and past versions, and clarify which drawings can be used for current practical decision-making. To prevent accidentally using old drawings, it is important to organize file names, storage locations, the title block within drawings, and the management lists.


Next, we will create a system that allows searching by route name and drawing number. If the necessary supplementary drawings cannot be found quickly, there is a risk of referring to old drawings or drawings for different sections. Organizing route names, route numbers, drawing numbers, the applicable section, and the creation date, and aligning paper documents with digital materials will improve searchability.


The third point is to record the basis for creation and the update history. If road area boundary lines, widths, centerlines, and structure locations are kept in a state where you can trace what they were based on, it will be easier to explain later. In addition to recording what was updated, also record the reasons why something was checked but left unchanged, so you avoid repeating the same checks.


The fourth is to link it with ledger records and related materials. The two-dimensional road ledger attachment map is not a standalone document. By managing it in connection with ledger records, as-built drawings, boundary documents, land acquisition materials, survey results, structure documentation, occupancy records, and site photographs, the meaning of lines and values on the drawings becomes clear.


The fifth is to manage accuracy information such as coordinate systems and scales. The accuracy available differs between paper drawings, scanned drawings, and digital drawings with coordinates. If you record the coordinate system, scale, creation method, survey data used, whether alignment was performed, and any accuracy-related notes, you can avoid overreliance on the drawings.


The sixth point is to ensure that on-site inspection results are incorporated into drawing updates. Even if differences in road areas, side ditches, boundary markers, points of width change, and structure locations are confirmed on site, if they are not reflected in the supplementary drawings or ledger records, old information will be used in subsequent work. It is important to establish a workflow from on-site verification, recording, and evidence cross-checking through to formal updating.


To make the drawing management of 2D road ledger maps more practical, a system that links position information acquired in the field to drawing updates is indispensable. 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 on-site road areas, centerlines, width-change points, gutters, manholes, boundary markers, and structure locations and recording them as high-precision position information. If you want to avoid leaving drawing management as a storage-centered task and instead maintain the accuracy of road ledger maps by linking field verification and update management, considering the use of LRTK can make it easier to streamline drawing management and improve the quality 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