search

CartoDB / odyssey.js

Making it easy to merge map and narrative
BSD 3-Clause "New" or "Revised" License
1.62k stars 188 forks source link

visjson support working? #205

Open pramsey opened 9 years ago

pramsey commented 9 years ago

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 commented 9 years ago

@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 commented 9 years ago

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

agoddard commented 9 years ago

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

pramsey commented 9 years ago

Does this vizjson work for you?

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

@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 commented 8 years ago

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?