Yes, we could replicate the content of /databricks/native/proj-data to a volume, cloud-native storage, dbfs (which we have deactivated by the way) or somewhere else. But after that, we have to change the environment variable PROJ_DATA pointing to the new location. If we change the environment variable, we introduce new issues. Guess what the native Databricks geospatial function relies on the same environment variable and do not work anymore correctly!

 

And the library (rasterio) use PROJ system library as it should. Additional Information about rasterio and PROJ_DATA