What causes JGD2011 not to match in CAD? 7 common mistakes and how to deal with them

Even when you are using JGD2011 in CAD, drawings can be misaligned, coordinates you entered may shift, or points measured on site may not overlap with the design drawings. Such troubles often arise not from simple operational mistakes but because the assumptions about coordinates are not consistent.

In practice, work proceeds while exchanging multiple datasets such as surveying results, design drawings, construction drawings, as-built control data, and coordinates obtained on site with field terminals. For that reason, looking at a single file may not reveal the cause; the recipient may assume it is JGD2011, while in reality different assumptions are mixed in.

When JGD2011 does not match, it is important not to blindly try to align by moving or rotating. Even if the view appears to overlap, temporary fixes can cause larger discrepancies downstream, leading to major rework in setting out on site, as-built checks, and redistribution to stakeholders. What is needed is to isolate the type of discrepancy, and for each cause, organize how to identify it and how to fix it.

This article explains seven causes that frequently occur in practice when JGD2011 does not match in CAD: wrong zone number, mixing in arbitrary coordinates, misidentification of control points, unit mismatch, leftover rotation, duplicate transformations, and poor information sharing. For each, it concretely organizes, from a practitioner’s perspective, the typical symptoms, how to distinguish them, what to check, and how to correct them.

Table of contents

• Initial thinking to organize when JGD2011 does not match

• Wrong zone number

• Wrong zone number

• Mixing in arbitrary coordinates

• Mixing in arbitrary coordinates

• Misidentification of control points

• Misidentification of control points

• Unit mismatch

• Unit mismatch

• Leftover rotation

• Leftover rotation

• Duplicate transformations

• Duplicate transformations

• Poor information sharing

• Poor information sharing

• How to organize operations to prevent recurrence of JGD2011 shifts

• Summary

Initial thinking to organize when JGD2011 does not match

Saying “JGD2011 does not match” actually bundles several different conditions. The suspected causes change depending on whether the drawing is translated uniformly, rotated by a constant angle, has distances changed, or only certain parts match while the whole is misaligned.

First, organize the type of displacement. For example, if all points are shifted by roughly the same amount to the east, west, north, or south, suspect a wrong zone number, misidentified control point, or different coordinate import conditions. If the orientation of shapes looks slightly tilted, leftover rotation or arbitrary coordinate transformation is more likely. If distances themselves do not match, suspect unit mismatch or how scale was handled. If it appears to match but does not overlap another reference, it may be that repeated transformations have moved it away from the original reference.

Next, confirm whether the data you opened is truly JGD2011 itself or a different coordinate system created based on JGD2011. In practice, data originally surveyed in a public coordinate system may be converted to an arbitrary coordinate system for ease of work. Colleagues may say “it was originally JGD2011,” but that refers to the source data and does not guarantee that the current numbers in the drawing are still JGD2011. Working with this distinction unclear makes isolating the cause impossible.

Also important is not to judge based on the drawing alone. Comparing multiple materials—coordinate lists, control point results, surveying records, drawing creation settings, and handover documentation—often reveals anomalies. When JGD2011 does not match, avoid deciding from the on-screen appearance alone; verify against at least two or more reference points.

From here, we will look at seven frequently occurring causes in practice in order.

1. Wrong zone number

The most representative cause of JGD2011 not matching is using the wrong zone of the plane rectangular coordinate system. Relying on the term JGD2011 alone and overlaying data without checking which zone is used can cause large position shifts. This is not a problem with the geodetic datum JGD2011 itself, but a mismatch in which projected coordinate system (zone) is used.

The plane rectangular coordinate system is divided into zones by region, and even with the same JGD2011, coordinates differ depending on the adopted zone. On site, the ordering documents or existing results may adopt one zone while the recipient loads the data in a different zone. Also, in projects spanning multiple districts or when reusing past results, data from different zones can easily mix.

A useful way to detect this mistake is to compare coordinates of known points. If a point’s coordinate values do not match the result table at all, yet the shape of the geometry itself is preserved, the zone number is likely wrong. The same applies when distances and shapes are largely preserved but the position is significantly offset. If you have points such as survey marks or control points with known correct coordinates, pick them up in CAD and compare to the results table to isolate the issue.

The remedy is straightforward: confirm the correct zone number and reload the original data with the correct settings. Avoid forcibly aligning by parallel translation on the screen. Even if you force-match different zones by moving, you will lose consistency with other drawings or future observations. First check ordering documents, survey result books, control point lists, drawing legends and notes, and delivery settings to unify the zone to be used across the project. Then review import and coordinate transformation settings and re-position the data.

As prevention, do not rely solely on filenames or drawing titles. Labels like “JGD2011 compatible” or “public coordinates drawing” are insufficient if the zone number is not explicitly stated. Data providers should share not only the JGD2011 notation but also the zone number, how the coordinate origin is handled, and whether arbitrary coordinates were used. Recipients should perform control point checks at the initial import to prevent major rework later.

2. Mixing in arbitrary coordinates

Another common case is mixing in arbitrary coordinates. This is particularly troublesome in practice because the drawing can often be used without apparent issues. For ease of work on site or internally, someone may place a reference point near the origin and align the drawing orientation, effectively converting it to arbitrary coordinates. Daily tasks can still proceed in that state, and the discrepancy often becomes apparent only when overlaying public coordinate data later.

There are several signs to detect mixed-in arbitrary coordinates. First, look at the digit length and trends of the coordinate values. JGD2011 plane rectangular coordinates have values corresponding to the site location, but arbitrary coordinates often start near the origin and have manageable values. For example, if values are organized to the hundreds or thousands based on a certain reference point, they may not be public coordinates. Also, when overlaying with other documents, if orientation and position are slightly off but internal dimensions are correct, arbitrary coordinate conversion may be suspected.

Another way to tell is whether known control point coordinates match within the drawing. If the coordinates in the survey results differ from the values you pick up in CAD, yet the linearity and dimensions inside the drawing feel correct, it is highly likely the drawing has been converted to arbitrary coordinates. Even if the creator says “it’s based on public coordinates,” that may describe the source; the actual file may no longer be in public coordinates.

To address this, clearly label whether the drawing is arbitrary coordinates or JGD2011. Ambiguity is the most dangerous. If it is arbitrary coordinates, verify the correspondence to the original public coordinates and reconstruct the coordinate transformation conditions using two or more control points. If no correspondence table remains, carefully determine what parallel translations and rotations were applied by using control points that can be rechecked on site.

Arbitrary coordinates themselves are not inherently bad in practice; they may be used for convenience in a small site. However, even then you must document the relationship to the original JGD2011 and clearly indicate it in file names, title blocks, and transfer documents. Circulating an arbitrarily transformed drawing as a “JGD2011 drawing” is a major cause of trouble.

3. Misidentification of control points

Misidentifying control points is also a frequent cause of JGD2011 not matching. There are multiple types of controls on site: public control points, construction control points, temporary benchmarks, and management points used for convenience. When these coexist, similar names can lead to confusion about which is which. If the drawing creator and the surveyor are different, or the work has passed through several handovers, it becomes easy to lose clarity about which point is the absolute reference.

This error is detectable when the offset is consistent but not as large as a zone mismatch. If aligning to a specific point makes the vicinity match but other parts diverge, or if checking against another known point reveals inconsistencies, the referenced point may be wrong or a same-name-but-different-generation point may be used.

Control point result tables and drawing notes may have similar point names but differ by generation due to updates. Reusing older results can mean the name is the same but the values have changed due to reestablishment or remeasurement. Therefore, check not only the point name but also the coordinate values, installation position, surrounding conditions, and observation records. If there are site photos or sketches, compare them to the drawing to detect misidentification.

As a remedy, do not rely on a single control point. Verify against at least two, preferably three or more points, and determine whether the issue is only translation or includes rotation. Relying on one point alone can make an incorrect point appear to fit and then fail elsewhere. Once the correct control points are determined, reestablish the drawing’s overall alignment based on those points, and review any drawings or calculations previously created under the wrong assumption.

Preventive measures include maintaining a control point list. Keep a management table with point names, coordinates, purposes, adoption dates, adoption reasons, and related drawings, and fix the official control points used during the work. This reduces confusion when personnel change. In CAD, separate absolute control points and auxiliary points into different layers or notes to lower the risk of misidentification.

4. Unit mismatch

Unit mismatch is a surprisingly overlooked cause when coordinates do not match. If CAD internal units, import settings, and the units used to create external data are not consistent, not only positions but distances and dimensions will be incorrect. It is not uncommon to chase a JGD2011 issue only to find that meters (ft) and millimeters (in) were mixed up.

A hallmark of unit mismatch is that relative relationships of control points and geometry are preserved while the overall size does not match. Symptoms include a segment length being a thousand times or one thousandth of the expected value, coordinate digit counts being unnaturally large, or the drawing appearance matching while dimension values or area calculations disagree. Especially when coordinates are imported as text or point clouds from external files, wrong units uniformly scale all points.

