You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just created a new Timemap (http://timemapper.okfnlabs.org/euhealthfutures/craft-beer-growth-for-timemapper) after jumping through the Google API issues. It's a large enough dataset so the response is slightly sluggish as detailed elsewhere. However, there does not seem to be direct coordination between the record selected in one pane of the other. I select McCarthy's Brewery in the Timeline and Crafty Divils is highlighted on the map. I cannot seem to see a pattern between the two. Regardless of record on the map or on the timeline, a non-corresponding record seems to be fetched.
Has anyone else run into this problem? I am about to run an annual TImeMapper workshop for my class and have just modified the tutorials for the Google issues (and also an odd Twitter authentication error) but now running into this...any recollections appreciated.
Thanks,
Shawn
The text was updated successfully, but these errors were encountered:
I just created a new Timemap (http://timemapper.okfnlabs.org/euhealthfutures/craft-beer-growth-for-timemapper) after jumping through the Google API issues. It's a large enough dataset so the response is slightly sluggish as detailed elsewhere. However, there does not seem to be direct coordination between the record selected in one pane of the other. I select McCarthy's Brewery in the Timeline and Crafty Divils is highlighted on the map. I cannot seem to see a pattern between the two. Regardless of record on the map or on the timeline, a non-corresponding record seems to be fetched.
Has anyone else run into this problem? I am about to run an annual TImeMapper workshop for my class and have just modified the tutorials for the Google issues (and also an odd Twitter authentication error) but now running into this...any recollections appreciated.
Thanks,
Shawn
The text was updated successfully, but these errors were encountered: