From 69acd47267cac066fb44989f252823dc4c03e812 Mon Sep 17 00:00:00 2001 From: Samuel Oey Date: Thu, 30 Oct 2014 18:30:28 +0000 Subject: [PATCH] Updated tracking app api v1 draft (markdown) --- wiki/tracking-app-api-v1-draft.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/wiki/tracking-app-api-v1-draft.md b/wiki/tracking-app-api-v1-draft.md index 3d108d5ac1c..ac46c046942 100644 --- a/wiki/tracking-app-api-v1-draft.md +++ b/wiki/tracking-app-api-v1-draft.md @@ -128,17 +128,17 @@ As general information, the tracking status of the smartphone is sent. **status** Either `start` or `stop`. -## Send Locations +## Send Measurements The main data sent by the app. -Locations should be sent live during an event. In case of missing network, locations are stored to the device and uploaded in a FIFO order as soon as a connection is available. +Measurements should be sent live during an event. In case of missing network, measurements are stored to the device and uploaded in a FIFO order as soon as a connection is available. GZIP compression is a must. Bulk uploads should be chunked, e.g. per 1,000 locations. ### Path - /event/{event_id}/competitor/{competitor_id}/locations + /event/{event_id}/competitor/{competitor_id}/measurements ### Verb @@ -147,7 +147,7 @@ GZIP compression is a must. Bulk uploads should be chunked, e.g. per 1,000 locat ### Request { - "locations" : [ + "measurements" : [ { "timestamp" : 14144160080000, "latitude" : 54.325246,