A reliable way to detect this is to check known distances. If a section that is clearly tens of meters (tens of ft) on site appears as tens of thousands in CAD, suspect unit settings. Also be cautious when coordinate values look extremely large. But because public coordinates can inherently have large values, you cannot judge by magnitude alone; examine both coordinate values and drawing dimensions together.

To fix this, clarify the unit used to create the source data and the unit the CAD accepts, and if necessary, reimport with the correct scale factor. Avoid individually scaling items to match, as such edits are hard to track and easily recur when shared. The best approach is to set the correct import conditions and read in the data again. If a unit mismatch is found after multiple datasets were integrated, identify when the scale diverged and trace back to correct all related files.

For prevention, clearly state units on handover. The drawing appearance alone may not reveal whether the basis is meters (ft) or millimeters (in). Unify unit notation in coordinate files, point lists, drawings, and quantity calculations, and create an intake procedure for the importer to verify units immediately; this helps quickly distinguish JGD2011-derived problems from unit-related ones.

5. Leftover rotation

Leftover rotation is a frequent cause in practice when JGD2011 does not match. This refers to leaving a drawing rotated for convenience and not returning it to the original orientation, or to a state where only rotation remains after arbitrary coordinate conversion. Because it may look more readable on the screen, it is often overlooked, but overlaying with public coordinates or site-measured coordinates shows the whole drawing tilted by a constant angle.

You can detect leftover rotation because aligning one point will produce larger discrepancies the farther you move from that point. With only a parallel shift, the offset is uniform everywhere, but when rotation remains, the offset increases with distance from the rotation center. Pay attention when major road centerlines or structural axes on site appear slightly tilted relative to the assumed direction; consultations about misalignment at drawing edges are often this case.

Comparing two known points makes it easier to determine. If aligning to the first point makes the second point misalign, and vice versa, suspect rotation or scale issues. If distances are largely preserved but only directions shift, leftover rotation is likely. If distances also differ, suspect unit mismatch as well.

The remedy is to determine the rotation angle using two or more control points and return the drawing to the correct orientation relative to public coordinates. However, responses differ depending on whether the rotation was applied purely for readability or was part of a planned arbitrary coordinate conversion. In the former case, you may be able to revert to the original angle via drawing history; in the latter, you need to trace the transformation conditions in the records. In any case, mathematically restore orientation based on known points rather than relying on approximate visual matching.

To prevent recurrence, distinguish between display rotation for drafting and actual coordinate rotation of the data. Display changes for readability are acceptable, but if you rotate the actual data, always leave a record of the history and purpose and communicate it when sharing. When personnel change, it may be unclear whether a rotation was intentional or a casual edit, and that later emerges as a JGD2011 mismatch.

6. Duplicate transformations

Duplicate transformations occur when coordinate transformations or corrections are applied multiple times to the same data. This happens when successive handlers feel “it’s off” and individually correct it, stacking new transformations onto the original. What may have been consistent after one transformation gradually drifts from the original reference with each redistribution or re-transformation, eventually making the cause untraceable.

This problem is alarming because dispersed editing histories make it hard to detect. One person may apply a parallel translation, another adds rotation, and another enables a transformation at import; individually these operations are small, but collectively they cause large drift. Moreover, each person believes they have “fixed” it, so later it becomes unclear which state is correct.

Signs include variations in control point positions across files for the same project, coordinate values fluctuating by version even with the same drawing name, or parts being transformed despite documentation claiming “not transformed.” Also suspect duplicate transformations when discrepancies vary by version rather than following a single clear cause. The characteristic is offsets that cannot be explained by one clear cause.

To address this, first decide on a definitive original. Rather than keep editing files of unknown transformation history, it is often faster to reconstruct from the most reliable source data. Then fix the stage at which each transformation is applied. For example, clearly separate the public coordinate original, an arbitrary coordinate working copy, and delivery files pre-transformed for handover; store them under distinct names and do not overwrite.

Prevent recurrence by using naming rules and history management for transformed files. If originals, transformed-for-correction, rotation-applied, and delivery versions are not distinguished, the next person may apply more transformations. Record the rationale and conditions for each transformation to make future troubleshooting much easier.

7. Poor information sharing

Finally, poor information sharing is actually the root cause of many troubles. Most cases of wrong zone number, mixed-in arbitrary coordinates, misidentified control points, unit mismatch, leftover rotation, and duplicate transformations could have been prevented if necessary information had been properly shared. Thus, poor sharing is both an independent cause and an entry point that induces other causes.

