You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-17Lines changed: 25 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -17,25 +17,12 @@ While GeoLambda was initially intended for AWS Lambda it is also useful as a bas
17
17
| 1.2.0 | 2.4.2 | Separate Python (3.7.4) image and Lambda Layer added |
18
18
| 2.0.0 | 3.0.1 | libgeotiff 1.5.1, proj 6.2.0 |
19
19
20
-
### Docker images
21
-
22
-
The Docker images used to create the Lambda layer are also published to Docker Hub, and thus are also suitable for general use as a base image for geospatial applications.
23
-
24
-
The developmentseed/geolambda image in Docker Hub is tagged by version.
20
+
#### Environment variables
25
21
26
-
$ docker pull developmentseed/geolambda:<version>
22
+
When using GeoLambda some environment variables need to be set. These are set in the Docker image, but if using the Lambda Layer they will need to be set:
27
23
28
-
Or just include it in your own Dockerfile as the base image.
29
-
30
-
```
31
-
FROM developmentseed/geolambda:<version>
32
-
```
33
-
34
-
The GeoLambda image does not have an entrypoint defined, so a command must be provided when you run it. This example will mount the current directory to /work and run the container interactively.
35
-
36
-
$ docker run --rm -v $PWD:/home/geolambda -it developmentseed/geolambda:latest /bin/bash
37
-
38
-
All of the GDAL CLI tools are installed so could be run on images in the current directory.
24
+
- GDAL_DATA=/opt/share/gdal
25
+
- PROJ_LIB=/opt/share/proj (only needed for GeoLambda 2.0.0+)
39
26
40
27
### Lambda Layers
41
28
@@ -86,6 +73,27 @@ See the [GeoLambda Python README](python/README.md). The Python Lambda Layer inc
The Docker images used to create the Lambda layer are also published to Docker Hub, and thus are also suitable for general use as a base image for geospatial applications.
79
+
80
+
The developmentseed/geolambda image in Docker Hub is tagged by version.
81
+
82
+
$ docker pull developmentseed/geolambda:<version>
83
+
84
+
Or just include it in your own Dockerfile as the base image.
85
+
86
+
```
87
+
FROM developmentseed/geolambda:<version>
88
+
```
89
+
90
+
The GeoLambda image does not have an entrypoint defined, so a command must be provided when you run it. This example will mount the current directory to /work and run the container interactively.
91
+
92
+
$ docker run --rm -v $PWD:/home/geolambda -it developmentseed/geolambda:latest /bin/bash
93
+
94
+
All of the GDAL CLI tools are installed so could be run on images in the current directory.
95
+
96
+
89
97
## Development
90
98
91
99
Contributions to the geolambda project are encouraged. The goal is to provide a turnkey method for developing and deploying geospatial applications to AWS. The 'master' branch in this repository contains the current state as deployed to the Docker Hub images `developmentseed/geolambda:latest` and `devlopmentseed/geolambda-python:latest`, along with a tag of the version. The 'develop' branch is the development version and is not deployed to Docker Hub.
0 commit comments