Avenza map not referenced means the app cannot read location data from that file until the map is properly georeferenced.
What Avenza Map Not Referenced Actually Means
When this message appears in Avenza Maps, the app is telling you that the file loaded as a map does not carry usable geographic data. The image may look like a normal map, yet the app has no way to match pixels on that image to real world coordinates.
The app checks every custom map as it imports it. It tries to read embedded geospatial tags such as projection, coordinate system, and tie points. If those tags are missing, damaged, or stored in a format Avenza Maps does not understand, the status line under the title reports that the map is not referenced.
In practice this means the blue location dot and any recorded tracks or placemarks cannot sit in the right spot on that map. The map behaves like a picture in a gallery instead of a working navigation layer.
Many users first notice the message when a familiar map from a store or a friend suddenly will not follow their location. The thumbnail still loads, yet the scale bar, grid readout, and cursor do not behave as expected. Treat this message as a warning that the file is safe to view but not safe to guide a hike, a fire line, or a survey task until the reference issue is cleared.
Avenza Map Reference Problems And Common Triggers
This error usually comes from one of a handful of issues. Some start in the desktop software that produced the file, while others relate to how the file moves between devices before import.
- Plain PDF Exported As An Image — Many print layouts from GIS or drawing tools export a flat PDF with no coordinate tags at all.
- Unreadable Coordinate System — Some custom projections and older local grids sit outside the list that Avenza Maps can read cleanly.
- Corrupted Or Stripped Metadata — Email tools, printers, and some cloud services can rewrite or flatten files in ways that remove geo tags.
- Low Quality Scans — A phone scan of a paper map or a screenshot from a website carries no coordinate data until a user adds control points in proper software.
Each of these paths produces a file that looks fine to the eye but fails the silent checks inside the app. That mismatch creates confusion for hikers, survey crews, and field teams who expect the GPS to sit on top of the drawn features.
A quick way to narrow down the trigger is to list every place the file passed through before landing on the phone. Cloud sync tools, office printers, and design teams often export several versions of the same map, and only one of them carries coordinates. Once you learn which export setting or workflow keeps the geo tags inside the file, you can reuse that recipe each season instead of chasing the same error again.
File Types That Do And Do Not Carry Map References
Before spending time on fixes, it helps to know which formats can store proper references for Avenza Maps. The app can handle several common file types but only when they carry geospatial tags set by compatible software.
| File Type | Reference Status | Notes For Avenza Maps |
|---|---|---|
| GeoPDF Or Geospatial PDF | Usually referenced | Best option from many GIS tools when exported with coordinate system and reference map set. |
| GeoTIFF | Usually referenced | Stores raster data and coordinates together; can be shared as custom maps in the app. |
| Standard PDF Or Image (JPG, PNG) | Not referenced | Works only after georeferencing steps in GIS or mapping software that writes new tags. |
When you export from QGIS, ArcGIS Pro, Global Mapper, or similar tools, always choose an option that keeps or creates geospatial tags. If the export dialog lists GeoPDF, GeoTIFF, or a check box for georeferenced output, that option usually gives the best chance of success in Avenza Maps.
Multi page documents deserve extra care. If a print layout exports several map pages inside one PDF, the app may only read reference tags from a single page. Single page exports with a clear map frame often give cleaner results and smaller file sizes, which also speeds up import, tiling, and offline use in the field.
Quick Checks To Fix The Error Inside Avenza Maps
Before rebuilding files, run a few checks on the device. These small steps often clear simple glitches that show the map not referenced banner in the status line even when the file itself is fine.
- Restart The App — Close Avenza Maps from the app switcher, reopen it, and load the custom map again.
- Remove And Reimport The Map — Delete the problem map from the library, then add the same file again from local storage or cloud storage.
- Update Avenza Maps — Open the app store, check for an update, and try again with the new version installed.
- Test On Another Device — Import the same file on a second phone or tablet to see whether the status line still reports that the map is not referenced.
If these checks clear the message, the issue likely came from a short term cache glitch in the app. If the message appears again after each import, the file almost certainly lacks proper georeferencing or uses tags that the app cannot read.
While you run these checks, pay attention to the text under each map title in the My Maps list. Status lines such as active, inactive, and map not referenced give quick clues about both licensing and technical health. Spend a moment tidying old copies and duplicates at the same time so that field staff only carry the latest, trusted versions of each map.
Step By Step Fixes In Your Mapping Software
When the problem sits inside the file, the cure starts in the desktop or laptop tool that produced the map. The exact screens differ between QGIS, ArcGIS Pro, Global Mapper, and other software, yet the main steps share the same shape.
- Confirm The Project Coordinate System — Open the project settings and check that a standard coordinate system such as WGS 84 or a well known local grid is in use.
- Align Layers Before Export — Make sure all layers line up in the map view and share either the same coordinate system or clear transformation rules.
- Set A Reference Map Or Data Frame — In print layouts, choose the map frame that should drive the GeoPDF tags.
- Pick A Geospatial Output Format — Choose GeoPDF or GeoTIFF in the export dialog instead of a flat PDF or simple image format.
- Check Export Options For Geo Tags — Turn on any check box that mentions georeferencing, map frame, or coordinate data in the export panel.
- Test The File Before Sharing — Open the exported map in a desktop viewer that can read coordinates and confirm that the cursor reports sensible lat and lon values.
These steps help the app read the embedded tags on the next import. Once the exported file behaves like a proper GeoPDF or GeoTIFF in other viewers, it usually loads without the error inside Avenza Maps.
Desktop software updates can also change the way geospatial tags appear inside exports. A plugin update or a new major release may add options, change names, or flip default settings. When a map that worked last season suddenly breaks the process, compare the current exporter screen with old screenshots or notes so you can spot any small change that affects the final file.
When You Need To Georeference A Plain Image
Sometimes the only copy of a map is a scan, a photo, or a design file that never carried coordinates. In that case the fix requires georeferencing the image in a GIS tool or in dedicated software that can assign control points.
- Pick A Georeferencing Tool — Use QGIS, ArcGIS, Geographic Imager, or another package that handles control point workflows.
- Add Clear Control Points — Drop pins on corners, grid intersections, or marked coordinates on the image that also appear on a trusted reference map.
- Enter Accurate Coordinates — Type the lat and lon or grid values for each control point from the reference map.
- Choose A Suitable Transformation Method — Select a simple linear or polynomial method that matches the way the paper map was drawn.
- Save To A Georeferenced Format — Export the adjusted image as a GeoTIFF or GeoPDF with the new tags embedded.
Once this process finishes, import the new file into Avenza Maps instead of the raw scan. The new version should carry the tags needed for the GPS to place your location correctly.
Good control points make the difference between a map that only looks straight and one that lines up with GPS to the meter. Wide spacing, clear ticks, and printed coordinate labels all help. If the paper source has blurry edges or stretched folds, spread points across the cleanest areas and drop any that pull the residual error line far away from the rest.
When To Contact The Avenza Help Team
If this warning keeps showing up even after careful exports and tests, the map may rely on a niche projection, a bug in a desktop exporter, or a new coordinate system that the app does not yet handle cleanly.
In that case gather a short bundle of details before you reach out. This set of facts gives the help team what they need to replicate the issue.
- Document The App Version — Note the Avenza Maps version number and the platform and version running on your phone or tablet.
- Record The Export Settings — Write down the coordinate system, output format, and any geospatial options chosen in the desktop exporter.
- Keep A Small Sample File — Prepare a single page or cropped map that still triggers the error so it is easy to share with the help team.
A small log for each project that lists source data, software version, export format, and test results can save hours later. That record turns each clean fix into a repeatable recipe that any teammate can follow again in daily work.
Once the message disappears and the map shows an active status, run a simple field style test. Drop a placemark at a road junction or building, then compare that point with aerial imagery or another trusted map. If lines and symbols agree across tools, you can trust that this copy is ready for offline trips, work orders, and training sessions without the surprise of the avenza map not referenced warning reappearing at a busy moment.
