Update on the TN 911 Database

May 23, 2025 | 911, postgis, QGIS

After not saying much up here for the last month – here’s an update on the TN 911 Database.

To catch you up if you don’t know – Tn has a NG911 setup and generally 97% of everyone is running ESRI Arc Something to input data. A few years ago I moved one county over to QGIS/PostGIS/Geoserver. Then a second county over to QGIS/PostGIS. By the time the second county had happened I had started moving some of this to github because there’s no way this turns into a thing and will just be a one off project.

Now I’m talking to county #3. Which now brings me to “things I have learned”. I should do that in bigger bolder letters.

  • I’m offering a cloud hosted solution. The Computers I run into aren’t the most optimal things in the world. It’s probably going to have an average $600 dollar a year prices tag (You mileage – errrr – bill may vary). Do you have to do it? No. Will it make everyone’s lives better? Yes.
  • I’ve been avoiding setting up default menus. I’m setting up default menus. I’ll include this as a part of the github repository.
  • I’m expanding the wiki.
  • So as part of the “default” menus I built a table to hold all the road types. There’s probably over 200 road types in the USPS standard. If you look at any county you really only have about 20 to 30 road types. So I’m going to provide a sql script to generate a road type table for your county that we can load and not scroll through 200+ road types. I did that for a lot of things and not just road type – but type is the easiest thing to show off.
  • I wasn’t including the new export methodology in the github repo but I’m going to – I just have to clean it up a bit and….write more stuff in the wiki
  • Bug fixing – Had a trigger that wouldn’t restore on a pg_dump and two scripts that had somehow stopped working properly.

So it’s really turning into a things and with ESRI’s move to “named licenses” I have more noise about alternative data solutions. If I get client #3 my new goal is for Client 4 and 5.

Until next time – I’m knee deep in Spatial SQL and possibly some python – but more on that later.

You may also like

The Trail Map – Part 1

The Trail Map – Part 1

A few posts ago I babbled about cartography. I've never had the patience for Cartography mainly because two things usually happen...well three things: the map can't be bigger than 8x11 the map must have everything on it Make the map however you want except we will...

My So called Life as a Map Maker

My So called Life as a Map Maker

I can sum it up: It's not much of one. Way back in my younger days I was infatuated with ArcPlot (which was the plotting portion of ArcINFO). From there I moved to Arcview, ArcMap, and eventually here to QGIS. All of my work typically revolves around Data. I usually...

Tricks with an ESRI File Geodatabase

Tricks with an ESRI File Geodatabase

A few years back I jumped in way over my head with QGIS/Postgis. I had moved a process out of one software and into my favorite two (QGIS/PostGIS) and little did I know the final output had to be a ESRI File Geodatabase. So what did I do? I shamed them into using a...