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 am currently experimenting with external tilesets and came across a question with relative URLs.
Assume a tileset a.json with a content.url pointing to another tileset b.json. b.json contains a content.url to a tile.b3dm content file. Further assume that a.json and b.json are not in the same path.
Now, my assumption was that a relative content.url to tile.b3dm must be given relative to b.json because it is referenced from this tileset. However, I was surprised to learn that it has to be relative to a.json. Is this the supposed behavior?
Cheers,
Claus
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up, a tile url should be relative to its tileset and not just the root tileset. I opened a pull request in Cesium: CesiumGS/cesium#3529
I am currently experimenting with external tilesets and came across a question with relative URLs.
Assume a tileset
a.json
with acontent.url
pointing to another tilesetb.json
.b.json
contains acontent.url
to atile.b3dm
content file. Further assume thata.json
andb.json
are not in the same path.Now, my assumption was that a relative
content.url
totile.b3dm
must be given relative tob.json
because it is referenced from this tileset. However, I was surprised to learn that it has to be relative toa.json
. Is this the supposed behavior?Cheers,
Claus
The text was updated successfully, but these errors were encountered: