kring
commented
1 month ago Thanks for the test case, but it is invalid. CesiumUtility::Uri::resolve("file:///C:/Temp/3d%20tiles", "tiles/1") should (and does) return file:///C:/Temp/tiles/1. If you want the original URI to be treated as a directory rather than file, add the trailing slash. For example, this works:
CHECK(
CesiumUtility::Uri::resolve("file:///C:/Temp/3d%20tiles/", "tiles/1") ==
"file:///C:/Temp/3d%20tiles/tiles/1");Think about it like this. In regular old HTML, if you have a web page at:
https://example.com/page.html
And inside there you have a link that looks like this:
<a href="path/foo.html">Some Link</a>
Where will you go when you click that? The answer is https://example.com/path/foo.html, not https://example.com/page.html/path/foo.html. The answer doesn't change if the original URL is https://example.com/page (that is, if you remove the file extension).
TheYarin
The
CesiumUtility::Uri::resolve()function does not seem to handle a base URI with spaces as expected, even when the spaces are encoded as%20. Specifically, I'm working with a file URI, so let's usefile:///C:/Temp/3d%20tiles/tileset.jsonas an example.Note: I am not sure the problem is within this specific function, this is just my suspicion. I encountered this issue while trying to load a 3DTiles tileset using Cesium for Unity.
If anyone with a dev environment for cesium-native set up could test that, this would be very helpful. Adding the following code to line 98 of
CesiumUtility/test/TestUri.cppmight save you some time:By the way, for some reason if the base URI is
file:///C:/Temp/3dtiles/tileset.json(assuming this path is correct) and the relative path istiles/1it still finds the right files somehow, despite ending up with what I expect is a URI to a subfolder of a file, which can't be right. Does anyone have any idea how?