Skip to main content
3 min read

Why your map loads the way it does

Open a large site on the 2D Map, the 3D Model or a tiled point cloud, and it appears almost at once, a little soft. Then it sharpens where you're looking. That is deliberate, not a glitch.

The short version

Those views are far too big to send in one piece. The viewer cuts them into thousands of small tiles and streams them as you need them, coarse ones first.

Views that stream, and views that don't

  • Views that stream in tiles include the 2D Map, the 3D Model, and point clouds that were processed into tiles.
  • Views that arrive as one file include the 3D Mesh and a point cloud that wasn't cut into tiles, sometimes after a lighter preview. Once loaded, they don't sharpen further.
  • The Flyover is a video, and plays like any other.

Coarse first, then fine

Every part of a streamed view exists at several levels of detail.

  • The rough pass lands first. The whole property shows up soft but complete.
  • Finer tiles replace it where you look. The viewer works out what fills your screen and swaps in sharper tiles there.
  • Off-screen stays cheap. The far side of the property stays rough until you go there.

That is why the picture seems to develop, and why a big property starts much like a small one.

Why detail arrives when you stop moving

While you move, what fills your screen changes many times a second, and each change needs fresh tiles. So the picture stays soft until you settle.

The most useful habit in the viewer: land on the view you want, then pause.

Your device sets its own budget

Phones, tablets and laptops have different amounts of memory, and running out makes a browser tab go blank. So streamed 3D views, such as the 3D Model and tiled point clouds, do not use one setting for everybody.

  • They measure the device they run on and give their tile cache a memory budget to match.
  • That budget is not fixed on the 3D Model. It grows while the device copes, pulls back when it strains, and remembers what it learned for your next visit.
  • What you've already loaded is kept, up to that budget, so returning to a spot is quicker than the first look.

How to get the best out of it

  • Zoom in rather than out. Close in, and the viewer spends everything on that area. Pull back, and the same budget covers far more ground, so it stays coarser.
  • Give the first look a good connection. After that, you mostly work from what's already on the device.
  • Let the loading screen finish before you fly.

Why not just download the file instead?

For big views like the map, the 3D Model and tiled point clouds, we don't hand you one file, because it's a worse deal:

  • You'd wait for all of it before seeing any of it.
  • It would have to fit in your device's memory at once, which a phone or tablet can't do with a large scan.
  • You'd need software to open it, and so would everyone you share it with.
  • It goes stale. After a re-flight your copy is out of date; a link always shows the current flight.

Streaming gives you a link that opens in a browser, on the device in your pocket, always current. For your own GIS or records, the downloads are still on your project page.

We tune this against real devices

The loading behavior and the memory budgets were measured on specific devices, on specific builds. They are measured again when we run a new round of device testing.

If yours struggles, tell us which device and what you saw.

Didn't find your answer? Contact us and we'll help you out.