top of page

Table of Contents

Premises for estimating the production costs of 2D road register attached maps

Element 1: Confirm the target road(s) and the scope of production

Element 2: Check the availability and organization status of existing materials

Element 3: Assess the necessity of on-site investigation and surveying

Element 4: Assess the difficulty of confirming road zones and boundaries

Element 5: Determine the amount of information to be mapped and the depth of attribute organization

Element 6: Confirm data formats and delivery specifications

Element 7: Consider the update history and the mechanism for maintenance and management

Approaches to reduce production costs without compromising quality

Summary


Assumptions for Estimating the Creation Cost of 2D Road Ledger Attached Maps

When considering the cost of creating a 2D road ledger map, the first thing to keep in mind is that the cost is not determined solely by the amount of drawing work. A road ledger map is a fundamental road management resource that organizes on a plan the road’s location, road area, centerline, width, length, intersection geometry, structures such as side ditches and bridges, and its relationship with surrounding features. Because it is used in many practical operations—road management, construction design, maintenance and repair, occupancy consultations, development consultations, boundary confirmation, disaster response, and ledger updates—verification of source materials, field checks, data organization, and the ease of updating after delivery have a greater impact than the drawing itself.


The factors that affect creation costs are not limited to the length of the target route or the number of drawings. The amount of work required can vary greatly depending on whether existing road ledgers and past attached drawings are complete, whether there are supporting documents for road areas and boundaries, whether on-site surveying is necessary, how extensive a verification of width and centerline alignment is required, to what extent structures and encroachments are to be displayed, and in what format the deliverable data will be prepared.


A frequent problem for practitioners when preparing estimates or placing orders is that, even though the work is referred to as "2D road ledger map creation," the scope of work differs from project to project. Whether it's simply digitizing existing paper drawings in a basic way, conducting field surveys to organize road areas and the positions of structures, verifying consistency with the road ledger records, or preparing attribute information with future digital management in mind, the necessary processes change entirely.


Also, if you try to reduce production costs by narrowing the scope of checks too much, rework may occur after delivery. Examples include drawings produced while the basis for the road boundary line is unclear, requiring later comparison with boundary documents; width indications that do not match the ledger records, necessitating corrections; and on-site structures that are not reflected, requiring re-survey. If you judge solely by initial costs, the overall burden may ultimately increase.


On the other hand, attempting to make everything high‑precision from the outset can make the workload larger than necessary. It is important to clarify whether the supplementary maps are intended for general road management, for decisions close to boundaries or design, or as digital data to streamline maintenance and ledger updates, and to define a scope of work that matches the intended purpose.


This article explains seven factors that influence the cost of creating 2D road ledger-attached drawings for practitioners. Rather than giving specific monetary amounts, it organizes which conditions affect the workload and the way estimates are formed, making it easier to clarify specifications before placing an order, compare estimates, and prevent rework after delivery.


Element 1: Confirm the target route and the creation scope

The first factors that influence the cost of creating two-dimensional road ledger maps are the specific route and the scope of creation. The amount of work required varies greatly depending on which route is mapped, from which starting point to which end point, and how extensive the mapped area is. While there is a general tendency for workload to increase simply with length, in practice not only length but also the complexity of the road shape, the number of connecting roads, the handling of intersections, and the method of dividing the drawings are important.


If the target route is straight and the road limits and centerline are relatively clear, the drawing work becomes easier to carry out. Conversely, for roads with many curves, roads with consecutive intersections, roads that mix narrow and widened sections, roads with frequent interfaces with bridges and waterways, or roads where development roads and branch lines connect in a complex way, the amount of information that needs to be checked increases. Even when the apparent length is short, the work becomes complicated if there are many intersections, corner cuts, or points where the road width changes.


The scope of the drawing work includes not only the road itself but also the question of how much of the surrounding features to display. Whether you only outline the road area, centerline, width, and start/end points, or whether you display side ditches, retaining walls, slopes, bridges, catch basins, signs, guardrails, sidewalks, adjacent waterways, and interfaces with private land, the required document checks and drafting workload will differ.


How intersections are handled also affects preparation costs. The scope to be checked differs depending on whether only straight sections are targeted or whether corner chamfers at intersections and the management classification with connecting roads are also being organized. In particular, where multiple roads intersect, it may be necessary to ensure alignment not only with the road area of the subject route but also with attached maps and management documents on the connecting roads' side.


If you place an order with an unclear scope, additional confirmations are likely to be required during the work. For example, although you may have originally intended to create only the main line, if it later becomes necessary to display branch lines, connecting roads, or intersection areas, the drawing scope and the scope of material checks will expand. To prevent this, it is important to clearly define the target routes, drawing scope, items to be displayed, and areas to be excluded before placing the order.


To estimate the cost of creating 2D road ledger attachment maps, you first need to clarify "how much to create." By confirming the scope—not only the route length but also intersections, branch lines, structures, surrounding features, sheet division, and connections with adjacent sheets—you can more accurately grasp the amount of work involved.


Element 2: Check for the presence and organization of existing materials

The second element is the presence and organization of existing documentation. Creating a 2D road ledger map is not simply a matter of visiting the site and drawing it from scratch. You must review the road ledger, existing attached maps, ledger records, as-built drawings, land maps, boundary documents, survey results, structure records, occupancy documents, and so on, and organize the road information based on those materials. Whether the existing documentation is sufficiently complete and well organized has a major impact on the cost of creating the map.


If existing road registers and their accompanying records are in order, it becomes easier to confirm basic information such as route name, start point, end point, length, width, and structure information. If existing attached maps are available and their creation date, update history, meanings of line types, and coordinate system are clearly indicated, they can be used as a starting point for mapping work. Conversely, when existing materials are scarce, or even if materials exist but their creation date or justification is unclear, the burden of searching for documents and performing additional verification increases.


Even when only paper drawings remain, the amount of work can increase. You need to scan the paper drawings, perform alignment as needed, capture the lines, and organize them as digital data. However, because paper drawings can stretch and scans can introduce distortions, they cannot necessarily be used as accurate positional information as-is. When overlaying them with field survey results or other map information, you must verify the coordinates and accuracy.


Even when multiple documents exist, the workload varies depending on how organized they are. If old drawings, new drawings, pre-construction drawings, as-built drawings, and verification drawings are mixed together, you must confirm which document is the latest and which is the official reference. When several drawings have similar names and the official version cannot be distinguished from the working version, organizing the documents alone can take a lot of time.


Whether materials concerning road areas and boundaries are available is also important. To accurately depict road area boundary lines, land maps, boundary documents, materials related to road areas, and on-site boundary marker information are required. If these are lacking, on-site surveys and additional verification of related documents may be necessary. If road area boundary lines are drawn without a clear basis, boundary confirmations and occupancy consultations after delivery are likely to cause problems.


The level of organization of existing documentation affects not only the creation cost but also the quality of the deliverables. If the documentation is well organized, you can efficiently produce supporting diagrams with a clear basis. Even when documentation is insufficient, by first clarifying what information is missing and deciding which information will be treated as confirmed and which will be treated as reference, you can reduce rework later.


Before placing an order, it is important to confirm whether existing documents are available, whether they are paper or digital, whether the latest version is clearly identified, and whether they are linked to related materials. If document organization is neglected, uncertainties increase during the drafting stage, which can result in expanded review and revision work.


Element 3: Determine the necessity of on-site investigation and surveying

The third factor is the need for on-site inspections and surveying. When creating two-dimensional road register supplementary maps, it may be possible to produce them using only existing materials, but in some cases on-site confirmation and surveys are required. Whether on-site surveys or measurements are needed, the extent of the area covered, and the required level of accuracy can greatly change the amount of work.


A site survey is necessary when there is a high likelihood that existing records differ from on-site conditions. When road improvements, side drain repairs, sidewalk construction, pavement repairs, relocation of objects occupying the road, disaster recovery, or changes in road ownership resulting from development activities have been carried out, old attached drawings alone may not be sufficient to grasp the current situation. Drawings may still show the position of the old side drain, while on site it has already been relocated.


During on-site surveys, we check the roadway area, pavement edges, side ditches, curbs, retaining walls, slopes, boundary markers, width-change points, intersection geometry, bridges, catch basins, and road appurtenances. In some cases, simply checking is sufficient, while in others surveying to obtain positional information is necessary. The amount of work varies depending on how much on-site information is obtained.


Whether surveying is necessary depends on the level of accuracy required for the deliverables. If you only need to organize the approximate location of a road, existing documents and a simple on-site check may suffice. On the other hand, if you want to manage road right-of-way lines, areas near boundaries, points where the road width changes, and the positions of structures with high accuracy, on-site surveying is necessary. If you plan to perform digital management or overlay the data with other spatial information in the future, preparing the deliverables with coordinates will make them easier to use in practice.


The more features there are to be surveyed, the greater the amount of work. Whether you only verify the road centerline or measure the road edges, gutters, boundary markers, structures, and points of width change will determine the amount of fieldwork and the effort required to organize the results. It is also important to record what each measured point represents. If you only have a point’s coordinates and cannot tell whether it denotes the outside of a gutter, the pavement edge, or a boundary marker, it will be difficult to reflect it on the road ledger map.


On-site conditions also have an impact. Roads with heavy traffic, narrow roads, roads with poor visibility, sections with dense vegetation, areas where structures are densely clustered, and roads in mountainous areas or along waterways require extra effort for on-site inspections and surveying. Safety management and adjustments to work hours may also be necessary.


To accurately estimate creation costs, it is important to clarify the purpose of the site survey before placing an order. The required work varies depending on whether you will only confirm current conditions, reflect the survey results on attached drawings, or retain them as the basis for ledger updates. By clarifying the need for on-site inspection and surveying at the outset, you can avoid unnecessary work while more easily ensuring the required level of accuracy.


Element 4: Assess the difficulty of confirming road areas and boundaries

The fourth element is the difficulty of confirming the road area and boundaries. In the creation of 2D road ledger maps, the road area line is extremely important information. The road area line indicates the extent managed as a road, and its meaning can differ from the pavement edge, the gutter edge, public-private boundaries, parcel boundaries, or the edges of structures. The amount of work varies greatly depending on how precisely this line is delineated.


If documentation related to road areas and boundaries is complete, drafting becomes much easier. With land maps, boundary determination documents, materials concerning the road area, on-site boundary marker information, and past on-site inspection records, you can verify the basis for the road area line. Conversely, if documentation is insufficient or the lines shown in the records do not match the physical structures on site, additional surveys and cross-checking of relevant documents will be necessary.


Boundary confirmation becomes difficult in cases such as old roads, roads with a history of widening, connection points with development roads, roads adjacent to waterways or slopes, and roads where side ditches or retaining walls are near the boundary. On site, even if the outside of a side ditch appears to be the boundary, the actual road boundary line may be located elsewhere. The paved extent does not necessarily indicate the entire road area.


Intersections and corner chamfers are also high-difficulty locations. Even if the road boundary lines are clear in straight sections, at intersections multiple roads connect, the boundary lines can widen and corner chamfers may be added. If you do not confirm the management jurisdiction and the land history of the connecting roads, you may not be able to map them correctly.


For deliverables that require decisions close to a boundary, on-site surveying and comparison with boundary documents become more important. The extent of verification varies between cases where the road area is shown merely as an outline for reference and those where accuracy is required for construction or occupancy negotiations. If the required level of boundary verification is not clearly specified when commissioning the work, discrepancies in the way the deliverable is understood will arise.


Also, if there are locations where the road boundary lines cannot be expressed definitively, you need to decide how to handle them. Depending on whether they will be displayed as reference due to insufficient documentation, subjected to additional investigation, or recorded as undetermined locations, the scope of work will change. Delivering ambiguous lines as if they were definitive information can cause problems in later practice.


Confirmation of road areas and boundaries not only influences the cost of creating two-dimensional maps attached to the road ledger, but also directly impacts the reliability of the deliverables. More important than the act of drawing lines itself is verifying the basis for those lines, cross-checking them with conditions on the ground, and leaving necessary annotations and records.


