…he end (seems better to me)

- change order of applying `cmocean` in `plotter` to the end
- adding `radius_separated_points` function that is to be used before m_quiver function to ensure that you have get equal spatial distribution of arrows
- change to `tidal_data_to_ob` function so that it keeps all tidal constituents for the boundary but sets to zero those which are not in the database to make it easier for user to set themselves later if desired.

…oints could end up going slightly below this causing NaNs in the projection

…ts themselves

…ints are not pushed outside and become NaNs (was limited to radius of 178 deg but made sure can go up to full 180 deg)

…to ourRangeSearch in case rangesearch does not exist in radius_separated_points function