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

Finalize what properties should be set in the glTF to 'required' #61

Open
corybarr opened this issue Sep 11, 2024 · 2 comments
Open

Finalize what properties should be set in the glTF to 'required' #61

corybarr opened this issue Sep 11, 2024 · 2 comments

Comments

@corybarr
Copy link
Contributor

No description provided.

@r-veenstra
Copy link
Contributor

@corybarr can you expand on this one?

@corybarr
Copy link
Contributor Author

Also linking in @lilleyse

When I created this issue pre-Bentley it made more sense. Now this seems like a big issue that'll probably get pushed past GTM.

I had one required property, but we removed it due to issues Sean was having in the tiler. I believe it was the category name. Now nothing is required.

I can see that validity of nothing being formally required at GTM until we nail down user cases or really look at the obvious candidates like elementId. But if we want a true intermediary format, then we might need to find analogs in IFC and require those, too. This also ties into whether or not we swap out the intermediary format.

Fundamentally, I think it needs a lot of work investigating the intermediary format before we lock this down. That may even entail making the specification of required moot.

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