search

mainehackerclub / open_vehicle_tracker

GPS web tracking system for vehicles
http://mainehackerclub.github.io/open_vehicle_tracker/
32 stars 21 forks source link

Backend API Challenges #6

Open Cribstone opened 11 years ago

Cribstone commented 11 years ago

There may be some issues when it comes to the backend server we use to interpret coordinates on a map. Apparently, Google Maps defines vehicle tracking and fleet management as "Commercial Use" and requires subscription to the Enterprise API which doesn't even involve GPS- http://techcrunch.com/2012/10/17/google-apis-for-location-tracking-gps-free-geolocation/ They also have a new service with its own API called Google Maps Coordinate- https://coordinate.google.com/request-access These services would undoubtedly require standard procurement procedures to deploy, which makes usage very unlikely.
Therefore, developing an Open Source back-end via OpenStreetMap/OpenWRT/OneBusAway may have to be the single most important component of this project.

bschrader commented 11 years ago

Wow. Good call.

On Fri, 05 Jul 2013 08:22:41 -0700 Andrew Jawitz notifications@github.com wrote:

There may be some issues when it comes to the backend server we use to interpret coordinates on a map. Apparently, Google Maps defines vehicle tracking and fleet management as "Commercial Use" and requires subscription to the Enterprise API which doesn't even involve GPS- http://techcrunch.com/2012/10/17/google-apis-for-location-tracking-gps-free-geolocation/ They also have a new service with its own API called Google Maps Coordinate- https://coordinate.google.com/request-access These services would undoubtedly require standard procurement procedures to deploy, which makes usage very unlikely.
Therefore, developing an Open Source back-end via OpenStreetMap/OpenWRT/OneBusAway may have to be the single most important component of this project.

Reply to this email directly or view it on GitHub: https://github.com/mainehackerclub/open_vehicle_tracker/issues/6

Benjamin Schrader ben@unepic.com

Derrick- commented 11 years ago

Have you looked at Bing maps? They are pretty anxious to attract developers I think

From: bschrader [mailto:notifications@github.com] Sent: Friday, July 5, 2013 8:49 PM To: mainehackerclub/open_vehicle_tracker Subject: Re: [open_vehicle_tracker] Backend API Challenges (#6)

Wow. Good call.

On Fri, 05 Jul 2013 08:22:41 -0700 Andrew Jawitz notifications@github.com<mailto:notifications@github.com> wrote:

There may be some issues when it comes to the backend server we use to interpret coordinates on a map. Apparently, Google Maps defines vehicle tracking and fleet management as "Commercial Use" and requires subscription to the Enterprise API which doesn't even involve GPS- http://techcrunch.com/2012/10/17/google-apis-for-location-tracking-gps-free-geolocation/ They also have a new service with its own API called Google Maps Coordinate- https://coordinate.google.com/request-access These services would undoubtedly require standard procurement procedures to deploy, which makes usage very unlikely. Therefore, developing an Open Source back-end via OpenStreetMap/OpenWRT/OneBusAway may have to be the single most important component of this project.

Reply to this email directly or view it on GitHub: https://github.com/mainehackerclub/open_vehicle_tracker/issues/6

Benjamin Schrader ben@unepic.com<mailto:ben@unepic.com>

— Reply to this email directly or view it on GitHubhttps://github.com/mainehackerclub/open_vehicle_tracker/issues/6#issuecomment-20546329.

Cribstone commented 11 years ago

I won't get into too much detail but in the transit tracking world the standard is OneBusAway- git@github.com:OneBusAway/onebusaway.wiki.git. OBA is meant to be OS agnostic so people can access the feeds from Bing, Google, OSM, or even Apple/Siri clients. The NYC BUSTIME OBA deployment apparently used some kind of OpenWRT-based server for the back-end and I'm trying to get more details from the OpenPlans team who built it. There may be some fundamental differences however between tracking snowplows and transit that would have to be considered in the backend configuration. Theoretically this shouldn't have any bearing on the actual hardware though.