v0.7.0

Mathislewald Upload

Use this streamlit application as an upload interface for the Mathislewald app.
The application should be run in a docker container, mounting the target directories
from the container to the host.

The container saves to the following locations:

• /src/data for inventory data
• /src/data/base for base layer GeoTIFFs
• /src/img for inventory images
• src/www for checksums

The data folder should be mounted inside a GeoServer geodata folder to serve the data via WMS and WFS.
The images can be mounted into an assets folder of a web-application, or a public path of a web proxy server.
The checksums should be mounted inside a public path of a web proxy server

Full Changelog: v0.6.0...v0.7.0

Version 0.6

This update fixes some errors and adds a preview plot to the inventory upload.
Additionally, the inventory images are now uploaded as a semicolon-separated list to add more than one image to a tree.

Finally, the checksums are fixed and should work for all uploads now

Full Changelog: v0.5.0...v0.6.0

Version 0.5

Description

With this version, more fine-grained target folder structures are possible. You can overwrite three different folder locations now:

1. The DATADIR for the base directory of Geoserver, here the base-layer will be uploaded to DATADIR/base and the inventory to the root of that folder
2. The WWWDIR indicates the location of the frontend application. At WWWDIR/assets/, a JSON of checksums will be created and in the WWWDIR/assets/img all inventory images are uplaoded.
3. The images location can optionally be overwritten using IMGDIR environment variable

Using a image folder outside of the React application is helpful, ie. to use a proxy to serve from a different location (ie. to restrict access to the application only).
Secondly, the upload app now creates a checksum.json in the assets folder of the React application. These checksums will be synchronized to the React app, to determine if data needs to be updated in the local storage. This way, we can significantly decrease the requests on the server, while the application is operated in online mode.

What's Changed

• Add checksums by @mmaelicke in #5

Full Changelog: v0.4.0...v0.5.0

Version 0.4

Basically a bugfix for the extraction of the image files, which are stored in a flat folder structure now.
Mentioning @JesJehle for reference.

Version 0.3

Two general improvements:

• The base layers are now stored in a sub-folder inside the data directory: /src/data/base to let Geoserver create a name-space for base data only
• The inventory data is now stored into geopackages. The user has the ability to save multiple layers into the geopackage

@JesJehle @JulFrey mentioning you for reference

Version 0.2

Description

Changed default path locations to the absolute paths inside the docker container. This should simplify the docker run command to:

docker run -d --restart always -p 8501:8501  -v /host/path/to/geoserver:/src/data -v host/path/to/nginx/img:/src/img ghcr.io/hydrocode-de/mathislewald-upload

What's Changed

• update paths by @mmaelicke in #4

New Contributors

• @mmaelicke made their first contribution in #4

Full Changelog: v0.1.0...v0.2.0

Initial Release

This is the first release of the data uploader for the Mathislewald Application. @JesJehle mentioning for reference. We can run this on the virtual machine.

Sample command for running:

docker run -d --restart always -p 8501:8501 -e DATADIR=/src/data -e IMGDIR=/src/img -v /host/path/to/geoserver:/src/data -v host/path/to/nginx/img:/src/img ghcr.io/hydrocode-de/mathislewald-upload