How to Map CSV Data with Lat/Long Coordinates Online

If you have a spreadsheet full of coordinates — store locations, survey waypoints, delivery addresses, or sensor readings — turning that data into a map should take seconds, not hours. GeoDataTools lets you drag a CSV file onto an interactive map viewer and see all your points instantly, with zero setup, no account, and no data leaving your browser. This guide explains how to map CSV lat/long data online and how to get the cleanest results from your spreadsheet.

Why Map CSV Data?

Coordinates locked inside a spreadsheet are hard to reason about. Mapping them reveals patterns that rows and columns hide: which delivery routes cluster together, where field survey gaps exist, how store locations relate to demographics, or whether event check-ins concentrate in a particular district. Practical use cases span nearly every industry:

• Retail and logistics: Plot store locations or depot addresses to audit geographic coverage and identify underserved areas.
• Field surveys: Visualize GPS waypoints collected during environmental assessments, infrastructure inspections, or agricultural surveys to spot sampling gaps.
• Events and marketing: Map registration or check-in data to understand attendance geography and plan future venue selection.
• Last-mile delivery: Drop a daily delivery manifest onto a map to sequence stops visually before loading a route planner.
• Research and journalism: Quickly validate geocoded datasets before publishing or sharing with collaborators.

In every case, the workflow is the same: export your data as CSV, open the GeoDataTools map viewer, and upload the file. No GIS software installation required.

What CSV Format Does GeoDataTools Support?

GeoDataTools auto-detects coordinate columns by scanning your CSV header row for common naming conventions. Your file needs at least two numeric columns containing WGS 84 decimal-degree coordinates (the format produced by GPS devices, Google Maps, and most geocoding services).

Recognised latitude column names (case-insensitive): lat, latitude, y

Recognised longitude column names (case-insensitive): lng, lon, long, longitude, x

Every other column becomes a feature attribute — visible in the pop-up when you click a point on the map and queryable in the attribute table. Useful optional columns include:

• name — displayed as the pop-up title
• description — shown as body text in the pop-up
• Any domain-specific fields: category, status, timestamp, value, etc.

A minimal valid CSV looks like this:

name,lat,lng,category
Central Depot,51.5074,-0.1278,logistics
East Hub,51.5155,-0.0726,logistics
West Store,51.4913,-0.1955,retail

Files must use comma, semicolon, or tab as the delimiter. UTF-8 encoding is recommended; UTF-8 with BOM (common from Excel) is also handled automatically.

Step-by-Step: Upload and Visualize Your CSV

Mapping your CSV data takes under a minute:

1. Open the viewer. Go to GeoDataTools map viewer. No account or sign-in is required.
2. Upload your file. Drag your .csv file onto the map canvas, or click the upload button and browse to your file. The parser runs entirely in your browser — your data is never sent to a server.
3. Review the detection summary. A panel shows the detected latitude and longitude columns, the total feature count, and a warning for any rows skipped due to missing or non-numeric coordinates.
4. See your points on the map. All valid rows appear as markers clustered by zoom level. The map auto-fits to the bounding box of your data so every point is immediately visible.
5. Click any feature. A pop-up opens showing all attributes for that row — every column from your CSV is listed. Use this to verify that properties imported correctly.
6. Explore and filter. Pan, zoom, and use the attribute table panel to sort or filter your dataset. You can highlight a subset of features based on any column value.

That is the complete workflow for a quick visual check. If you need to share the result or use the data in another GIS tool, the next section covers exporting to GeoJSON.

Converting CSV to GeoJSON

GeoJSON is the web standard for geographic data and is accepted by Leaflet, Mapbox, QGIS, ArcGIS Online, and dozens of other tools. Converting your CSV to GeoJSON preserves all attributes and produces a single portable file you can reuse across projects.

Use the dedicated CSV to GeoJSON converter for a standalone conversion without loading the full map viewer:

1. Open the CSV to GeoJSON converter.
2. Drop your CSV file onto the upload area. The tool parses the file, auto-detects coordinate columns, and shows a live preview of the feature count and first few rows.
3. Confirm the detected column mapping. If the auto-detection picked the wrong columns, use the dropdown selectors to correct them.
4. Click Download GeoJSON. The resulting .geojson file contains a FeatureCollection where each CSV row is a Point Feature and all other columns are properties.

Once you have the GeoJSON file you can:

• Drag it back into the GeoDataTools map viewer for full interactive exploration.
• Open it in QGIS (Layer → Add Layer → Add Vector Layer) for desktop GIS analysis.
• Load it into a Mapbox GL JS or Leaflet map as a data source for a custom web application.
• Upload it to ArcGIS Online, Google Earth, or any other GeoJSON-compatible platform.

Browse all converter tools for additional formats including KML, Shapefile, and TopoJSON.

Tips for Clean CSV Data

A few preparation steps will prevent the most common import problems and give you cleaner results:

• Use standard column names. Rename custom column headers like GPS_North or coord_y to lat and lng before uploading. This guarantees auto-detection works without manual adjustment.
• Use decimal degrees, not DMS. Coordinates must be in decimal-degree format (e.g., 48.8584), not degrees-minutes-seconds (e.g., 48°51'30"N). Convert DMS to decimal degrees before exporting: decimal = degrees + minutes/60 + seconds/3600, with negative values for South and West.
• Check coordinate ranges. Valid latitude is −90 to +90; valid longitude is −180 to +180. If your values are large integers like 523456 or 4649776, your data is in a projected coordinate system (such as UTM) rather than WGS 84 and needs reprojection first.
• Remove blank rows and header duplicates. Extra blank lines at the end of a CSV export or repeated header rows from merged sheets will produce skipped-row warnings. Clean these in your spreadsheet application before exporting.
• Keep the delimiter consistent. Do not mix commas and semicolons within the same file. If your data contains commas (e.g., an address field), ensure values are properly quoted: "123 Main St, Suite 4".
• Save as UTF-8. When exporting from Excel, choose CSV UTF-8 (Comma delimited) rather than the plain CSV option to avoid encoding issues with accented characters and non-Latin scripts.

Common CSV Mapping Errors and Fixes

Even well-structured CSVs occasionally produce unexpected results. Here are the most frequent issues and how to resolve them:

• All points appear in the ocean or at 0°, 0°. The coordinate columns were not detected, or lat and lng are swapped. Open the column selector in the viewer or converter, manually assign the correct columns, and confirm that latitude values fall in the range −90 to +90.
• "0 features loaded" after upload. Every row was skipped. Likely causes: the header row uses unrecognised column names, coordinates contain non-numeric characters (degree symbols, spaces, commas as decimal separators), or the file is saved with the wrong encoding. Open the file in a text editor and inspect the raw content.
• Fewer features than expected. Rows with empty, null, or non-numeric coordinate values are silently skipped. The detection summary panel shows the skip count. Filter your CSV for blank cells in the lat/lng columns and either fill them in or remove those rows before re-uploading.
• Pop-up shows garbled text or question marks. An encoding mismatch — the file was saved as Windows-1252 or Latin-1 but parsed as UTF-8. Re-save from Excel using CSV UTF-8 (Comma delimited) or convert the encoding with a text editor such as Notepad++ (Encoding → Convert to UTF-8).
• Mixed delimiters — some rows have 3 fields, others have 5. An address or description column contains unquoted commas. Wrap all text fields in double quotes in your spreadsheet before exporting, or use a tab-delimited export and rename the file to .tsv before uploading.
• Map loads but points are clustered in a single country instead of globally. The CSV uses a comma as the decimal separator (common in European locales), turning 48,8584 into two separate fields. Open the file and replace decimal commas with decimal points, then save and re-upload.

If you continue to encounter problems after following these steps, inspect the raw file in a plain text editor to verify the actual delimiter, line endings, and encoding before uploading again.