-
Notifications
You must be signed in to change notification settings - Fork 6
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
HTM-1302: Integrate 3D functionality in Tailormap #617
base: main
Are you sure you want to change the base?
Conversation
steinkobben
commented
Apr 24, 2024
•
edited
Loading
edited
- Move Cesium code from MapService to OpenlayersMap
- Think about a way to add Terrains to Cesium (configurable ION token? hosted terrains? default no terrain?)
- Write additional functions to manage 3D layers
- Update checks for layer trees in admin-applications for 3D layers
- Check which function in viewer work or not when viewing in 3D
- Think about how to improve performance
- Use authorization for 3D Tileset services
# Conflicts: # projects/map/src/lib/models/layer-manager.model.ts
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.
something is off in the deployment, seems to be an undefined problem with new backed deployed, seems to be working: https://snapshot.tailormap.nl/pull-request/617/cesium/nl/app/3d_utrecht
# Conflicts: # package-lock.json # projects/admin-core/src/lib/admin-core.module.ts # projects/admin-core/src/lib/catalog/catalog-base-tree/catalog-base-tree-node/catalog-base-tree-node.component.ts
… between applications
projects/admin-core/src/lib/application/application-form/application-form.component.ts
Outdated
Show resolved
Hide resolved
...pplication-layer-tree/application-layer-tree-node/application-layer-tree-node.component.html
Outdated
Show resolved
Hide resolved
projects/admin-core/src/lib/application/helpers/application-tree.helper.ts
Outdated
Show resolved
Hide resolved
projects/admin-core/src/lib/catalog/geo-service-form/geo-service-form.component.ts
Show resolved
Hide resolved
projects/core/src/lib/components/feature-info/feature-info/feature-info.component.ts
Outdated
Show resolved
Hide resolved
projects/core/src/lib/components/feature-info/feature-info/feature-info.component.ts
Outdated
Show resolved
Hide resolved
projects/core/src/lib/components/feature-info/feature-info/feature-info.component.ts
Outdated
Show resolved
Hide resolved
@@ -52,6 +52,9 @@ export class TreeComponent implements OnInit, OnDestroy { | |||
@Input() | |||
public dragHandleSelector?: string; | |||
|
|||
@Input() | |||
public singleLayerChecked = false; |
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.
Check if this can be removed if you use useRadioInputs
instead
this.componentRegistrationService.getRegisteredComponents$(this.area), | ||
this.store$.select(selectIn3DView), | ||
]).pipe( | ||
map(([ components, in3D ]) => { |
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.
Don't think this will ever happen. These base components are not registered through the ComponentRegistrationService so I think this can be removed. Maybe you want to let other (external) components register whether they could run in 3d or not, then that should be filtered. But for base components this is not needed I suspect.