Decide, as Element 5, the amount of information to visualize and the depth of attribute organization

The fifth element is the amount of information to be depicted and the depth of attribute organization. A two-dimensional road register map can include not only road boundary lines and centerlines, but also width, length, start and end points, intersection geometry, gutters, catch basins, bridges, retaining walls, slopes, guardrails, signs, lighting, sidewalks, encroachments, and surrounding features. However, it is not always best to map everything in fine detail. It is important to organize the information required according to the intended purpose.


The more information that is depicted, the more preparation and verification work is required. A supplementary drawing that only organizes road boundary lines and centerlines requires different document checks, field surveys, drafting, annotations, and cross-checking from a supplementary drawing that organizes structures, road appurtenances, points of width change, encroachments, and surrounding features. While adding more information can make drawings more practical for use in operations, it also increases the information that must be managed.


Even when organizing width information, the depth of the work differs. The amount of work changes depending on whether you simply record a representative width, organize width changes by segment, or distinguish between roadway area width, effective width, and paved width. On roads with many width-change points, segment management and the organization of notes require extra effort.


The same applies to structural information. When displaying the locations of features such as gutters, catch basins, bridges, and retaining walls, it is necessary to verify them against the site and the as-built drawings. The work also changes depending on whether structures are simply shown on the drawings as symbols or are given attribute information such as type and management details. If drawing display and attribute management are separated, the data structure must also be organized.


The depth of attribute organization also affects the creation cost. If you are only drawing lines and text on the plans, the work will be centered on drafting, but if you assign attribute information to road boundary lines, centerlines, structures, and width sections, the task becomes more of a data-preparation effort. Organizing items such as route numbers, sections, widths, update dates, source documents, structure types, and on-site verification status will make later searching and updating easier, but it increases the initial workload.


On the other hand, packing too much information into a drawing can make it difficult to read. One option is to show the main information on the drawing and manage detailed information through attributes or separate documents. In practice, the important thing is to decide the right balance between drawing display and attribute organization based on how the supplementary drawings will be used.


Before placing an order, it is important to organize who will use the deliverables, in what situations, and what information they will use. The amount of information required will vary depending on whether the material is an attached figure for viewing, data for updating records, or documentation for on-site verification and construction consultations. By clarifying the amount of information and the depth of attribute organization, it becomes easier to set a scope of work that is neither excessive nor insufficient.


Confirm data formats and delivery specifications as Element 6

The sixth element is data formats and delivery specifications. The cost of creating 2D road ledger maps varies depending on the format in which the deliverables are produced and the condition in which they are delivered. The work required differs depending on whether view-only drawings are sufficient, editable drawing data is needed, the data must be prepared as coordinate-referenced digital data, or whether attribute information and management tables are to be included.


Viewing data is often organized in a format that makes it easy for stakeholders to check the contents of drawings. On the other hand, when editing or future updates are anticipated, data needs to be organized with lines, text, shapes, attribute information, layer structure, and coordinate systems. Even drawings that look the same can vary greatly in how easy they are to update after delivery depending on whether their internal data has been organized.


When delivering data with coordinates, you must clearly specify the coordinate system, reference points, alignment method, and accuracy information. The work differs significantly between simply delivering scanned images of paper drawings as-is and preparing data that reflects field survey results and can be managed by coordinates. If you plan to overlay the data with other spatial information or field survey results in the future, it is important to organize how coordinates are handled from the outset.


Layer and classification rules also affect the delivery specifications. If you don’t decide in advance how to separate road boundary lines, centerlines, road edges, structures, annotations, background features, reference lines, and so on, it will be difficult to edit later. If line types, colors, symbols, and text notation rules are not standardized, managing multiple drawings together will become confusing.


Confirm the scope of documents to be included in the deliverables. Depending on whether you include not only the drawing data but also ledger records, update history, a list of reference materials used, field inspection records, survey results, photographs, and management tables, the work required to organize them will differ. If you plan to continuously update the maps attached to the road ledger after delivery, it will be more practical for operational use to deliver not only the drawings but also the supporting materials and histories in a form that allows them to be traced.


