Since one of the project goals is to be easy to contribute, besides having a contribution guide (#57 ) we also need our code to be consistent.

I think we should use some linting to make our code easier to understand.

We could use ESlint

edit: we already use elsint, but not for checking code. We should create some rules

When you redo an analysis, and go back to the analysis screen it continues to show shoreline and transect data from the previous analysis.

CONTRIBUTING.md is not a good description of how to contribute to the project. And it needs to be translated to English.

Once I create a layer, I can't remove it anymore. The remove button is not working

CASSIE needs a license file.

Cassie should also show the hour the image was taken, so the user can find sea level information about it.

An advanced user (with extended DSAS experience) has reported that the rate of change for "EPR" does not seem accurate for the examples given (paper, tutorial, manual).

Therefore, we have to check if the actual EPR calculations are right by comparing with some verified DSAS analysis product.

Landsat seems to struggle in finding the right place for this image

Image ID is: LANDSAT/LT05/C01/T1_SR/LT05_220079_19990918

The region is the Cabeçuda Beach in Itajaí

When in layer creation form, if I press enter to submit (instead of pressing the create button) the program crashes.

Describe the bug
When a user selects the English language on the website, it does not remain in English after a refresh of the page.

To Reproduce
Steps to reproduce the behavior:

1. Go to the home page
2. Select the en-US language from the top right-hand corner menu
3. Refresh the page

Expected behavior
The language should remain in English after the refresh.

To make it easier for the user to select images to be analyzed.

When getting images, cassie should be able to use singular form, if the range is in the singular (like one year)

We can easily solve this by using a simple ternary operation choosing between a singular form (year) or plural (years)

Problem

This is a bad programming pattern.
The dialogs are automatic registered on importing, which leads the MainPage to have lots of "unused imports".

Expected

The Dialog component should be exported as it is and registered by the page that wants to use it.

Discussed in https://github.com/lia-univali/cassie/discussions/67

import CoastlineEvolutionDialog from "../../components/dialog/CoastlineEvolutionDialog";
import CoastlineConfigDialog from "../../components/dialog/CoastlineConfigDialog";
import NewLayerDialog from "../../components/dialog/NewLayerDialog";
import ImageSelectionDialog from "../../components/dialog/ImageSelectionDialog";

Problem

It is necessary to adjust the viewing parameters so that images can use the whole spectrum of brightness.
The problem is that image histogram distribution is not homogeneous enough.

It makes the image hard to visualize.

Solution

The solution is to change the min and max luminosity (when visualizing) by removing an X percentile of pixels count from both ends of the histogram.

When clicking on a line in the legend, only transects of that color should appear

After the analysis is complete, the page increases the height and creates a white space at the bottom.

After a shoreline analysis is done and the user wants to reanalyze the same images, the transects from the first analysis remain in the AOI (area of interest).

The ShorelineS algorithm is able to describe large coastal transformations based on relatively simple principles of alongshore transport gradient driven changes as a result of coastline curvature, including under highly obliquely incident waves, and consideration of splitting and merging of coastlines, and longshore transport disturbance by hard structures. An arbitrary number of coast sections is supported, which can be open or closed and can interact with each other through relatively straightforward merging and splitting mechanisms. Rocky parts or structures may block wave energy and/or longshore sediment transport. These features allow for a rich behavior including shoreline undulations and formation of spits, migrating islands, merging of coastal shapes, salients and tombolos.

Describe the bug
Although it isn't used, Cassie doesn't remove a baseline when the user cancels it

To Reproduce
In the processing page, start making a coastline analysis and then can it while drawing the baseline

Expected behavior
The canceled baseline should be deleted

Screenshots

Technical review
the problem only happens when you cancel the baseline while drawing

If you doubleclick and go to params screen, it will be deleted when you create the next one

Solution
The handleAnalyzeCoastline function