-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
layers-to-h5 not working from bash #26
Comments
@MRossol still hit a snag using
|
I updated dask in the env, can you try again |
Still getting an odd error:. The I ran using the jupyter notebook and it worked. So this case isn't critical, but would be helpful to figure out for the future.
|
This is probably working as designed. The un projected coordinates probably vary a little and so the code is rejecting it. I can make a branch with a looser acceptance of differing coordinates and have a kwarg for required precision. Sound good? |
We'd presumably end up with lon/lats that are slightly different, right? Will that cause an issue during the KDTree operation, or would the longitude/latitude already loaded into the .h5 be used instead? |
The coordinates will not be overwritten, so the previous coordinates would be used in the techmap. In fact, if the techmap has already been established, the coordinates wont be used at all. |
yeah, then that sounds like it would work fine. |
Can you open a feature request and close this? |
Bug Description
When running rev-to-h5 from bash, the code appears to expect a key that is not previously set.
Full Traceback
Code Sample
Bash code:
And
transfer.json
looks like this:Charge code
WEPG.10348.08.01.03
The text was updated successfully, but these errors were encountered: