Tyler Sutterley comments

Results 78 comments of


                                            Tyler Sutterley

add `points_from_xy` to `GeoSeries` class

Removing z makes things simpler :) applied `black` formatting so we'll see how it goes with CI happy to contribute!

add `points_from_xy` to `GeoSeries` class

``` RuntimeError: The Poetry configuration is invalid: - [extras.pipfile_deprecated_finder.2] 'pip-shims

NameError: name 'i1' is not defined

sorry @GKG1312 and @ChaoEcohydroRS, not sure how I didn't see this. I'm putting in a PR #75 to hopefully fix this for you.

NameError: name 'i1' is not defined

yep should just be `[idx]`. fixed in #76

NameError: name 'i1' is not defined

thanks for tracking these down! I haven't touched these notebooks in a while since [sliderule](https://slideruleearth.io/) now has most of the functionality

pyTMD.compute.tide_currents needing both u_* and v_* rather than only u_*

I believe that is for backwards compatibility for when TPXO9-atlas models had served the u and v currents in separate files (see #258). I only have access to the binary...

pyTMD.compute.tide_currents needing both u_* and v_* rather than only u_*

you're right that is a problem. It's in the `pathfinder` function within the `io.model` class. There's a file check to make sure everything exists. I need to fix this.

pyTMD.compute.tide_currents needing both u_* and v_* rather than only u_*

I'm working on this now. Can you verify for me that the TPXO9-atlas-v5 netCDF4 files have both components?

pyTMD.compute.tide_currents needing both u_* and v_* rather than only u_*

Perfect thanks! I'll get this in as part of a PR I started earlier and will put out a release today. Thanks for your help on this. I don't really...

pyTMD.compute.tide_currents needing both u_* and v_* rather than only u_*

should be in cm/s