-
Notifications
You must be signed in to change notification settings - Fork 34
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
write
of a Raster with crs fails
#482
Comments
I also get a similar error, when I set the mappedcrs and also for EPSG(4326). |
The crs is not the problem, its a bug... it should probably let you use points, which dont need the bounds matrix. But is this data really points or is it intervals? You need to specify that. You can use a keyword in the dimension that will get passed to the lookup: |
The data should be Intervals. How do I decide which locus to use? |
Is it ok to just import the LookupArrays module if you need that stuff? I often have this: using Rasters.LookupArrays Otherwise its a lot of common words exported by default. The locus is where your axis values fall inside the interval - start center or end. They seem to be at the start of the months? CF standards specify they should be the center, so they will get converted when you write. |
YAXArrays.jl will need to properly specify the lookups |
Thanks, setting the sampling to intervals fixed my immidiate problem for now. I think it is ok to import the LookupArrays module, but then it should be stated that the Intervals type lives in the LookupArrays submodule. For example in |
Yeah all these things need more docs. Its mostly not mentioned because it was previously all exported. Good that solved yoir problem |
I am trying to write a Raster for which I specified the crs manually during construction to disk and I get the following error:
I thought, that this is only going to write the crs information into the metadata of the file, because in my real use case the X and Y coordinates are already in the CRS and it is just that the metadata is missing.
The text was updated successfully, but these errors were encountered: