I noticed some differences between the docs and the source code. By default scheme is ``None`` and ``equal_interval`` mustn't end with an s otherwise an exception is raised. I also changed the link because the current URL resolves to a 404 error.
Not doing so resulted in incorrect dtypes when the
result was empty since numpy could not automatically
determine the dtype. This then had the effect of
indexing dropping columns unexpectedly.
Closes#685
* Fix for when read_file bbox crs does not match target file crs
* added tests for read_file with GeoSeries/GeoDataFrame boundary
* Group related tests in test_io
* Make adjustment to read_file bounding box doc
* BUG: Save z dimension in file writes
In so doing, add the has_z attribute to series. The check in determining
the geometry type is pretty simplistic. Given how fiona is thinking
about geometry types now (https://github.com/Toblerity/Fiona/issues/465)
I didn't see a clearly better way.
* Add test for a 3d polygon, too
* TST: Add has_z test
* TST: Mix 2D/3D polygons in file writes
Removed the pandas assert_frame_equal test because it will no longer
pass anywhere due to the 2D/3D handling, which doesn't look like
something there's any way around without changes to fiona (or possibly
GDAL?).
* Remove descartes from install requirements
The descartes import in plotting is hidden, so it is not a hard
dependency, and should not be required for installation.
* Update install reqs in README.md
* Raise ValueError using to_file with bool column
Fiona doesn't support writing to files with boolean type. There was some
discussion of converting to int and writing to file anyway, but at a
minimum seems useful to raise a clearer message about the problem.
* Improve warning with to_file on bool column
Can optionally set the size of points in a scatter plot of point
geometries to be specified by the value of a column in the frame. Note
that it does not perform any normalization at present, so very small or
very large values in the column specified lead to less than desirable
results. Also no checks on user, so if a user specifies a column with a
non numeric type, it does throw a slightly less than clear error.
* fixed nybb
* rearrange chloropleths example
* added badge to MyBinder
* extra formatting on README
* add extra info in chrolopleths.ipynb
* Update choropleths example
* BUG: sjoin modifies original frame (#525)
Original pandas table's index names are no
longer changed by sjoin() call. Includes
some unit-tests. Fixes issue #525
* New code to fix issue that is compatible with pandas 0.16.2 - 0.20.3
* applied suggested changes to test_sjoin.py
As of 0.20.0, pandas .ix is deprecated. This switches all such instances
to the label based .loc indexer. (In searching for usage, I also noticed
the CHANGELOG contained an error in describing the introduction of the
.cx indexer.)
All current overlay tests have indices for which loc/iloc give the same
result. Since ix will be deprecated, add a test to distinguish behavior
between the two.
* TST: Set test gdf crs to silence crs warning
The symmetric difference test compared a frame with a crs to one
without. It didn't seem that this was intentional, so set the second
frame crs to the first so that the tests run without warnings.
Warning below:
geopandas/tests/test_geom_methods.py::TestGeomMethods::()::test_symmetric_difference_series
/home/james/python/geopandas/geopandas/base.py:29: UserWarning: GeoSeries crs mismatch: {'init': 'epsg:4326', 'no_defs': True} and None
other.crs))
geopandas/tests/test_geom_methods.py::TestGeomMethods::()::test_symmetric_difference_operator
/home/james/python/geopandas/geopandas/base.py:29: UserWarning: GeoSeries crs mismatch: {'init': 'epsg:4326', 'no_defs': True} and None
other.crs))
* Add test intended to catch CRS warning
`plot_dataframe` now accepts a `legend_kwds` argument, through which a user can pass keyword arguments accepted by the call to matplotlib's legend function (if `legend=True`).
Use geopy's get_geocoder_for_service to map strings to the proper class
to use, so a geopandas user can use any available geopy Geocoder. Also
provide option to use a Geocoder instance, rather than the string
mapping, which is potentially more transparent.
Joris Van den Bossche