Skip to content

Comments

r.in.gdal: fix and enable test#3339

Merged
petrasovaa merged 1 commit intoOSGeo:mainfrom
petrasovaa:r.in.gdal-test
Jan 8, 2024
Merged

r.in.gdal: fix and enable test#3339
petrasovaa merged 1 commit intoOSGeo:mainfrom
petrasovaa:r.in.gdal-test

Conversation

@petrasovaa
Copy link
Contributor

@petrasovaa petrasovaa commented Jan 7, 2024

This should fix r.in.gdal test. I changed the expected east/west to match the actual imported data, which also matches what gdalinfo reports on the testdata. Why this wasn't the case before, I don't know.

Relevant output from gdalinfo on the test dataset:

Files: data/elevation3d.nc
Size is 150, 135
Origin = (630000.000000000000000,228500.000000000000000)
Pixel Size = (100.000000000000000,-100.000000000000000)
Corner Coordinates:
Upper Left  (  630000.000,  228500.000) 
Lower Left  (  630000.000,  215000.000) 
Upper Right (  645000.000,  228500.000) 
Lower Right (  645000.000,  215000.000) 
Center      (  637500.000,  221750.000) 

@petrasovaa petrasovaa added this to the 8.4.0 milestone Jan 7, 2024
@petrasovaa petrasovaa self-assigned this Jan 7, 2024
@github-actions github-actions bot added CI Continuous integration raster Related to raster data processing Python Related code is in Python module labels Jan 7, 2024
@petrasovaa petrasovaa merged commit 03111f1 into OSGeo:main Jan 8, 2024
@petrasovaa petrasovaa deleted the r.in.gdal-test branch January 8, 2024 16:16
HuidaeCho pushed a commit to HuidaeCho/grass that referenced this pull request Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous integration module Python Related code is in Python raster Related to raster data processing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants