GeoPackage Tips: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 09:40, 9 October 2023 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,785 edits No edit summary Tag: Visual edit ← Older edit		Latest revision as of 12:39, 6 February 2025 view source Emilie Nielsen (talk \| contribs) Administrators 6,275 edits →Introduction
(2 intermediate revisions by 2 users not shown)
Line 5: Supports spatial indexing, greatly reducing loading and viewing times, making it much faster to work within GIS packages. Faster to write from TUFLOW than the shapefile format. For more information, ~~see~~refer to Section 4.4.3 of the <u>[https://~~www~~docs.tuflow.com/~~downloads/tuflow-classichpc~~classic-~~archive~~hpc/manual/latest/~~#2023 2023~~ ~~Release~~TUFLOW ~~Notes~~Manual]</u>. = Database Organisation = There are many ways to organise model inputs when using GPKG. This allows modellers to decide how they structure their inputs files, for example some options include: ~~single~~Single database for an entire project ~~separate~~Separate database for each control file (e.g. geometry, boundary control file) ~~separate~~Separate database for an existing or developed case ~~separate~~Separate databases for each type of input (e.g. elevation, materials, culverts) == Referencing a GeoPackage Database == Line 202: For more information, see the <u>[[QGIS_TUFLOW_Apply_GPKG_Layer_Names\| Updating a GPKG Layer Name]]</u> =Tutorials= Free TUFLOW tutorials using the GeoPackage format are availble via: <u>[[Tutorial Introduction\|TUFLOW HPC Tutorials]]</u>