Open alex-s-gardner opened 5 months ago
latitude => "/gt1l/land_ice_segments/latitude"
. One could possibly even derive the name from a single string by taking the last of the split on /
.Nitpick, I would use step
instead of stride
to keep it similar to the built-in range
we have.
@evetion what additional functionality do you need in H5ToTable
to satisfy SpaceLiDAR
s needs? Is it just the ability to pass a function to apply to variables upon read?
I brainstormed about it in https://github.com/evetion/SpaceLiDAR.jl/issues/58:
size/datatype and its shared dimensions(!), as well as a function that would be applied on loading
But it might be better suited for an extended or prepared var that implements the same interface? These requirements are for automatically including the dimensions of requested variables, being slightly more type stable, and being able to error when two incompatible variables (different lengths) are selected for the same table.