Built because the old way was daft.
Finding the data behind a public web map was a pain even for me, and I do this for a living.
The routine went like this. Open developer tools. Watch the network requests scroll past. Guess which one is the service. Copy it. Clean up the URL. Paste it into QGIS and hope. If it did not work, go back and guess again.
Every GIS person I know has done this, and every one of them has lost an afternoon to it. The information was never hidden, exactly. The map drew itself with it, right in front of you. It was just buried under a pile of requests that nobody should have to read.
So I built Geo Hound to make that automatic. Browse the map, and the services are just caught, saved with their metadata, and formatted for QGIS or ArcGIS Pro. No developer tools. No guessing.
Then the idea grew
The detector was for people like me: GIS people who want the data in their own software. But that is not who most web map visitors are.
Most people looking at a public web map will never install QGIS. Not because they are not smart enough, but because desktop GIS is a cliff, and their question is small. Which district has the most consented wells? How far is this from that? Is my place in the flood zone? They are staring at a map that contains the answer and cannot ask it anything.
So instead of only helping GIS people take data back to their software, why not bring the GIS to where people already are? We built a workbench into the browser: real layers, a real attribute table, real analysis. Then we put an assistant on top of it, so you can ask a map a question in plain English and get an answer and a map back.
That is the arc: it started as “help GIS people grab data” and turned into “give everyone their own GIS analyst in the browser”. Both halves are still there, and both are free.
MapScaping
Geo Hound is a MapScaping product. MapScaping is also the home of the MapScaping Podcast, which has spent years talking to people across the geospatial industry about what they build and why.
A lot of Geo Hound comes out of those conversations, and out of the same frustration turning up again and again in different accents. The tools are good. The data is public. Getting from one to the other is harder than it needs to be.
How it is paid for
The detector and the workbench are free, and there is no account. They do not cost us anything per user, so they do not cost you anything.
The assistant does cost money per question, because it calls a model, so that is the part you can pay for: up to ten free questions a month, and after that credits you buy once that never expire. No subscription. That is the whole business model, and it is on the pricing page with no small print.
There is no advertising, no data selling, and no tracking in the extension. Your browsing is not the product. The privacy policy is written in plain language and says exactly what happens.