JSON Records to GeoJSON Converter
Convert records with latitude and longitude columns into a GeoJSON Point FeatureCollection with preserved properties.
Your input is sent to this site only after you choose Convert on server. The conversion runs for this request and no history is saved. Upload up to 4 MiB combined; Office files have a 2 MiB limit.
Enter your text
Edit the example text or paste your own content.
Choose your options
The defaults work for most files. Change a setting only when you need to.
How to use JSON Records to GeoJSON Converter
- Load the working example or provide your own input.
- Review the format options, then select Convert on server to process the input.
- Check the result and download the output file.
What this tool does
Prepare location records for a mapping tool that accepts GeoJSON. Select the top-level property names containing latitude and longitude. Each record becomes a Point feature using the required longitude-first coordinate order, while its other properties remain available for labels or styling. The output is a FeatureCollection that can be downloaded with a GeoJSON extension.
Supported formats and limits
Coordinates must be finite numbers or plain numeric strings, with latitude between minus ninety and ninety and longitude between minus one hundred eighty and one hundred eighty. Missing or invalid coordinates reject the conversion instead of silently dropping records. This assumes geographic longitude and latitude and does not reproject a grid coordinate system or geocode addresses. Input must be an array of at most ten thousand objects with bounded JSON depth and safe integer values.
Example input
[{"name":"Kyiv","lat":50.4501,"lon":30.5234},{"name":"Bratislava","lat":48.1486,"lon":17.1077}]What should I check before using the result?
Coordinates must be finite numbers or plain numeric strings, with latitude between minus ninety and ninety and longitude between minus one hundred eighty and one hundred eighty.
Is input uploaded?
This tool sends input to this site’s conversion API after you select Convert on server. Files use bounded workers and, when needed, private temporary folders deleted after processing or cancellation. No conversion history is saved. The converter does not upload files to a third-party conversion service.