-
Notifications
You must be signed in to change notification settings - Fork 358
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
Add i3s catalog item #7158
Add i3s catalog item #7158
Conversation
6525652
to
bb12991
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ljowen - looking great and good job figuring out the complexities of the model layer. I have just added a few suggestions.
dc8249e
to
21a5faf
Compare
Apply api changes from "commander" Ignore [css] prop for styled components, explicitly ignore other props on bare html elements
* refactor the DateTimeParameterEditor to be a functional component * add the proptypes check to appease the tests * format and minor code tidy * update CHANGES.MD * add the currentTime from timelineStack as the default date time in WPS params * no need to set dateValue when declaring it with useState * remove unnecessary call to updateParameters * check parameter.value when the DateTimeEditor reloads * use moment to correctly format the date/time * missing import for WebFeatureServiceCatalogGroupTraits * add CHANGES entry * clean up the initial load of DateTimeParameterEditor.jsx * make DateTimeParameterEditor a tsx, remove useState * clean up CHANGES * update CHANGES.md
… Cesium3dTilesStyleMixin Reload i3s if previously destroyed
6fcab20
to
b21172a
Compare
- update CHANGES.md
) { | ||
feature._cesium3DTileFeature.color = originalColor; | ||
try { | ||
feature._cesium3DTileFeature.color = originalColor; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This throws an error as internally the features model reference becomes stale when LoD changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good @ljowen - i have left some comments, will do another pass to check the feature picking.
Just noting some things we should tackle maybe in a separate PR:
- Splitter support (easyish)
- Clipping box (might need some thinking/refactoring)
I've added splitter support, I think Clipping box might have to be a follow up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ljowen - Looks good to go.
On the feature selection issue, we have the same problem for 3d-tiles so might be good to create a separate issue.
The build error seems to be from prettier.
What this PR does
Fixes #6416
Test me
How should reviewers test this?
Init source:
http:https://ci.terria.io/add-i3s-support/#clean&https://gist.githubusercontent.com/ljowen/445d4ba31ef521b36875ae7555b8a78b/raw/a821943f2e993ca8ae23fe739e71b8ce258edc1e/frankfurtI3S.json
Other I3S examples:
Known Issues
Checklist
doc/
.