Passage Data

Check a file →

Someone sent me a shapefile and I cannot open it

Shapefile (ESRI)

What you are seeing — a consultant, an agency or a colleague sent you a zip, and inside it are files with the same name and different extensions. None of them open in anything you have.

The short answer

Nothing is wrong with the files. A shapefile is not one file — it is a set that only means something together, and your computer has no application registered for any of them.

.shp is the geometry: the points, lines or shapes themselves, and nothing else. .dbf is the table: the rows and columns, and no geometry. .shx is an index that lets a reader jump between records. .prj is one line of text saying what the coordinates MEAN — which country's grid, which datum. .cpg, when it is there, names the character set the text is in.

The two that matter most are the ones people delete. Without the .dbf you have shapes with no information attached. Without the .prj nobody can say where on Earth the numbers point — and a reader that guesses will be confidently wrong by tens or hundreds of metres.

So: keep the whole folder together, and when you send it on, send the zip rather than the file that looked most important.

What to do right now

  1. Zip the whole folder, if it did not arrive as one.
  2. Drop the zip into the viewer to see the shapes and the columns, and to read what coordinate system the file declares.
  3. If you only need the table — the rows and columns, no geometry — the .dbf opens on its own, and LibreOffice Calc reads it for free.
  4. If you need it in Google Earth, take the KML from the viewer.
  5. If you need it as a Darwin Core Archive for a biodiversity portal, the converter reads the same zip.
See what is in it

Drop the zip and read what the file actually contains. Free until 1 September 2026, 00:00 UTC · no account · your rows are discarded after the check.

Open the file you were sent →

Why we can say that

5,064records already published to GBIF
0findings in GBIF's vocabulary
4,268findings from ours
31.7%came back clean

Measured on a file GBIF had already accepted and served — their validator asks will this load, and it had. Every figure is read from ops/data.json, never typed here. We issue no rating and no seal — each finding names the rule it applied.

Related