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

Wide corridor problem #12360

Closed
davidbourrel opened this issue Dec 5, 2024 · 3 comments
Closed

Wide corridor problem #12360

davidbourrel opened this issue Dec 5, 2024 · 3 comments

Comments

@davidbourrel
Copy link

davidbourrel commented Dec 5, 2024

@ggetz ggetz added needs feedback On hold until additional info is supplied and removed needs triage labels Jan 2, 2025
@ggetz
Copy link
Contributor

ggetz commented Jan 2, 2025

Hi @davidbourrel! Could you help us understand the use case for these wide corridors? I ask because it may help us understand if there is another route to achieve this. For instance, it's common for users to represent satellite swaths with polygons rather than corridors.

@davidbourrel
Copy link
Author

davidbourrel commented Jan 7, 2025

Hi ! Thanks for your response !

We have several satellites and each satellite have his "swath" at the same time. This is what our application looks like with 2 satellites:

Cesium-corridor

Code:

<Entity name={name}>
   <CorridorGraphics
        width={width}
        positions={positions.map((p) => new Cartesian3(p.x, p.y, p.z))}
        material={color.withAlpha(0.5)}
        height={1}
        cornerType={CornerType.BEVELED}
    />
</Entity>

width: are between 888093 and 941185

We want the same thing, except the little bug ^^. We have lots of points, so I may need to use data-decimation to make a corridor with polygons I think.

When to use corridor so ? I didn't understand that, I thought it was the perfect case to use it.

@ggetz ggetz removed the needs feedback On hold until additional info is supplied label Jan 14, 2025
@ggetz
Copy link
Contributor

ggetz commented Jan 14, 2025

Thanks @davidbourrel!

We're already tracking this in #10654. I'm going to close your issue to keep the discussion in one place and move your comment there. If you have any further input on this, please post it there instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants