-
Notifications
You must be signed in to change notification settings - Fork 57
3D Selector for model parts #2255
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
Comments
Personally, I think it is likely that this is impractical for many viewer implementers to achieve on a geometry level (e.g., creating a crop or subset of geometry based on a 3D polygon selector). At the Basel working meeting on October 26 2023, there was general support for either considering selecting parts of models to be out of scope or at least to put this on the back-burner until 3D spec work has progressed significantly further. However, this style of selector will probably still be very important for allowing text label annotations to target a 3D polygonal region, even if it is not used for selecting parts of 3D models to annotate into a Scene. |
Suggest that this issue should be split - the original issue likely deferred, and a new issue created for targeting specific 3D regions of a scene. |
Split into #2269, propose defer this original issue for now. |
+1 to defer |
(decisions and suggestions from IIIF/3d#11 (comment))
If the entirety of a 3D model is to be painted into a
Scene
, the painting annotation body is just the content resource:If only part of the model is required, a SpecificResource with a Selector is required.
From the Napoli workshop, the proposal is a WktSelector:
https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry
Note that the value uses POLYGONZ not POLYGON: https://gis.stackexchange.com/a/206631
It is up to the client to determine how it extracts the part from the whole.
Note that a full example of a SpecificResource may also have one or more transforms (as #xx) if only part of the model is required.
The text was updated successfully, but these errors were encountered: