-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement segmentation as part of the package #41
Conversation
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.
Hey @cforgaci , I finally managed to move forward with the segmentation module. Happy to hear your thoughts, for now only tests are missing.
Thinks to think on (maybe later on):
- which functions should be exported and which should remain private (we should fix it consistently everyewhere)?
- should we create a module for all the general-purpose geometry-related functions e.g. to buffer, split, find longes geometry, etc. (
geometry.R
or maybe even bettersf.R
?)
TODO:
|
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.
@fnattino many thanks for this! I left some comments and suggestions, nothing fundamental. Can you please have a look?
We then delineate segments in the corridor. The algorithm spits the corridor using river-crossing transversal edges that form continuous lines in the network: | ||
|
||
```{r eval=FALSE} | ||
# TODO remove eval=FALSE when the corridor is available as packaged data |
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.
Yes, this still needs to be added, but it falls outside the scope of this PR. Where should we save that? It is neither bucharest_osm
, nor bucharest_dem
, so it would make sense that it is a separate object called bucharest_delineation
or bucharest_del
which contains the corridor
, segments
and riverspace
. Then we can use bucharest_del$corridor
here. What do you think @fnattino?
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.
Maybe bucharest_delineation
? Will use this here and raise an issue pointing to this thread.
Maybe we expose only the top-level functions; in the
|
Co-authored-by: Claudiu Forgaci <[email protected]>
Co-authored-by: Claudiu Forgaci <[email protected]>
Co-authored-by: Claudiu Forgaci <[email protected]>
Co-authored-by: Claudiu Forgaci <[email protected]>
Co-authored-by: Claudiu Forgaci <[email protected]>
Hi @cforgaci - I think I have addressed all the comments, do you want to have a look? |
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.
Looks good @fnattino! This looks ready to be merged.
No description provided.