-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bug Report: Some transects have their origin and end point swapped #173
Comments
Here are some ideas we discussed in the Slack.
|
I've been working on analyzing our transects and fixing the transects that were in the wrong direction or were wrong. The transects for Hawaii were in pretty bad shape and required quite a lot of cleaning. I'm posting them here before adding them to the next CoastSeg version. Transects_grid_region_2_cleaned_version.zip Remaining Tasks
|
Here is region 30 transects fixed puerto_rico_fix_transects.zip |
Alright region 29 was pretty easy |
region 0 was the easiest I just had to run
|
These transects have been merged into main and all the transects are now facing the correct direction |
Some transects have their origin and end point swapped.
Description:
Users have reported that certain transects, especially those around Fire Island, don't have their origin set as the landward point. Instead, the origin is set seaward. We need to devise a method to identify which transects have their origin in the sea and then swap the points for those specific transects. After rectifying the transects, it's crucial to update the Zenodo release.
Steps to Reproduce:
get_transects_points.py
located incoastseg/scripts
with the transect geojson file generated in step 2origin_points.geojson
generated by step 3 into geojson.ioExpected Behavior:
All transects should have their origin as the landward point.
Actual Behavior:
Some transects have their origin set seaward.
Possible Solution:
Additional Information:
The text was updated successfully, but these errors were encountered: