7 Checks to Improve the Data Accuracy of 2D Road Ledger Maps

Two-dimensional supplementary maps of the road register are important drawings that organize, in plan view, the road’s area, width, length, boundaries, structures, occupancy items, surrounding topography, and so on, and are used as fundamental reference materials for road management. Because the road register itself is involved in many tasks—administrative management, maintenance and repair, occupancy consultations, road improvements, disaster response, explanations to residents, design review, and more—if the data accuracy of the supplementary maps is low, it can easily lead to rework during on-site verification and to incorrect judgments.

Especially when updates are made repeatedly based on paper drawings or older electronic drawings, even if they look tidy, small problems can accumulate over time—coordinate shifts, scale inconsistencies, mixed line types, missing attribute information, and discrepancies with current conditions. To be able to trust and use 2D road ledger attached drawings in practice, it is important not simply to draw the drawings neatly but to make clear which information was checked, by what standards, and to what extent.

In this article, we outline seven perspectives that practitioners should check to improve the data accuracy of two-dimensional maps attached to road ledgers. We explain them so they can be applied to new creation, digitization, updates, acceptance inspection of outsourced deliverables, and review of existing ledgers.

Table of Contents

• Confirm the alignment between the reference coordinates and the drawing positions

• Confirm the basis for the road areas and boundary lines

• Confirm the numerical consistency of width, length, area, and other values

• Confirm discrepancies between existing site features and the drawing representations

• Confirm the consistency of layers, line types, symbols, and annotations

• Confirm the linkage between attribute information and geometric data

• Confirm the update history and inspection records

• Improving the accuracy of two-dimensional road register attached maps requires balancing field verification and data management

• Summary

Confirm consistency between reference coordinates and drawing positions

When improving the data accuracy of 2D road ledger maps, the first thing to confirm is the alignment between the reference coordinates and the drawing position. Because road ledger maps are often used by overlaying them with map information, survey results, field investigation findings, and design drawings, it is extremely important to ensure that the entire drawing’s position is based on the correct reference.

In old road ledger maps, there may remain drawings that are merely scans of paper plans, ones drawn in arbitrary coordinates, or those created based on past surveying standards. Such drawings may appear fine on their own, but when overlaid with other map data or the latest survey data, the road centerline, boundary lines, intersection locations, and positions of structures can be displaced. Even discrepancies on the order of tens of centimeters (several to a few dozen inches) can become a major problem when confirming boundaries or checking road widths.

The first step in verification is to determine which coordinate system, geodetic datum, scale, and units the drawing was created in. Even if the drawing file contains coordinate information, that does not necessarily mean it aligns with the actual on-site coordinates. This is because the drawing’s origin may have been set arbitrarily, it may contain distortions originating from paper drawings, or past conversion work may have introduced rotations or scaling.

Specifically, select multiple easily identifiable points—known points, road intersections, bridge ends, manholes, road boundary markers, public control points, etc.—and compare the positions on the drawings with positions from field surveys or reliable base maps. If you align using only a single point, you will only detect translational errors. Use two or more points to check for rotation and scale discrepancies, and, if possible, examine error trends in both the longitudinal and transverse directions of the road.

It is also important to distinguish whether the entire drawing is uniformly displaced or only certain sections are shifted. If the displacement is uniform, it may be possible to correct it as a coordinate transformation or alignment issue; however, if only certain sections are shifted, possible causes include having pasted a different drawing during a past update, partial manual edits, or insufficiently reflecting the current conditions after road improvements. If you apply a blanket correction without separating the causes, you risk inadvertently moving areas that were actually correct.

When vectorizing using a scanned drawing as the background, it is also necessary to check for errors caused by paper expansion or contraction, skew during scanning, and insufficient resolution. Paper drawings can subtly deform depending on storage conditions and printing settings. If there is a drawing frame, grid lines, or coordinate grid, verify that they are at uniform intervals; if partial distortion is present, consider not only simple scaling but also section-by-section correction or redrawing.

