Skip to content

feat: add angle subdivision cli option#41

Open
ryan-berger wants to merge 1 commit intomainfrom
angle-divisions
Open

feat: add angle subdivision cli option#41
ryan-berger wants to merge 1 commit intomainfrom
angle-divisions

Conversation

@ryan-berger
Copy link
Member

We currently only calculate 360 different lines of sight with our azimuthal projection. This can potentially lead to a lack of coverage, especially in very long lines of sight. This adds a command line option --angle-subdivisions which allows for a user-configured angle subdivision to get coverage up to .01 of a degree

@ryan-berger ryan-berger changed the title feat: add angle division cli option feat: add angle subdivision cli option Feb 11, 2026
@ryan-berger ryan-berger requested a review from tombh February 11, 2026 07:25
We currently only calculate 360 different lines of sight with our azimuthal projection.
This can potentially lead to a lack of coverage, especially in very long lines of sight.
This adds a command line option --angle-subdivisions which allows for a user-configured
angle subdivision to get coverage up to .01 of a degree
@tombh
Copy link
Collaborator

tombh commented Feb 13, 2026

Another thing I thought, is there a simple smoke test for this? Like how much do the TVS and Longest Line unit tests change with more angles? And did you try making a heatmap PNG?

We also need to update the viewshed code to be able to create viewsheds from increased angles. We can just make an issue for that.

@tombh
Copy link
Collaborator

tombh commented Feb 16, 2026

Just thought of something else: we're losing fidelity because the angle is stored as i16. So we could either bump up the type, or I wonder if we store some metadata somewhere that defines the subdivision count? 32,767 is sooo nearly 360*100!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants