---
title: "My Maps: Some rows couldn’t be shown – causes and fix — Import Desk"
description: "What the My Maps message Some rows couldn’t be shown means, the usual causes in your spreadsheet data, and how to find the rows responsible."
url: "https://importdesk.io/articles/my-maps-some-rows-couldnt-be-shown-causes-and-fix"
updated: "2026-11-19"
---

[Articles](https://importdesk.io/articles)

# My Maps: Some rows couldn’t be shown – causes and fix

November 19, 2026 · 6 min read

“Some rows couldn’t be shown” is a message people report seeing in Google My Maps after importing a spreadsheet, when some of the rows could not be placed on the map. Google’s Help does not describe this wording, so no one can say the cause is certain. In practice it usually points to the data in those rows: a blank location, a repeated heading row, or coordinates that are swapped or damaged. To find them, compare your sheet with what appeared on the map and check the location columns row by row.

## What does “Some rows couldn’t be shown” mean?

My Maps guides and users describe the message as a sign that part of your file was read but not every row could be turned into a point. The rows that did work appear on the map. The rows that did not are the ones you need to track down.

Because the wording comes from what people report rather than from Google’s Help page, treat it as a symptom, not a diagnosis. It tells you that something in some rows stopped them being placed. It does not tell you which rows or why. The sections below cover the common reasons and how to check for each.

## What usually causes “Some rows couldn’t be shown”?

Google My Maps Help says the file needs a column that holds location information. That can be latitude-longitude values, addresses, place names or WKT geometry. When a row has nothing usable in that column, there is nothing for the map to place. These are the common reasons reported, not guaranteed ones.

### A blank location cell

A row where the address or coordinate cell is empty cannot be placed. This often happens at the bottom of a sheet, where stray empty rows were left behind, or in the middle where someone cleared a cell and forgot about it.

### A heading row repeated in the data

Google says the first row of the file should hold the titles. If the same titles appear again further down, for example because two exports were pasted one under the other, that second heading row contains words where coordinates should be. It cannot be placed.

### Swapped latitude and longitude

If the two values are in the wrong columns, or one pair was typed the wrong way round, the point may land far from where you meant, or may not be placeable at all. A value that is valid as a longitude can be impossible as a latitude, because each has its own possible range.

### Damaged or placeholder coordinates

Coordinates can be damaged by extra text in the cell, a stray symbol, or a value cut short during an export. Another common placeholder is 0,0, which is a real spot on the globe but almost never the place you meant. A row holding it usually means the real coordinates were never filled in.

### Addresses that are too vague

If you are using addresses instead of coordinates, an entry that is only a town name, a partial street name, or a typo may not be specific enough to place. This one is less predictable, so check the address itself rather than assuming.

### A file larger than the limits

Google My Maps Help advises not importing more than 2,000 rows in one file. A layer can hold 2,000 lines, shapes or places, a map can have 10 layers, and the whole map can hold 10,000 lines, shapes or places.

Google does not say what happens to rows beyond 2,000 in one import. People report that only part of a larger file appears, but that is reported, not documented. If your sheet is over the advised size, this could be the reason rows are missing, so it is worth ruling out first.

## How do I find the rows responsible?

Do this in your spreadsheet program, working on a copy so the original stays untouched.

1. Count the data rows in your sheet, not including the heading row.
2. Count the places that appear in the layer on the map. The gap between the two numbers is roughly how many rows were left out.
3. Check the size first. If the sheet has more than 2,000 data rows, the missing rows may simply be the overflow. Split the file into smaller ones and import each as its own layer.
4. Sort or filter by the location column. If you use latitude and longitude, filter each column for blanks. Blank cells will group together, which makes them easy to spot.
5. Look for repeated headings. Search the location column for the column title, such as the word Latitude, appearing in a row other than the first.
6. Scan the coordinate values. Look for text, symbols or words in cells that should hold only a number. Look for any row where both values are zero.
7. Check for swapped pairs. Sort the latitude column from smallest to largest, then from largest to smallest, and look at the extremes. A value that would be impossible as a latitude is a strong hint that the columns are the wrong way round on that row.
8. Check address-only rows. Read the entries that fail and see whether they are specific enough for a person to find on a map.
9. Fix or remove the rows you found, save the sheet as CSV, and import it again.

If the numbers still do not match after those steps, repeat the checks on the rows nearest the gap. Missing rows often sit together, such as at the end of a pasted block.

## Check the import steps as well

Import is done on a computer. Add a layer or open an existing one, choose Import, then pick the columns that hold the location and the title. If you chose the wrong column for the location, many rows can fail at once, so confirm that the column you picked really is the one with coordinates or addresses.

If an import will not work at all, Google suggests checking that the file is in a correct format and allowing [https\://mymaps.google.com/](https://mymaps.google.com/) to open your Drive.

## What should I do once I have found the rows?

Decide for each row whether you can supply the right value yourself. If you know the real address or coordinates, type them in. If you do not, remove the row or move it to a separate list, so the rest of the data imports cleanly. Do not guess a coordinate, because a wrong point on a map is harder to notice than a missing one.

Keep your original file. Make your changes in a copy so you can always go back.

## What if the sheet is too big to check by hand?

Checking a few hundred rows by eye is manageable. Checking thousands is slow and easy to get wrong, and a sheet near the file limit may also need splitting before it will import properly.

[My Maps Splitter](https://importdesk.io/my-maps-splitter) is built for this problem: a location sheet that Google My Maps will not import cleanly. You open a CSV in your browser. It checks that latitude and longitude are plain numbers in range, and sets aside rows with 0,0 and swapped pairs. It accepts rows that have only an address when the address is specific enough. It then exports layer files of up to 2,000 rows each, and lists every row it sets aside along with the reason, so you know exactly which rows to look at.

There are limits. It never looks up, guesses or corrects a coordinate or address, so rows it sets aside are yours to fix. It does not connect to Google, and it cannot promise how My Maps will treat every file. Your original file is kept. You can see a free preview before paying, and the download is a one-time payment.

## Quick checklist

- Does your sheet have more than 2,000 data rows? Split it.
- Is the first row the only heading row?
- Does every row have a value in the location column?
- Are latitude and longitude in separate columns, the right way round, and plain numbers?
- Are there any rows with 0,0?
- Are address-only rows specific enough to find on a map?
- Did you pick the correct location and title columns during import?

For the current limits and wording, check Google’s own My Maps Help page, since it is the source for any numbers that may change.

## Get your location sheet into My Maps, row by row

Your file stays in your browser. You pay only if you download the result.

[Check my file free](https://importdesk.io/app/my-maps-splitter)[About My Maps Splitter](https://importdesk.io/my-maps-splitter)

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "author": {
    "@type": "Organization",
    "name": "Import Desk"
  },
  "dateModified": "2026-11-19T13:02:08.916Z",
  "datePublished": "2026-11-19T13:02:08.916Z",
  "description": "What the My Maps message Some rows couldn’t be shown means, the usual causes in your spreadsheet data, and how to find the rows responsible.",
  "headline": "My Maps: Some rows couldn’t be shown – causes and fix",
  "publisher": {
    "@type": "Organization",
    "name": "Import Desk"
  }
}
```