Poor information sharing takes many forms: stating only “JGD2011” without the zone number, failing to distinguish original and working files, omitting whether arbitrary coordinates were used, not specifying units, not indicating which control points were adopted, giving only drawings without coordinate lists or result tables, and so on. The recipient must guess missing information, and when those guesses are wrong, coordinate mismatches occur.

Detect this by focusing on the lack of handover materials rather than the drawing itself. When the cause is not apparent the moment you open the file, suspect poor information sharing. If evidence to judge correctness is missing, if you must inquire to learn the assumptions, or if explanations vary among people, the problem is information management rather than coordinates. On-site discrepancies are the result; the real cause is inadequate design of information sharing.

The remedy is to standardize a minimum handover template listing necessary information. At a minimum, share the adopted coordinate system, zone number, units, control point information, whether arbitrary coordinates were used, whether rotation or translation was applied, original file name, creation date, creator, and reference materials. Even just sharing these items prevents many problems. Circulating drawings alone is particularly dangerous for data like JGD2011 where assumptions are critical.

Countermeasures for poor sharing also involve the recipient’s checking procedures. Upon receipt, immediately perform control point checks and confirm any doubts early. If problems surface later in the process, the impact spreads to drawing corrections, quantity recalculations, site re-surveys, and re-sharing. Refusing to accept incomplete handover materials reduces overall rework.

How to organize operations to prevent recurrence of JGD2011 shifts

We have covered seven causes, but the crucial point in practice is not to stop at individual remedies. If operations do not change, the same problems will recur even after fixing an issue. To handle JGD2011 stably, you need mechanisms across site and office, surveying and drafting staff, prime and subcontractors to align the assumptions about coordinates.

First, define originals. Clearly separate which files are the public coordinate originals, which are working files in arbitrary coordinates, and which are processed for delivery, and do not overwrite files with the same name. Ambiguous originals lead to someone editing a file for appearance and that edited file becoming treated as the standard, causing duplicate transformations and sharing problems.

Next, establish control point checks at project start. Simply adopting a habit of verifying at least two known points immediately upon receiving drawings will catch many wrong zone numbers, mixed-in arbitrary coordinates, and leftover rotations early. Delaying this until later means corrections after drawing work and quantity calculations increase costs dramatically.

Also, keep a history of transformations. If you record which data was transformed, for what purpose, and under what conditions, future reviewers can judge correctly. Without history, you must rely on individual memory, which almost certainly causes confusion in long projects. In coordinate work, traceability is more important than just matching the appearance.

On-site verification measures are also important. Checking alignment solely on drawings can miss discrepancies with actual positions. Having a system to quickly confirm control points or known points on site makes it easier to detect mismatches at the drawing stage. Especially for tasks where positional accuracy matters—such as construction and as-built verification—connect drawing-level and field-level consistency.

When you want to streamline on-site checks, consider using an iPhone-mounted high-precision GNSS positioning device such as LRTK. When you want to verify on site based on JGD2011 or public coordinates, such a device lets you quickly compare drawing control points and management points with site positions. This makes it easier to verify CAD data assumptions in the practical workflow, enabling early detection of coordinate discrepancies and reducing rework. Rather than trying to solve problems only by editing drawings, think of coordinate operations including on-site verification to reduce JGD2011 troubles.

Summary

The causes of JGD2011 not matching in CAD cannot be dismissed as mere software setting mistakes. In practice, misalignments of assumptions—wrong zone numbers, mixed-in arbitrary coordinates, misidentified control points, unit mismatches, leftover rotation, duplicate transformations, and poor information sharing—often occur in combination. Moreover, fixes that only match the appearance temporarily will inevitably recur in later processes.

What matters is isolating the cause from how the misalignment manifests. Whether the whole set shifts uniformly, the orientation is tilted, distances change, or only particular points mismatch, different items should be suspected. And confirming not only the drawing but also control point results, coordinate lists, transformation histories, and handover documents leads to the quickest resolution.

To handle JGD2011 correctly, confirm the correct zone number, clarify differences from arbitrary coordinates, verify control points with multiple points, manage units and transformation histories, and align shared information. Because coordinate errors have large downstream impacts, do not resort to ad hoc fixes after a problem occurs; instead, establish operations that make recurrence unlikely from the start.

If you want to make JGD2011 operations more reliable including on-site and drawing alignment, consider incorporating measures such as an iPhone-mounted high-precision GNSS positioning device like LRTK, and strengthen verification flows based on public coordinates. By operating with on-site verification rather than confining processes to CAD, you can practically reduce worries about JGD2011 not matching.