Skip to content
This repository has been archived by the owner on Nov 2, 2018. It is now read-only.

location history feature #3

Closed
houqp opened this issue Aug 6, 2013 · 5 comments
Closed

location history feature #3

houqp opened this issue Aug 6, 2013 · 5 comments
Labels
enhancement
Milestone
Backlog

Comments

@houqp
Copy link

houqp commented Aug 6, 2013

quote from martin:

I would like to give you some suggestions for your map app. It would be nice to have a "location history" feature integrated with owncloud and mobile client ... something like google's latitude for the users who do not like to share their location with the rest of the world inteligence... :-) personaly I am using location history for my monthly business trips accounting. Is this a big effort to create such a feature?
@jancborchardt
Copy link
Contributor

@brantje I think you said you wanted this too. It’s something for the future though. We have to get basic map stuff working first.

@bugzy
Copy link

bugzy commented Aug 21, 2014

Would this sort of feature align with miataru server, which already has clients on various platforms, is opensource, and already has a stable API for tracking. See http://miataru.com/ This may very be worth considring in #1 on collaboration with opensource map applications.

@brantje
Copy link
Contributor

brantje commented Aug 21, 2014

Will look at it. But first maps will support osmand

@jancborchardt
Copy link
Contributor

Yep – focus is on already widely used systems. And following that we have plenty of other features which are more important.

@jancborchardt jancborchardt added this to the Backlog milestone Aug 22, 2014
@brantje
Copy link
Contributor

brantje commented Sep 9, 2014

Support for OsmAnd and GPSLogger is already in master.
Closing this one.

DJaeger added a commit to DJaeger/maps that referenced this issue Jun 5, 2015
@DJaeger
Update timestamp of locationprovider
e0d077b 
This adds the possibility to support timestamps with and without milliseconds as well as textual datetime descriptions.
This is needed as different clients use different formats and with this they don't need different parameters.
For example Osmand uses timestamps with milliseconds and GPSLogger uses textual datetime descriptions.
Before Osmand was not working like it was said here:
owncloud-archive#3 (comment)
@DJaeger DJaeger mentioned this issue Jun 5, 2015
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@houqp @jancborchardt @brantje @bugzy