I'm starting a new thread since I now have HTTPS working (thanks @Leyrah for pointing me in the right direction) with the final domain name FlightsForBites.com. Here's the previous thread. I've learned so much on this forum that this project was my way of giving back. I consider it complete. I'll certainly fix bugs and will entertain enhancements. Enjoy!
Now that you're done having fun, I can second the suggestion to covert it to a serverless lambda architecture someone else posted. That will suck any and all joy of programming right outta ya and you'll never attempt this folly again. (grats on getting the SSL plumbing worked out!)
No worries. John Denver one sang, "Some days are diamonds, some days are stone." My interpretation of that is ... "sometimes it just beez dat way" ...
Doesn’t find the following airports or restaurants within 100 miles: DEN, APA, CFO, COS, ABQ, SLC, EGE, SBS…. Definitely doesn’t have all US airports in the database.
It does. As of now, the closest restaurant to DEN is 251 miles away. Try "searching" for "Denver" and you'll see it.
Since the app is crowd sourced and has only been running since August, people have only entered 223 restaurants. Coverage of some areas in the country is thin. Enter restaurants you've been to but don't see! That said, I'm in Destin right now and met a guy by the pool whose from Texas and is a pilot. His favorite restaurant is already in FlightsForBites
I figured out the issue I was having - the www subdomain is not set up and therefor https://www.flightsforbites.com/ doesn't work but omitting the www does. I don't know if @Mahneuvers wants to fix this or not, it's not a huge issue but definitely caught me by surprise. I filled up a bunch of Texas restaurants, especially ones that are ~300mi from KEDC. I'd like to think I contributed to that one
the app isn’t saying there are NO restaurants within 251 miles, it’s saying Denver pilots are a bunch of slackers and haven’t ENTERED any restaurants.
FlightsForBite.com has crossed the 250 restaurant mark! Thanks to everyone for entering their favorite restaurants.
Is there a way to correct or propose corrections to an entry? Or link to a specific restaurant entry? I think Rick's Cafe Boatyard is incorrectly marked as located at 51OK instead of EYE. Also, would it be possible to add a feature to find places in a path between two (or more) airports? would be nice to plan stops when flying long cross countries with a fuel stop AND food stop!
Post here or send an email to the address mentioned on the site. I'll fix Rick's. You can find the restaurants close to a course comprising of up to four airports. Just separate the airport codes with commas.
Rick's Cafe Boatyard was actually associated to both airports likely b/c both airport names contain "Eagle Creek". I deleted the 51OK record. Thanks for pointing this out. If this turns out to be a common issue I'll update the UI to allow people to change the airport associated with a restaurant.
Share it wherever you'd like. The more pilots crowd sourcing the better the data will be for everyone.
One of the guys on one of the FB groups made an excel sheet w Michigan airport restaurants… I’ll see f I can find it! THANK YOU SO MUCH FOR YOUR EFFORTS!
And you would also likely be no longer reachable, driven insane by the endless "feature requests" from your "testers".
The site reflects the first airport database I found. Didn't really think about it until someone raised the issue in the original thread. I could try to find a mapping table and convert. The easiest path forward was to put on the find page instructions to omit the K.
mapping table? cant you test the length of the input, and if it's length 4 and starts with K, only use characters 2-4 as your search term? IIRC the FAA data has a column for ICAO and non-ICAO airport identifiers if you truly needed a map. been a few years since I played with it though.
If you’re going to do the K, you might as well do the P, so we don’t leave the eskimos and hula girls out.
Let me know the edit you tried. I'm guessing it was the Google maps link. There's an issue I haven't yet resolved regarding abbreviated phone generated links.