You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
An 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.
A 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.
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: