Add test case for missing columns in SQLite datasource. Refs #2579
Default to string type when column type could not be determined. Refs #2579
Add test case for missing columns in SQLite datasource, using subquery. Refs #2579
fix error message in geojson plugin
python bindings: update copyright year
use qi::locals<std::size_t> for per parse feature id generation and remove generate_id phoenix function
(NOTE: ids start from 1)
fix text-line-wrap grid ids
feature_collection_grammar : allow passing start_id at parse time - #2582
feature_collection_grammar: make argument order consistent across parsing rules - #2582
feature_collection_grammar: fix a mistake - #2582
Merge pull request #2580 from StevenLooman/master

Tests and fix for SQLite datasource missing column
use four letter abriviations to determine datatypes (https://www.sqlite.org/datatype3.html)
more c++11 typed enums
use c++11 typed enum in vertex.hpp
drop unsupported geotiff output - refs #967
handle/throw on invalid encoding for ucnv_open
iwyu
convert raster_symbolizer_test to use full image comparisons
Ignore overviews with 0 scale in pgraster

refs #2551

Postgis raster_columns view is returning NULL values for raster
overviews with large scale factors. That issue in postgis is described
in http://trac.osgeo.org/postgis/ticket/3006

This causes two main problems:

  - The first overview with scale = NULL is wrongly chosen for rendering
    always

  - The messed up scaling factor causes the render symbolizer to spent
    an insane amount of CPU and memory to render a messed up tiles.

The patch in postgis is expected to be released with the new version, a
few months from now.

Conflicts:
	plugins/input/pgraster/pgraster_datasource.cpp
use font-feature-settings per text_item