Files
gods-eye-view/changelog.d/1807-library-server-routing.md
T
Sameh Khamis 9554d6ea71 Serve the Data Library from any server, and let a server shape it (#1807)
A server can answer the library with createLibraryHandler, a fetch handler, and shape what it offers: hide entries (listed: false) or route browser-direct ones through itself (fetch: proxied). View-bounded entries ask for a grid-snapped box, and GeoParquet is read on the server within it. Applications can pass their own tile and data fetchers (createApplicationTools({library: {fetchTile, fetchData}})), and with library.requireCatalog a catalog that does not answer offers nothing and is asked again later. Tile paths have one spelling: integer z/x/y without leading zeros, within the grid and the entry's zooms. A server's index and partition reads are bounded and counted against its subrequest limit.
2026-11-17 23:34:00 -08:00

654 B

  • The Data Library's proxy is a fetch handler any server can mount (createLibraryHandler, sources/library). A server can hide catalog entries or route browser-direct ones through its proxy, view-bounded entries ask it for a grid-snapped box, answers are cacheable for cacheSeconds, and an application can fetch library tiles and datasets through its own cache (createApplicationTools({ library })) and offer only what the server's catalog names, nothing while it does not answer (requireCatalog). Tile paths and view boxes have one spelling, and partitioned reads can be capped per process and per request (samehkhamis, #1807).