Verification of reference coordinates affects all subsequent processes. No matter how carefully you enter road area lines, widths, lengths, occupancies, appurtenances, and management boundaries, if the overall position of the drawing is offset, reliability in linking with other data and in field verification will be reduced. In accuracy checks of 2D road ledger-attached drawings, the basic practice is to first confirm not the visual appearance of the drawing but whether it is located in the correct place in terms of coordinates.

Verify the basis for road zones and boundary lines

One of the most important pieces of information on a two-dimensional road ledger map is the road area and its boundary lines. The road area is fundamental information indicating the extent managed by the road administrator, and it is directly linked to many practical decisions such as occupancy permits, boundary negotiations, road improvements, maintenance and repairs, and clarifying relationships with adjacent private land. Therefore, it is insufficient for a boundary line to be merely drawn on the map; it is necessary to confirm on what basis that line was created.

On maps attached to the road ledger, road boundary lines, road area lines, public–private boundaries, parcel boundaries, structure locations, and the existing road edge tend to be easily confused. In particular, on older drawings line types may not have been clearly distinguished, annotations may be insufficient, and past persons in charge may have treated the existing line as if it were a boundary. Because lines that look the same can have different legal or administrative meanings, clarifying what each line signifies is the first step toward improving accuracy.

What should be checked are the source documents for the boundary lines. Organize which documents you used as the basis for inputting the lines, such as land survey results, boundary determination maps, road area determination documents, as-built drawings for road improvement works, past road ledger records, cadastral survey results, cadastral maps, land registration–related documents, and measurement results of on-site boundary markers. If you treat lines with a clear documentary basis the same as lines inferred from current conditions, problems may arise later during boundary negotiations or when explaining to residents.

Also, attention must be paid to discrepancies between the road area boundary line and the actual road edge. On site, the edge of pavement, the outer edge of a gutter, retaining walls, slopes, curbs, and so on may appear to be the road edge, but these are not necessarily the boundary of the road area. The road area may lie outside such structures, or the boundary may lie inside them. To improve the accuracy of two-dimensional road registry maps, it is important not only to verify on-site features but also to distinguish and record the line representing the management area from the lines that are visible on site.

When checking boundary lines, it is effective to focus on intersections, road curvature sections, connections with bridges and waterways, interfaces with private property, sections with a history of widening, and sections where old and new roads coexist. These locations tend to have complicated lines due to past construction or changes in land use, and they are also places where errors are likely to occur when updating drawings. If you only check straight sections and conclude there are no problems, you may overlook important points of change.

Furthermore, the continuity of boundary lines is also important. Verify whether the road area boundary lines are not interrupted midway, whether they are correctly connected at intersections, and whether they are consistent with adjacent map sheets or the appendices of adjacent routes. Even if each drawing is well arranged on its own, when overlaid with neighboring drawings the boundary lines may be offset by tens of centimeters (tens of in), lines may overlap, or road areas may be unnaturally missing. Because road ledger appendices are used for the entire route, consistency is required not only in the completeness of each drawing but also as continuous management documentation.

Clearly documenting the basis for boundary lines is also useful for future updates. Even if the person in charge changes later, knowing which lines are based on definitive sources and which lines are provisional current-condition inputs makes it easier to determine priorities for rechecking and corrections. The accuracy of two-dimensional road ledger attached maps is greatly improved not only by drawing lines in detail, but by ensuring that the meaning and basis of each line can be explained.

Confirm numerical consistency of widths, lengths, areas, etc.

In 2D road ledger maps, it is important not only to depict the shape of the road as a drawing but also to ensure consistency with numerical values such as width, length, and area recorded in the road ledger records and management documents. If the shape on the drawing does not match the figures in the ledger, it becomes difficult to determine which should be treated as correct in situations such as road management, occupancy, repair planning, asset management, and explanations to residents.

