Map snapshot PNG. Apparently, LLM is quite competent when reading map images. It can say, “Oh, that's not all London coverage.” “ “Oh, this and this street is a problem (without having street data).”
Plus one. (I’m the author of GeoSQL.) This is why I personally store data in local PostGIS. The whole map harness is running locally, except for Claude. I did not write SQL since April. I am making 1-2 analytics projects per week.
Thanks for sharing, and thanks for making the video you shared. A couple thoughts. Is PostGIS king in this area? I've been liking duckDB as it does not require a server. Is there a good alternative to PostGIS in the duckDB world? Maybe just plain GeoParquet files read in through duckDB?
In the example in your video are any special GEOMETRY functions being used in the underlying SQL? Or, could your data just have been in plain postgres?
A similar product GeoSQL is Malloy which puts a semantic layer on top of your data for better LLM understanding. Malloyyo gives you an MCP server for precise and auditable interaction with your data.
I’ve been working on a backend for Kepler.gl and testing it with public datasets from BigQuery. I thought it might be interesting for the HN audience to see what kind of free spatial datasets exist in BigQuery marketplace and how they can be visualised.
That said, some of the skill frameworks like gstack created 10x productivity gain for me. IMO, worth sharing here.