-
Notifications
You must be signed in to change notification settings - Fork 7
Problem with axis order #40
Comments
Thanks, David and sorry for the late reply. What exactly is going wrong? |
Ah OK this is interesting. Maybe a better approach would be to store WKT strings in image collections. |
Sorry, but the option |
dear Marius |
Great, thanks! Please share with marius.appel@uni-muenster.de |
You should have received an email with the link. |
Many thanks, could you also share the code / command you used to generate the image collection? Using R, I get:
This seems correct, so my guess is that simply the config options are not set properly from C++ (I need to check). |
First of all, thank you very much for your help and my apologies for my bad English. |
Thanks for sharing, this sounds really interesting and I have to a admit that the documentation of the C++ part is really still missing important parts (e.g. compilation on Windows). That being said, I had a look at the pafyc_gdalcubes_create_images_collections/main.cpp file, maybe simply adding the following line before you use any gdalcubes functions can solve the axis order issue?
|
Great to hear, let me know if anything does not work! |
Dear author
Your project is just greath
Using new versions of proj, from GDAL, the first axis in geographic CRSs is latitude and the second axis es longitude.
I think the solution is compile including an easy change:
srs.SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER)
in every OGRSpatialReference object
Best
David
The text was updated successfully, but these errors were encountered: