CSV to GeoJSON Converter

Convert CSV files with latitude/longitude columns to GeoJSON point features for mapping.

Tested tool guide Tested browser tools Checked August 16, 2026

What CSV to GeoJSON Converter does and how it behaves

CSV to GeoJSON Converter turns rows that already contain latitude and longitude into GeoJSON point features for mapping. It reads the coordinate fields from the table and places each pair in a Point geometry, producing structured geographic JSON rather than another table. It does not geocode postal addresses; the CSV must already supply coordinates. The common surprise is axis order: source columns are often described as latitude/longitude, but a GeoJSON position is written longitude first, then latitude.

How the result is produced

Coordinate mapping

The conversion needs one latitude field and one longitude field. For each row represented as a point, longitude becomes the first number in geometry.coordinates and latitude becomes the second. GeoJSON uses decimal-degree WGS 84 positions, so projected coordinates such as easting and northing are not interchangeable with longitude and latitude.

Feature output

A Point geometry represents one location, while its containing Feature provides the geographic object consumed by GeoJSON-compatible mapping software. The generated point features are collected into the converter's JSON result. Processing occurs in the browser, so coordinate records do not need to be uploaded to a conversion service. Copy or save the result for use elsewhere.

Good uses

Turn a spreadsheet of sensor stations with existing latitude and longitude fields into point data for a web map.
Prepare store, venue, or field-survey coordinates for software that accepts GeoJSON.
Convert an exported CSV of GPS observations into JSON that can be inspected or versioned with other mapping data.

Limits and checks

Confirm the output axis order is [longitude, latitude]. Reversing the values can place a valid-looking point on the wrong continent or outside latitude's valid range.
The converter is not an address geocoder. A street, city, postal code, or place name without numeric coordinates is insufficient.
Check the coordinate reference system and units first. Projected eastings and northings, radians, and degree-minute-second text do not become WGS 84 decimal-degree positions merely by being wrapped in GeoJSON.

Common questions

Will it geocode an address-only CSV?

No. It builds points from coordinate columns already present in the table. Use a geocoding step to obtain latitude and longitude first, then add those values to the CSV. Review the geocoder's match quality before conversion because a syntactically valid coordinate can still identify the wrong location.

What coordinate order should I expect?

GeoJSON writes a two-number geographic position as [longitude, latitude], even when a CSV presents latitude before longitude. For example, latitude 40 and longitude -75 correspond to coordinates [-75, 40]. This ordering is required by the GeoJSON format and is a frequent cause of swapped or misplaced points.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.