-
Notifications
You must be signed in to change notification settings - Fork 39
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
Support GDAL /vsicurl and /vsizip prefixes to DEM paths #596
Comments
Note - with a small modification to the library, it can load these kinds of files. For the very large ArduPilot terrain data, the call to RasterIO to load data results in a segmentation fault.
We can take the approach I did in grid_map_geo and allow users to configure the maximum DEM size to load (in pixel-counts). Unfortunately, attempting to load a raster too big results in a segmentation fault, which is an existing vulnerability of this code. I haven't found any way to do robust runtime protections in a platform-portable way. Protecting against this is a separate problem. Interestingly, the |
Desired behavior
Allow users to supply DEM data to Gazebo that is zipped, or DEM data to Gazebo that is remotely hosted. I would like all of the following able to be supplied to the
Load()
function:Alternatives considered
Preventing users from using anything except local raw DEM files and stuff in Fuel.
Implementation suggestion
/vsizip
prefix to the path/vsicurl/<your_server_address>
to the pathUse case:
Example files - these are all zipped DEM hosted on a server
Additional context
You can add the following code block to
Dem_TEST.cc
and observe gazebo fail to load the data.The text was updated successfully, but these errors were encountered: