Esri / Esri/i3s-lib

If we change the default tile size 32 to 64, the display will be incorrectl.

Open
#11 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
31
Forks
14
PR merge metrics
No merged PRs in 30d

Description

Hello, @rvargasESRI @whatnick @vsautin1

We tried changingthe default tile size 32 to 64, as follows:
std::vector> grids;
grids.emplace_back(std::move(elevation_data));
build_downsampled_grids(size, grids.front().data(), **64**, grids);
std::reverse(std::begin(grids), std::end(grids));

//
auto writer = create_writer(slpk_file_path);
if (!writer)
return 1;

ENU_to_WGS_transformation transformation({ -123.4583943, 47.6204856 });
i3slib::i3s::Node_id node_id = 0;

if(!process(*writer, size, cell_size, grids, textures, **64**, 128, 0, **64**, { 0, 0 }, 128, { 0, 0 }, node_id, &transformation))
return 1;

Then run the app and get the new slpk , and published it to be a scene service. And, it shows that the scene service display normally in the browser.

Why the exception? Did we miss any other parameter?

Looking forward to your response.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the scene-service display problem using the shown build_downsampled_grids and process entry points with tile size 64. Compare every tile-size-related argument in those calls and verify the generated SLPK in a browser; done means the 64-sized output displays correctly without the reported exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.