How to Plot CSV Latitude and Longitude Points Online

If your CSV already has latitude and longitude columns, you do not need geocoding to make a quick map. You need a viewer that can read the coordinate columns, skip invalid rows, show approximate bounds, and draw the points without changing the original file.

BaseToolbox has a CSV Map Viewer for that exact workflow. Paste a small sample or open a CSV file in the browser, choose the latitude and longitude columns, and preview the points on a 3D globe without uploading the file to a server.

Quick Answer

To plot CSV latitude and longitude points online, use a browser-local CSV map viewer, select the latitude column, select the longitude column, preview the rows, and check skipped rows and bounds before sharing or importing the data elsewhere. If the points appear in the wrong country, first check coordinate order, signs, and invalid values.

When a CSV Map Preview Is Enough

A CSV preview is useful when the file already contains coordinates. Common examples include:

• store, office, or asset locations
• field survey points
• delivery stops
• sensor positions
• city or airport examples
• exported spreadsheet rows with lat and lng columns

This is different from address geocoding. If the CSV only has street addresses, city names, or postal codes, a local viewer cannot magically place them on a map without a geocoding service. For privacy-sensitive data, that distinction matters. Coordinates can be previewed locally; address-to-coordinate conversion usually requires an external data source.

Prepare the Columns First

Before mapping, make the coordinate fields obvious. Use clear headers such as:

Purpose	Good column names
Latitude	lat, latitude, y
Longitude	lon, lng, longitude, x
Label	name, label, title, city

Latitude values should usually be between -90 and 90. Longitude values should usually be between -180 and 180. Empty cells, text values, swapped columns, and accidental zeros can all produce a misleading map.

If the viewer auto-detects the wrong columns, override the selection manually before trusting the preview.

Latitude-Longitude vs GeoJSON Order

CSV files are often written as latitude, then longitude because that is how people say coordinates in conversation. GeoJSON uses the opposite order: longitude, then latitude.

For CSV mapping, a row might look like this:

name,latitude,longitude
San Francisco,37.7749,-122.4194

In GeoJSON, the same point would be written as:

[-122.4194, 37.7749]

Do not copy a GeoJSON coordinate pair into CSV without checking which number belongs in which column. A swapped pair can still be numeric, so the file may parse correctly while the point lands on the wrong side of the world.

Check Bounds Before You Share the Map

Bounds summarize the minimum and maximum latitude and longitude found in the valid rows. They are one of the fastest ways to catch bad data.

For example, if a CSV of London office locations produces bounds that include latitude 0 and longitude 0, one row may contain missing values that became 0,0. If a city-only dataset covers multiple continents, you may have a swapped coordinate, a mistaken sign, or a row from a different export.

Also check the skipped-row list. A few skipped rows may be fine during exploration, but a high skipped count usually means the header names, delimiter, decimal format, or coordinate columns need cleanup.

Keep Sensitive Location Data Local

CSV map files can contain sensitive information even when they do not include names or emails. Coordinates may reveal customer addresses, future store locations, equipment positions, or delivery patterns. Labels and notes can also expose internal IDs or business context.

A browser-local preview reduces that risk because the file is read with browser APIs and the coordinates are rendered locally. Still, you should treat screenshots and exported images as data too. If the map shows private points, do not paste the screenshot into public tickets, docs, or chat channels without review.

When to Use CSV, GeoJSON, or a Generic 3D Map Viewer

Use the CSV viewer when your data is a spreadsheet of points. It is simple, fast, and easy to explain to non-GIS teammates.

Use a GeoJSON globe viewer when your data contains lines, polygons, feature properties, or nested geometry. GeoJSON is better for routes, service areas, boundaries, and multi-shape map layers.

Use the 3D Map Viewer when you want one place to try a small CSV or GeoJSON layer and compare how the format behaves on the same globe.

Safe CSV Mapping Checklist

1. Start with a small sample.
2. Confirm the delimiter and headers parse correctly.
3. Select the latitude and longitude columns.
4. Check valid points, skipped rows, duplicates, and bounds.
5. Look for values outside the normal coordinate range.
6. Verify that points appear in the expected country or region.
7. Export a screenshot only if the points are safe to share.

Quick Answer Revisited

If you have latitude and longitude columns, plotting a CSV online should be a local preview task, not a data upload task. Map the coordinate columns, check skipped rows and bounds, verify the location visually, and only then decide whether the data is ready for a dashboard, GIS workflow, or public map.