In particular, road width is an item that should be checked carefully for accuracy in 2-dimensional road ledger attachment drawings. There are different ways of defining road width depending on the purpose, such as overall width, carriageway width, sidewalk width, shoulder width, and effective width. If it is unclear what the width shown on the drawing represents, misunderstandings can arise during on-site verification or design review. For example, the numerical value will differ depending on whether the width includes the gutter, is measured from pavement edge to pavement edge, or is the width of the entire road area.

When checking road width, confirm whether measurements are taken perpendicular to the road centerline, whether the measurement locations at curves and intersections are appropriate, and whether points where the width changes are correctly reflected. Even if there are no problems in straight sections, in curved sections or tapering areas a simple distance measurement on the drawing may not correspond to the width used in actual road management. Also, in sections where widening work or sidewalk improvements were carried out in the past, only the ledger values may have been updated while the attached drawing shapes remain outdated.

Regarding length, it is also necessary to confirm how the road centerline is defined. Road length is often managed as the centerline length from the route's starting point to its end point, but if the centerline on the drawing does not pass through the center of the roadway area, or if the treatment of intersections is unclear, measurement results will differ. When line segments are finely divided or curves are represented as polylines, the measured length can change depending on the measurement method, so caution is required.

For area consistency checks, the closed state of road-area polygons is important. When a road area is represented only by lines, the area must be created as a closed shape in order to calculate the area accurately. Slight gaps, overlaps, or self-intersections can cause the area calculation to be incorrect. Even if it appears closed visually, endpoints can be separated when zoomed in, so verify that the geometry is closed.

When checking numerical consistency, compare the values automatically measured from the drawings with the values recorded in the ledger records. However, rather than immediately judging a mismatch as an error, it is important to check rounding procedures, measurement standards, the time when past materials were created, and differences in the interpretation of road boundaries. Older ledgers may be based on approximate surveys or measurements taken from paper drawings, which can lead to differences from values calculated from the latest electronic data. To determine whether such differences are within an acceptable range or significant enough to require updating the ledger, verification criteria should be established in advance.

Also, the consistency between annotations on the drawing and the attribute data must not be overlooked. Even if the width is written as text on the drawing, a different value may be registered in the attribute information. When paper drawings are digitized, only the annotations may remain and the graphical attributes may not have been updated. In practice, it is desirable to cross-check the drawing display, attribute information, ledger records, and actual on-site measurements, and to record the cause and the adopted value if there are discrepancies.

Numeric values such as width, length, and area are clear indicators of the reliability of road ledger attached maps. By not only improving the appearance of the drawings but also keeping them in a state that allows numerical explanation, two-dimensional road ledger attached maps become easier to use as management documents.

Check for discrepancies between existing site features and their representation on drawings

To improve the data accuracy of two-dimensional road ledger maps, it is necessary to verify how well the information on the drawings matches the current field features. Roads change over time. Pavement repairs, side ditch rehabilitation, sidewalk improvements, intersection upgrades, slope reinforcement, drainage facility renewal, installation of signs and guardrails, and relocation of encroachments—small changes like these accumulate, causing old attached maps to gradually diverge from conditions on the ground.

In verifying current conditions, it is important not only to look at the road boundary lines but to comprehensively examine the features that make up the road. Pavement edges, sidewalk–carriageway boundaries, gutters, catch basins, curbs, retaining walls, slopes, bridges, transverse culverts, road lighting, guardrails, signs, pavement markings, driveways, and sidewalk curb depressions are all pieces of information frequently referenced in road management. Check to what extent these are depicted on the attached drawings, whether their positions match the current conditions, and whether any obsolete features remain.

There are several types of discrepancies between existing field features and their representation on drawings. One is positional discrepancy. For example, a gutter line may be drawn inside the roadway compared with its actual location, the edge of a sidewalk may be shown wider than it really is, or the shape of a corner cut at an intersection may remain outdated. Another is an existence discrepancy: a new guardrail may be installed on site but not shown on the drawing, or conversely a structure that has been removed may still appear on the drawing. Furthermore, there are shape discrepancies. The extents of slopes and retaining walls, the transitions before and after bridges, and the blending in road-widening areas sometimes cannot be fully represented by simple straight lines.

