A conda-smithy repository for basemap-data-hires.
Shell Batchfile Python
Latest commit 7967c9a Feb 10, 2017 @ocefpaf ocefpaf committed on GitHub Merge pull request #10 from ocefpaf/rerender
re-render with auto
Failed to load latest commit information.
ci_support rerender with auto Jan 14, 2017
recipe Update commit hash Nov 14, 2016
.gitattributes MNT: Updated the feedstock for conda-smithy version 1.7.0. Dec 29, 2016
.gitignore Initial commit of the basemap-data-hires feedstock. Mar 25, 2016
.travis.yml re-render with auto Feb 10, 2017
LICENSE re-render with auto Feb 10, 2017
README.md MNT: Updated the feedstock for conda-smithy version 1.7.0. Dec 29, 2016
circle.yml rerender Oct 9, 2016
conda-forge.yml Re-render the feedstock after CI registration. Mar 25, 2016


About basemap-data-hires

Home: http://matplotlib.org/basemap

Package license: GPL-2.0

Feedstock license: BSD 3-Clause

Summary: Plot on map projections (with coastlines and political boundaries) using matplotlib.

Current build status

Linux: Circle CI OSX: TravisCI Windows: AppVeyor

Current release info

Version: Anaconda-Server Badge Downloads: Anaconda-Server Badge

Installing basemap-data-hires

Installing basemap-data-hires from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge

Once the conda-forge channel has been enabled, basemap-data-hires can be installed with:

conda install basemap-data-hires

It is possible to list all of the versions of basemap-data-hires available on your platform with:

conda search basemap-data-hires --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by CircleCI, AppVeyor and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.


feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating basemap-data-hires-feedstock

If you would like to improve the basemap-data-hires recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/basemap-data-hires-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.