JSON-FG to GeoJSON

JSON-FG to GeoJSON Converter

JSON-FG is an OGC geospatial JSON format that builds on familiar JSON patterns while supporting richer geospatial semantics than classic GeoJSON alone. Convert it to GeoJSON locally in your browser, inspect the map preview first, and export the generated files without uploading anything to a server.

Source Format Guide

What is JSON-FG?

JSON-FG is an OGC geospatial JSON format that builds on familiar JSON patterns while supporting richer geospatial semantics than classic GeoJSON alone.

JSON-FG was created to make JSON-based geospatial exchange more expressive for modern data needs, including cases where classic GeoJSON assumptions become restrictive.

It is appealing to teams that want JSON ergonomics but also need clearer feature typing, more explicit geospatial semantics, and a path beyond older web-only conventions.

Common Workflows

Common use cases

Experimental or standards-driven API payloads.
Data pipelines that want JSON readability but more formal semantics.
Converting modern OGC-aligned datasets into web-friendly JSON form before distribution.

Ecosystem

Where you will encounter it

OGC-aligned experiments and modern API design.
JSON-centric geospatial exchange workflows.
Toolchains that need more semantics than classic GeoJSON.

Strengths

Why teams choose JSON-FG

Keeps the practical benefits of JSON while extending geospatial expressiveness.
Better fit for workflows that outgrow classic GeoJSON assumptions.
Strong option for systems that want modern standards alignment in JSON form.

Limitations

Where JSON-FG gets awkward

Ecosystem support is still narrower than GeoJSON because not every tool reads JSON-FG yet.
Teams may still need a fallback conversion for older clients.
Some users are less familiar with it, which can slow adoption outside standards-aware environments.

File Structure

Common file extensions and sidecar files

.jsonfg

Common extension used to signal that the JSON document follows JSON-FG conventions.

.json

Generic JSON extension sometimes used in practice, though it is less explicit than .jsonfg.

Conversion Rationale

Why convert JSON-FG to GeoJSON?

Teams commonly convert JSON-FG into GeoJSON when they need a web-friendly format that is easy to inspect and debug.

Teams convert JSON-FG when downstream systems only understand older formats such as GeoJSON, shapefile, or KML.
They also convert into JSON-FG when they want a JSON representation with richer semantics than a plain GeoJSON export.
GeoJSON is readable as plain text and widely supported in web mapping libraries and APIs.
It is a practical handoff format when you need to validate geometry and attributes quickly.

FAQ

Frequently asked questions about JSON-FG

How is JSON-FG different from GeoJSON?

JSON-FG keeps JSON-based geospatial exchange but aims to support richer semantics and fewer historical constraints than classic GeoJSON.

When should I use JSON-FG?

Use it when you want JSON ergonomics but need a more standards-driven geospatial model than a simple GeoJSON payload.

Why would I still convert JSON-FG to GeoJSON?

GeoJSON still has broader day-to-day support across web clients and desktop tools, so conversion is often needed for compatibility.

Related Converters

More JSON-FG conversion paths

JSON-FG to GeoPackage

Open, preview, and convert JSON-FG data locally in your browser.

JSON-FG to ESRI Shapefile

Open, preview, and convert JSON-FG data locally in your browser.