Loading Profile...
Dopplr API:add_trip, iso 8601 date and Daylight savings time.
Dopplr API:add_trip "start|finish { iso 8601 date }", in certain circumstances, sets the date of the trip incorrectly due to DST. If I specify the start or end date as e.g. 20090621T23nnnnZ i.e. 21/06/2009 23:nn:nn (GMT) which is actually 22/06/2009 00:nn:nn (BST), Dopplr sets the date of the leg's date to 21/06/2009. I believe what's happening is that the server seems only to process the date and ignores the time details.
Not a show stopper as I can handle this my side, but not obvious from the current API docs.
Not a show stopper as I can handle this my side, but not obvious from the current API docs.
I’m JustLettingYouKnow
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Dopplr doesn't currently do time-level trip start/end points. The API is written the way it is for future expansion, so I don't break all API-using apps as and when Dopplr gets better at things. Sorry about the confusion there. You can send _just_ '2009-03-01' as the start/finish if you want to be sure about the day that Dopplr uses.
The company and 1 other person say
this solves the problem
EMPLOYEE
