Copasetic Flow

 Google changed their billing scheme for geocoding in March. Previously, all users were given a $200 credit for Google geocoding per month. Google removed the credit and replaced it with 10,000 geocoding calls per month, and my bill went up! I've known for a while that my pytest code is running every time the QSO tracker is automatically kicked off by github, (which is about 4 times per hour.) Those test cases make seven Google geocoding API calls each. As of April, they mattered. Adding up all the calls assuming that my QSO tracker spots me zero times in a month and that I log no QSOs, so just the calls from the test cases, gives: geocodes runs/hour hours days/month geocodes/month 7 4 24 30 20160 which is well over the free limit. I asked ChatGPT to change my action  so that the test cases would only run when Python files in the repo changed. This was NOT vibe coding. I had to ask ChatGPT to fix its own coding errors 3 times, handing it the error message each time. It did i...

 I released my first Python Package last week! I've been using Datasette to analyze my QSO logs for several months . It's been a really useful tool since it's already setup with quite a bit of mapping fucntionality via various plugins . At the same time, the gang and I have been working with the Google Maps API and kml files to map the paths between amateur radio staions in our QSOs.  A few weeks ago, Simon Willison announced Datasette Enrichments . One of the first exampels was a geocoder (an enrichment that produces the longitude and latitude of an address) using opencage . This opened my eyes to the possibilities of taking the gang's and my original mapping utilities I mentioned above, and implementing them with a number of datasette enrichments and plugins. What was missing however, was a way to do this with Google Maps instead of opencage. Missing until last week that is! The gang and I worked through creating the google maps geocoding enrichment . Then, I worked...