# gmtbinstats¶

Bin data and determine statistics per bin

## Synopsis¶

**gmt gmtbinstats** [ *table* ] **-G***outgrid*
**-I***increment*
**-C****a**|**d**|**g**|**i**|**l**|**L**|**m**|**n**|**o**|**p**|**q**[*quant*]|**r**|**s**|**u**|**U**|**z**
**-R***region*
**-S***search_radius*
[ **-E***empty* ]
[ **-N** ]
[ **-T**[**h**|**r**] ]
[ **-V**[*level*] ]
[ **-W**[**+s**] ]
[ **-bi**binary ]
[ **-di**nodata ]
[ **-e**regexp ]
[ **-f**flags ]
[ **-g**gaps ]
[ **-h**headers ]
[ **-i**flags ]
[ **-n**flags ]
[ **-qi**flags ]
[ **-r**reg ]
[ **-w**flags ]
[ **-:**[**i**|**o**] ]
[ **--PAR**=*value* ]

**Note:** No space is allowed between the option flag and the associated arguments.

## Description¶

**gmtbinstats** reads arbitrarily located (x,y[,z][,w]) points
(2-4 columns) from standard input [or *table*] and for each
node in the specified grid layout determines which points are
within the given radius. These point are then used in the
calculation of the specified statistic. The results may be
presented as is or may be normalized by the circle area to
perhaps give density estimates. Alternatively, select
hexagonal tiling instead or a rectangular grid layout.

## Required Arguments¶

*table*A 2-4 column ASCII file(s) [or binary, see

**-bi**] holding (x,y[,z][,w]) data values. You must use**-W**to indicate that you have weights. Only**-Cn**will accept 2 columns only. If no file is specified,**gmtbinstats**will read from standard input.

**-C****a**|**d**|**g**|**i**|**l**|**L**|**m**|**n**|**o**|**p**|**q**[*quant*]|**r**|**s**|**u**|**U**|**z**Choose the statistic that will be computed per node based on the points that are within

*radius*distance of the node. Select one of**a**for mean (average),**d**for median absolute deviation (MAD),**g**for full (max-min) range,**i**for 25-75% interquartile range,**l**for minimum (low),**L**for minimum of positive values only,**m**for median,**n**the number of values,**o**for LMS scale,**p**for mode (maximum likelihood),**q**for selected quantile (append desired quantile in 0-100% range [50]),**r**for the r.m.s.,**s**for standard deviation,**u**for maximum (upper),**U**for maximum of negative values only, or**z**for the sum.

**-G***outgrid*Give the name of the output grid file.

**-I***xinc*[**+e**|**n**][/*yinc*[**+e**|**n**]]*x_inc*[and optionally*y_inc*] is the grid spacing.**Geographical (degrees) coordinates**: Optionally, append a increment unit. Choose among**m**to indicate arc minutes or**s**to indicate arc seconds. If one of the units**e**,**f**,**k**,**M**,**n**or**u**is appended instead, the increment is assumed to be given in meter, foot, km, Mile, nautical mile or US survey foot, respectively, and will be converted to the equivalent degrees longitude at the middle latitude of the region (the conversion depends on PROJ_ELLIPSOID). If*y_inc*is given but set to 0 it will be reset equal to*x_inc*; otherwise it will be converted to degrees latitude.**All coordinates**: If**+e**is appended then the corresponding max*x*(*east*) or*y*(*north*) may be slightly adjusted to fit exactly the given increment [by default the increment may be adjusted slightly to fit the given domain]. Finally, instead of giving an increment you may specify the*number of nodes*desired by appending**+n**to the supplied integer argument; the increment is then recalculated from the number of nodes, the*registration*, and the domain. The resulting increment value depends on whether you have selected a gridline-registered or pixel-registered grid; see GMT File Formats for details.**Note**: If**-R***grdfile*is used then the grid spacing and the registration have already been initialized; use**-I**and**-r**to override these values.

**-R***xmin*/*xmax*/*ymin*/*ymax*[**+r**][**+u***unit*]Specify the region of interest. (See full description) (See cookbook information).

## Optional Arguments¶

**-E***empty*Set the value assigned to empty nodes [NaN].

**-N**Normalize the resulting grid values by the area represented by the search

*radius*[no normalization].

**-S***search_radius*Sets the

*search_radius*that determines which data points are considered close to a node. Append the distance unit (see Units). Not compatible with**-T**.

**-T**[**h**|**r**]Instead of circular, possibly overlapping areas, select non-overlapping tiling. Choose between

**r**ectangular**h**exagonal binning. For**-Tr**, set bin sizes via**-I**and we write the computed statistics to the grid file named in**-G**). For**-Th**, we write a table with the centers of the hexagons and the computed statistics to standard output (or to the file named in**-G**). Here, the**-I**setting is expected to set the*y*increment only and we compute the*x*-increment given the geometry. Because the horizontal spacing between hexagon centers in*x*and*y*have a ratio of \(\sqrt{3}\), we will automatically adjust*xmax*in**-R**to fit a whole number of hexagons.**Note**: Hexagonal tiling requires Cartesian data.

**-V**[*level*]Select verbosity level [

**w**]. (See full description) (See cookbook information).

**-W**[**+s**]Input data have an extra column containing observation point weight. If weights are given then weighted statistical quantities will be computed while the count will be the sum of the weights instead of number of points. If your weights are actually uncertainties (one sigma) then append

**+s**and we compute weight = 1/sigma.

**-bi**[*ncols*][**t**] (more …)Select native binary format for primary input. [Default is 3 (or 4 if

**-W**is set) columns].

**-di***nodata*(more …)Replace input columns that equal

*nodata*with NaN.

**-e**[**~**]*“pattern”*|**-e**[**~**]/*regexp*/[**i**] (more …)Only accept data records that match the given pattern.

**-f**[**i**|**o**]*colinfo*(more …)Specify data types of input and/or output columns.

**-g**[**a**]**x**|**y**|**d**|**X**|**Y**|**D**|[*col*]**z***gap*[**+n**|**p**] (more …)Determine data gaps and line breaks. 0x20 .. just an invisible code

**-h**[**i**|**o**][*n*][**+c**][**+d**][**+m***segheader*][**+r***remark*][**+t***title*] (more …)Skip or produce header record(s).

**-i***cols*[**+l**][**+d***divide*][**+s***scale*][**+o***offset*][,*…*][,**t**[*word*]] (more …)Select input columns and transformations (0 is first column,

**t**is trailing text, append*word*to read one word only).**-n**[**b**|**c**|**l**|**n**][**+a**][**+b***BC*][**+t***threshold*]Append

**+b***BC*to set any boundary conditions to be used, adding**g**for geographic,**p**for periodic, or**n**for natural boundary conditions. For the latter two you may append**x**or**y**to specify just one direction, otherwise both are assumed. [Default is geographic if grid is geographic].

**-qi**[~]*rows*[**+c***col*][**+a**|**f**|**s**] (more …)Select input rows or data range(s) [default is all rows].

**-r**[**g**|**p**] (more …)Set node registration [gridline].

**-wy**|**a**|**w**|**d**|**h**|**m**|**s**|**c***period*[/*phase*][**+c***col*] (more …)Convert an input coordinate to a cyclical coordinate.

**-:**[**i**|**o**] (more …)Swap 1st and 2nd column on input and/or output.

**-^**or just**-**Print a short message about the syntax of the command, then exit (NOTE: on Windows just use

**-**).**-+**or just**+**Print an extensive usage (help) message, including the explanation of any module-specific option (but not the GMT common options), then exit.

**-?**or no argumentsPrint a complete usage (help) message, including the explanation of all options, then exit.

**--PAR**=*value*Temporarily override a GMT default setting; repeatable. See gmt.conf for parameters.

## Units¶

For map distance unit, append *unit* **d** for arc degree, **m** for arc
minute, and **s** for arc second, or **e** for meter [Default], **f**
for foot, **k** for km, **M** for statute mile, **n** for nautical mile,
and **u** for US survey foot. By default we compute such distances using
a spherical approximation with great circles (**-jg**) using the authalic radius
(see PROJ_MEAN_RADIUS). You can use **-jf** to perform
“Flat Earth” calculations (quicker but less accurate) or **-je** to perform
exact geodesic calculations (slower but more accurate; see
PROJ_GEODESIC for method used).

## Grid Values Precision¶

Regardless of the precision of the input data, GMT programs that create grid files will internally hold the grids in 4-byte floating point arrays. This is done to conserve memory and furthermore most if not all real data can be stored using 4-byte floating point values. Data with higher precision (i.e., double precision values) will lose that precision once GMT operates on the grid or writes out new grids. To limit loss of precision when processing data you should always consider normalizing the data prior to processing.

## Examples¶

**Note**: Below are some examples of valid syntax for this module.
The examples that use remote files (file names starting with `@`

)
can be cut and pasted into your terminal for testing.
Other commands requiring input files are just dummy examples of the types
of uses that are common but cannot be run verbatim as written.

To examine the population inside a circle of 1000km radius for all nodes in a 5x5 arc degree grid, using the remote file @capitals.gmt, and plot the resulting grid using default projection and colors, try:

```
gmt begin map
gmt gmtbinstats @capitals.gmt -a2=population -Rg -I5 -Cz -Gpop.nc -S1000k
gmt grdimage pop.nc -B
gmt end show
```

To do hexagonal binning of the data in the file mydata.txt and counting the number of points inside each hexagon, try:

```
gmt count mydata.txt -R0/5/0/3 -I1 -Th -Cn > counts.txt
```

## See Also¶

blockmean, blockmedian, blockmode, gmt, nearneighbor, triangulate, xyz2grd