Skip to content
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

Location tracking API spec #28

Open
stefanb opened this issue Jul 11, 2018 · 3 comments
Open

Location tracking API spec #28

stefanb opened this issue Jul 11, 2018 · 3 comments

Comments

@stefanb
Copy link

stefanb commented Jul 11, 2018

In long distance events (marathons, orienteering, mountain running, sailing...) it is common to provide real-time GPS tracking of individual athletes/teams. Current specification does not support this and would make sense to agree on a standard.

The only mention of latitude and longitude is currently in the general event location (eg a stadium).

@espinr
Copy link
Contributor

espinr commented Jul 11, 2018

Thanks @stefanb.

So, I see this as a new property of competitors (i.e., athlete) taking part in a competition (CompetitionAction). Apart from the transponderId, bibNumber, etc., a trackingURL property? Should it be a URL to a web service that produces lat/long coordinates? Could it be just a webpage with a map and the representation of the athlete's location?

@stefanb
Copy link
Author

stefanb commented Jul 11, 2018

The use cases I see are:

  • A GPS-enabled device (eg wristwatch or phone form factor) sends coordinates to some REST service - currently each (device or phone app) manufacturer provides some service in a cloud, all incompatible with each other, isolating their customer in a bubble, not supported anymore as soon as a new model comes out. Manufactures could feed the data trough their cloud for older devices, but newer ones (certified) would need to send it to a service designated by event organisers directly.
  • Fans track the athletes (regardless of their device or app manufacturer), all on the same map (could be provided either by event organiser or their sponsor website or phone apps (eg an overlay on a navigation device)
  • An athlete (cyclist on bike or tactician on a sailboat) analyses their competitors on a laptop or a tablet (eg just a simple time gap or advanced telematics)
  • TV broadcasters consume the data to make nice visualisations and overlays.
  • After the competition the athlete (or coaches, or fans) can download all the data for thorough analysis

@espinr
Copy link
Contributor

espinr commented Jul 12, 2018

Great! Thinking in broader terms and, in order to accommodate this property for those requirements, I propose something like this:
trackingUrl: URL of a webpage, service or endpoint that represents the location of an athlete during a competition or while performs an exercise workout.

Schema.org already has a trackingUrl property, that is similar but for deliveries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants