mapcache_detail(1)

πŸ’– mapcache_detail β€” like, the manual page, bestie πŸ’–

okay so this is the manual for mapcache_detail, which lives in section 1 of the manual. it's a coverage analysis tool for SQLite caches. that's the whole vibe. let's get into it 🫢


✨ NAME ✨

mapcache_detail β€” coverage analysis tool for SQLite caches


🌸 SYNOPSIS 🌸

mapcache_detail [options]

that's it. that's the whole shape of it. just options, no positional args, no drama πŸ‘‘


πŸ’… DESCRIPTION πŸ’…

so mapcache_detail is a coverage analysis tool for SQLite caches. like literally that's what it is. it looks at your SQLite cache and tells you what's covered. iconic behavior honestly πŸ’–


πŸŽ€ OPTIONS πŸŽ€

  • -c, --config file β€” the configuration file, i.e. /path/to/mapcache.xml. yes bestie, point it at your xml πŸ’…
  • -D, --dimension DIMENSION_NAME=VALUE β€” sets the value of a dimension. the format is DIMENSIONNAME=VALUE. you can use this one multiple times for multiple dimensions, so go off 🌈
  • -t, --tileset name β€” the tileset you wanna analyze πŸ—ΊοΈ
  • -g, --grid name β€” the grid you wanna analyze ✨
  • -e, --extent minx,miny,maxx,maxy β€” the extent you wanna analyze, formatted as minx,miny,maxx,maxy. cannot be used with --ogr-datasource πŸ™ˆ
  • -d, --ogr-datasource data source β€” an OGR data source to pull features from. cannot be used with --extent πŸ’€
  • -l, --ogr-layer layer β€” the OGR layer inside that OGR data source. cannot be used with --ogr-sql 🧚
  • -w, --ogr-where filter β€” a filter to apply on the OGR layer's features. cannot be used with --ogr-sql 🌸
  • -s, --ogr-sql SQL query β€” an SQL query to filter inside the OGR data source. cannot be used with --ogr-layer or --ogr-where 😭
  • -z, --zoom minzoom,maxzoom β€” sets the min and max zoom levels to analyze, separated by a comma, eg: 12,15 πŸ”
  • -q, --query value β€” sets the query used for counting tiles in a rectangle. the default value works with the default schema of SQLite caches, so lowkey just leave it alone unless you know what you're doing 🀫
  • -o, --short-output β€” only existing SQLite files get reported. missing SQLite files are still taken into account for level and global coverage, so don't think they're gone bestie, they're just not showing up in the output πŸ‘€

🌈 EXAMPLE 🌈

wanna analyze tile coverage of the tileset osm with the g grid? the default extent is the whole world and the default zoom level is 0, so this is like, the chill version:

mapcache_detail --config mapcache.xml --tileset osm --grid g

same thing as beforehand, but now with explicit zoom levels 9 to 12 and an explicit extent covering Switzerland:

mapcache_detail --config mapcache.xml --tileset osm --grid g --zoom 9,12 --extent 663000,5751230,1167680,6075050

like?? look at those numbers. Switzerland really said "here's my bounding box" πŸ‡¨πŸ‡­βœ¨


lowkey reminder: --extent and --ogr-datasource cannot hang out together, and --ogr-sql does not vibe with --ogr-layer or --ogr-where. pick a lane bestie πŸ’–

and that's the whole page!! this one's from the mapcache_detail(1) manual, dated 27 June 2026 πŸŽ€ ily, go analyze some caches, periodt πŸ’…πŸ¦‹

πŸ“¦ where this page comes from