You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sebsel 7152579d01 Merge remote-tracking branch 'aaronpk/master' 7 years ago
compass add database migrations for #6 7 years ago
.gitignore gitignore 7 years ago
CONTRIBUTING.md add readme and contributing.md 9 years ago
README.md Merge pull request #5 from sebsel/docs 7 years ago
screenshot-mapview.jpg add screenshot of the mapview 7 years ago

README.md

Compass

Compass is a GPS tracking server that stores data in flat files.

mapview

Setup

In the compass directory, copy .env.example to .env and fill in the details. Install the dependencies with composer.

API

After you create a tracking database, you can visit the database's settings page to get a read or write token. These tokens are used with the API to update or retrieve data.

Writing

To write to a database, make a POST request in JSON format with the following keys:

POST /api/input

  • locations - a list of GeoJSON objects
  • token - the write token for the database (as a query string parameter or in the post body)

The GeoJSON objects must have at least one property, "timestamp", which is can be any value that can be interpreted as a date. The object can have any additional properties you wish.

The open source iOS GPS Logger will send data in this format by default.

POST /api/input?token=XXXXXXX HTTP/1.1
Content-type: application/json

{
  "locations": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [-122.621, 45.535]
      },
      "properties": {
        "timestamp": "2017-01-01T10:00:00-0700",
        "horizontal_accuracy": 65
      }
    }
  ],
  "token": "XXXXXXX"
}

Reading

To read a database, make a GET request as follows:

Get all data for a calendar day

GET /api/query

  • token - (required) the read token for the database
  • tz - (optional, default UTC) timezone string (e.g. America/Los_Angeles) which will be used to determine the absolute start/end times for the day
  • format - (optional, default "full") either "full" or "linestring"
  • full - return one JSON record for each result in the database
  • linestring - combine all the returned results into a GeoJSON linestring
  • date - specify a date to return all data on that day (YYYY-mm-dd format)

Get the last location before a given timestamp

GET /api/last

  • token - (required) the read token for the database
  • tz - (optional, default UTC) timezone string (e.g. America/Los_Angeles) which will be used to determine the absolute start/end times for the day
  • before - (optional, default to now) specify a full timestamp to return a single record before this date (the point returned will be no more than 24 hours before the given date)
  • geocode - (optional) if "true", then the location found will be reverse geocoded using Atlas to find the city and timezone at the location

Find the last location matching a clock time

GET /api/find-from-localtime

This API method can help you answer the question "Where was I when my watch read 9:30am on July 15th?".

Timestamps in Exif data do not include the timezone offset, and there is no standard mechanism for including the timezone offset in Exif. Some Canon cameras put the offset in a field, but not all of them do. You can use this method to find your location given an Exif date.

  • token - (required) the read token for the database
  • input - specify a clock time in the format YYYY-mm-dd HH:MM:SS

This will query the database and find the closest matching location for when your clock read that time.

Credits

Compass icon by Ryan Spiering from the Noun Project.

Screenshot of the map view by Sebastiaan Andeweg.

License

Copyright 2015 by Aaron Parecki

Compass is licensed under the Apache 2.0 license

Compass is built using the Lumen framework, which is licensed under the MIT license