6 Criteria to Avoid Confusion When Organizing Line Types in 2D Road Ledger Attached Maps

Table of Contents

• Why organizing line types is important in two-dimensional road ledger maps

• Criterion 1: Separate the meanings of lines according to their roles in road management

• Criterion 2: Do not confuse road area lines with boundary-related lines

• Criterion 3: Manage centerlines and road edge lines as separate systems

• Criterion 4: Do not use the same line type for current physical features and management information

• Criterion 5: Use representations that make it possible to distinguish confirmed information from reference information

• Criterion 6: Align with layer names and legends that are easy to update

• Common mistakes that occur when organizing line types

• Apply line-type rules to field verification and update management

• Summary

Why organizing line types is important in 2D road ledger attached maps

A two-dimensional road ledger map is a road management document used to organize, in plan view, the road’s location, road area, centerline, width, length, intersection geometry, structures such as gutters and bridges, and the relationships with surrounding features. Because it is referenced for road construction, occupancy consultations, development consultations, boundary confirmation, maintenance and repair, disaster response, ledger updates, and the like, it is important that anyone can read the lines on the drawings and interpret what they mean in the same way.

In 2D road ledger maps with insufficient line-type organization, the road-area line, road centerline, road edge, pavement edge, gutter edge, public–private boundary, parcel boundary, structure lines, and reference lines tend to be represented similarly. Even if the drafter understands their meanings, personnel who review the maps later may not be able to distinguish them. As a result, the road-area line may be mistakenly read as the pavement edge, the outside of a gutter may be treated as a boundary line, or the centerline may be regarded as merely a drafting guide line.

What becomes a problem in practice is not that the lines look similar, but that the meaning of the lines is not conveyed. A road boundary line indicates the area managed as a road. The center line is the axis for route management. Pavement edges and gutter edges are lines that indicate on-site structures and current conditions. Public–private boundaries and lot boundaries are lines related to land boundaries. Although all of these are represented as lines on drawings, their practical meanings differ greatly.

If line types are not organized, requests for revisions after delivery will also increase. Reviewers are likely to point out comments such as "Is this line a roadway boundary line?", "Is this dashed line a boundary or a reference line?", "The centerline and the existing road edge are on the same layer", and "The legend and the drawing display do not match." Organizing line types is a necessary task not only to tidy the appearance of drawings but also to maintain the reliability of documents used for road management.

Also, a two-dimensional road ledger map is not finished once it has been created. It is continuously updated to reflect road improvements, side-ditch repairs, road occupancy works, disaster recovery, development attribution, boundary verification, and other changes. If line types and layers are well organized, tasks such as updating only the road area lines, verifying extensions of only the centerline, or aligning only structures with field survey results become easier. Conversely, when lines that have multiple meanings are treated the same way, the risk increases that necessary lines will be accidentally deleted during updates or reference lines will be treated as official lines.

This article explains six criteria to avoid confusion when organizing line types in two-dimensional road ledger annex maps. By organizing from the perspectives of the road’s management role, road area and boundaries, centerline and road edge, existing features and management information, confirmed information and reference information, and layer names and legends, you can reduce misinterpretation of drawings and make it easier to create road ledger annex maps that are resilient to updates after delivery.

As Criterion 1, classify the meanings of lines by their roles in road management

The initial criterion for organizing line types is to classify the meanings of lines according to their roles in road management. In two-dimensional road register attached maps, lines should not be classified only by their visual appearance but should be organized based on what they are meant to manage. When the role of a line is clear, it becomes easier to determine line types, layers, legends, and annotations.

The lines that appear on maps attached to the road ledger can be broadly divided into lines indicating management boundaries, lines indicating route axes, lines showing existing site features, lines related to boundaries, lines indicating structures, and reference display lines. A representative line indicating the management boundary is the road area line. A representative line indicating the route axis is the road centerline. Existing site features include pavement edges, gutter edges, curbs, and slope edges. Lines related to boundaries provide information on public–private boundaries and parcel boundaries. Structures include bridges, retaining walls, manholes, cross drains, and guardrails.

If you decide line types solely for visual convenience without assigning roles, it will cause confusion later. For example, if you draw the road boundary line and the pavement edge as solid lines of the same thickness, someone reading the drawing will have difficulty determining which one defines the road area for management purposes. If the centerline and survey auxiliary lines are represented identically, it will be unclear whether the centerline may be used for extension calculations or station management.

Separating lines according to their roles in road management makes it easier for those viewing the drawings to make judgments. To confirm the road area, refer to the road area line. To confirm the route length or start and end points, refer to the center line. To confirm the positions of on-site structures, refer to existing site features or structure lines. For checks involving boundaries, distinguish whether the line is based on boundary-related documents or is shown for reference.

When creating drawing data in CAD or similar, reflect this division of roles in layer management. Separating layers for road boundary lines, centerlines, existing road edges, structures, annotations, and reference information makes verification and updates easier. It is important not just to change display colors, but to distinguish meanings as part of the data structure.

Dividing the meaning of lines according to their roles in road management is the foundation of organizing line types. If this remains ambiguous, confusion will arise in all subsequent boundary verification, width classification, centerline classification, incorporation of field survey results, and pre-delivery checks. First, clarify the role of each line, and then determine the line types and layers according to those roles.

Criterion 2: Do not confuse the road area line with the boundary-related line

The second criterion is not to confuse road area lines with boundary-related lines. One of the lines that requires the most attention on a two-dimensional road ledger-attached map is the road area line. The road area line indicates the extent managed as a road. By contrast, lines related to public-private boundaries, parcel boundaries, land acquisition boundaries, and on-site boundary markers are lines concerned with land or rights. These may coincide in some cases, but they are not always the same.

The road area may include not only the carriageway but also sidewalks, shoulders, gutters, drainage facilities, slopes, retaining walls, planting strips, and margins necessary for management. Therefore, the pavement edge or gutter edge visible at the roadside may not coincide with the road boundary line. If the road boundary line is drawn using the same line type as the public–private boundary or parcel boundary, readers may confuse the extent of road management with land boundaries.

When displaying boundary-related lines, manage them using different line types or layers than road boundary lines. Lines based on boundary documents, cadastral boundaries shown for reference, and lines indicating on-site structures as boundary guides each have different meanings. In particular, if lines based on boundary confirmation documents are represented the same way as boundary-related lines imported as background information, confirmed information and reference information will become mixed.

We also verify the basis for the road boundary lines. We manage which documents were used as the basis for creating the boundary lines, such as land acquisition maps, materials related to road areas, boundary documentation, as-built drawings, maps attached to the existing road ledger, and results of field surveys. It is safer not to treat road boundary lines backed by clear supporting documents the same as lines that are shown only for reference due to insufficient materials.

Confusion between road boundary lines and property boundary lines tends to occur at intersections and corner-cut areas. At intersections the road area widens, and management divisions for corner cuts, sidewalks, gutters, cross drains, and connecting roads overlap. Even where area lines are clear on straight sections, at intersections it may be necessary to cross-check with boundary records and land acquisition records.

In practical work on organizing line types, road area lines are treated as one of the most important control lines and are clearly distinguished from boundary-related lines. It is important to display road area lines prominently and clearly—by using thicker lines, for example—and to depict boundary-related lines with different line types or annotations so that those reading the drawings can intuitively understand the difference. Avoiding confusion between road area lines and boundary-related lines is fundamental to preventing discrepancies in understanding regarding construction extents, occupancy extents, boundary verification, and ledger updates.

Manage the centerline and the road edge line as separate systems under Standard 3

The third criterion is to manage the centerline and the road edge lines as separate systems. In two-dimensional road ledger maps, the road centerline and the road edge lines are both related to the road’s shape and therefore tend to be treated the same. However, the centerline is the axis for route management, while the road edge lines indicate current conditions, the boundary of the road area, and the positions of pavement and structures. Because their roles differ, line types and layers need to be organized separately.

The road centerline is the line that indicates the alignment of a route from its starting point to its end point. It serves as the reference for organizing items such as length, stationing, construction sections, inspection points, structure locations, and maintenance history. While it may lie at the center of the road area, in cases of one-sided widening, a sidewalk on one side, intersections, or curves, the visually apparent center and the administratively defined centerline may not coincide.

There are several types of road edge lines, such as the road area edge, pavement edge, gutter edge, curb, slope edge, and retaining wall edge. If these are all treated collectively as road edges, it becomes unclear which line should be used as the reference for measuring the roadway width, which line represents on-site structures, and which line denotes the boundary of the road area. If the centerline and road edge lines are placed in the same layer, it also becomes difficult to later extract only the centerline to check its length.

The continuity of the centerline is critical. If it is interrupted partway, unnaturally bent at intersections, or misaligned at connections with adjacent drawings, it will hinder route management. In contrast, road edge lines are more susceptible to influences such as changes in carriageway width, structures, intersection geometry, and on-site improvements, and are checked from a different perspective than the centerline. It is important to reflect this distinction in the classification of line types.

When organizing centerlines, it is more practical to manage them linked to the start point, end point, route number, centerline length, and update history. Road edge lines should be separated according to their meaning—such as road area boundaries, pavement edges, gutter edges, and structure edges. Treat the centerline as a single, clear management axis and separate road edge lines as information about current conditions and areas, which makes reading and updating drawings easier.

This distinction also applies to width delineation. Width is often delineated perpendicular to the centerline, but unless it is made clear which road edge is used as the reference for measurement, the meaning of the width value changes. To distinguish whether it is the road area width, the paved width, or the effective width, standardization of the line types for the centerline and the road edge lines is essential.

If the centerline and the road edge lines are managed in separate systems, the 2D road ledger map becomes easier to use as a road management resource. By separating the axis used for route management from the lines representing the actual field geometry, length checks, width checks, structure checks, and update work all become easier to organize.

Criterion 4: Do not use the same line type for existing features and management information

The fourth criterion is not to use the same line type for existing site features and management information. In 2D road ledger attachment drawings, what is visible on site and road-management information are displayed on the same drawing. Existing site features include pavement edges, gutters, curbs, retaining walls, slopes, manholes, bridges, entrances and exits, surrounding waterways, and building outlines. Management information includes road boundary lines, road centerlines, width sections, start and end points, and management boundaries. If these are represented with the same line type, readers of the drawing may confuse the physical lines on site with the management lines.

Current on-site features are information indicating the locations of structures and features that can be observed in the field. For example, the edge of a gutter or a curb is often recognized on site as the edge of a road, but that does not necessarily mean it represents the road boundary or another boundary line. The same applies to the edge of paving. The area that is paved may not coincide with the area managed as roadway.

Management information is information organized based on road registers and road management. Road boundary lines indicate the scope for road management. The centerline is the axis of route management. The start and end points indicate the management section. These may correspond to structures on site, but they are not the actual on-site features. Therefore, it is desirable that management information be expressed so that it can be distinguished as higher-level information than the on-site features.

If existing feature lines and management information are assigned the same line type, confusion can arise during corrections and updates. For example, if the location of a roadside ditch changes due to ditch renovation, the existing feature line will be subject to update. However, the road boundary line does not necessarily change. If existing feature lines and management information are treated the same, there is a risk that the road boundary line could be mistakenly modified along with the roadside ditch location update.

The same applies to structures. Bridges, retaining walls, manholes, guardrails, signs, and so on are important information related to road management, but their meaning is different from road boundary lines and centerlines. If structure lines are displayed with the same line weight as management lines, the drawings become hard to read. Adjust line types and display methods according to importance to make the difference from management lines clear.

Existing site features are often updated based on field survey results and as-built drawings. Meanwhile, management information needs to be reconciled with ledger records, road area documents, and start/end point information. This difference in the basis for updates should also be reflected in the organization of line types.

Not using the same line type for existing on-site features and management information prevents misinterpretation of drawings and makes decision-making clearer during updates. Separating the lines that indicate what is present on site from those used for road-management decisions is an important criterion for enhancing the practical utility of two-dimensional maps attached to the road ledger.

Criterion 5: Use expressions that distinguish confirmed information from reference information

The fifth criterion is to use expressions that make it possible to distinguish between definitive information and reference information. In two-dimensional road ledger maps, information that can be treated as definitive based on source documents and reference information displayed as background or to assist verification may be mixed together. If this difference is not clear on the drawings, reference information could be mistakenly used as official management information.

Confirmed information refers to data treated as road management information based on sources such as road ledgers, documents concerning road areas, boundary documents, survey results, and as-built drawings. Examples include road area lines, official centerlines, start and end points as recorded in the ledger, and organized width sections. On the other hand, reference information includes background features, surrounding topography, unverified current-condition lines, information transcribed from old drawings, and lines whose positional accuracy is not sufficient.

If confirmed information and reference information are drawn with the same line type, people using the drawings cannot distinguish between them. For example, a cadastral-style line imported as background may appear to be an official boundary line. A drainage line that has not been field-checked may be treated as the current location of a structure. To prevent this, display reference information less prominently than control lines, and add annotations where necessary.

Handling unverified areas is also important. Due to insufficient documentation or lack of on-site verification, it may be impossible to determine road boundary lines or the positions of structures. If such information is displayed using the same line types as confirmed information, users may later be misled. It is safer to use line types, layers, and annotations that clearly indicate the information is unverified or for reference only.

Be careful with information carried over from old drawings. Lines based on past road register maps or paper drawings may not match current on-site conditions or survey results. If old information is kept for reference, make sure it is distinguishable from the current official line. Expressing old center lines, old road edges, old structure locations, etc., in the same way as current information will cause confusion when updating.

Separating confirmed information from reference information also helps clarify the scope of responsibility after delivery. When it is clear which parts are verified deliverables and which are shown for reference, reviewers and users can use the drawings appropriately. Conversely, drawings that present everything with the same visual weight may look neat but are difficult to use for practical decision-making.

When organizing line types, it is important to present definitive information clearly and to express reference information so it is less likely to be misunderstood. By reflecting line accuracy and the strength of supporting evidence in the map representation, the reliability and usability of the 2D road register map are enhanced.

Align layer names and legends to be easy to update as Criterion 6

The sixth criterion is to standardize layer names and the legend so they are easy to update. Two-dimensional road ledger maps are not documents that are completed and finished at the time of delivery. They are updated in response to road improvements, side-ditch repairs, occupancy works, development attribution, disaster recovery, boundary verification, and so on. Therefore, when organizing line types, it is necessary to consider not only current readability but also ease of future editing and verification.

Layer names should be understandable not only to the creator but also to those who will review them later. It is desirable to use names that convey the role of the line, such as road boundary line, road centerline, existing road edge, pavement edge, gutter, structures, boundary relationships, reference information, notes, and background features. Abbreviations used only during work or names unique to a particular person will not make sense at handover.

Splitting layers into too many small parts makes management cumbersome, but combining them too much makes updates difficult. At a minimum, separating road boundary lines and centerlines, existing features, structures, and reference information makes them easier to handle in practice. Width annotations and start/end point markings should also be placed on separate layers as needed, which makes checking and updating drawings easier.

The legend must match the line types on the drawing. Avoid situations such as line types shown in the legend that are not used on the drawing, line types that appear on the drawing but are not in the legend, or the same line type being used with multiple meanings. It is important that someone viewing the drawing for the first time can determine the meaning of the lines by referring to the legend.

When creating multiple drawings, ensure that layer names and line types do not vary across the drawings. If the same roadway boundary line uses different line types in different drawings, the same centerline has different layer names, or the representation of structures differs between drawings, it becomes difficult to manage them after delivery. It is important to establish unified rules and apply them to all drawings.

Linking update history and verification status with layers is also an effective approach. If you distinguish lines that reflect on-site survey results, lines carried over from existing drawings, and lines shown for reference, you will know which areas should be prioritized for checking in the future. However, if line types become too complex the drawings can become difficult to read, so consider supplementing them with a legend or management tables.

Standardizing layer names and the legend to make them easy to update is the finishing touch in organizing line types. If you arrange them with not only the drawing’s appearance but also data usability, updatability, and ease of handover in mind, the 2D road ledger attached drawings will serve as management documents that remain useful for a long time.

Common Mistakes When Organizing Line Types

When organizing line types in two-dimensional road ledger maps, there are several typical mistakes. The most common is representing the road area boundary line and the current road edge in the same way. Pavement edges and gutter edges are lines visible on site, but they have a different meaning than the road area boundary line. If the same line type is used, it becomes easy to confuse the administrative extent of the road with the positions of on-site structures.

Next, there is a mistake of treating the centerline like an auxiliary line. The road centerline is an important management axis for organizing length, start and end points, survey stations, construction sections, and inspection information. If it is treated the same as drafting auxiliary lines or lines that indicate the center of the road shape, it becomes difficult to later extract and manage the centerline alone.

Confusion between boundary relationship lines and reference lines is also common. Lines imported as background or transcribed from old documents can appear to be official boundary lines. If it is not made clear whether a line is based on boundary records or is merely a reference indication, misunderstandings can arise during boundary verification and occupancy consultations.

Unclear layer names are also a major problem. If abbreviations only the creator understands, interim names left from the work process, or layers with overlapping meanings remain, the person responsible for updates after delivery will be confused. Layer names need to be organized so that the role of each line is clear.

There are also errors where the legend and the drawing display do not match. If a line type shown in the legend as a road boundary line is used on the drawing to mean something else, users cannot make a determination. The legend is not mere decoration but a convention for reading the drawing. It must always match the line types on the drawing.

Having too many line types can make drawings difficult to read. Subdividing lines in detail can be effective in itself, but if the representation becomes too complex, people looking at the drawing won't be able to remember the meanings of the lines. It's important to make key control lines clear, and to strike a balance with readability by managing detailed information and attributes in separate documents as needed.

To prevent these mistakes, it is important to decide on line-type organization at the specification stage before creation, rather than leaving it until the end of the work. Decide in advance how to classify road boundary lines, centerlines, existing site features, boundary relationships, structures, and reference information, and if you create drawings according to those rules, there will be less need for major cleanup work later.

Leveraging line-type rules for on-site verification and update management

Organizing line types not only improves the readability of drawings but also supports field verification and update management. In 2D road ledger maps, there are many situations where you must decide which lines should reflect information confirmed on site and which should be maintained based on ledger documents. When rules for line types are clear, it becomes easier to appropriately reflect field verification results on the drawings.

For example, if an on-site inspection confirms that the position of a side ditch has changed, the feature that should be updated is the side ditch line as a current ground feature. However, that does not necessarily mean the road boundary line will change. Updating the road boundary line may require cross-checking with land acquisition documents and materials related to the road boundary. If line types are organized, you can separately determine updates to current ground features and management lines.

The same applies to the centerline. Even if the pavement shape changes after road improvements, how the centerline in the ledger is handled relates to the start and end points, the length, and stationing management. If the centerline is mechanically adjusted to match the current road center, it may disrupt consistency with the ledger records. If the centerline is organized as a separate layer as a management axis, it can be updated carefully while checking the differences with the current shape.

Line-type rules are also useful for field verification records. If you record whether a measured point is the pavement edge, the outside of a gutter, a boundary marker, or a structure corner and reflect each in the corresponding line type, the basis for updating drawings becomes clear. It is important not to import only coordinate values but to link the meaning of the measured feature with the line type.

In update management, distinguishing between confirmed information and reference information is particularly important. If you make it possible to tell apart lines that have been field-verified, lines carried over from existing materials, and unverified reference lines, it becomes easier to determine what to check at the next update. By combining update histories, management tables, and line-type rules, you can maintain the reliability of drawings over the long term.

Line-type rules also help align understanding among stakeholders. When road management personnel, surveyors, drafters, and on-site inspectors share the same line-type rules, confirmations such as "this line is a road boundary," "this line is an existing side ditch," or "this line is a reference marking" proceed smoothly. The need to explain the meaning of lines each time is reduced, and there are fewer requests for corrections and rework.

Organizing line types in 2D road ledger attached drawings is not work done solely for creating drawings. It is a set of rules that supports field verification, incorporation of survey results, ledger updates, and post-delivery operations. By incorporating the line-type rules into practical workflows, the road ledger attached drawings can become more user-friendly management documents.

Summary

To avoid confusion when organizing line types in two-dimensional (2D) road ledger drawings, it is important to classify lines not only by their appearance but by the meanings they carry for road management. Road area lines, centerlines, existing road-edge lines, boundary-related lines, structure lines, and reference lines may all appear as the same "line" on the drawings, but their practical roles differ. By reflecting these differences in line types, layers, and legends, you can reduce misinterpretation and requests for corrections.

The first criterion is to categorize the meanings of lines by their roles in road management. If you classify lines that indicate the management extent, lines that indicate the route axis, lines that indicate existing site features, lines related to boundaries, lines that indicate structures, and lines that indicate reference information, the overall policy for organizing the drawings becomes clear.

The second point is not to confuse the road area boundary line with boundary relationship lines. The road area boundary line indicates the area managed as a road and does not always coincide with the public–private boundary, parcel boundaries, the pavement edge, or the edge of side ditches. Lines based on boundary records and lines shown for reference must also be distinguished and expressed in a way that does not cause misunderstanding.

The third is to manage the centerline and the road edge line in separate systems. The centerline is the management axis of the route and is related to length, stationing, construction sections, and inspection information. The road edge line is a line indicating the current condition or extent, such as the boundary of the road area, the pavement edge, the gutter edge, and the edge of structures. By not treating the two in the same way, it becomes easier to organize road widths and verify lengths.

The fourth point is not to use the same line type for existing on-site features and management information. Pavement edges, gutters, curbs, retaining walls, and manholes are features that can be confirmed on site, but they have a different meaning from road boundary lines or centerlines. It is important to ensure that updates to on-site structures and updates to road management lines can be evaluated separately.

The fifth point is to use expressions that allow confirmed information and reference information to be distinguished. If confirmed information based on source materials and reference information shown as background or supplementary are rendered with the same line style, users may mistakenly treat them as official information. It is safer to make unconfirmed locations and reference displays distinguishable by line style or annotations.

The sixth point is to standardize layer names and the legend to make updates easy. Organize items such as road area lines, centerlines, existing road edges, structures, boundary relationships, reference information, and notes under clear layer names, and make the legend consistent with the drawing display. Using the same rules across multiple drawings makes post-delivery updates and handovers easier.

Line-type organization is a practical rule not only for creating easy-to-read drawings but also for streamlining field verification and update management. By clearly defining which line types will represent the pavement edges, gutters, boundary markers, and structure locations confirmed on site, the accuracy of updates to the road ledger’s attached drawings will improve.

To more reliably advance the organization of line types in 2D road ledger-attached maps, it is important to link position information acquired in the field with the meanings of the lines on the drawings. LRTK, a GNSS high-precision positioning device that can be attached to and used with an iPhone, is a good option for verifying on-site features such as road zones, centerlines, side ditches, catch basins, boundary markers, points of width change, and structure locations, and recording them as high-precision positional information. If you want to reflect field positional information while organizing the meanings of individual line types, considering the use of LRTK can help improve the quality of 2D road ledger-attached maps and streamline update work.