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

Entwine info freeze when missing tiles #326

Open
julienperrot opened this issue Oct 9, 2024 · 1 comment
Open

Entwine info freeze when missing tiles #326

julienperrot opened this issue Oct 9, 2024 · 1 comment

Comments

@julienperrot
Copy link

Hello,

We observe in certain cases a blockage of entwine info when tile files are missing in the ept-data directory.

This blockage is not systematic for the same pyramid (approximately once every 3 or 4 times).
This blockage is reproduced on several different environments.
This blockage never seems to occur when the pyramid is complete.

The command executed is as follows:
entwine info --input "/path_to_ept.json" --verbose --deep --threads 8

verbose and threads have been modified without changing the behavior.
Entwine is version 3.1.0.

Thank you in advance.

@connormanning
Copy link
Owner

While this may be a bug, I would first point out that entwine info is not intended to be used with EPT data, but rather to gather metadata information about unindexed source files before indexing into EPT. See the doc here: "The info command is used to aggregate information about unindexed point cloud data prior to building an Entwine Point Tile dataset". We try to support EPT as input in the rare case that you want to rebuild data from existing EPT datasets, but this is not generally a widely expected use-case.

For gathering information about an EPT dataset, you can use pdal info. Since pdal is a dependency of Entwine, you should have it available wherever you are currently trying to use entwine info. Note that PDAL's EPT reader also expects your EPT data to be fully readable, but you can use the option readers.ept.ignore_unreadable (doc) to skip nodes that cannot be read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants