- remove py27 dev build (pandas master no longer supports python 2.7) and replace with pandas 0.23 build
- py37 dev build: move installing pandas and matplotlib master to separate steps in travis yml file (otherwise the conda create step takes too long)
- remove conda-forge/label/dev label for fiona (was still installing the rc instead of actual released version)
See ResidentMario/geoplot#69: depending on how the data are subsampled, we stumble into a potential bug in geoplot. So fixing the random state with a working one to prevent this.
* TST: Make port settable or gettable from env
As raised in #822, may be useful to have the postgis port settings more
generic.
* Add other postgres env settings too
* Add more documentation on postgis test setup
* Consider a new plotting artist for improving colormap legends
* test: add a unit test for verifying legend height
* plotting: manage 'cax' argument without 'ax' one
* test: add a missing 'abs(.)' function to cax height test
* doc: complete 'mapping.rst' with details about the choropleth legends
* Update mapping.rst
Make explanation of colorbar example more concise
Travis CI tests were failing recently for one specific build, see https://github.com/conda-forge/gdal-feedstock/issues/261
Fixed by removing the pin of matplotlib to 1.5.3 (but added `gdal=2.3` to keep at older gdal version).
Also added `nomkl` to have a built with numpy/openblas from conda-forge (not that it should matter though).
* Add very basic benchmarks for file reading/writing
Just created a moderate sized series and frame and tested reading and
writing.
* Add benchmarks for other file extensions
The request to google is frequently (always?) failing in the past few
months, so use geocodefarm instead for the example of how to use
geocoding in geopandas.
* updated the demo dataset
new shapefiles from http://www.naturalearthdata.com/downloads/110m-cultural-vectors/110m-admin-0-countries/
* script to create example dataset
Reads the earth data from naturalearth.com as a geojson and selects the 6 columns used to create the example datasets.
* changed shapefile source
added the .zip file from naturalearth.com with version 4.1.0 shapefiles. Also added a line that changes column names to lowercase to match the example dataset
* removed .zip shapefile
I wasn't sure if I should include the .zip or not. It's removed now. Thank you for clarifying.
* added module docstring
* Make small revisions to demo dataset creation file
* access to all mapclassify schemes including keywords (#235, #357)
* test for classificaition_kwds
* scheme docstring to get rid of selection of schemes
* Explicit list of possible schemes in docstring
* New classification schemes in docs (and changed PySAL to mapclassify)
* import all mapclassify clasifiers instead passing them explicitly
* inspect compatible with python 2
* fix getargspec for python 2.7
* minor update of docs
* added method for getting long-definition of epsg codes
* more testing for explicit_crs_from_epsg
* more testing for explicit_crs_from_epsg
* added new function `epsg_from_crs`
* ignore nan in setting mn and mx
* test if vmin vmax set correctly for array with NaN
* test compatible with older versions
* reference to issue and shorter assert in test
* TST: test read_postgis with NULL geometry
Though GIS databases permit NULL values in the geometry field, read_postgis throws exceptions when it encounters them.
test_read_postgis_null_geom defines this test case with sqlite3 database, and support functions are revised to support it.
create_sqlite is revised to loosen data type restrictions and follow [recommendations from the python manual](https://docs.python.org/3/library/sqlite3.html)
- connection parameter instead of filename to allow for in-memory database
- 'with' statement for transaction management
- parameter substitution instead of string operations
validate_boro_df strips NULL values before checking geometry type.
* TST: replace sqlite test with spatialite test
The original SQLite test reflected unlikely usage for geospatial analysis.
In parity with PostGIS, the new test runs against SQLite with SpatiaLite enabled.
For coverage, test geometries read as text and binary.
* TST: add libspatialite as a test dependency
* TST: add conda-forge testing environment for Python 2.7
add this environment to continuous integration
conda-forge Python 2.7 enables loadable SQLite extensions with conda-forge/python-feedstock#227
adding this environment enables SpatiaLite tests
* BUG: fix read_postgis & GeoDataFrame to accept NULL geometry values
read_postgis failed to load nullable binary geometry data while GeoDataFrame raised exceptions on NULL in the geometry field.
This fixes both issues.
It moreover adds logic to detect python version & load geometries from
python 2 buffers as necessary.
* ENH DOC: drop hex_encoded parameter from read_postgis & from_postgis
drop hex_encoded, since sqlite3 represents binary & text as distinct Python data types
adjust names to clarify this distinction
adjust documentation to clarify geometry is expected in WKB representation (which was implicit)
add example SpatiaLite usage reflecting this expectation
* Fixing minor misspelling in Contributing.md file
* Updating CONTRIBUTING file to reflect python 3.x
* Support for Python v 2.7 edits
* Consistent capitalization of Python
* Adjust python support version
Géraud