When delivering in multiple formats, you also need to check consistency between the formats. Confirm that the content of the editable data and the view-only data match, that drawing numbers and update dates are consistent, and that no outdated versions are mixed in. The more delivery formats there are, the more items you need to verify.


Data formats and delivery specifications affect not only the initial creation costs but also the maintenance costs after delivery. Delivering in a simple format can reduce the initial workload, but it may increase the effort required later when updates or integrations become necessary. It is important to anticipate future uses at the time of creation and decide on the required delivery specifications.


Consider update history and maintenance mechanisms as Element 7

The seventh element is the revision history and maintenance system. The two-dimensional road ledger map is not a document that is created once and then finished. It is a record that is continually updated in response to road improvements, side ditch repairs, sidewalk maintenance, road occupancy works, development attribution, disaster recovery, boundary confirmations, and the like. Therefore, whether a mechanism to make updates easy is put in place at the time of creation affects the scope of work and the production cost.


Deciding how thoroughly to organize the update history is important. When recording when an update was made, which section was updated, and which documents it was based on, you need to organize management information in addition to producing drawings. Having an update history makes it easier to trace the rationale during the next update and to verify the history of past road alignments and width changes.


When preparing data with maintenance and management in mind, it is also necessary to manage official versions, working versions, and past versions. Deciding in advance which drawings are the latest official documents, which are for verification, and where past versions will be stored helps reduce the risk of using incorrect drawings after delivery. Keeping drawing numbers, route names, update dates, and supporting documents in a manageable state makes long-term operation easier.


A mechanism for reflecting on-site verification results in updates also affects creation costs. It is necessary to decide how to organize photos, location information, and survey results obtained on site, and which lines or attributes they should be reflected in. If you are simply delivering drawings the work is limited, but if you establish the workflow from on-site verification through ledger updates you will also need to set up management tables and operational rules.


When planning for future digital management, linking attribute information and related documents becomes important. Assigning route numbers and section information to road centerlines, linking update dates and supporting documents to road boundary lines, and associating facility information with structures will make searching and updating easier. However, the amount of initial setup work will increase.


On the other hand, if you produce deliverables in a simplified manner without planning a maintenance system, manual work may increase with every update after delivery. Issues such as not knowing which line is the latest, being unable to trace supporting documents, site verification results not being reflected in the drawings, and past versions coexisting with the official version can arise. How much you put operational procedures in place at the initial stage will greatly affect the long-term burden.


When considering the cost of creating two-dimensional road register maps, it's important to look not only at the time of creation but also at how they will continue to be updated after delivery. If update histories and maintenance mechanisms are properly designed, road register maps will become management documents that can be used for a long time.


How to Reduce Production Costs Without Compromising Quality

To keep the cost of producing 2D road ledger attachment maps down while ensuring quality, it is important not simply to reduce tasks but to separate necessary work from unnecessary work. Because road ledger attachment maps are practical working documents, unjustified simplifications tend to cause rework later. On the other hand, including excessive precision or unnecessary information that does not match the purpose will inflate the workload.


The first step is to clarify the intended use. Specify whether it will be used for general road management, for preliminary checks related to construction or occupancy consultations, whether it should include checks near boundaries, or whether it is being planned with future digital management in mind. When the purpose is clear, it becomes easier to determine the required accuracy, the items to display, the scope of on-site surveys, and the delivery specifications.


Next, organize the existing materials first. Check to what extent road ledgers, existing attached drawings, as‑built drawings, boundary documents, survey results, site photographs, and so on are available, and separate materials that can be used from those that require additional verification. If you postpone organizing materials, unclear points are likely to be discovered during drafting, making verification and corrections more prone to repetition.


Prioritization can also be effective. Rather than preparing all routes to the same level of detail, one approach is to concentrate efforts on sections with planned construction, sections with frequent boundary confirmations, sections with many occupancy consultations, sections where existing drawings are outdated, and sections that are important for disaster response. It is also practical to keep lower-priority sections at an overview level and increase their precision when the need arises.


