Prevent view crashing if ST_LENGTH(re.progression3d_geometry) is null or 0

[rbovard]

No description provided.

[cymed]

In what situation do you need to digitise a reach with a length of 0 m?

Also I feel like using a coalesce will be quicker in production

[sjib]

Thank you for this improvement.

I think it is good if this case of length = 0 m is treated and does not create a crash of the plugin (mistakes can happen or we import data from another system and then have such cases - I have seen a lot of cases that you never thought about in the last 20 years).
@rbovard Maybe a warning could be added for length = 0 - this would help to find such cases easily

[rbovard]

That's it, if you import data from external sources it makes the view crash.

@cymed The error is division by zero, so we need to check if the value is >0 (not only not null with COALESCE no?)

@sjib What do yo mean about this warning? You want me do something in this PR?

[sjib]

@rbovard This adaption of the view is maybe not the best place to add a warning. But we have similar issues with the length profile. So thinking where to add a check and what especially it should highlight on this might be a good thing. Can you create an extra issue?

[rbovard]

Done.