Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Geosql: A Claude/Codex skill for geospatial data

github.com

Post reply on HN
Print view View original

21–29 of 29 posts

Re: Geosql: A Claude/Codex skill for geospatial data

#21

Post by willtemperley »

sylveapp wrote: post #18
willtemperley wrote: post #8

Earlier quoted context omitted.

20 year GIS dev here. Looks pretty useful for data exploration. I'd say one of the more compelling GeoAI things I've seen. The problem is there's really a lot of data out there and it's a lot of work to move it around, e.g. between S3 buckets. There's also a ton of GIS SAAS vendors who are pure rent-seekers: I'm looking at a newer offering charging $23 per month for 10GB storage. This has more utility than their offe…

Unrelated, but as someone who is on the verge of also creating another GIS offering do you think there is any value to creating a low cost hosting platform centered around data portability? This came out of frustration with the existing landscape of offerings and I put together something that I wish existed.

Hard to say without hearing what the product is, but personally I'll avoid anything that wants to lock up my data and charge me for it.

Re: Geosql: A Claude/Codex skill for geospatial data

#22

Post by jonash54 »

cpa wrote: post #19

This space is very active. I work at the French mapping agency, and we're currently building MCPs to work with our data. See: https://github.com/ignfab/geocontext (French) Beta MCP instance: https://geollm.beta.ign.fr/geocontext/mcp Unrelated, but also take a look at the nice high-density LiDAR point data we have! https://visionneuse-lidarhd.ign.fr/?px=4441970.281583222&py=...

LOVE the fact that LiDAR is OpenData!

I am currently working on a website https://hillsha.de that makes it easy to download LiDAR las/laz files for almost every place in europe, the US and some other regions. I also made an iOS app for the same use-case, which can render the LiDAR data in 3D and 2D without PDAL and GDAL. It uses a vibe-coded library instead that combines both in native Swift. The iOS app is still in testing but works great.

Implementing France was a lot more comfortable than almost every other country, very well structured metadata and naming conventions. So thanks for that

(i work at the german mapping agency but this is a private project since i just love working with LiDAR hillshades)

Re: Geosql: A Claude/Codex skill for geospatial data

#24

Post by delfrrr »

OtherShrezzing wrote: post #9

>4x improvement on geospatial tasks with map in the loop. The graph shows a baseline 2% task success rate improving to to 8% task success rate, but the evals section details 100% success rates across the board. I'm not sure what the effectiveness of this skill is from the readme. Is it 8% success, or 100% success?

It's not % it's number of evals. Here is how I did evaluation https://dekart.xyz/blog/how-to-evaluate-claude-skill-output-...

Re: Geosql: A Claude/Codex skill for geospatial data

#25

Post by delfrrr »

willtemperley wrote: post #21
sylveapp wrote: post #18

Earlier quoted context omitted.

Unrelated, but as someone who is on the verge of also creating another GIS offering do you think there is any value to creating a low cost hosting platform centered around data portability? This came out of frustration with the existing landscape of offerings and I put together something that I wish existed.

Hard to say without hearing what the product is, but personally I'll avoid anything that wants to lock up my data and charge me for it.

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.

Here is a video explaining roughly how I work now: https://www.youtube.com/watch?v=JCOhkE0rPWA

Re: Geosql: A Claude/Codex skill for geospatial data

#26

Post by delfrrr »

satoyoshidev wrote: post #15

For the maps-in-loop part, what does the agent actually read back from Dekart each round to catch the geometry errors?

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).”

Re: Geosql: A Claude/Codex skill for geospatial data

#27

Post by delfrrr »

minraws wrote: post #5

If I see another skill or markdown on hackernews I might just consider leaving the platform. What even is the point of sharing markdowns... Either LLMs will be so good in a few months this will be redundant. Or it won't be and LLMs are a dead end and there are better ways to build with LLMs

If you check into the docs, skill is the entry point for the map harness for Claude. You need to install the skill and run the Docker image.

That said, some of the skill frameworks like gstack created 10x productivity gain for me. IMO, worth sharing here.

Re: Geosql: A Claude/Codex skill for geospatial data

#28

Post by mrtimo »

delfrrr wrote: post #23

Hey, I'm the author of GeoSQL. Found this thread after realizing the repo got 400 stars last week. Ask me anything.

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.

Re: Geosql: A Claude/Codex skill for geospatial data

#29

Post by satoyoshidev »

delfrrr wrote: post #26
satoyoshidev wrote: post #15

For the maps-in-loop part, what does the agent actually read back from Dekart each round to catch the geometry errors?

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).”

Didn't expect a plain screenshot to be enough for that. Thanks.
Post reply on HN