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

HTM-1302: Integrate 3D functionality in Tailormap #617

Open
wants to merge 94 commits into
base: main
Choose a base branch
from
Open

Conversation

steinkobben
Copy link
Contributor

@steinkobben steinkobben commented Apr 24, 2024

  • 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

Copy link

github-actions bot commented Apr 24, 2024

Test Results

  1 files  ±0  202 suites  +2   7m 34s ⏱️ +15s
505 tests +6  505 ✅ +6  0 💤 ±0  0 ❌ ±0 
586 runs  +7  586 ✅ +7  0 💤 ±0  0 ❌ ±0 

Results for commit d801a8d. ± Comparison against base commit 888c317.

♻️ This comment has been updated with latest results.

@mprins mprins added the enhancement New feature or request label Jun 25, 2024
@github-actions github-actions bot added the Stale This has not been worked on label Aug 26, 2024
@github-actions github-actions bot removed the Stale This has not been worked on label Sep 2, 2024
@mprins mprins changed the title [WIP] HTM-1302 Cesium HTM-1302: Integrate 3D functionality in Tailormap Jan 31, 2025
@mprins mprins marked this pull request as ready for review January 31, 2025 16:13
Copy link
Contributor

@mprins mprins left a 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

@mprins mprins enabled auto-merge (squash) February 1, 2025 10:04
# 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
@@ -52,6 +52,9 @@ export class TreeComponent implements OnInit, OnDestroy {
@Input()
public dragHandleSelector?: string;

@Input()
public singleLayerChecked = false;
Copy link
Collaborator

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 ]) => {
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants