GeoJSON to SVG Map

Features

• Paste GeoJSON and see it drawn as an SVG map in real time
• Supports Point, LineString and Polygon plus their Multi forms
• Accepts Feature, FeatureCollection and GeometryCollection
• ⚠️ Flips the latitude y axis so north is up (unflipped it looks like a map but is upside down)
• Three projections: equirectangular, Mercator and raw longitude and latitude
• Adjustable stroke colour, fill colour and stroke width; optional vertices and graticule
• Reports the feature count, coordinate count and bounding box
• ⚠️ Raises an error past the coordinate cap instead of freezing the tab
• Copy the SVG source or download a .svg file
• Everything runs in your browser and nothing is uploaded

How to use

1. Paste the GeoJSON into the input box
2. Pick a projection and change the colours or stroke width if you want
3. Tick vertices or the graticule
4. Check the preview plus the feature count and bounding box, then copy or download the SVG

FAQ

Why does the map flip the y axis?

Because latitude grows northwards while the SVG y axis grows downwards, so the two point in opposite directions. Without flipping, the whole map is upside down — and it still looks like a map (the sea is still the sea, the land is still the land), which makes the mistake very hard to catch by eye. The approach here is to negate the projected y, so northern-hemisphere points land in the upper part of the picture.

What is the difference between Mercator and equirectangular?

Equirectangular treats longitude and latitude directly as plane coordinates (`x = longitude`, `y = -latitude`): simplest, but it stretches horizontally at high latitudes (Greenland looks enormous). Mercator applies a non-linear transform to latitude (`y = ln(tan(π/4 + φ/2))`), so local shapes are truer — which is why web maps use it — but it still distorts at high latitudes, and latitude has to be clamped to ±85.0511 (beyond that it tends to infinity). For a small area the two are indistinguishable.

Why does my GeoJSON say there are too many coordinates?

Because it has more than twenty thousand coordinate points. A high-precision border or coastline dataset easily has hundreds of thousands, and drawing them all as `<path>` elements freezes the tab — with no error, just a page that gets slower and slower, which is hard to trace. So there is a cap here, and going past it is reported clearly so you can simplify the geometry first (with something like mapshaper) and try again.

Can the result be used directly as an image?

Yes. What you copy is a complete SVG with `xmlns`, so it can be saved as a `.svg` file, dropped into a web page, or opened in Illustrator or Figma for further editing. It is vector, so it stays sharp at any size.