Tired of seeing ugly maps – Translate Simple JSON into maps

Name: Tired of seeing ugly maps – Translate Simple JSON into maps
Availability: InStock
Author: milind-soni

by milind-soni·Mar 1, 2026·3 points·0 comments

Visit Project View on HN

AI Analysis

●●SolidSolve My ProblemSlick

JSON-to-map compiler with LLM streaming, but Mapbox/Maplibre already own this space.

Strengths

•Streaming JSON updates mean maps render token-by-token from LLM outputs—genuine UX win for AI apps.
•DuckDB SQL widgets query data client-side with viewport-reactive aggregations, no backend needed.
•One spec handles markers, layers, choropleths, legends—reduces boilerplate vs raw Maplibre.

Weaknesses

•Map visualization tooling is crowded (Mapbox, Maplibre, Deck.gl, Folium); JSON abstraction doesn't overcome incumbent lock-in.
•No evidence of adoption or real-world production usage; landing page is marketing without user stories.

Post Description

I am tired of seeing maps that look bad or fighting with the map documentation just to put some simple data on maplibre, I have been working with deckgl for a long time and thought that we dont need the unnecessary boilerplate around the maps to define the most common interactions and widgets, you can infact write it as a simple JSON and render it. Using this in my projects personally, looking for feedback