If you are seeing GIS layers not aligning, take heart: the cause is usually a missing or wrong coordinate system. Check each layer’s spatial reference first, and the fix is often quick.
This page is one part of the wider topic of geospatial terrain visualization, where layers from several providers are often stacked in one view.
| Item | Value |
|---|---|
| Files in the tutorial’s sample shapefile folder | seven files |
| Position where unlocated data tends to appear (Null Island) | 0 degrees latitude and 0 degrees longitude |
| EPSG code found for British National Grid in the tutorial | 27700 |
| Geographic transformation path limit in ArcGIS Pro | two transformation steps |
| Vertical transformation path limit in ArcGIS Pro | four total transformation steps |
| Date the Esri tutorial was last tested | May 20, 2026, using ArcGIS Pro 3.7 |
These figures come from Esri’s tutorial on fixing data that appears in the wrong place and its documentation on datum transformations. They can change as software and data are updated, so check the source before you rely on them.
Why map layers end up in the wrong place
Most misaligned layers trace back to the coordinate system. Esri’s tutorial on misplaced data explains that when data appears in the wrong location, the coordinate system is usually not defined, or is defined incorrectly.
Coordinates on their own are not a location. The same tutorial stresses that latitude and longitude values do not define a place unless you also know which coordinate system the numbers belong to.
Four situations account for most cases:
- The layer has coordinates but no coordinate system, so the software has nothing to position it with.
- The layer has a coordinate system that does not match its numbers.
- Two layers use different geographic coordinate systems, and the needed datum transformation is missing or switched off.
- The map itself uses a coordinate system that makes no sense for the data, so no transformation is available.
A classic sign of a missing definition is data landing at Null Island. The tutorial places it where the prime meridian and the equator meet, at 0 degrees latitude and 0 degrees longitude, and says that data drawing there usually means the layer is missing the metadata that defines its coordinate system (Esri tutorial). Its flood layer drew in the middle of the ocean rather than exactly there, but near enough that the same problem was the likely cause.
How do you check which coordinate system a layer uses?
Read what the layer declares instead of guessing from where it draws. In ArcGIS Pro, the Esri tutorial uses this route:
- Right-click the layer in the Contents pane and choose Properties.
- In the Layer Properties window, click Source.
- Expand the Spatial Reference section and read the coordinate system.
A layer reporting an unknown coordinate system is the prime suspect. For shapefiles, a missing .prj file is a clue: the tutorial’s sample folder held seven files that together make one shapefile, yet none was named FloodAreas.prj, the file that would normally carry the coordinate system information (Esri tutorial).
Check the map as well. The ArcGIS Pro documentation on geographic datum transformations notes that both maps and their layers have coordinate systems, and they are not always the same.
As a diagnostic trick, you can set a map to an unknown coordinate system. Layers then draw without the usual automatic positioning operations, so you can visually compare the raw spatial references of several layers (ArcGIS Pro documentation). Treat it as a temporary lens only, because that documentation says unknown coordinate systems are not suitable for creating, editing, measuring or analyzing data.
Finding the correct coordinate system for a layer
When a layer has no definition, the job becomes research. Start with whoever supplied the data: in the tutorial, the colleague said the layer was a subset of a larger dataset from the Environment Agency (Esri tutorial).
Then work through the provider’s pages:
- Open the data item page and search for the words coordinate system, spatial reference and projection.
- If that page is silent, follow its link to the provider’s data platform and search there too.
- Expand any spatial information section and look for a coordinate reference system link or code.
In the tutorial, the item page mentioned no coordinate system, and the first platform page lacked the keywords as well. Only a spatial information section further down listed a coordinate reference system link ending in 27700 (Esri tutorial).
That number is an EPSG code. EPSG stands for European Petroleum Survey Group, which publishes a database of coordinate system information, and the tutorial says a four- or five-digit EPSG number is most likely the identifier code. Opening the link showed the name British National Grid three times, so 27700 was probably the coordinate system of the flood data (Esri tutorial).

Define Projection or Project: which tool fixes it?
The two tools sound alike but do different jobs. Define Projection overwrites the coordinate system information stored with a dataset, and Esri intends it for datasets whose coordinate system is unknown or incorrect (tool reference).
It changes the label, not the shapes. Its documentation says it does not modify any geometry, and that to transform geometry into another coordinate system you use the Project tool instead (tool reference).
In the tutorial, assigning British National Grid to the flood layer moved the data out of the ocean. It then drew on either side of the Humber estuary on the east coast of England and aligned with the basemap (Esri tutorial).
Protect yourself before overwriting a layer you believe is wrongly defined. Write down the original coordinate system first, because undoing the tool means running it again and redefining the original one (Esri tutorial).
The tool reference also lists limits worth knowing:
- If the input already has a known coordinate system, the tool issues a warning but runs successfully.
- Defining a coordinate system is not supported for a feature class in an enterprise geodatabase that has existing records.
- It is not supported for a feature class inside a feature dataset, because the feature dataset determines the coordinate system for all feature classes in it.
When a datum transformation is the real culprit
If both layers are correctly defined yet still sit apart, look at the datum transformation. Esri describes it as a calculation that converts between geographic coordinate systems so data is properly aligned, and ArcGIS Pro applies one automatically whenever a layer’s geographic coordinate system differs from the map’s (transformation documentation).
A transformation affects drawing only. The data itself is not changed, and none is needed when layers differ in projected coordinate system but share the same underlying geographic one (datum transformation overview).
To inspect what is happening, open the Transformation tab in Map Properties. It lists the layers’ coordinate systems, the map’s, and the suggested transformations, and you can choose a different one from the Transformation path menu (transformation documentation).
For troubleshooting, you can temporarily choose Do not transform to confirm that a transformation explains the gap. Keep in mind that your data will not necessarily align properly while it is on (transformation documentation).
If you know a transformation is required but none is offered, the same page suggests three explanations:
- The map’s geographic coordinate system has no spatial overlap with the data’s, which usually means the map is not in a coordinate system that makes sense for the data.
- The path between the two systems is too complex: in the documentation, a geographic path is limited to two transformation steps, and a vertical path allows up to four total steps.
- The needed transformation requires a file that is not part of the ArcGIS Pro installation and must be installed separately.
Basemaps can skew the suggestions too. A map with a basemap has a global extent, and ArcGIS Pro offers an option to ignore basemap extents when listing and automatically choosing transformations (transformation documentation).
On-the-fly alignment is handy for exploring, but it costs drawing performance and accuracy. Esri recommends one coordinate system for the map and all its data, using the Project tool for vector data and the Project Raster tool for raster data (datum transformation overview).
A repeatable checklist for misaligned layers
Work from the cheapest check to the most involved one:
- Zoom to each layer and note where it lands: near Null Island, on the wrong continent, or only slightly offset.
- Read each layer’s spatial reference in its properties, and note the map’s coordinate system.
- For an unknown definition, research the provider’s metadata for an EPSG code.
- Record the original definition, then apply Define Projection and check the result against a trusted basemap.
- If definitions are right but layers still differ, review the Transformation tab.
- Where practical, use Project so that everything shares one coordinate system.
If your file is a scanned map or image with no real-world coordinates at all, the problem is a different one, and georeferencing in GIS is the place to look. If terms such as layer and spatial reference are still unfamiliar, a primer on what is GIS will make the steps above easier to follow.
Frequently asked questions
Why does my layer appear in the ocean off West Africa?
Show answer
It most likely carries coordinates but no declared coordinate system. The Esri tutorial treats that as the probable cause of its flood layer sitting there, and the layer moved to England only after the correct system was assigned (Esri tutorial).
Does Define Projection reposition my features?
Show answer
Not by itself. The tool edits the stored definition and leaves geometry as it was, so recalculating coordinates is a job for Project (tool reference).
Is it fine to leave transformations switched off?
Show answer
Treat that setting as a short diagnostic switch. With it on, ArcGIS Pro warns that layers will not necessarily align (transformation documentation).
Can I measure distances in a map with an unknown coordinate system?
Show answer
It is not advisable. The Measure tool returns unitless planar quantities only, and Esri says the internal units cannot be considered true meters, so no measurements or calculations should rely on them (ArcGIS Pro documentation).



