Good call on the changelog being front and center, moving it a bit further down now.
Thanks! UK/EU geocoding may or may not happen in the future :)
1,174 karma · joined June 29, 2012
http://github.com/MiniCodemonkey bsky.app/profile/codemonkey.io
Interests: DevOps, Entrepreneurship, Hardware, Laravel, Remote Work
Good call on the changelog being front and center, moving it a bit further down now.
Thanks! UK/EU geocoding may or may not happen in the future :)
Example:
./some_script.sh; curl https://nudge.sh/YOUR_TOKEN
Just need to register your phone number at nudge.sh to get a token (don’t worry, your data is safe and not shared with anyone or used for any other purpose)
Edit: typo
1. We decided to use geolocation because it removes one more form field. It also makes it easier to expand to additional countries (https://github.com/MiniCodeMonkey/curbside/issues) we may reconsider in the future.
2. Happy to explore adding additional ways to tackle the problem. For now, we just have a simple map of stores to visualize coverage: https://curb.run/stores
Fixed the typo. Thanks!
We realized that curbside pickups is a great compromise for everybody's health and safety right now.
We built Curb Run because we found it very difficult to get a curbside pickup slot at our local Wegmans. Willing to drive a bit further away to another location, I hacked together a little script that would check for pickup slots across multiple stores in a radius.
Fast forward, friends and family started hearing about this and asked if we could help them too. We ended up turning this into a web app for everybody to use -- and with many more stores and chains across the US.
We hope that this can help you as well!
The idea was to make the API curl as simple and short as possible, to the point where you could probably memorize it. Would be trivial to then add additional notification targets server-side, based on user preference.
I.e. sending a Slack message -- even in the simplest form requires a rather long URL with a JSON body that has a couple of fields.
Goal for us is KISS. Keeping everything as simple as possible -- both in terms of infrastructure, ease of use and cost.
Primary we're using Metabase in front of multiple MariaDB instances. Metabase is absolutely fantastic!
We also have a couple of additional small projects:
- A small Node.js app that receives events live via fluentbit, saves them off in MariaDB and sends text message notifications via Twilio when certain thresholds are exceeded
- A small "ETL" app that polls the Stripe and QuickBooks API to mirror data in a MariaDB database so we can easily access it from Metabase
Here’s a couple of options:
geocode.earth -> Worldwide coverage
geocod.io -> US/Canada only, but supports spreadsheets, data appends and batch geocoding
smartystreets.com -> Ideal for USPS address verification
Disclaimer: I’m the co-founder of Geocodio
> ./provision
provision usage:
./provision environment role [hostname]
This script will provision the given role in the specified environment using Ansible
If a hostname is specified, provisioning will be limited to that specific serverHere’s an older video with some interesting details: https://m.youtube.com/watch?v=KX_0c9R4Fng
The Pi Zero really has an awesome form factor, but many of the projects I come up with either require more performance (i.e. needing a Rasperry Pi 3) or are simply better suited for a microcontroller such an ESP32 or ESP8266.
1x Raspberry Pi 3 running Home Assistant with a Z-Wave USB Dongle (Home Automation)
1x Raspberry Pi 3 running OctoPrint (Host/remote-control for 3D Printer)
1x Raspberry Pi 3 running FullPageOS (Full-screen Chromium in kiosk mode) displaying a server statusboard in our home office
Next project: 1x Raspberry Pi Zero W to run Unifi Controller
I have a couple of original Model B+ sitting around unused right now - just not powerful enough for any of the above projects.
(Update: Formatting)
Forward Geocoding (Converting the addresses to latitude/longitude): https://gist.github.com/MiniCodeMonkey/13c02d45089478182c3d1...
Reverse Geocoding (Converting the lat/lon to addresses): https://gist.github.com/MiniCodeMonkey/13c02d45089478182c3d1...
Based on the above definition, geocod.io's accuracy for reverse geocoding of this list is 95.2%
Putting this together with dbatten's original findings, the list would look like this:
Google: 97% ($4 per 1,000)
Geocod.io: 95.2% ($0.50 per 1,000)
Mapbox: 95% ($0.50 per 1,000)
TomTom: 73%
As of Monday, both co-founders are working on it full time as a fully bootstrapped business.