During field verification, it is more efficient to focus on locations where changes are likely to occur than to inspect all routes at the same density. Intersections, areas around schools and public facilities, sections with sidewalks already installed, sections adjacent to rivers and waterways, slope sections in mountainous areas, sections with past construction history, and sections with many complaints or inquiries are places where discrepancies between drawings and actual conditions are likely to occur. If maintenance and repair records or as-built drawings are available, cross-checking them can reduce omissions in verification.

Methods for on-site verification also affect accuracy. Site photos alone can make positional relationships hard to understand, and if the photo’s shooting direction and location are not recorded, it can be easy to get confused when later reflecting them in drawings. For features confirmed on site, recording the location information, shooting direction, date of confirmation, confirmer, and the feature’s condition together makes them easier to use as the basis for drawing revisions. If observations made in the field are left only as paper notes, you may not be able to identify the location after returning to the office, so it is effective to take measures to leave records with location information.

Also, when the current conditions and the drawings differ, it is necessary to decide whether to immediately revise the drawings to match the current conditions. The map attached to the road ledger is not a current-condition map but a drawing that organizes information for road management. If changes in current features affect the road area or management information, updates are necessary, but entering temporary conditions during construction or temporary structures as permanent information can cause confusion. When you find discrepancies with the current conditions, it is important to confirm whether the change is permanent, a temporary condition during construction, or something that should be recorded as part of management.

Field verification is the task of validating drawing accuracy on site. No matter how well-organized the desk-based data is, if it does not match the actual site it becomes difficult to use in practice. To improve the quality of 2D road ledger attached maps, an operational procedure that regularly checks discrepancies with current on-site features and records the nature of those discrepancies and the decisions on corrections is indispensable.

Confirm standardization of layers, line types, symbols, and annotations

The data accuracy of 2D road ledger drawings is not determined solely by positions and numerical values. Whether layers, line types, symbols, and annotations are standardized also has a major impact on practical usability and reliability. If the same information is represented differently across drawings, checking takes longer and it can lead to misinterpretation or omissions during updates.

In maps attached to the road ledger, many pieces of information overlap: road-area boundary lines, road centerlines, property boundary lines, pavement edges, gutters, sidewalks, structures, encroachments, reference points, notes, dimension lines, and so on. To manage these appropriately, it is necessary to separate layers for each type of information and establish rules for line types, colors, widths, and symbols. Drawings created without such rules may have road-area boundary lines and existing-condition lines represented the same way, notes placed on the same layer as graphic elements, or unnecessary auxiliary drawing lines left behind.

The key point to check is whether the layer names match their contents. If a layer name indicates a road area but actually contains pavement edge lines, if boundary lines are mixed into a structure layer, or if old revision/correction layers remain, those conditions need to be corrected. For drawings produced by subcontractors or by multiple drafters, layer usage can differ by operator, so this is an item that should always be checked during deliverable acceptance.

Standardizing line types and symbols is also important. Road area boundary lines are of high administrative importance, so they must be represented in a way that can be clearly distinguished from other lines. If centerlines, boundary lines, structure lines, auxiliary lines, and dimension lines use similar representations, it becomes difficult to discern them when printing or viewing. Also, to make drawings practical to use, ensure representations do not rely solely on color so their meaning remains clear even when the drawings are printed in black and white.

Check the content, placement, orientation, size, and overlap of text in annotations. Annotations such as road width, route names, start and end points, lot numbers, names of structures, survey stations, and notes are important when reading drawings. However, if text overlaps map features, is too small relative to the scale, or is cut off across the map frame, it can cause misreading. In particular, annotations of road width should be placed so that the applicable section and the measurement location are clear.

Checking symbols and the legend is also essential. Confirm that the symbols used in the drawings match the legend, that the same symbol is not used with multiple meanings, and that no outdated symbols remain. Because roadside appurtenances and encroachments can be difficult to interpret from symbols alone, it is desirable to ensure they can be understood in conjunction with the legend and notes.

Also, consistency of information across drawing boundaries is important. If a side ditch is shown as a solid line on one drawing but as a dashed line on the adjacent drawing, it can cause confusion when reviewing the entire route. Even when working on individual drawings, you ultimately need to place adjacent drawings side by side and verify that the layer structure, line types, annotations, and symbol representations are continuous.

When layers and representation rules are well organized, later searching, extraction, updating, and display switching become easier. Tasks such as displaying only road areas, checking only structures, and extracting only update targets are streamlined. Conversely, drawings with inconsistent representation rules require human inspection for content verification, causing rework each time updates are made. To improve the accuracy of 2D road ledger attached maps, it is important to check not only their visual neatness but also whether they are organized as structured data.

Verify the linkage between attribute information and geometry data

To make practical use of two-dimensional road ledger maps, it is important that geometric data and attribute information are correctly linked. Road ledger maps are not merely collections of lines and text; their value as management documents increases when combined with information such as route name, route number, management classification, width, length, structure type, update date, source documents, and verification status.

If the linking between geometries and attributes is insufficient, information may appear to be present visually but become difficult to use for searching, aggregation, or update management. For example, even if the road width is written as text on a drawing, if it is not registered as an attribute of the road centerline or the road area polygon, it cannot be used to extract data by width or for segment-based management. Conversely, there are also cases where the attribute data contains the width while the annotation on the drawing remains outdated.

Points to check are whether the necessary attributes have been registered for each feature, whether attribute values are left blank or are still placeholder entries, and whether the correspondence between features and attributes is misaligned. Road centerlines may require route names, start and end points, length, and management classification. Road areas may require area, area type, supporting/reference documents, and update dates. Structures may be associated with type, location, manager, installation date, and inspection information. Which attributes should be assigned depends on the business purpose, but it is important to define the minimum required items and verify the input status.

When verifying the accuracy of attribute information, pay attention to inconsistencies in character representation. Even for the same route name, variations in notation can cause entries to be treated as separate data in searches and aggregations. If full-width and half-width characters, kanji and kana, abbreviations and official names, numeric notation, or the presence or absence of spaces are not standardized, it will create extra work when using the data later. If you plan to use road ledger maps over the long term, it is desirable to establish input rules for attribute values and bring them closer to a state where they can be checked mechanically.

When it comes to the relationship between geometry and attributes, it is also important not to assign too many meanings to a single geometry. For example, if a long road centerline is created as a single line, you cannot separate attributes when the width or management classification changes along the way. As a result, although conditions actually differ by segment, the whole is treated as having the same attributes. At locations where attributes change — such as width change points, boundaries of management sections, or boundaries of construction history — you need to appropriately split the geometry.

On the other hand, be careful not to over-segment. Shapes that are too fine-grained make management more complicated and can cause missed updates and duplication. The unit used to split shapes should match the unit you want to manage in practice. You need to design the shape structure after considering which unit you want to view information by—such as road ledger records, maintenance management sections, construction sections, or inspection sections.

Attribute information is linked with on-site inspections and update histories. When a structure is inspected in the field, if the inspection date and results are attached to the geometry, it becomes easier to determine which information is outdated at the next update. Conversely, if inspection records are dispersed across separate files or paper documents, it becomes difficult to judge whether the information on the drawings is up to date. To develop two-dimensional road ledger maps into highly accurate management data, it is ideal to handle geometries, attributes, supporting evidence, and update histories as an integrated whole as much as possible.

Linking attribute information with geometric data directly contributes to improving the efficiency of future road management. To smoothly carry out searches, aggregation, map display, report generation, field inspections, and update management, geometries must not only be drawn correctly but also have data attached that explains what those geometries represent. When improving the accuracy of two-dimensional road ledger maps, it is essential to verify both visible information and invisible attribute information.

