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.
This commit is contained in:
Sameh Khamis authored and GitHub committed 2026-11-17 23:34:00 -08:00
1 parent 7b4c84a717
commit 9554d6ea71
15 files changed
+1510 -395

No files matched your search

+1
View File
@@ -293,6 +293,7 @@
"./sources/reference": "./src/sources/reference.js",
"./layers/submarine-cables/source": "./src/layers/submarineCables/bundledSource.js",
"./sources/http-body": "./src/sources/httpBody.js",
"./sources/library": "./src/library/proxy.js",
"./sources/overpass": "./src/sources/overpass.js",
"./search/nominatim": "./src/search/nominatim.js",
"./sources/nominatim": "./src/sources/nominatim.js",