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

Torque is adapting the timezone depending on browser's local time #929

Closed
iriberri opened this issue Dec 14, 2015 · 6 comments

Comments

Projects
None yet
5 participants
@iriberri
Copy link
Contributor

commented Dec 14, 2015

Time ago we deployed this change: #534 that we removed afterwards because most of data is not "timezone curated" and it gets imported as UTC, which provokes time shifts in the client side when a torque map is being seen.

Last week I noticed this behaviour was happening again. You can take a look at an example here: https://team.cartodb.com/u/iriberri/viz/538719ae-a247-11e5-ad2b-0e31c9be1b51

The source data for this map is: https://team.cartodb.com/u/iriberri/tables/untitled_table_485/table

image

@iriberri

This comment has been minimized.

Copy link
Contributor Author

commented Dec 14, 2015

7615698

@iriberri

This comment has been minimized.

Copy link
Contributor Author

commented Dec 23, 2015

If this is taken care of before Jan 7th, please let me know :)

@ghost

This comment has been minimized.

Copy link

commented Jan 23, 2016

Hey, I have had the same issue. I recently took a trip to New Zealand, and mapped a lot of data. Now, the torque slider shows I was doing things in the middle of the night, and sleeping all day!
This really should be fixed, please let me know if anything does get fixed!

@oriolbx

This comment has been minimized.

Copy link
Contributor

commented Feb 9, 2016

I'm experiencing the same issue. 8090966

@BrunoSalerno

This comment has been minimized.

Copy link

commented Apr 11, 2016

Any news on this?

@nobuti

This comment has been minimized.

Copy link
Contributor

commented Nov 16, 2016

There has been no activity on this issue for several months and that's why we are closing it (automatically). If you think this still needs to be addressed please reopen it. The good news is that we are now working on the next version of CARTO.js, stay tuned.

@nobuti nobuti closed this Nov 16, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.