MobileEats 2.0

Awhile back I shared a pet project of mine called MobileEats aimed at taking Twitter geo-data and plotting it on a Google Map. It seemed like a no-brainer of an idea to connect mobile food vendors with customers by letting them know where they are. Since the first launch I have overhauled the look and feel of the site to be more conducive to a single screen browsing experience and learned a lot about building a "web app" along the way.

However, I have run into a very serious problem. Mobile food vendors in Nashville, apparently, don't understand how to use GeoData in their tweets. Of the 38 Trucks the site monitors, only two of them regularly post with geodata and one of those does so haphazardly. Without the geodata, the site is pretty useless. So, I'm left with two choices: re-code the site to send Twitter data through a series of hoops involving Google Calendar, GeoData Mapping and GeoLocation Requests (good looking out from Dale Liszka on that solution) OR just try the system out with a different city where the vendors are maybe a little more educated on how to press that "Share Location" button when they send out updates.

It's super disappointing that this didn't work as expected right out of the gate but given that it's a pet project not meant to generate any income, I can't be too bummed. So, I'm looking for another city to try this out on. I'm skeptical to go with a well established scene like LA or Portland but it's likely that those vendors know how to harness the geodata better.

TL:DR: there's a new looking version of MobileEats but the map plotting is fairly useless due to lack of geolocation data being included in tweets. What city should I try next or should I just ditch the whole thing?