* Added support for Proj6 and GDAL 3
* install proj6
* build proj with local installation dir
* conditional proj dependency
* added proj4 flags for all gdal versions
* Restore debian data tests
* Version specific proj configuration
* Fix string comp expression
* Explicit matrix
* Restructure build matrix
* Remove wait from proj build script
* Call script with bash
* Fix version text
* Bash syntax
* Correct PROJOPTs
* Use xvfb service
* Back to proj 4.8 for older GDAL
* Fix syntax error
* Add verbosity to tests
* Take proj off library path, remove gdal-bin package
* Install PROJ and GDAL to same prefix
* Set up runtime env
* Try 4.9.3
* Source build scripts
* Switch to case for versions
* set trace
* Test existence of share/gdal directory
The proj install script created the gdal install directory so a
test for just that is not sufficient.
* Test for share/proj
* Run tests under gdb
* Forgot the run command
* Wait 20 for GDAL
* travis_wait
* Restructure build script, less boilerplate
* Back to trusty
* dist: trusty
* Remove gdb
* Allow 3.0.1/6.1.1 to fail, some changes since 3.0.0/6.1.0
- I doubt compat with GDAL 1.9 is needed nowadays
- Addition of test against GDAL trunk (with a allow_failures), to detect
either GDAL bugs or integration issues at earliest stage. GDAL is rebuilt
if the revision changed, otherwise the cached build is used
Also tests for the CLI.
Much refactoring on rio bounds and shapes was done
here. Profiling needs to be done to see what can be done
to speed it up.
Closes#127.
See draft-ietf-json-text-sequence-04
http://tools.ietf.org/html/draft-ietf-json-text-sequence-04
for a description of JSON text sequences. In a nutshell, this
means a feature collection as a LF-seperated sequence of feature
objects that can be parsed and processed incrementally. Is this
the first implementation in a geographic application? I haven't
seen others yet.
A deprecation warning is raised from the transform property and
an affine property is added to provide the new feature.
For method and function arguments, we sniff out GDAL geotransforms
and try to do the right thing with them, also raising deprecation
warnings in these cases.