Field surveys should be narrowed down according to their objectives. Rather than measuring every point in detail, focusing on the points needed to confirm road boundary lines, locations where roadway width changes, positions of structures, intersections, and places where existing documentation does not match on-site conditions will efficiently improve accuracy. However, because measured points will be unusable later unless their meanings are recorded, the quality of on-site records must be ensured.


Delivery specifications should be decided according to how they will be used in the future. If they are only for viewing, a simple delivery may be sufficient, but if you anticipate updates or integration, layer organization, attribute information, update history, and coordinate information will be necessary. It is important to consider not only the initial creation costs but also the work involved in future updates.


To keep creation costs down, the most effective approach is to concretely specify "how much is needed" before placing an order. By clarifying the scope, document review, on-site survey, items to be displayed, delivery specifications, and the scope of update management, the assumptions for estimates will be aligned and comparisons will be easier. To manage creation costs without reducing quality, it's important not to cut tasks but to narrow the specifications to those that match the intended purpose.


Summary

The factors that influence the cost of creating 2D road ledger-attached maps are not limited to the number of sheets or the route length. Multiple conditions affect the amount of work, such as the scope of the area, the condition of existing materials, the necessity of field surveys or measurements, the difficulty of confirming road zones and boundaries, the amount of information to be mapped, delivery specifications, and the system for update management.


The first element is the target route and the scope of the work. The complexity of the work changes not only with whether the target route is long or short, but also with how many intersections, branch lines, bridges, waterways, width-change points, and connections to adjacent drawings there are. It is important to clearly define from the outset what is included.


Second is the availability and organization of existing documents. If the road register, existing attached maps, as-built drawings, boundary records, and survey results are well organized, it becomes easier to streamline the work. On the other hand, if documents are outdated, the official version is unclear, only paper drawings are available, or supporting documentation is insufficient, the burden of document verification and additional investigation increases.


The third is the necessity of on-site investigations and surveying. In some cases it can be created using only existing materials, but on sections where road improvements or local changes have occurred, on-site verification is indispensable. If highly accurate positional information is required, work to reflect the survey results in the attached drawings will also be necessary.


The fourth is the difficulty of confirming road areas and boundaries. To avoid confusing road area lines, public–private boundaries, parcel boundaries, pavement edges, and side-ditch edges, it is necessary to cross-check with land acquisition and boundary records. Verification work tends to become more complex at intersections, corner cuts, development roads, and sections involving slopes or watercourses.


The fifth is the amount of information to be illustrated and the depth of attribute organization. The workload varies depending on whether you organize only the road area lines and centerlines, or also include road widths, structures, encroachments, surrounding features, and attribute information. It is important to consider the balance between readability on the drawing and usability as management data.


The sixth item is the data format and delivery specifications. The scope of work will vary depending on whether drawings for viewing only are sufficient, or whether editable drawing files, coordinate-attached data, attribute information, update histories, and a list of related documents are required. If you anticipate future updates or integration with other data, you need to organize the delivery specifications up front.


The seventh point is the system for update history and maintenance. The two-dimensional road ledger supplementary map is not something that is finished once created; it is a document that should be updated to reflect changes in the road. If you organize the update history, official version control, incorporation of field verification results, and linking to related documents, you can make it easier to reduce rework after delivery.


To properly manage production costs, it is important not to focus solely on minimizing expense but to clearly define the required precision and scope of work. While avoiding specifications that are excessive for the intended purpose, not omitting key elements—such as roadway areas, road width, the centerline, on-site verification, and supporting documentation—will ultimately lead to a balance of quality and efficiency.


When considering the cost of producing two-dimensional road ledger maps, the quality of the positional information obtained in the field is also important. LRTK, a GNSS high-precision positioning device that can be attached to and used with an iPhone, is a good option for tasks that involve confirming on-site road areas, centerlines, width-change points, gutters, manholes, boundary markers, and structure locations and recording them as high-precision positional information. If you want to efficiently reflect field verifications and survey results in two-dimensional road ledger maps and plan for post-creation update management, considering the use of LRTK can make it easier to reduce rework and improve the quality of road management documentation.


Next Steps:
Explore LRTK Products & Workflows

LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.

LRTK supercharges field accuracy and efficiency

The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.

bottom of page