Skip to content
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

r.buildvrt: document performance issues with external data #4441

Merged
merged 6 commits into from
Oct 31, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions raster/r.buildvrt/r.buildvrt.html
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ <h2>NOTES</h2>
the original raster maps which is only valid if the original raster
maps remain in the originally indicated mapset. A VRT can also be built
from raster maps registered with <em><a href="r.external.html">r.external</a></em>.
However, there are known performance issues with GRASS VRTs build
over external, registered data (see below).

<p>
Reading the whole VRT is slower than reading the equivalent single
Expand Down Expand Up @@ -48,6 +50,15 @@ <h3>VRT from a DEM in the North Carolina sample dataset</h3>
r.buildvrt file=tilelist.csv output=elev_state_50m_vrt
</pre></div>

<h2>KNOWN ISSUES</h2>
Users may experience significant performance degradation with virtual rasters build
with <em>r.buildvrt</em> over GDAL-linked (<em>r.external</em>) raster maps, especially
with slower file systems with latency like NFS. Performance degradation can also be
noticable on local file systems, but is usually less severe.
<p>
For GDAL-linked raster maps it is thus recommended to build GDAL VRTs, e.g with
<em>gdalbuildvrt</em>.

<h2>SEE ALSO</h2>

<em>
Expand Down
Loading