'\" -*- coding: us-ascii -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
.TH osgearth_backfill 1 "19 April 2019" "" ""
.SH NAME
osgearth_backfill \- specialty tool for post-processing TMS datasets
.SH SYNOPSIS
'nh
.fi
.ad l
\fBosgearth_backfill\fR \kx
.if (\nx>(\n(.l/2)) .nr x (\n(.l/5)
'in \n(.iu+\nxu
\fItms.xml\fR [\fB--bounds\fR \fIxmin\fR \fIymin\fR \fIxmax\fR \fIymax\fR | \fB--min-level\fR \fIlevel\fR | \fB--max-level\fR \fIlevel\fR | \fB--db-options\fR \fIoptions\fR]
'in \n(.iu-\nxu
.ad b
'hy
.SH DESCRIPTION
\fBosgearth_backfill\fR is a specialty tool that is used to
post-process TMS datasets. Some web mapping services use completely
different datasets at different zoom levels. For example, they may use
NASA BlueMarble imagery until they reach level 4, then abruptly switch
to LANDSAT data. This is fine for 2D slippy map visualization but can be
visually distracting when viewed in 3D because neighboring tiles at
different LODs look completely different.
.PP
\fBosgearth_backfill\fR lets you generate a TMS dataset like
you normally would (using
\fBosgearth_package\fR(1),
or another tool) and then "backfill" lower levels of detail from a
specified higher level of detail. For example, you can specify a max
level of 10 and LODs 0-9 will be regenerated based on the data found
in level 10.
.SH OPTIONS
.TP 
\fItms.xml\fR
Path to the tms.xml file
.TP 
\*(T<\fB\-\-bounds\fR\*(T> \fIxmin\fR \fIymin\fR \fIxmax\fR \fIymax\fR
bounds to backfill (in map coordinates; default=entire map)
.TP 
\*(T<\fB\-\-min\-level\fR\*(T> \fIlevel\fR
The minimum level to stop backfilling to. (default=0)
.TP 
\*(T<\fB\-\-max\-level\fR\*(T> \fIlevel\fR
The level to start backfilling from. (default=inf)
.TP 
\*(T<\fB\-\-db\-options\fR\*(T> \fIoptions\fR
db options string to pass to the image writer in quotes
(e.g., "JPEG_QUALITY 60")