-
Notifications
You must be signed in to change notification settings - Fork 48
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
Unnamed coordinate frames of the same type cause bounding_box error #398
Comments
In the grand tradition of figuring things out after publicly asking about them, I realized that this is because both the input and output frame end up with the identical generic name "CoordinateFrame" and the GWCS machinery seems to get confused getting the transform, instead returning
It seems like using unnamed coordinate frames shouldn't be a failure mode, or at least that the error message resulting from that case should be more informative, so I'm going leave this issue open and rename it. |
There's another report for this issue - #327. |
Sorry about the duplicate! I'll go ahead and close this issue. |
I'm trying to construct a very simple dummy GWCS to essentially just do an identity transform from pixel to pixel coordinates. I would have thought the code below would be sufficient, but I'm getting an error trace related to
pixel_bounds
andbounding_box
. I thought that havingpixel_bounds
set asNone
was a common use case, so this surprised me. Would you please let me know if there's something wrong with my code below, or if this is a bug in GWCS?This results in the following when trying to actually use the dummy GWCS:
The text was updated successfully, but these errors were encountered: