offshore data bounds

[grantbuster]

Bug Description

Bug to track offshore data input issues related to physical boundaries / limits.

Offshore input rules we have discovered:
1. Depth must be positive in meters
2. All distance columns have to be positive and > 0 (there are a lot of log(distance) operators in the nrwal equations)
3. All distance columns have to be in km (not meters!)
4. Hs_average must be > 0 (there are log(hs_average) operators in the nrwal equations)
5. fixed_downtime and floating_downtime are fractional and must be >0 and <1 (there are x/(1-downtime) operators in the nrwal equations)
6. Monopile eqns break down at large depth values (there is an exp(depth) operator in the monopile eqns)

[MRossol]

1. fixed here:

   reVX/reVX/offshore/offshore_inputs.py

   Lines 445 to 446 in a89e141

   	if layer == 'bathymetry':
   	layer_out = np.abs(layer_out)

2. fixed here:

   reVX/reVX/offshore/offshore_inputs.py

   Lines 283 to 284 in a89e141

   	# exclude onshore pixels
   	tech_map[self[offshore_dset] <= 0] = -1

3. fixed here:

   reVX/reVX/offshore/offshore_inputs.py

   Lines 447 to 448 in a89e141

   	elif layer == 'dist_to_coast':
   	layer_out /= 1000

4. fixed here:

   reVX/reVX/offshore/offshore_inputs.py

   Lines 453 to 454 in a9a22f0

   	elif layer.startswith('weather_downtime'):
   	layer_out[layer_out <= 0] = downtime_tolerance

5. fixed here:

   reVX/reVX/offshore/offshore_inputs.py

   Lines 455 to 456 in a9a22f0

   	if 'wave_height' not in layer:
   	layer_out[layer_out >= 1] = 1 - downtime_tolerance

6. Will need to be done in NRWAL