-
Notifications
You must be signed in to change notification settings - Fork 188
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
documentation: odyssey w/ cartodb map #180
Comments
@lauraguzman do you think you could spend an hour of your remaining to just write up a bit better in the odyssey docs how to use CartoDB layers? |
Hi Andrew, Sure thing. Quick confirmation, I understand that the way to use Carlos - Can you clarify how/for what I could use the links you provided? On Wed, Aug 6, 2014 at 2:42 PM, Andrew W. Hill notifications@github.com
|
sure, I'll give you a shout in IM On Thu, Aug 7, 2014 at 4:23 PM, Laura Guzman notifications@github.com
www.cartodb.com |
Yep, that's how. That seems perfect. there is a piece in the documentation On Thu, Aug 7, 2014 at 10:23 AM, Laura Guzman notifications@github.com
|
Added use of vizjson to documentation page, all set. |
in the last days several use cases of using Odyssey + CartoDB have come up to support in the last days. Until a proper integration comes, it would be great to document this. While doing this maybe you can find the next links interesting.
odyssey story
http://bl.ocks.org/anonymous/raw/254629f0f008a0251fa2
markdown for the editor
https://gist.github.com/matallo/404c1db74352973c151f
visualization in CartoDB
http://team.cartodb.com/viz/0e6d42da-1bb6-11e4-b59c-0e10bcd91c2b/public_map?title=true&description=true&search=false&shareable=true&cartodb_logo=true&layer_selector=false&legends=false&scrollwheel=true&fullscreen=true&sublayer_options=1&sql=&sw_lat=28.21910487587188&sw_lon=-16.802215576171875&ne_lat=28.341856236004716&ne_lon=-16.53167724609375
public table (with the videos for the visualization)
http://team.cartodb.com/u/matallo/tables/untitled_table_1/public
/cc @andrewxhill @lauraguzman
The text was updated successfully, but these errors were encountered: