Support for batch table hierarchy (do NOT merge)

EricBoix commented 6 years ago

This PR should not be merged and is only a base for commenting/discussing some WIP as proposition for issue #27 .

Jeremy-Gaillard commented 6 years ago

Thanks for your work on this PR.

A few remarks before I take a closer look to the PR:

The extensions don't seem to be registered in the tileset (extensionUsed, extensionRequired)
I don't think tileset should have a header attribute (i.e. replace self.header["attribute"] by self.attribute, or just change the name if you want to keep all attributes in a dictionary)
Replace BoundingVolume.set by BoundingVolume.setBox, BoundingVolume.setRegion, BoundingVolume.setSphere so you don't need to test the validity of the volume afterwards
I imagine that your already aware, but this PR will need to be split into a few PRs (I'd say tileset, validating and batch table hierarchy)
Be wary with your commit comments: the first line should be a summary of the commit. Some of your commits are misleading because the summary is the first line of a list

delhomer commented 4 years ago

Oslandia / py3dtiles