FMTC Docs
Project Links💝 Support Me
v9
v9
  • flutter_map_tile_caching
  • ❔Is FMTC Right For Me?
  • 💝Supporters
  • 📃(Proprietary) Licensing
  • 🚀Get Started
    • Quickstart
    • Installation
    • Example Application
    • v8 -> v9 Migration
    • Full API Reference
  • 🌐General
    • Initialisation
    • Backends
    • Error Handling
    • Tips
  • 📂Stores & Roots
    • Introduction
    • Stores
      • Management
      • Statistics
      • Metadata
    • Roots
      • Statistics
      • Recovery
    • flutter_map Integration
  • 📲Bulk Downloading
    • Introduction
    • 1️⃣Create A Region
    • 2️⃣Prepare For Downloading
    • 3️⃣Start Download
    • Control Downloads
    • Testing Tile Server
  • 🗃️External
    • Introduction
    • Exporting
    • Importing
  • flutter_map Docs
Powered by GitBook

© Luka Stillingfleet (JaffaKetchup)

On this page

Was this helpful?

Export as PDF
  1. Stores & Roots

Introduction

PreviousTipsNextStores

Last updated 1 year ago

Was this helpful?

FMTC uses a root and stores to structure its data.

There is generally a single root (which generally corresponds to a single ), which contains multiple stores. Cached tiles can belong to multiple stores, which keeps duplication minimized.

The structures use the ambient backend when a method is invoked on it, not at construction time.

Therefore, it is possible to construct an FMTCStore/FMTCRoot (see below) before initialisation, but 'using' it will throw RootUnavailable.

📂
backend