update changelog, version, and readme with new ARNs

Author: matthewhanson

CHANGELOG.md

@@ -6,6 +6,30 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+
+## [v2.0.0] - 2019-10-25
+
+Updated GDAL, PROJ, and Geotiff libraries.
+
+### Package versions
+- GDAL_VERSION=3.0.1
+- PROJ_VERSION=6.2.0
+- GEOS_VERSION=3.8.0
+- GEOTIFF_VERSION=1.5.1
+- HDF4_VERSION=4.2.14
+- HDF5_VERSION=1.10.5
+- NETCDF_VERSION=4.7.1
+- NGHTTP2_VERSION=1.39.2
+- OPENJPEG_VERSION=2.3.1
+- CURL_VERSION=7.66.0
+- LIBJPEG_TURBO_VERSION=2.0.3
+- PKGCONFIG_VERSION=0.29.2
+- SZIP_VERSION=2.1.1
+- WEBP_VERSION=1.0.3
+- ZSTD_VERSION=1.4.3
+- OPENSSL_VERSION=1.0.2
+
+
 ## [v1.2.0] - 2019-10-24
 
 ### Added
@@ -32,6 +56,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - WEBP_VERSION=1.0.3
 - ZSTD_VERSION=1.4.3
 
+
 ## [v1.1.0] - 2018-03-22
 
 ### Added
@@ -65,6 +90,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - WEBP_VERSION=1.0.1
 - ZSTD_VERSION=1.3.8
 
+
 ## [v1.0.0] - 2018-07-27
 
 #### Versions:
@@ -79,5 +105,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - GDAL_VERSION=2.3.1
 
 [Unreleased]: https://github.com/sat-utils/sat-stac/compare/master...develop
+[v2.0.0]: https://github.com/developmentseed/geolambda/compare/1.2.0...2.0.0
+[v1.2.0]: https://github.com/developmentseed/geolambda/compare/1.1.0...1.2.0
 [v1.1.0]: https://github.com/developmentseed/geolambda/compare/1.0.0...1.1.0
 [v1.0.0]: https://github.com/developmentseed/geolambda/tree/1.0.0

README.md

@@ -15,6 +15,7 @@ While GeoLambda was initially intended for AWS Lambda it is also useful as a bas
 | 1.0.0     | 2.3.1 | |
 | 1.1.0     | 2.4.1 | |
 | 1.2.0     | 2.4.2 | Separate Python (3.7.4) image and Lambda Layer added |
+| 2.0.0		| 3.0.1 | libgeotiff 1.5.1, proj 6.2.0 |
 
 ### Docker images
 
@@ -40,6 +41,24 @@ All of the GDAL CLI tools are installed so could be run on images in the current
 
 If you just wish to use the publicly available Lambda layer you will need the ARN for the layer in the same region as your Lambda function. Currently, GeoLambda layers are available in `us-east-1`, `us-west-2`, and `eu-central-1`. If you want to use it in another region please file an issue or you can also create your own layer using this repository (see instructions below on 'Create a new version').
 
+#### v2.0.0
+
+| Region | ARN |
+| ------ | --- |
+| us-east-1 | arn:aws:lambda:us-east-1:552188055668:layer:geolambda:3 |
+| us-west-2 | arn:aws:lambda:us-west-2:552188055668:layer:geolambda:3 |
+| eu-central-1 | arn:aws:lambda:eu-central-1:552188055668:layer:geolambda:3 |
+
+#### v2.0.0-python
+
+See the [GeoLambda Python README](python/README.md). The Python Lambda Layer includes the libraries `numpy`, `rasterio`, `GDAL`, `pyproj`, and `shapely`.
+
+| Region | ARN |
+| ------ | --- |
+| us-east-1 | arn:aws:lambda:us-east-1:552188055668:layer:geolambda-python:2 |
+| us-west-2 | arn:aws:lambda:us-west-2:552188055668:layer:geolambda-python:2 |
+| eu-central-1 | arn:aws:lambda:eu-central-1:552188055668:layer:geolambda-python:2 |
+
 #### v1.2.0
 
 | Region | ARN |

VERSION

@@ -1 +1 @@
-1.2.0
+2.0.0b1