artemp 38da080f82 make concrete image_data type names more expressive and explicit about color channels/depth: ... image_data_32 -> image_data_rgba8 image_data_8 -> image_data_gray8 image_data_16 -> image_data_gray16 image_data_float32 -> image_data_gray32f NOTE: currently image_data_gray16::pixel_type = std::int16_t (signed 16 bit int) to match GDAL should we support unsigned types?		2014-12-04 11:02:42 +01:00
..
csv	update copyright year	2014-11-20 15:25:50 +01:00
gdal	make concrete image_data type names more expressive and explicit about color channels/depth:	2014-12-04 11:02:42 +01:00
geojson	feature_collection_grammar : allow passing start_id at parse time - #2582	2014-11-24 12:26:11 +01:00
occi	update copyright year	2014-11-20 15:25:50 +01:00
ogr	update copyright year	2014-11-20 15:25:50 +01:00
osm	update copyright year	2014-11-20 15:25:50 +01:00
pgraster	make concrete image_data type names more expressive and explicit about color channels/depth:	2014-12-04 11:02:42 +01:00
postgis	update copyright year	2014-11-20 15:25:50 +01:00
python	silence boost warnings	2014-10-21 16:37:27 -07:00
raster	make concrete image_data type names more expressive and explicit about color channels/depth:	2014-12-04 11:02:42 +01:00
rasterlite	make concrete image_data type names more expressive and explicit about color channels/depth:	2014-12-04 11:02:42 +01:00
shape	update copyright year	2014-11-20 15:25:50 +01:00
sqlite	use four letter abriviations to determine datatypes (https://www.sqlite.org/datatype3.html)	2014-11-25 11:09:42 +01:00
templates	don't call *params.get<std::string>("type"), instead use static datasource::name()	2014-06-26 10:51:24 +01:00
topojson	update copyright year	2014-11-20 15:25:50 +01:00