Render extracted shorelines as points instead of interpolated linestrings
Description:
Instead of utilizing Coastsat's function to interpolate the points for the extracted shorelines, the proposal is to save them directly as points within a GeoJSON file. Subsequently, these points should be rendered on the map.
Proposed Solution:
Modify the extraction function to save shoreline points directly without interpolation.
Save these points to a GeoJSON file.
Update the map rendering function to display these points.
Alternative Solutions:
[ ] Consider providing an option for users to toggle between viewing interpolated linestrings and raw points, catering to different user preferences.
Benefits:
Direct representation of extracted data without interpolation, ensuring accuracy.
Potentially faster processing and rendering times as interpolation is skipped.
Provides a clearer view of data density and distribution.
Drawbacks:
Without interpolation, the visual representation might appear fragmented or less continuous.
Some users might prefer the visual continuity provided by linestrings.
Additional Context:
This change might affect other visualization tools or functions that rely on the current interp
Render extracted shorelines as points instead of interpolated linestrings
Description: Instead of utilizing Coastsat's function to interpolate the points for the extracted shorelines, the proposal is to save them directly as points within a GeoJSON file. Subsequently, these points should be rendered on the map.
Proposed Solution:
Alternative Solutions:
Benefits:
Drawbacks:
Additional Context: