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

Draft riverspace delineation #27

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

Draft riverspace delineation #27

wants to merge 2 commits into from

Conversation

cforgaci
Copy link
Contributor

@cforgaci cforgaci commented Dec 2, 2024

@fnattino I drafted the riverspace delineation starting from this approach. As an additional step, I subtracted the first line of buildings form ther resulting isovist. This creates a more accurate first line:

image

However, it does not solve some less accurate boundary details, both in the back and in the front of buildings:

image

image

Whenever the river is underground, the river centreline could be used as a fallback option for viewpoints:

image

The overall delineation is ready for review. If you agree, we can fix the above details within the CRiSp repo.

@cforgaci cforgaci requested a review from fnattino December 2, 2024 15:10
@cforgaci cforgaci self-assigned this Dec 2, 2024
@cforgaci cforgaci changed the title Draft riverspace delineation notebook Draft riverspace delineation Dec 2, 2024
@cforgaci cforgaci linked an issue Dec 2, 2024 that may be closed by this pull request
1 task
Copy link
Contributor

@fnattino fnattino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing @cforgaci , seems to be working well! We can definitely merge it and refine details when porting to CRiSp.

It can probably be improved performance-wise, as I think creating many sf instances (e.g. for each rays) adds quite some overhead.

Maybe we can also think whether such visibility analisis could be implemented as a separate package to facilitate reuse in other contexts as well?

notebooks/riverspace/riverspace_bucharest.qmd Outdated Show resolved Hide resolved
@cforgaci
Copy link
Contributor Author

cforgaci commented Dec 13, 2024

Thanks @fnattino for the review. I will then merge and create a module in CRiSp based on this prototype.

It can probably be improved performance-wise, as I think creating many sf instances (e.g. for each rays) adds quite some overhead.

I will create an issue on this in CRiSp once the module is created.

Maybe we can also think whether such visibility analisis could be implemented as a separate package to facilitate reuse in other contexts as well?

Good idea! I will also draft a package on this and we can remove the module from CRiSp once the package is functional.

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.

Riverspace delineation
2 participants