What is a 3D Road Ledger Attached Map? Creation Steps and 5 Checks to Avoid Failure

A three-dimensional road ledger attached map is a concept for organizing the road management information handled in road ledger attached maps by linking not only planimetric positions but also elevation information and three-dimensional current-condition information. By making it easier to grasp in three dimensions documents related to road areas, carriageway widths, and boundaries, as well as road structures, drainage facilities, sidewalks, slopes, level differences, and road appurtenances, it can potentially help improve the efficiency of maintenance management, construction planning, occupancy negotiations, disaster response, and renewal works.

However, a 3D road ledger map is not completed simply by creating point cloud data or a 3D model. Since it will be treated as a road ledger, it is necessary to organize the coordinate system, vertical datum, road area, management boundaries, current-condition accuracy, attribute information, and update rules. Even if it looks well organized, if the supporting documentation and update procedures are unclear, the result will tend to be difficult to use in practice, so caution is required.

Table of Contents

• What is a three-dimensional road register map?

• Why is three-dimensional mapping required?

• Differences from two-dimensional road register maps

• Information and prerequisites to organize before creating

• Steps for creating a three-dimensional road register map

• Check 1: Align the coordinate system and vertical datum

• Check 2: Clarify the road area and management boundaries

• Check 3: Confirm the accuracy and missing data of existing-condition data

• Check 4: Harmonize attribute information and drawing representation

• Check 5: Decide the delivery format with a view to update operations

• Conclusion: A three-dimensional road register map is not something you create and finish but a document to be used continuously

What is a 3D Road Ledger Attached Map?

A three-dimensional attached drawing for the road ledger is a document that organizes the drawing information accompanying the road ledger, including not only planimetric positions but also elevation information, to make it easier to use for road management. In general, a road ledger is a record that organizes the basic information of roads managed by road administrators, and it relates to confirming the road type, route, area, length, width, structure, encroachments, and road appurtenances.

Traditional road ledger maps have been used as planimetric materials to confirm information such as road location, road area, width, boundary information, intersections, bridges, side ditches, sidewalks, and road appurtenances. In contrast, three-dimensional road ledger maps make it easier, when needed, to handle road surface elevations, level differences at curbs and side ditches, slope angles of cut-and-fill slopes, and three-dimensional shapes around retaining walls and bridges.

In road management operations, it is necessary to accurately understand how far the road is within the scope of management, which facilities are located where, and how the shape has changed before and after updates. Although a certain level of management can be performed with only two-dimensional drawings, roads are in reality three-dimensional objects that have slopes, level differences, intersections, drainage directions, and height relationships among structures. For that reason, it can be difficult to judge from plan views alone, and situations arise that require on-site verification or cross-checking with other drawings.

Three-dimensional road register maps can be used as a mechanism to supplement parts that relied too heavily on on-site inspections with data. For example, the road’s cross slope and longitudinal slope, gutter heights, step differences between sidewalks and roadways, and the positional relationships of structures near the road area and private property boundaries can be organized together with data that include three-dimensional coordinates and attribute information. This makes preliminary checks before visiting the site, explanations among stakeholders, and consideration of future construction easier.

However, 3D road ledger maps are not intended to unconditionally replace statutory road ledgers or existing road ledger maps. Even if a clean three-dimensional display can be produced, its value as a practical reference diminishes if the road boundaries are unclear or if it is not consistent with existing ledgers. What is important is not showing the current conditions in three dimensions, but organizing them in a way that allows the information necessary for road management to be correctly interpreted.

Why Is Three-Dimensionalization Required?

One reason 3D road ledger maps are attracting attention is the increasing complexity of road management operations. Roads are not finished when newly built; they undergo continuous updates over the long term, such as repairs, improvements, occupancy, disaster response, traffic safety measures, barrier-free measures, and drainage improvements. Furthermore, many departments and organizations are involved with roads, and road managers, designers, contractors, surveyors, occupiers, and maintenance operators all need to refer to the same information.

In such cases, plan views alone can make it difficult to grasp heights and three-dimensional interferences. For example, when considering the location of a curb cut on a sidewalk, not only the planimetric position but also the level difference with the roadway, the slope, the direction of drainage, and the relationship to existing manholes and gutters are important. When managing slopes and retaining walls, structures that appear close on a plan may have very different actual relationships due to elevation differences. In locations where vertical relationships are complex, such as bridges, underpasses, grade-separated interchanges, and embankment sections, the benefits of 3D modeling become particularly evident.

Also, updating road ledger maps is also a burden. As drawings increase with each construction project and as-built drawings and survey results are stored separately, it takes time to grasp the latest status. When past drawings, current-condition surveys, as-built drawings, photos, and field notes are scattered, it becomes difficult to make decisions when personnel change. By organizing information as three-dimensional road ledger maps, it becomes easier to view the current condition, structure, attributes, and history in an integrated way.

It also helps with on-site explanations and consensus building. If you explain the road area, level differences, obstructions, and the work area using plan views alone, it may be understandable to those with technical expertise but does not necessarily ensure that all stakeholders share the same understanding. With three-dimensional documentation, the road shape and changes in elevation are easier to share intuitively, making it less likely that items will be overlooked or that misunderstandings will occur. In particular, when it comes to maintenance and renovation planning, clearly conveying the on-site situation helps prevent rework.

Differences from 2D Road Ledger Maps

The main difference between two-dimensional road ledger maps and three-dimensional road ledger maps is how positional information is handled. In two-dimensional drawings, the road centerline, road boundary lines, road width, and the positions of structures are represented in plan view. While effective for understanding the road’s shape and management extent, height/elevation, gradient, level differences, and vertical overlaps need to be supplemented by longitudinal profiles, cross sections, structural drawings, annotations, site photographs, and similar materials.

On the other hand, in three-dimensional road ledger maps, each object can be given height information. This allows the spatial relationships of the road surface, curbs, gutters, sidewalks, slopes, retaining walls, sign posts, lighting poles, bridge components, drainage inlets, and so on to be confirmed three-dimensionally, making them easier to understand in a form that is close to the actual site conditions. Even objects that appear overlapped on a plan view can be more easily recognized as separate structures by including height information.

However, making things 3D does not eliminate the need for 2D drawings. For verification as attachments to the road register, for printing, for explaining to stakeholders, and for cross-checking with existing materials, planar drawing representations remain important. In practice, it is important to distinguish the information that should be managed in 2D drawings from the information that should be checked with 3D data. It is easier to organize your approach if you consider 3D road register attachments not as a complete replacement for traditional drawings but as a way to augment existing register information and improve site understanding and ease of updating.

Furthermore, because 3D data contains more information, it becomes difficult to handle if managed improperly. Point clouds may be too large to open, attribute names may not be standardized, coordinate systems may be unknown and not align with other data, and it may be unclear which file is the latest when updates are made. Problems that were hard to notice in 2D drawings as long as visual consistency was maintained tend to surface in 3D as inconsistencies in coordinates, elevations, attributes, and file structure. Therefore, it is essential to be mindful of operations from the creation stage.

Information and Preconditions to Organize Before Creation

Before creating a 3D road ledger map, you need to clarify the purpose first. The level of detail required will vary depending on whether it is to be used for maintenance and management of the entire road network, for renewal of a specific route, to strengthen management of encroachments and appurtenances, or to support situational awareness and recovery planning during disasters. Producing highly detailed 3D data while the purpose remains unclear can result in outputs that are not referenced in actual practice.

Next, determine the scope. In the road register map, management targets cover a wide range, including the road area, road centerline, start and end points, intersections, bridges, tunnels, sidewalks, side ditches, slopes, and road appurtenances. By deciding in advance whether to 3D-model the entire route or only the sections scheduled for rehabilitation, and how far outside the road area to include for reference, you can appropriately manage the survey extent and the amount of data.

Reviewing existing materials is also important. Organize existing road registers, attached maps, as-built drawings, survey results, control point information, boundary confirmation documents, repair histories, occupancy information, site photographs, and other materials, and decide which information will be treated as reference documents. If old drawings differ from current conditions, do not simply adopt the current conditions alone; it is necessary to confirm how they should be handled from a road management perspective. In particular, information related to boundaries or zones should not be judged solely by on-site appearance; it is important to carefully verify consistency with management records.

Also, you should confirm the usage environment for the deliverables in advance. Decide on items such as the 3D data formats that can be handled within the agency or company, the lightweight nature of data intended for viewing, plan drawings for printing, methods for attribute searches, and the editing formats that future personnel responsible for updates can work with, so that you can avoid the failure of deliverables being unusable after delivery. Even if data are created in advanced formats, if only a limited number of people can view them, their usefulness as maps attached to the road ledger will be limited.

Procedure for Creating 3D Road Ledger Attached Maps

Creating 3D road ledger supplementary maps typically follows the sequence of defining objectives, collecting reference materials, field measurement, data processing, mapping, attribute organization, verification, and delivery. The first thing to do is to clarify the intended use of the deliverables and the required accuracy. Whether the maps will be used to confirm road boundaries, to manage the positions of appurtenances, or as baseline data for construction planning will affect the measurement density and the features to be mapped. Omitting this step can lead to producing excessive data or, conversely, lacking necessary information.

Next, collect existing materials and establish the prerequisites for on-site measurement. Review existing road ledger attached maps, plan views, longitudinal and cross-sectional drawings, as-built drawings, control point results, boundary documents, and repair histories, and identify the locations that should be prioritized for on-site verification. Sections where the road alignment is complex, intersections, areas immediately before and after bridges, locations where the road boundary is unclear, and places that have been previously modified are parts that are easily overlooked during on-site measurement.

Field measurements acquire the positions, elevations, and shapes of road surfaces and structures. Acquisition methods include point observations with surveying instruments, continuous measurements from vehicles or on foot, shape reconstruction from photographs, and laser scanning, among others. Regardless of which method is chosen, the important point is not just to capture the overall form of the site but to ensure that information required for the road ledger attached map—such as boundaries, centerlines, widths, structures, appurtenances, and drainage facilities—can be obtained at an accuracy that allows them to be interpreted.

After measurement, organize the acquired data and check for unnecessary points and areas with large errors. Vehicles, pedestrians, vegetation, temporary structures, shadows, and reflections can introduce points that differ from the actual site conditions. Point clouds and 3D data may look detailed at first glance, but if they are used to create drawings while still containing unwanted objects, they can lead to incorrect lines and surfaces. Verify the condition of each item—road surfaces, curbs, gutters, slopes, and structures—and perform additional surveying or corrections as needed.

After that, extract the elements required for the road ledger map from the three-dimensional data. Road centerlines, road boundary lines, carriageway widths, shoulders, sidewalks, gutters, drainage inlets, appurtenances, slopes, retaining walls, and so on are mapped in a form usable for management. At this stage, it is important not only to refine the appearance but also to link the items to attribute information. Assigning attributes such as the type of object, management number, installation location, date of update, source documents, and verification status makes it easier to search and update later.

Finally, we confirm the results and organize the delivery format. We overlay with existing ledgers, compare with on-site photos, verify coordinates and elevations, check drawing representations, and check for missing attribute information, then deliver in a format that the actual users can open. Three-dimensional road ledger drawings are not complete at the time of creation; they are materials that are updated later to match subsequent construction and repairs. Structuring them so they are easy to update at the time of delivery determines their long-term value.

Check 1: Align coordinate system and vertical datum

One of the most important checks for 3D road ledger maps is the coordinate system and vertical datum. In plan views it can be hard to notice a problem if things appear to overlap visually, but with 3D data, if the coordinate system or vertical datum is shifted, positions will not align when overlaid with other materials. When integrating the road ledger, survey results, construction completion drawings, and current measurement data, it is necessary to clarify which coordinate system to use and which vertical datum to apply to elevations.

Height information, in particular, requires careful attention. The elevation of the road surface, the top of curbs, the bottom of gutters, the shoulder and toe of slopes, and the top edges of structures are important for on-site decisions and design reviews. However, when provisional height references and official elevations are mixed, correct judgments cannot be made by looking at the numbers alone. Construction documents may use a temporary bench as the reference, while ledger management may need to conform to a different standard. Therefore, it is important to state the approach to height references within the deliverables so that data creators and users can work from the same assumptions.

Also, if the existing road ledger maps are old, they may not exactly match the current survey data. In such cases, instead of simply overwriting the drawings to match the new three-dimensional data, you need to confirm the cause of the discrepancy. The appropriate response depends on whether the road alignment was changed by past construction, the discrepancy is due to the creation accuracy of the existing drawings, or there is a coordinate transformation issue. If you apply corrections without identifying the cause, it may become difficult later to explain the boundaries or the scope of management.

In practice, it is effective to use control points and known points to verify the positions of field measurement data and to identify discrepancies with existing records using representative points. Treating intersections, the ends of structures, distinctive points on road centerlines, and clearly defined points near boundaries as check points makes it easier to assess overall consistency. In three-dimensional road ledger maps, only when both planimetric positions and elevations are correctly managed will the results be durable enough for future use.

Check 2: Clarify the road area and management boundary

A common mistake in 3D road ledger maps is confusing the actual on-site shape with the management boundary. In point clouds and 3D models, the road surface, gutters, curbs, structures on the private-land side, vegetation, fences, and so on appear continuous, so looking only at the on-site shape can give the impression that the road area is clear. However, the areas and boundaries for road management cannot necessarily be determined solely from the apparent positions of structures.

Road boundary lines, management boundaries, private land boundaries, locations of encroachments, and the extent of construction works each have different meanings. In some cases the area under management extends to the outside of the side ditch, and in other cases the position of a structure does not coincide with the boundary. On older roads there may also be discrepancies between the on-site structures and the areas shown in the records. When creating 3D road ledger attached maps, it is necessary to distinguish and clearly represent which lines indicate the road area, which lines indicate existing structures, and which lines are reference information.

When handling boundary information, review existing road ledgers, boundary verification documents, land acquisition records, past construction drawings, and similar materials, and organize the supporting evidence. If you treat lines obtained from field measurements as boundary lines as-is, you may later be unable to provide a management explanation. In particular, in locations where road widening, sidewalk improvements, slope repairs, or drainage renovations have been carried out, it is important to carefully confirm whether the existing on-site structures coincide with the management lines.

Also, creating 3D data makes it easier to grasp the vertical relationships within road areas. Under bridges, in underground passages, at grade-separated crossings, on top of retaining walls, and at the lower parts of slopes, it can be difficult to understand the scope of management from plan views alone. Using three-dimensional data makes it easier to check which facilities are located at which heights, but for that reason, if the definition of management targets is left ambiguous, confusion grows. It is important to manage boundary lines, structure lines, and reference lines separately and to present drawings in a way that users will not misunderstand.

Check 3: Verify the accuracy and missingness of current-condition data

The quality of three-dimensional road ledger maps is largely determined by the accuracy of the current-condition data. Dense point clouds and three-dimensional models can make the results look accurate, but that does not necessarily mean the information required for road ledger maps has been captured correctly. In locations with poor measurement conditions, where there are many obstacles, areas hidden by vegetation, where vehicles were parked, inside drainage facilities, or in places occluded by level differences, the necessary information may be missing.

When using it as an attachment to the road ledger, it is more important that the points required for management are captured than the overall appearance. For example, confirming road width requires the road edges and curb positions. Managing drainage facilities requires the locations and relative elevations of inlets, gutters, and culverts. To check the barrier-free condition of sidewalks, information on level differences and slopes is necessary. If these elements are missing, even three-dimensional data becomes difficult to use for practical decision-making.

For accuracy verification, it is important not only to check overlaps between measurement datasets but also to cross-check with points that can be clearly confirmed on site. Use points that are easy to re-identify later—control points, road studs, corners of structures, manhole centers, curb corners—to check for positional and elevation offsets. When multiple measurement methods are used, consider the error tendencies of each method. Data acquired while moving is suitable for gaining a broad overview, but supplemental measurements may be required to verify finer details. Photo-derived data is easily affected by visibility, and laser measurements are also influenced by reflection and occlusion.

If there are missing sections, it is important to manage them as verification statuses rather than hiding them from the deliverables. If unconfirmed sections, estimated sections, and on-site verified sections are presented in the same way, users may mistakenly treat them as confirmed information. In 3D road ledger maps, making it clear not only the accuracy of the information but also which parts have been verified and which are for reference helps prevent failures.

Check 4: Align attribute information and drawing representation

3D road register maps are not sufficient with shape data alone. For use in road management, it is necessary to assign attribute information to the objects. Attribute information refers to management information that cannot be determined from shape alone, such as facility type, management number, route name, installation location, length, width, material, installation year, update history, confirmation date, and reference documents. By organizing these items, the data becomes usable as a register rather than merely a three-dimensional display.

A common reason attribute information fails is that names and classifications are not standardized. If the same facility is labeled as a gutter in one place, a drainage channel in another, and a waterway elsewhere, searching and aggregating becomes difficult. The same goes for road appurtenances: if classifications such as signposts, light poles, guardrails, and bollards are ambiguous, staff may be unsure how to proceed when making updates. In 3D road ledger maps, the design of attribute fields is as important as detailed geometric modeling.

Consistency with drawing representations is also essential. Even if a three-dimensional display makes the form easy to understand, if line types and legends become hard to distinguish when output as a plan view, it becomes difficult to use in conventional workflows. Road boundary lines, centerlines, structure lines, ancillary items, and reference information need to be represented so that users can distinguish them. In particular, representing confirmed information and reference information with the same appearance can lead to misjudgments.

Attribute information and drawing representations also affect post-delivery updates. When new construction is carried out, if it is not decided which attributes should be updated, how to retain old information, or where to record the update date and supporting documents, the reliability of the register will gradually decline. Although it may require a little extra effort at the time of creation, standardizing attribute fields, naming conventions, layer structures, and display rules will make future update work easier.

Check 5: Decide the delivery format with update operations in mind

A 3D road ledger map is not finished once it has been created and delivered. Roads are constantly changing due to repairs, occupancy, improvements, disaster recovery, and traffic safety measures. Therefore, no matter how precise the initial deliverable is, if it is delivered in a format that cannot be updated, the discrepancy with current conditions will grow over time. To keep using it in practice, it is necessary to decide on a delivery format that anticipates update operations.

The first thing to consider is who will update, how frequently, and over what scope. Even if large-scale updates covering entire routes are carried out by specialist staff, small repairs and changes to appurtenances may be recorded by on-site personnel. Without a mechanism that allows changes to be recorded easily in the field, update information becomes scattered across photos and notes and remains unreflected in the ledger. To make effective use of a 3D road registry map, it is important to establish a workflow that feeds field-generated change information back into the registry.

You should also decide on delivery formats carefully. Organizing editable data, lightweight viewing data, print-ready plans, attribute lists, and change logs according to their intended uses makes them easier to use. Combining everything into a single heavy file makes it difficult for staff who only want to view the data. Conversely, dividing the data into too many small parts can make it unclear which version is the latest. It is important to separate data by use while making version control and update rules clear.

You should also prepare for future system changes and changes in personnel. Relying solely on formats that can be opened only in specific environments may hinder long-term ledger management. Because road ledger maps are materials intended for long-term use, it is necessary to prioritize ease of editing, ease of viewing, and ease of handover. Clearly recording the data storage location, file name, update history, creation conditions, survey date, reviewer, and supporting documents will make it easier for successors to make decisions.

A three-dimensional road ledger map designed with update operations in mind is not merely a deliverable but becomes the foundation of road management. It makes it easier to reference the same information in various situations such as current-condition inspections, construction reviews, maintenance planning, occupancy negotiations, explanations to residents, and checks during disasters. For that reason, it is important to design not only for completeness at the time of creation but also to include mechanisms that allow continuous updating.

Summary: 3D road ledger attached maps are not something you create and finish; they are documents to be continually used.

3D road ledger maps not only indicate the position and boundaries of roads but also make it easier to grasp road surface elevation, the three-dimensional relationships of structures, the locations of roadside fixtures, and the conditions of drainage and level differences. Because they allow confirmation of elevation differences and complex shapes that were difficult to read on conventional 2D road ledger maps, they have the potential to improve efficiency in maintenance management, construction planning, occupancy negotiations, disaster response, and renewal work.

However, making something three-dimensional does not automatically create a good ledger. If the coordinate system and vertical datum are not aligned, if road areas are conflated with existing structures, if the current-condition data have gaps, if attribute information is not standardized, or if update procedures have not been established, the result may look impressive but be difficult to use in practice. To avoid failure with 3D road ledger maps, it is necessary to place as much emphasis on clarifying objectives before creation as on designing post-creation operations.

What is particularly important is to accurately preserve the information necessary for road management. By clearly defining the extent of the road area, which structures are subject to management, which data have been verified, and which documents are used as the basis, you create a register that remains easy to interpret even when personnel change. Three-dimensional data should be maintained not only to make the site easier to visualize, but as a resource to support decision-making in road management.

When creating a 3D road ledger map, it is easier to proceed if you first confirm the relationship between the existing ledgers and the current conditions, and organize the necessary measurement scope and management items. After that, by checking the coordinate system, vertical datum, boundaries, current-condition accuracy, attributes, and update methods one by one, you will arrive at results that are less likely to require rework later. A 3D road ledger map is not a document that is finished once created; it is important to design it as a resource that will be continuously updated to reflect changes in road management.