Check the update history and inspection records

To continuously maintain the data accuracy of two-dimensional road ledger attached maps, it is essential to check the update history and inspection records. Road ledger attached maps are not documents that are completed once and for all; they are updated in response to road construction, repairs, boundary changes, installation of occupying objects, changes in current conditions, the addition of survey results, and other factors. If it is unclear when, who, what, and on what basis modifications were made, it becomes difficult to determine the reliability of the data.

In drawings that do not retain a revision history, old and new information tend to become mixed. For example, the road right-of-way lines may have been updated while width annotations remain outdated, structures may be new but centerlines still reflect the old road alignment, or site photos may be current but the date they were incorporated into the drawing is unknown. Such drawings may look neat at first glance, but they increase the amount of verification work required in practice.

The items that should be recorded in an update history are the update date, the section being updated, the content of the update, supporting/reference documents, the worker, the verifier, and the inspection results. It is not necessary to manage everything in a complicated way, but at minimum it is important to be able to trace which locations were changed and for what reasons. Whether the update reflects the as-built drawings from road improvement works, the results of field surveys, or corrections of errors in past drawings will change the meaning of the update.

Inspection records should document which aspects were checked after drafting the drawings. By defining check items such as coordinate alignment, boundary lines, widths, lengths, areas, existing site features, layers, annotations, attributes, and map-sheet/frame connections, variation in inspections can be reduced. If each person uses a different checking method, the same deliverable can vary in quality. Standardizing the check items makes it easier to evaluate outsourced deliverables and to conduct in-house verification.

Also, storing the pre-update data is important. If an error is found after a modification or if you need to check a past state, it becomes difficult to restore without the pre-update drawings. An operation that overwrites and saves only the latest version makes it impossible to track when and which information changed. Implementing version control and keeping the ability to review the differences before and after updates helps with detecting incorrect changes and preparing explanatory materials.

When checking update histories, we also examine how they correspond to construction histories and on-site inspection records. If road construction has been completed but the supplementary drawings have not been updated, discrepancies between the field and the register will widen. Conversely, if planning-stage drawings are mistakenly reflected in the register, road shapes that do not actually exist may be recorded. It is important to distinguish between information that has been confirmed as complete and information that is in planning or under construction.

Inspection records are not merely administrative procedures; they serve as the basis for explaining data accuracy. When residents or relevant agencies make inquiries, being able to show when the information was confirmed and which documents serve as the basis increases the reliability of the response. In road management operations, not only the drawings themselves but also the processes by which the drawings were created and verified are important information.

To maintain the accuracy of 2D road ledger attached maps over the long term, it is necessary to consider updates and inspections together. Updating is not the end; it is important to establish a process to verify the updates, record them, and carry them forward to the next update. If update histories and inspection records are properly maintained, it becomes easier to preserve drawing quality even when personnel change, and road ledger attached maps can continue to be used as reliable management documents.

Improving the Accuracy of 2D Road Ledger Attached Maps Requires Balancing Field Verification and Data Management

To enhance the data accuracy of 2D road ledger-attached maps, it is important to advance both on-site verification and data management in a balanced way. Even if accurate information is obtained on site, accuracy cannot be maintained if the way it is reflected in the drawings is inadequate. Conversely, even if data formats and layer structures are well organized, if reconciliation with current conditions is lacking, the materials will be difficult to use in practice.

Road ledger attached maps are materials that connect on-site road management with in-office administrative operations. In the field, boundary markers, side ditches, pavement edges, structures, changes in road width, encroachments, and surrounding terrain are checked. In the office, that information is organized as drawing data, ledger records, attribute information, and update history. If this connection does not work well, what was confirmed on site may not be reflected in the drawings, or information on the drawings may not be verifiable in the field.

