-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Low-Cost GPS Tracking System #2
Comments
Cellular Data ApproachAn estimate for data usage is around 8-10MB/mo per vehicle. Prices on this one are iffy, but some providers have IoT services that offer pay-as-you-go schemes. The only issue is that these can become overpriced really fast.
Text-based ApproachA median estimate for 15-second interval updates over 30 days is about 90K texts. Assuming a 90-byte packet size (out of 160 max) for the trolley number, direction, lat/long, and onboard system time (to calculate delay from sent/received at the server). An SMS-based protocol will have to be used to relay data if it's more cost-efficient than using data-only cellular services. Sending data
Receiving data |
Not entirely related to transit docs, but cities like Sweetwater have piloted a small real-time tracking system before. It eventually died off since the developer disappeared(?) and the expenses of $5/month were too high. Ideally, cities are interested in low-cost but effective solutions that will improve ridership. Real-time tracking and accessible data is one way to do that.
Here I'll be listing some ways to cut down costs on wireless-based GPS trolley tracking.
The text was updated successfully, but these errors were encountered: