A Map Image May Need Its Companion Files to Stay Georeferenced
An image can open successfully while losing information needed to place it correctly in mapping software. Before forwarding only the visible picture, ask how the delivered package stores its georeferencing and which companion files the recipient needs. A clean-looking screenshot is not a substitute for that package.
Identify where the positioning information is stored
Esri’s raster documentation explains that image-to-world transformation information may be stored in an image header or a separate world file. Naming conventions can vary. Ask the provider to identify the actual image and its associated files rather than guessing from an extension or renaming them independently. A format that supports embedded information does not prove that every particular export contains the complete information the recipient expects.
Preserve the coordinate-reference context
A world file’s transformation numbers do not by themselves name every coordinate-system assumption needed for the project. Retain the provider’s coordinate-reference, units and related metadata with the package. Confirm which files the intended software actually uses, especially where header information and a companion file could differ. Do not edit values to make an image line up visually or treat an approximate transformation as a verified survey control result.
Check the handoff before using it for a decision
Ask the recipient to open the original package in the intended environment and confirm whether it locates and displays as agreed. Record the delivery version and any unresolved reference issue. If only a picture is needed for a presentation, label that derivative appropriately and preserve the original data separately. The goal is a usable transfer, not a promise that georeferencing establishes accuracy, legal boundaries or the suitability of every measurement taken from the image.
Copyable worksheet
Use one row for each field. Mark unknown information clearly and retain the original records.
| Field | Your note |
|---|---|
| Original image and package version | ____________________ |
| Required companion file names | ____________________ |
| Coordinate reference and units | ____________________ |
| Recipient software and import outcome | ____________________ |
| Derivative-view limitations and unresolved checks | ____________________ |
Worked example
Illustrative example: a fictional manager forwards a JPEG without its accompanying georeferencing files. The recipient can view it but cannot reproduce the agreed map placement. The original package is supplied and its reference information reviewed rather than manually stretching the picture until it appears to fit.