.. _cartopy: https://scitools.org.uk/cartopy/docs/latest/

.. _basemap: https://matplotlib.org/basemap/index.html

.. _seaborn: https://seaborn.pydata.org

.. _pandas: https://pandas.pydata.org

.. _xarray: http://xarray.pydata.org/en/stable/

.. _rainbow: https://doi.org/10.1175/BAMS-D-13-00155.1

.. _xkcd: https://blog.xkcd.com/2010/05/03/color-survey-results/

.. _opencolor: https://yeun.github.io/open-color/

.. _cmocean: https://matplotlib.org/cmocean/

.. _fabio: http://www.fabiocrameri.ch/colourmaps.php

.. _brewer: http://colorbrewer2.org/

.. _sciviscolor: https://sciviscolor.org/home/colormoves/

.. _matplotlib: https://matplotlib.org/stable/tutorials/colors/colormaps.html

.. _seacolor: https://seaborn.pydata.org/tutorial/color_palettes.html

.. _texgyre: https://frommindtotype.wordpress.com/2018/04/23/the-tex-gyre-font-family/

.. _why:

============
Why proplot?
============

Matplotlib is an extremely versatile plotting package used by
scientists and engineers far and wide. However,
matplotlib can be cumbersome or repetitive for users who...

* Make highly complex figures with many subplots.
* Want to finely tune their annotations and aesthetics.
* Need to make new figures nearly every day.

Proplot's core mission is to provide a smoother plotting experience for
matplotlib's most demanding users. We accomplish this by *expanding upon*
matplotlib's :ref:`object-oriented interface <usage_background>`. Proplot
makes changes that would be hard to justify or difficult to incorporate
into matplotlib itself, owing to differing design choices and backwards
compatibility considerations.

This page enumerates these changes and explains how they address the
limitations of matplotlib's default interface. To start using these
features, see the :ref:`usage introduction <usage>`
and the :ref:`user guide <ug_basics>`.

.. _why_less_typing:

Less typing, more plotting
==========================

Limitation
----------

Matplotlib users often need to change lots of plot settings all at once. With
the default interface, this requires calling a series of one-liner setter methods.

This workflow is quite verbose -- it tends to require "boilerplate code" that
gets copied and pasted a hundred times. It can also be confusing -- it is
often unclear whether properties are applied from an `~matplotlib.axes.Axes`
setter (e.g. `~matplotlib.axes.Axes.set_xlabel` and
`~matplotlib.axes.Axes.set_xticks`), an `~matplotlib.axis.XAxis` or
`~matplotlib.axis.YAxis` setter (e.g.
`~matplotlib.axis.Axis.set_major_locator` and
`~matplotlib.axis.Axis.set_major_formatter`), a `~matplotlib.spines.Spine`
setter (e.g. `~matplotlib.spines.Spine.set_bounds`), or a "bulk" property
setter (e.g. `~matplotlib.axes.Axes.tick_params`), or whether one must dig
into the figure architecture and apply settings to several different objects.
It seems like there should be a more unified, straightforward way to change
settings without sacrificing the advantages of object-oriented design.

Solution
--------

Proplot introduces the `proplot.axes.Axes.format` command to resolve this.
Think of this as an expanded and thoroughly documented version of the
`matplotlib.artist.Artist.update` command. `~proplot.axes.Axes.format` can modify things
like axis labels and titles and apply new :ref:`"rc" settings <why_rc>` to existing
axes. It also integrates with various :ref:`constructor functions <why_constructor>`
to help keep things succinct. Further, the `proplot.figure.Figure.format`
and `proplot.gridspec.SubplotGrid.format` commands can be used to
`~proplot.axes.Axes.format` several subplots at once.

Together, these features significantly reduce the amount of code needed to create
highly customized figures. As an example, it is trivial to see that...

.. code-block:: python

   import proplot as pplt
   fig, axs = pplt.subplots(ncols=2)
   axs.format(color='gray', linewidth=1)
   axs.format(xlim=(0, 100), xticks=10, xtickminor=True, xlabel='foo', ylabel='bar')

is much more succinct than...

.. code-block:: python

   import matplotlib.pyplot as plt
   import matplotlib.ticker as mticker
   import matplotlib as mpl
   with mpl.rc_context(rc={'axes.linewidth': 1, 'axes.edgecolor': 'gray'}):
       fig, axs = plt.subplots(ncols=2, sharey=True)
       axs[0].set_ylabel('bar', color='gray')
       for ax in axs:
           ax.set_xlim(0, 100)
           ax.xaxis.set_major_locator(mticker.MultipleLocator(10))
           ax.tick_params(width=1, color='gray', labelcolor='gray')
           ax.tick_params(axis='x', which='minor', bottom=True)
           ax.set_xlabel('foo', color='gray')

Links
-----

* For an introduction, see :ref:`this page <ug_format>`.
* For `~proplot.axes.CartesianAxes` formatting,
  see :ref:`this page <ug_cartesian>`.
* For `~proplot.axes.GeoAxes` formatting,
  see :ref:`this page <ug_geoformat>`.
* For `~proplot.axes.PolarAxes` formatting,
  see :ref:`this page <ug_polar>`.

.. _why_constructor:

Class constructor functions
===========================

Limitation
----------

Matplotlib and `cartopy`_ define several classes with verbose names like
`~matplotlib.ticker.MultipleLocator`, `~matplotlib.ticker.FormatStrFormatter`,
and `~cartopy.crs.LambertAzimuthalEqualArea`. They also keep them out of the
top-level package namespace. Since plotting code has a half life of about 30 seconds,
typing out these extra class names and import statements can be kind of a drag.

Parts of matplotlib's interface were actually designed with this in mind.
`Backend classes <https://matplotlib.org/faq/usage_faq.html#what-is-a-backend>`__,
`native axes projections <https://matplotlib.org/stable/api/projections_api.html>`__,
`axis scales <https://matplotlib.org/stable/gallery/scales/scales.html>`__,
`colormaps <https://matplotlib.org/stable/tutorials/colors/colormaps.html>`__,
`box styles <https://matplotlib.org/stable/api/_as_gen/matplotlib.patches.FancyBboxPatch.html>`__,
`arrow styles <https://matplotlib.org/stable/api/_as_gen/matplotlib.patches.FancyArrowPatch.html>`__,
and `arc styles <https://matplotlib.org/stable/api/_as_gen/matplotlib.patches.ConnectionStyle.html>`__
are referenced with "registered" string names,
as are `basemap projections <https://matplotlib.org/basemap/users/mapsetup.html>`__.
So, why not "register" everything else?

Solution
--------

In proplot, tick locators, tick formatters, axis scales, property cycles, colormaps,
normalizers, and `cartopy`_ projections are all "registered". This is accomplished
by defining "constructor functions" and passing various keyword arguments through
these functions.

The constructor functions also accept intuitive inputs alongside "registered"
names. For example, a scalar passed to `~proplot.constructor.Locator`
returns a `~matplotlib.ticker.MultipleLocator`, a
lists of strings passed to `~proplot.constructor.Formatter` returns a
`~matplotlib.ticker.FixedFormatter`, and `~proplot.constructor.Cycle`
and `~proplot.constructor.Colormap` accept colormap names, individual colors, and
lists of colors. Passing the relevant class instance to a constructor function
simply returns it, and all the registered classes are available in the top-level
namespace -- so class instances can be directly created with e.g.
``pplt.MultipleLocator(...)`` or ``pplt.LogNorm(...)`` rather than
relying on constructor functions.

The below table lists the constructor functions and the keyword arguments that use them.

================================  ============================================================  ==============================================================================  ================================================================================================================================================================================================
Function                          Return type                                                   Used by                                                                         Keyword argument(s)
================================  ============================================================  ==============================================================================  ================================================================================================================================================================================================
`~proplot.constructor.Proj`       `~cartopy.crs.Projection` or `~mpl_toolkits.basemap.Basemap`  `~proplot.figure.Figure.add_subplot` and `~proplot.figure.Figure.add_subplots`  ``proj=``
`~proplot.constructor.Locator`    `~matplotlib.ticker.Locator`                                  `~proplot.axes.Axes.format` and `~proplot.axes.Axes.colorbar`                   ``locator=``, ``xlocator=``, ``ylocator=``, ``minorlocator=``, ``xminorlocator=``, ``yminorlocator=``, ``ticks=``, ``xticks=``, ``yticks=``, ``minorticks=``, ``xminorticks=``, ``yminorticks=``
`~proplot.constructor.Formatter`  `~matplotlib.ticker.Formatter`                                `~proplot.axes.Axes.format` and `~proplot.axes.Axes.colorbar`                   ``formatter=``, ``xformatter=``, ``yformatter=``, ``ticklabels=``, ``xticklabels=``, ``yticklabels=``
`~proplot.constructor.Scale`      `~matplotlib.scale.ScaleBase`                                 `~proplot.axes.Axes.format`                                                     ``xscale=``, ``yscale=``
`~proplot.constructor.Colormap`   `~matplotlib.colors.Colormap`                                 :ref:`2D plotting commands <ug_2dplots>`                                        ``cmap=``
`~proplot.constructor.Norm`       `~matplotlib.colors.Normalize`                                :ref:`2D plotting commands <ug_2dplots>`                                        ``norm=``
`~proplot.constructor.Cycle`      `~cycler.Cycler`                                              :ref:`1D plotting commands <ug_1dplots>`                                        ``cycle=``
================================  ============================================================  ==============================================================================  ================================================================================================================================================================================================

Links
-----

* For more on axes projections,
  see :ref:`this page <ug_proj>`.
* For more on axis locators,
  see :ref:`this page <ug_locators>`.
* For more on axis formatters,
  see :ref:`this page <ug_formatters>`.
* For more on axis scales,
  see :ref:`this page <ug_scales>`.
* For more on datetime locators and formatters,
  see :ref:`this page <ug_datetime>`.
* For more on colormaps and normalizers,
  see :ref:`this page <ug_apply_cmap>`.
* For more on color cycles, see
  :ref:`this page <ug_apply_cycle>`.

.. _why_spacing:

Automatic dimensions and spacing
================================

Limitation
----------

Matplotlib plots tend to require lots of "tweaking" when you have more than one
subplot in the figure. This is partly because you must specify the physical
dimensions of the figure, despite the fact that...

#. The subplot aspect ratio is generally more relevant than the figure
   aspect ratio. An aspect ratio of ``1`` is desirable for most plots, and
   the aspect ratio must be held fixed for :ref:`geographic and polar <ug_proj>`
   projections and most `~matplotlib.axes.Axes.imshow` plots.
#. The subplot width and height control the "apparent" size of lines, markers,
   text, and other plotted content. If the figure size is fixed, adding more
   subplots will decrease the average subplot size and increase the "apparent"
   sizes. If the subplot size is fixed instead, this can be avoided.

Matplotlib includes a `tight layout algorithm
<https://matplotlib.org/stable/tutorials/intermediate/tight_layout_guide.html>`__
that generally obviates the need to tweak `~matplotlib.gridspec.GridSpec` spacing
parameters like `left`, `bottom`, and `wspace`. However, this algorithm is disabled
by default, and it cannot apply different amounts of spacing between different
subplot row and column boundaries.

Solution
--------

By default, proplot fixes the physical dimensions of a *reference subplot* rather
than the figure. The reference subplot dimensions are controlled with the `refwidth`,
`refheight`, and `refaspect` `~proplot.figure.Figure` keywords, with a default
behavior of ``refaspect=1`` and ``refwidth=2.5`` (inches). If the `data aspect ratio
<https://matplotlib.org/stable/gallery/subplots_axes_and_figures/axis_equal_demo.html>`__
of the reference subplot is fixed (as with :ref:`geographic <ug_geo>`,
:ref:`polar <ug_polar>`, `~matplotlib.axes.Axes.imshow`, and
`~proplot.axes.Axes.heatmap` plots) then this is used instead of `refaspect`.

Alternatively, you can independently specify the width or height of the *figure*
with the `figwidth` and `figheight` parameters. If only one is specified, the
other is adjusted to preserve subplot aspect ratios. This is very often useful
when preparing figures for submission to a publication. To request figure
dimensions suitable for submission to a :ref:`specific publication <journal_table>`,
use the `journal` keyword.

By default, proplot also uses :ref:`its own tight layout algorithm <ug_tight>` --
preventing text labels from overlapping with subplots. This algorithm works with the
`proplot.gridspec.GridSpec` subclass rather than `matplotlib.gridspec.GridSpec`, which
provides the following advantages:

* The `proplot.gridspec.GridSpec` subclass interprets spacing parameters
  with font size-relative units rather than figure size-relative units.
  This is more consistent with the tight layout `pad` arguments
  (which, like matplotlib, are specified in font size-relative units)
  and obviates the need to adjust spaces when the figure size or font size changes.
* The `proplot.gridspec.GridSpec` subclass permits variable spacing
  between rows and columns, and the tight layout algorithm takes
  this into account. Variable spacing is critical for making
  outer :ref:`colorbars and legends <ug_cbars_legends>` and
  :ref:`axes panels <ug_insets_panels>` without "stealing space"
  from the parent subplot -- these objects usually need to be
  spaced closer to their parents than other subplots.
* You can :ref:`override <ug_tight>` particular spacing parameters
  and leave the tight layout algorithm to adjust the
  unspecified spacing parameters. For example, passing ``right=1`` to
  `~proplot.figure.Figure.add_subplots` fixes the right margin
  at 1 font size-width while the others are adjusted automatically.
* Only one `proplot.gridspec.GridSpec` is permitted per figure,
  considerably simplifying the tight layout algorithm calculations.
  This restriction is enforced by requiring successive
  `~proplot.figure.Figure.add_subplot` calls to imply the same geometry and
  include only subplot specs generated from the same `~proplot.gridspec.GridSpec`.

Links
-----

* For more on figure sizing, see :ref:`this page <ug_autosize>`.
* For more on subplot spacing, see :ref:`this page <ug_tight>`.

.. _why_redundant:

Working with multiple subplots
==============================

Limitation
----------

When working with multiple subplots in matplotlib, the path of least resistance
often leads to *redundant* figure elements. Namely...

* Repeated axis tick labels.
* Repeated axis labels.
* Repeated colorbars.
* Repeated legends.

These sorts of redundancies are very common even in publications, where they waste
valuable page space. It is also generally necessary to add "a-b-c" labels to
figures with multiple subplots before submitting them to publications, but
matplotlib has no built-in way of doing this.

Solution
--------

Proplot makes it easier to work with multiple subplots and create clear,
concise figures.

* Axis tick labels and axis labels are automatically
  :ref:`shared and aligned <ug_share>` between subplot in the same
  `~proplot.gridspec.GridSpec` row or column. This is controlled by the `sharex`,
  `sharey`, `spanx`, `spany`, `alignx`, and `aligny` figure keywords.
* The figure `proplot.figure.Figure.colorbar` and `proplot.figure.Figure.legend`
  commands can easily draw colorbars and legends intended to reference more than
  one subplot in arbitrary contiguous rows and columns. See the
  :ref:`next section <why_colorbars_legends>` for details.
* The `~proplot.axes.Axes.panel_axes` (shorthand `~proplot.axes.Axes.panel`) commands
  can draw :ref:`thin panels <ug_panels>` along the edges of subplots. This
  can be useful for plotting 1D summary statistics alongside 2D plots.
* A-b-c labels can be added to subplots simply using the :rcraw:`abc`
  setting -- for example, ``pplt.rc['abc'] = 'A.'`` or ``axs.format(abc='A.')``.
  This is possible because `~proplot.figure.Figure.add_subplot` assigns a unique
  `~proplot.axes.Axes.number` to every new subplot.
* The `proplot.gridspec.SubplotGrid.format` command can easily format multiple subplots
  at once or add colorbars, legends, panels, twin axes, or inset axes to multiple
  subplots at once. A `~proplot.gridspec.SubplotGrid` is returned by
  `proplot.figure.Figure.subplots`, and can be indexed like a list or like a 2D
  array (in which case the indices match the subplot grid extents).

Links
-----

* For more on axis sharing, see :ref:`this page <ug_share>`.
* For more on panels, see :ref:`this page <ug_panels>`.
* For more on colorbars and legends, see :ref:`this page <ug_cbars_legends>`.
* For more on a-b-c labels, see :ref:`this page <ug_abc>`.
* For more on subplot grids,  see :ref:`this page <ug_subplotgrid>`.

.. _why_colorbars_legends:

Simpler colorbars and legends
=============================

Limitation
----------

In matplotlib, it can be difficult to draw `~matplotlib.figure.Figure.legend`\ s
along the outside of subplots. Generally, you need to position the legend
manually and tweak the spacing to make room for the legend.

Also, `~matplotlib.figure.Figure.colorbar`\ s drawn along the outside of subplots
with e.g. ``fig.colorbar(..., ax=ax)`` need to "steal" space from the parent subplot.
This can cause asymmetry in figures with more than one subplot. It is also generally
difficult to draw "inset" colorbars in matplotlib and to generate outer colorbars
with consistent widths (i.e., not too "skinny" or "fat").

Solution
--------

Proplot includes a simple framework for drawing colorbars and legends
that reference :ref:`individual subplots <ug_cbars_axes>` and
:ref:`multiple contiguous subplots <ug_cbars_figure>`.

* To draw a colorbar or legend on the outside of a specific subplot, pass an
  "outer" location (e.g. ``loc='l'`` or ``loc='left'``)
  to `proplot.axes.Axes.colorbar` or `proplot.axes.Axes.legend`.
* To draw a colorbar or legend on the inside of a specific subplot, pass an
  "inner" location (e.g. ``loc='ur'`` or ``loc='upper right'``)
  to `proplot.axes.Axes.colorbar` or `proplot.axes.Axes.legend`.
* To draw a colorbar or legend along the edge of the figure, use
  `proplot.figure.Figure.colorbar` and `proplot.figure.Figure.legend`.
  The `col`, `row`, and `span` keywords control which
  `~proplot.gridspec.GridSpec` rows and columns are spanned
  by the colorbar or legend.

Since `~proplot.gridspec.GridSpec` permits variable spacing between subplot
rows and columns, "outer" colorbars and legends do not alter subplot
spacing or add whitespace. This is critical e.g. if you have a
colorbar between columns 1 and 2 but nothing between columns 2 and 3.
Also, `~proplot.figure.Figure` and `~proplot.axes.Axes` colorbar widths are
now specified in *physical* units rather than relative units, which makes
colorbar thickness independent of subplot size and easier to get just right.

Links
-----

* For more on single-subplot colorbars and legends,
  see :ref:`this page <ug_cbars_axes>`.
* For more on multi-subplot colorbars and legends,
  see :ref:`this page <ug_cbars_figure>`.
* For new colorbar features,
  see :ref:`this page <ug_cbars>`.
* For new legend features,
  see :ref:`this page <ug_legends>`.

.. _why_plotting:

Improved plotting commands
==========================

Limitation
----------

A few common plotting tasks take a lot of work using matplotlib alone. The `seaborn`_,
`xarray`_, and `pandas`_ packages offer improvements, but it would be nice to
have this functionality built right into matplotlib's interface.

Solution
--------

Proplot uses the `~proplot.axes.PlotAxes` subclass to add various `seaborn`_,
`xarray`_, and `pandas`_ features to existing matplotlib plotting commands
along with several additional features designed to make your life easier.

The following features are relevant for the 1D plotting commands like
`~proplot.axes.PlotAxes.line` (equivalent to `~proplot.axes.PlotAxes.plot`)
and `~proplot.axes.PlotAxes.scatter`:

* The `cycle` keyword is interpreted by the `~proplot.constructor.Cycle`
  :ref:`constructor function <why_constructor>` and applies
  :ref:`property cyclers <ug_apply_cycle>` on-the-fly. This permits succinct
  and flexible property cycler declaration.
* The `legend` and `colorbar` keywords draw :ref:`on-the-fly legends and colorbars
  <ug_cbars_axes>` using the result of the plotting command. Note that colorbars can
  be drawn from :ref:`lists of artists <ug_cbars>` (see `~proplot.axes.Axes.legend`).
* The default `ylim` (`xlim`) in the presence of a fixed `xlim` (`ylim`) is now
  adjusted to exclude out-of-bounds data. This can be useful when "zooming in" on
  a dependent variable axis but can be disabled by setting :rcraw:`axes.inbounds`
  to ``False`` or passing ``inbounds=False`` to plot commands.
* The `~proplot.axes.PlotAxes.bar` and `~proplot.axes.PlotAxes.barh` commands accept 2D
  arrays and can :ref:`stack or group <ug_bar>` successive columns. Likewise, the
  `~proplot.axes.PlotAxes.area` and `~proplot.axes.PlotAxes.areax` commands (shorthands
  for `~proplot.axes.PlotAxes.fill_between` and `~proplot.axes.PlotAxes.fill_betweenx`)
  accept 2D arrays and can :ref:`stack or overlay <ug_bar>` successive columns.
* The `~proplot.axes.PlotAxes.bar`, `~proplot.axes.PlotAxes.barh`,
  `~proplot.axes.PlotAxes.vlines`, `~proplot.axes.PlotAxes.hlines`,
  `~proplot.axes.PlotAxes.area`, and `~proplot.axes.PlotAxes.areax`
  commands accept a `negpos` keyword argument that :ref:`assigns different colors
  <ug_negpos>` colors to "negative" and "positive" regions.
* The `~proplot.axes.PlotAxes.linex` and `~proplot.axes.PlotAxes.scatterx` commands
  are just like `~proplot.axes.PlotAxes.line` and `~proplot.axes.PlotAxes.scatter`,
  but positional arguments are interpreted as *x* coordinates or (*y*, *x*) pairs.
  There are also the related commands `~proplot.axes.PlotAxes.stemx`,
  `~proplot.axes.PlotAxes.stepx`, `~proplot.axes.PlotAxes.boxh` (shorthand for
  `~proplot.axes.PlotAxes.boxploth`), and `~proplot.axes.PlotAxes.violinh` (shorthand
  for `~proplot.axes.PlotAxes.violinploth`).
* The `~proplot.axes.PlotAxes.line`, `~proplot.axes.PlotAxes.linex`,
  `~proplot.axes.PlotAxes.scatter`, `~proplot.axes.PlotAxes.scatterx`,
  `~proplot.axes.PlotAxes.bar`, and `~proplot.axes.PlotAxes.barh` commands can
  quickly draw vertical or horizontal :ref:`error bars or "shading" <ug_errorbars>`
  using a variety of keyword arguments. This is often more convenient than
  working directly with `~matplotlib.axes.Axes.errorbar`.
* The `~proplot.axes.PlotAxes.parametric` command draws clean-looking
  :ref:`parametric lines <ug_parametric>` by encoding the parametric
  coordinate using colormap colors rather than text annotations.

The following features are relevant for the 2D plotting commands like
`~proplot.axes.PlotAxes.pcolor` and `~proplot.axes.PlotAxes.contour`:

* The `cmap` and `norm` :ref:`keyword arguments <ug_apply_cmap>` are interpreted
  by the `~proplot.constructor.Colormap` and `~proplot.constructor.Norm`
  :ref:`constructor functions <why_constructor>`. This permits succinct
  and flexible colormap and normalizer application.
* The `colorbar` keyword draws on-the-fly :ref:`colorbars <ug_cbars_axes>`
  using the result of the plotting command. Note that "inset" colorbars can also
  be drawn, analogous to "inset" legends (see `~proplot.axes.Axes.colorbar`).
* The `~proplot.axes.PlotAxes.contour`, `~proplot.axes.PlotAxes.contourf`,
  `~proplot.axes.PlotAxes.pcolormesh`, and `~proplot.axes.PlotAxes.pcolor` commands
  all accept a `labels` keyword. This draws :ref:`contour and grid box labels
  <ug_labels>` on-the-fly. Labels are automatically colored black or white
  according to the luminance of the underlying grid box or filled contour.
* The default `vmin` and `vmax` used to normalize colormaps now excludes data
  outside the *x* and *y* axis bounds `xlim` and `ylim` if they were explicitly
  fixed. This can be disabled by setting :rcraw:`cmap.inbounds` to ``False``
  or by passing ``inbounds=False`` to plot commands.
* The `~proplot.colors.DiscreteNorm` normalizer is paired with most colormaps by
  default. It can easily divide colormaps into distinct levels, similar to contour
  plots. This can be disabled by setting :rcraw:`cmap.discrete` to ``False`` or
  by passing ``discrete=False`` to plot commands.
* The `~proplot.colors.DivergingNorm` normalizer is perfect for data with a
  :ref:`natural midpoint <ug_norm>` and offers both "fair" and "unfair" scaling.
  The `~proplot.colors.SegmentedNorm` normalizer can generate
  uneven color gradations useful for :ref:`unusual data distributions <ug_norm>`.
* The `~proplot.axes.PlotAxes.heatmap` command invokes
  `~proplot.axes.PlotAxes.pcolormesh` then applies an `equal axes apect ratio
  <https://matplotlib.org/stable/gallery/subplots_axes_and_figures/axis_equal_demo.html>`__,
  adds ticks to the center of each gridbox, and disables minor ticks and gridlines.
  This can be convenient for things like covariance matrices.
* Coordinate centers passed to commands like `~proplot.axes.PlotAxes.pcolor` are
  automatically translated to "edges", and coordinate edges passed to commands like
  `~proplot.axes.PlotAxes.contour` are automatically translated to "centers". In
  matplotlib, ``pcolor`` simply truncates and offsets the data when it receives centers.
* Commands like `~proplot.axes.PlotAxes.pcolor`, `~proplot.axes.PlotAxes.contourf`
  and `~proplot.axes.Axes.colorbar` automatically fix an irritating issue where
  saved vector graphics appear to have thin white lines between `filled contours
  <https://stackoverflow.com/q/8263769/4970632>`__, `grid boxes
  <https://stackoverflow.com/q/27092991/4970632>`__, and `colorbar segments
  <https://stackoverflow.com/q/15003353/4970632>`__. This can be disabled by
  passing ``edgefix=False`` to plot commands.

Links
-----

* For the 1D plotting features,
  see :ref:`this page <ug_1dplots>`.
* For the 2D plotting features,
  see :ref:`this page <ug_2dplots>`.
* For standardization of 1D positional arguments,
  see :ref:`this page <ug_1dstd>`.
* For standardization of 2D positional arguments,
  see :ref:`this page <ug_2dstd>`.

.. _why_cartopy_basemap:

Cartopy and basemap integration
===============================

Limitation
----------

There are two widely-used engines for working with geographic data in
matplotlib: `cartopy`_ and `basemap`_.  Using cartopy tends to be
verbose and involve boilerplate code, while using basemap requires plotting
with a separate `~mpl_toolkits.basemap.Basemap` object rather than the
`~matplotlib.axes.Axes`. They both require separate import statements and extra
lines of code to configure the projection.

Furthermore, when you use `cartopy`_ and `basemap`_ plotting
commands, "map projection" coordinates are the default coordinate system
rather than longitude-latitude coordinates. This choice is confusing for
many users, since the vast majority of geophysical data are stored with
longitude-latitude (i.e., "Plate Carrée") coordinates.

Solution
--------

Proplot can succinctly create detailed geographic plots using either cartopy
or basemap as "backends". By default, cartopy is used, but basemap can be used
by passing ``basemap=True`` to axes-creation commands or by setting :rcraw:`basemap`
to ``True``. To create a geographic plot, simply pass the `PROJ <https://proj.org>`__
name to an axes-creation command, e.g. ``fig, ax = pplt.subplots(proj='pcarree')``
or ``fig.add_subplot(proj='pcarree')``. Alternatively, use the
`~proplot.constructor.Proj` constructor function to quickly generate
a `cartopy.crs.Projection` or `~mpl_toolkits.basemap.Basemap` instance.

Requesting geographic projections creates a `proplot.axes.GeoAxes`
with unified support for `cartopy`_ and `basemap`_ features via the
`proplot.axes.GeoAxes.format` command. This lets you quickly modify geographic
plot features like latitude and longitude gridlines, gridline labels, continents,
coastlines, and political boundaries. The syntax is conveniently analogous to the
syntax used for `proplot.axes.CartesianAxes.format` and `proplot.axes.PolarAxes.format`.

The `~proplot.axes.GeoAxes` subclass also makes longitude-latitude coordinates
the "default" coordinate system by passing ``transform=ccrs.PlateCarree()``
or ``latlon=True`` to plotting commands (depending on whether cartopy or basemap
is the backend). And to enforce global coverage over the poles and across longitude
seams, you can pass ``globe=True`` to 2D plotting commands like
`~proplot.axes.PlotAxes.contour` and `~proplot.axes.PlotAxes.pcolormesh`.

Links
-----

* For an introduction,
  see :ref:`this page <ug_geo>`.
* For more on cartopy and basemap as backends,
  see :ref:`this page <ug_backends>`.
* For plotting in `~proplot.axes.GeoAxes`,
  see :ref:`this page <ug_geoplot>`.
* For formatting `~proplot.axes.GeoAxes`,
  see :ref:`this page <ug_geoformat>`.
* For changing the `~proplot.axes.GeoAxes` bounds,
  see :ref:`this page <ug_zoom>`.

.. _why_xarray_pandas:

Pandas and xarray integration
=============================

Limitation
----------

Scientific data is commonly stored in array-like containers
that include metadata -- namely, `xarray.DataArray`\ s, `pandas.DataFrame`\ s,
and `pandas.Series`. When matplotlib receives these objects, it ignores
the associated metadata. To create plots that are labeled with the metadata,
you must use the `xarray.DataArray.plot`, `pandas.DataFrame.plot`,
and `pandas.Series.plot` commands instead.

This approach is fine for quick plots, but not ideal for complex ones. It requires
learning a different syntax from matplotlib, and tends to encourage using the
`~matplotlib.pyplot` interface rather than the object-oriented interface. The
``plot`` commands also include features that would be useful additions to matplotlib
in their own right, without requiring special containers and a separate interface.

Solution
--------

Proplot reproduces many of the `xarray.DataArray.plot`,
`pandas.DataFrame.plot`, and `pandas.Series.plot`
features directly on the axes plotting commands themselves.
This includes :ref:`grouped or stacked <ug_bar>` bar plots
and :ref:`layered or stacked <ug_bar>` area plots from two-dimensional
input data, auto-detection of :ref:`diverging datasets <ug_autonorm>` for
application of diverging colormaps and normalizers, and
:ref:`on-the-fly colorbars and legends <ug_cbars_axes>` using `colorbar`
and `legend` keywords.

Proplot also handles metadata associated with `xarray.DataArray`, `pandas.DataFrame`,
`pandas.Series`, and `pint.Quantity` objects. When a plotting command receives these
objects, it updates the axis tick labels, axis labels, subplot title, and
colorbar and legend labels from the metadata. For `~pint.Quantity` arrays (including
`~pint.Quantity` those stored inside `~xarray.DataArray` containers), a unit string
is generated from the `pint.Unit` according to the :rcraw:`unitformat` setting
(note proplot also automatically calls `pint.UnitRegistry.setup_matplotlib`
whenever a `~pint.Quantity` is used for *x* and *y* coordinates and removes the
units from *z* coordinates to avoid the stripped-units warning message).
These features can be disabled by setting :rcraw:`autoformat` to ``False``
or passing ``autoformat=False`` to any plotting command.

Links
-----

* For integration with 1D plotting commands,
  see :ref:`this page <ug_1dintegration>`.
* For integration with 2D plotting commands,
  see :ref:`this page <ug_2dintegration>`.
* For bar and area plots,
  see :ref:`this page <ug_bar>`.
* For diverging datasets,
  see :ref:`this page <ug_autonorm>`.
* For on-the-fly colorbars and legends,
  see :ref:`this page <ug_cbars_axes>`.

.. _why_aesthetics:

Aesthetic colors and fonts
==========================

Limitation
----------

A common problem with scientific visualizations is the use of "misleading"
colormaps like ``'jet'``. These colormaps have jarring jumps in
`hue, saturation, and luminance <rainbow_>`_ that can trick the human eye into seeing
non-existing patterns. It is important to use "perceptually uniform" colormaps
instead. Matplotlib comes packaged with `a few of its own <matplotlib_>`_, plus
the `ColorBrewer <brewer_>`_ colormap series, but external projects offer
a larger variety of aesthetically pleasing "perceptually uniform" colormaps
that would be nice to have in one place.

Matplotlib also "registers" the X11/CSS4 color names, but these are relatively
limited. The more numerous and arguably more intuitive `XKCD color survey <xkcd_>`_
names can only be accessed with the ``'xkcd:'`` prefix. As with colormaps, there
are also external projects with useful color names like `open color <opencolor_>`_.

Finally, matplotlib comes packaged with ``DejaVu Sans`` as the default font.
This font is open source and include glyphs for a huge variety of characters.
However in our opinion, it is not very aesthetically pleasing. It is also
difficult to switch to other fonts on limited systems or systems with fonts
stored in incompatible file formats (see :ref:`below <why_dotproplot>`).

Solution
--------

Proplot adds new colormaps, colors, and fonts to help you make more
aesthetically pleasing figures.

* Proplot adds colormaps from the `seaborn <seacolor_>`_, `cmocean <cmocean_>`_,
  `SciVisColor <sciviscolor_>`_, and `Scientific Colour Maps <fabio_>`_ projects.
  It also defines a few default :ref:`perceptually uniform colormaps <ug_perceptual>`
  and includes a `~proplot.colors.PerceptualColormap` class for generating
  new ones. A :ref:`table of colormap <ug_cmaps_included>` and
  :ref:`color cycles <ug_cycles_included>` can be shown using
  `~proplot.demos.show_cmaps` and `~proplot.demos.show_cycles`.
  Colormaps like ``'jet'`` can still be accessed, but this is discouraged.
* Proplot adds colors from the `open color <opencolor_>`_ project and adds
  `XKCD color survey <xkcd_>`_ names without the ``'xkcd:'`` prefix after
  *filtering* them to exclude perceptually-similar colors and *normalizing* the
  naming pattern to make them more self-consistent. Old X11/CSS4 colors can still be
  accessed, but this is discouraged. A :ref:`table of color names <ug_colors_included>`
  can be shown using `~proplot.demos.show_colors`.
* Proplot comes packaged with several additional :ref:`sans-serif fonts
  <ug_fonts_included>` and the entire `TeX Gyre <texgyre_>`_ font series. TeX Gyre
  consists of open-source fonts designed to resemble more popular, commonly-used fonts
  like Helvetica and Century. They are used as the new default serif, sans-serif,
  monospace, cursive, and "fantasy" fonts, and they are available on all workstations.
  A :ref:`table of font names <ug_fonts_included>` can be shown
  using `~proplot.demos.show_fonts`.

Links
-----

* For more on colormaps,
  see :ref:`this page <ug_cmaps>`.
* For more on color cycles,
  see :ref:`this page <ug_cycles>`.
* For more on fonts,
  see :ref:`this page <ug_fonts>`.
* For importing custom colormaps, colors, and fonts,
  see :ref:`this page <why_dotproplot>`.

.. _why_colormaps_cycles:

Manipulating colormaps
======================

Limitation
----------

In matplotlib, colormaps are implemented with the
`~matplotlib.colors.LinearSegmentedColormap` class (representing "smooth"
color gradations) and the `~matplotlib.colors.ListedColormap` class (representing
"categorical" color sets). They are somewhat cumbersome to modify or create from
scratch. Meanwhile, property cycles used for individual plot elements are implemented
with the `~cycler.Cycler` class. They are easier to modify but they cannot be
"registered" by name like colormaps.

The `seaborn`_ package introduces "color palettes" to make working with colormaps
and property cycles easier, but it would be nice to have similar features integrated
more closely with matplotlib.

Solution
--------

Proplot tries to make it easy to manipulate colormaps and property cycles.

* All colormaps in proplot are replaced with the `~proplot.colors.ContinuousColormap`
  and `~proplot.colors.DiscreteColormap` subclasses of
  `~matplotlib.colors.LinearSegmentedColormap` and `~matplotlib.colors.ListedColormap`.
  These classes include several useful features leveraged by the
  :ref:`constructor functions <why_constructor>`
  `~proplot.constructor.Colormap` and `~proplot.constructor.Cycle`.
* The `~proplot.constructor.Colormap` function can merge, truncate, and
  modify existing colormaps or generate brand new colormaps. It can also
  create new `~proplot.colors.PerceptualColormap`\ s -- a type of
  `proplot.colors.ContinuousColormap` with linear transitions in the
  :ref:`perceptually uniform-like <ug_perceptual>` hue, saturation,
  and luminance channels rather then the red, blue, and green channels.
* The `~proplot.constructor.Cycle` function can make property cycles from
  scratch or retrieve "registered" color cycles from their associated
  `~proplot.colors.DiscreteColormap` instances. It can also make property
  cycles by splitting up the colors from registered or on-the-fly
  `~proplot.colors.ContinuousColormap`\ s and `~proplot.colors.PerceptualColormap`\ s.

Proplot also makes all colormap and color cycle names case-insensitive, and
colormaps are automatically reversed or cyclically shifted 180 degrees if you
append ``'_r'`` or ``'_s'`` to any colormap name. These features are powered by
`~proplot.colors.ColormapDatabase`, which replaces matplotlib's native
colormap database.

Links
-----

* For making new colormaps,
  see :ref:`this page <ug_cmaps_new>`.
* For making new color cycles,
  see :ref:`this page <ug_cycles_new>`.
* For merging colormaps and cycles,
  see :ref:`this page <ug_cmaps_merge>`.
* For modifying colormaps and cycles,
  see :ref:`this page <ug_cmaps_mod>`.

.. _why_norm:

Physical units engine
=====================

Limitation
----------

Matplotlib uses figure-relative units for the margins `left`, `right`,
`bottom`, and `top`, and axes-relative units for the column and row spacing
`wspace` and `hspace`.  Relative units tend to require "tinkering" with
numbers until you find the right one. And since they are *relative*, if you
decide to change your figure size or add a subplot, they will have to be
readjusted.

Matplotlib also requires users to set the figure size `figsize` in inches.
This may be confusing for users outside of the United States.

Solution
--------

Proplot introduces the physical units engine `~proplot.utils.units` for
interpreting `figsize`, `figwidth`, `figheight`, `refwidth`, `refheight`,
`left`, `right`, `top`, `bottom`, `wspace`, `hspace`, and keyword arguments in a
few other places. Acceptable units include inches, centimeters, millimeters,
pixels, `points <https://en.wikipedia.org/wiki/Point_(typography)>`__, `picas
<https://en.wikipedia.org/wiki/Pica_(typography)>`__, and `em-heights
<https://en.wikipedia.org/wiki/Em_(typography)>`__ (a table of acceptable units
is found :ref:`here <units_table>`). Em-heights are particularly useful, as the
figure text can be a useful "ruler" when figuring out the amount of space you
need. The `~proplot.utils.units` function also translates rc settings assigned
to `~proplot.config.rc_matplotlib` and `~proplot.config.rc_proplot`, e.g.
:rcraw:`axes.labelpad`, :rcraw:`legend.handlelength`, and
:rcraw:`subplot.refwidth`.

Links
-----

* For more on physical units,
  see :ref:`this page <ug_units>`.

.. _why_rc:

Flexible global settings
========================

Limitation
----------

In matplotlib, there are several `~matplotlib.rcParams` that would be
useful to set all at once, like spine and label colors. It might also
be useful to change these settings for individual subplots rather
than globally.

Solution
--------

In proplot, you can use the `~proplot.config.rc` object to change both native
matplotlib settings (found in `~proplot.config.rc_matplotlib`) and added proplot
settings (found in `~proplot.config.rc_proplot`). Assigned settings are always
validated, and special settings like ``meta.edgecolor``, ``meta.linewidth``, and
``font.smallsize`` can be used to update many settings all at once. Settings can
be changed with ``pplt.rc.key = value``, ``pplt.rc[key] = value``,
``pplt.rc.update(key=value)``, using `proplot.axes.Axes.format`, or using
`proplot.config.Configurator.context`. Settings that have changed during the
python session can be saved to a file with `proplot.config.Configurator.save`
(see `~proplot.config.Configurator.changed`), and settings can be loaded from
files with `proplot.config.Configurator.load`.

Links
-----

* For an introduction,
  see :ref:`this page <ug_rc>`.
* For more on global settings,
  see :ref:`this page <ug_config>`.

.. _why_dotproplot:

Loading stuff
=============

Limitation
----------

Matplotlib `~matplotlib.rcParams` can be changed persistently by placing
``matplotlibrc`` files in the same directory as your python script. But it
can be difficult to design and store your own colormaps and color cycles for
future use. It is also difficult to get matplotlib to use custom ``.ttf`` and
``.otf`` font files, which may be desirable when you are working on
Linux servers with limited font selections.

Solution
--------

Proplot settings can be changed persistently by editing the default ``proplotrc``
file in the location given by `~proplot.config.Configurator.user_file` (this is
usually ``$HOME/.proplot/proplotrc``) or by adding ``proplotrc`` files to either
the current directory or any parent directory. Adding files to parent directories
can be useful when working in projects with lots of subfolders.

Proplot also automatically registers colormaps, color cycles, colors, and font
files stored in the ``cmaps``,  ``cycles``, ``colors``, and ``fonts`` folders in
the location given by `~proplot.config.Configurator.user_folder` (this is usually
``$HOME/.proplot``). You can save colormaps and color cycles to these
folders simply by passing ``save=True`` to `~proplot.constructor.Colormap` and
`~proplot.constructor.Cycle`. To manually register these files, or to
register arbitrary input arguments, you can use `~proplot.config.register_cmaps`,
`~proplot.config.register_cycles`, `~proplot.config.register_colors`, or
`~proplot.config.register_fonts`.

Links
-----

* For the ``proplotrc`` file,
  see :ref:`this page <ug_proplotrc>`.
* For registering colormaps,
  see :ref:`this page <ug_cmaps_dl>`.
* For registering color cycles,
  see :ref:`this page <ug_cycles_dl>`.
* For registering colors,
  see :ref:`this page <ug_colors_user>`.
* For registering fonts,
  see :ref:`this page <ug_fonts_user>`.
