-
Notifications
You must be signed in to change notification settings - Fork 25
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
std::bad_alloc core dump example #6
Comments
Hi @jsta did you end up figuring this out? I don't know anything about C++ but I was assuming that this meant that the file was too large to fit in RAM. Do you know if this is not the issue? Thanks, |
@jsta: That's a 49GB allocation, so it's not surprising it would fail. Are those dimensions (104576x117376) cells correct? |
I'm getting slightly under those numbers but pretty close. It is quite large. |
@jsta : Given that the file is only 1.1GB, I'm struggling to see how the dataset itself could be that large. |
It's 1.7 GB when extracted as a tif. I don't know if it'll help but here is the gdalinfo lake_bathymetric_elevation_model.tif
|
Thanks, @jsta. Does the raster contain large areas of no_data or with pixels that are all the same value? (Does it look like it would compress nicely?) |
I'm encountering a similar issue trying to rescue a File Geodatabase raster from https://www.fs.usda.gov/rds/archive/products/RDS-2019-0030/RDS-2019-0030.zip (U.S. Forest Service Riparian Areas layer).
This is a national (U.S.) layer, at 10m resolution (though w/ only 2 integer values, and lots of NoData, so the geodatabase is only around 2.15 GB, though an uncompressed version would be much larger. Does ArcRasterRescue have a method for handling rasters that are too large to fit in RAM? |
I'm trying to extract a raster from the gdb located at:
https://gisdata.mn.gov/dataset/water-lake-bathymetry
Running into an error (copied below) that I thought I'd share:
arc_raster.exe data/mn_bathy/water_lake_bathymetry.gdb/ 0 lake_bathymetric_elevation_model
The text was updated successfully, but these errors were encountered: