toblerity / fio-buffer Goto Github PK

@geowurster this is awesome. We've talked about it elsewhere, but I want to mention it here, too: I'd love to see support for fio-cat's feature sequences so that we can have unlimited pipe fun like

$ fio cat example.shp | \
> fio buffer --distance 10 | \
> fio buffer --distance "-10" | \
> fio collect | \
> geojsonio

See Toblerity/Fiona#282

Consider the following situations:

1. fio buffer --src-crs reads, buffers, and writes in the input CRS.
2. fio buffer --src-crs --buf-crs buffers geometries in a different CRS but reprojects to the original CRS before writing.
3. fio buffer --src-crs --buf-crs --dst-crs reads geometries in one CRS, buffers, in another, and reprojects to a third before writing.
4. fio buffer --src-crs --dst-crs reads and buffers geometries in one CRS but reprojects to another before writing.
5. fio buffer --buf-crs --dst-crs buffers in one and writes to another.

Item 4 should probably buffer in the --dst-crs?

Waiting on Toblerity/Fiona#213

• Add a unittest to verify that the command is registering properly with fio
• Update setup.py to require Fiona>=1.6.0
• Run tests and check Travis
• Pull onto v01.1 branch
• Push to PyPi
• Tag a release in git

• Change ownership
• Update __source__ tag in __init__
• Update setup.py

/ cc @sgillies

If the changes aren't breaking, lets make it 0.2 and hit 1.0 later.

Probably worth waiting at least 24 hours before trying to fix. The first post-migration test on Travis just ran, so it might take a bit for Travis to fully recognize the ownership change.

Travis can build and test if the tests interact directly with the CLI command instead of through fio.

Give everything a nice scrub.