Open msbentley opened 2 years ago
This apparently was intended behavior due to a issue in NumPy at the time the code was written. See method here.
I will look if the issue still exists. If not, I may consider adjusting the current behavior.
OK, many thanks - I'll work around it on my side in the interim.
So far I could not replicate the NumPy issue going back pretty far, but I need to look further.
I have a data product with columns defined like:
However when I read this table in pds4_tools, the colon seems to be stripped, e.g.
and if I try to index by the correct name I get an error, e.g.
but instead I have to access the field with an underscore:
Is this a bug, or intended? Currently, for various reasons, I'm getting the field names from the table manifest, where the values are correct, and then this fails when using the field name to access the data.