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

visjson support working? #205

Open
pramsey opened this issue Mar 5, 2015 · 6 comments
Open

visjson support working? #205

pramsey opened this issue Mar 5, 2015 · 6 comments

Comments

@pramsey
Copy link

pramsey commented Mar 5, 2015

Try as I might, adding this line to my MD in the sandbox does nothing.

 -vizjson: "https://pramsey.cartodb.com/api/v2/viz/817bab8a-b888-11e4-bb41-0e018d66dc29/viz.json"

(Since the map is of canada, I also do this to a chapter so I can see it)

 - center: [48.9620, -122.7385]
 - zoom: 10
@agoddard
Copy link

@pramsey did you end up figuring this out? I think I'm seeing something similar - but only with certain viz.json docs, not others.

@pramsey
Copy link
Author

pramsey commented Mar 26, 2015

Aha. No, I never did get any satisfaction on this one.

@agoddard
Copy link

@pramsey k, will see what I can find & let you know

@pramsey
Copy link
Author

pramsey commented Apr 7, 2015

Does this vizjson work for you?

http://pramsey.cartodb.com/api/v2/viz/817bab8a-b888-11e4-bb41-0e018d66dc29/viz.json

@agoddard
Copy link

@pramsey negative. One thing I've also noticed is that when vizjson's are updated, the odyssey map doesn't seem to pick up the changes sometimes, for example I have one currently showing two layers, one is "visible": true: and the other is "visible": false, yet the false one is showing and the true one is not. With my current vizjson, I was also able to show a number of linestrings and a separate layer of points, but when I added a SQL query to show only a subset of those points, the points render correctly but the linestrings no longer render.

@ebrelsford
Copy link

I'm also having problems using vizjson from Sandbox, commenting out this line does the trick.

In my case, the issue is that layer_name doesn't match the database table name, so an invalid SQL statement is create. I'm guessing the templates would be better off grabbing sql from the layer options?

ebrelsford added a commit to ebrelsford/odyssey.js that referenced this issue Dec 9, 2015
Partial fix to CartoDB#205. Attempt to use the layer's sql in its options, if this
fails create the sql statement as it was previously.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants