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

Tile selection issues #3170

Closed
slozier opened this issue Nov 5, 2015 · 1 comment
Closed

Tile selection issues #3170

slozier opened this issue Nov 5, 2015 · 1 comment

Comments

@slozier
Copy link
Contributor

slozier commented Nov 5, 2015

There appears to be issues with tile selection. In my sample code below, the lat/lon I selected is in the 032 tile section on Bing maps. The height is below ground for the WGS84 model, but above ground when using a terrain provider.

If I run my sample in the sandcastle, the camera is below ground and a number of "incorrect" tiles are loaded (I can see them being downloaded using dev tools in the browser). For example, the following tile is loaded:
http://ecn.t1.tiles.virtualearth.net/tiles/a31023233033312000303.jpeg?g=4462

There might be two issues here:

  • I don't think tiles should be loaded when we are looking at their back face
  • Why are the tiles on the opposite side of the globe loading to such resolution? (e.g. 31023233033312000303 instead of just 310)?
var widget = new Cesium.CesiumWidget('cesiumContainer');
var target = Cesium.Cartesian3.fromDegrees(-73.870152, 40.778059, -5);
var offset = new Cesium.HeadingPitchRange(0, -1, 1);
widget.camera.lookAt(target, offset);
@pjcozzi
Copy link
Contributor

pjcozzi commented Nov 7, 2015

Thanks for the report, @slozier. It's possible that Cesium's screen-space error / bounding volume pixel size computation has an issue with negative heights. We'll update here when we know.

slozier added a commit to slozier/cesium that referenced this issue Nov 11, 2015
slozier added a commit to slozier/cesium that referenced this issue Nov 11, 2015
bagnell added a commit that referenced this issue Nov 19, 2015
@slozier slozier closed this as completed Nov 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants