CesiumGS / 3d-tiles

Specification for streaming massive heterogeneous 3D geospatial datasets :earth_americas:
2.13k stars 469 forks source link

Download multiple children in a single request #9

Open pjcozzi opened 9 years ago

pjcozzi commented 9 years ago

See When using replacement refinement, can multiple children be combined into one request?.

We may design 3D Tiles to support downloading all children in a single request by allowing tiles.json to point to a subset of a file for a tile's content similiar to glTF buffer and bufferView.

pjcozzi commented 8 years ago

Is anyone interested in this for the draft 1.0 spec? If so, can you please describe your use case?

pjcozzi commented 8 years ago

Requested by @e-andersson.

pjcozzi commented 8 years ago

Example:

"tiles": {
    "level1-id" : "0/0/0.b3dm"
},
// ...
"content": {
  "tile": "level1-id",
  "byteOffset": 0,
  "byteLength": 1024
}
pjcozzi commented 7 years ago

This will be a great feature, but am pushing 1.0 to narrow scope.

mramato commented 7 years ago

I know the link in the description alludes to this already, but given that HTTP/2 support is now standard in all browsers, is this still needed? Does it provide any benefit other than reducing the number of tile requests?

GatorScott commented 7 years ago

Not sure when HTTP/2 support became available in each browser, but keep in mind that not all users are able to use the latest browser.

pjcozzi commented 7 years ago

@austinEng is evaluating HTTP/2 vs. combing vs. both. Results TBA soon.

mramato commented 7 years ago

Awesome, looking forward to the results and methodology (since HTTP/2 server configuration probably comes into play as well)

pjcozzi commented 6 years ago

Would love to do this, but pushing post 1.0 for scope.

ptrgags commented 3 years ago

This issue came up in discussion today. Some notes:

CC @lilleyse @sanjeetsuhag

kring commented 3 years ago

gRPC (or other similar library) might be useful to make a server/client architecture that can bundle tiles together in a single request

But HTTP/2 can already do this, right?