For improved accuracy, it is important during on-site inspections to record information in a way that can be easily incorporated into drawings later. Having photos that show the inspection location, positioning results, notes, the type of feature inspected, the inspection date, and the inspector makes the office-side updating work go smoothly. This is especially effective when road sections are long or similar structures occur consecutively, since photos alone can make it difficult to pinpoint locations, so recording them together with location information is useful.

Also, rather than reflecting all on-site verification results uniformly, it is necessary to organize them according to their importance for management. Information that underpins the ledger—such as road areas and boundaries, road widths, and major structures—should be confirmed with high accuracy, while minor notes and reference information should be handled separately according to update frequency and intended use, making it easier to balance work efficiency and quality.

In recent years, it has become easier to utilize location information acquired on-site for updating drawings. Traditionally, the workflow often involved taking notes on paper drawings in the field and then re-editing the drawings at the office, which made it easy for mistakes to occur in identifying locations and transcribing information. Nowadays, keeping location-tagged records on-site and using that information to verify and update the two-dimensional maps attached to the road ledger has become a practical approach.

What is important in that process is not to overtrust the positional information obtained on-site, but to verify it against the standards and supporting documents of the road ledger map. Even if a point measured on site is accurate, if you do not distinguish whether it is a road boundary line, an existing structure, or a reference point, you may end up registering it as a line with an incorrect meaning. The accuracy of measuring position and the accuracy of judging the meaning of the information are separate things. By ensuring both, the quality of the road ledger map is improved.

Improving the accuracy of 2D road ledger map attachments is not something that can be completed with a single large-scale update. It is gradually improved through various opportunities such as day-to-day road management, reflecting the completion of construction, recording during field surveys, inspecting outsourced deliverables, and verifying information when responding to inquiries. For that, rules that ensure verification according to the same standards even when personnel change, and a system that reliably preserves on-site information, are necessary.

As a means to streamline on-site verification and make it easier to retain the basis for drawing updates, one method is to utilize high-precision field positioning devices such as LRTK (an iPhone-mounted GNSS high-precision positioning device). If confirmation points near road boundaries, locations of gutters and structures, measurement points for width verification, and positions where current-condition photos were taken can be recorded together with high-precision positional information, they become easier to use for decisions on updating 2D road ledger-attached maps and for accuracy verification. If you want to improve the data accuracy of road ledger-attached maps, it is effective to consider an operational approach that, in addition to desk-based drawing checks, acquires accurate positions in the field and links them to drawing management.

Summary

To improve the data accuracy of 2D road ledger attached maps, it is important not to check drawings based on appearance alone, but to comprehensively verify them from multiple perspectives: coordinates, boundaries, numerical values, current conditions, representation rules, attribute information, and update history. Road ledger attached maps are basic materials for road management and are referenced in many situations such as boundary consultations, width verification, maintenance and repair, construction planning, explanations to residents, and occupation management. Therefore, slight discrepancies or insufficient information can lead to significant rework in later operations.

First, it is fundamental to verify the consistency between the reference coordinates and the positions on the drawings, and to ensure they remain reliable when overlaid with other map data or survey results. Next, clarify which documents served as the basis for the lines representing road areas and boundary lines. Furthermore, check that numerical values such as width, length, and area are consistent with ledger records and drawing indications, and carefully review any discrepancies with the existing site features.

Furthermore, standardizing layers, line types, symbols, and annotations is essential to ensuring drawings remain easy to use over time. If attribute information and geometric data are correctly linked, searching, aggregating, and managing updates become easier. Keeping revision histories and inspection records allows past changes to be tracked and makes it easier to maintain quality even when personnel change.

Improving the accuracy of two-dimensional maps attached to the road ledger is not a one-off corrective task but the establishment of a continuous management system. By accurately recording information obtained from on-site inspections, organizing it as drawing data, and preserving the supporting evidence and history, the maps attached to the road ledger become reliable reference materials for practical use. In particular, if you want to streamline position verification in the field, leveraging high-precision positioning such as LRTK and linking on-site information with the two-dimensional maps attached to the road ledger makes it easier to achieve both accuracy and speed in update operations.