geovisio 2.10.0__tar.gz → 2.11.0__tar.gz

{geovisio-2.10.0 → geovisio-2.11.0}/.gitignore

@@ -7,7 +7,6 @@ env
 instance
 __pycache__
 config.py
-docker/models/
 .vscode/
 site/
 *.mo

{geovisio-2.10.0 → geovisio-2.11.0}/.gitlab-ci.yml

@@ -99,6 +99,13 @@ test:
       - make i18n-po2code
       - pytest -vv -m "not skipci"
 
+dependencies-lock:
+  stage: test
+  image: ghcr.io/astral-sh/uv:0.9.2-python3.11-bookworm-slim
+  script:
+    # enforce that the lock file is up to date.
+    # Updating this lock file is important to ensure the production servers will use the right versions
+    - uv lock --check
 
 publish-develop:
   rules:

geovisio-2.11.0/.pre-commit-config.yaml

@@ -0,0 +1,12 @@
+repos:
+-   repo: https://github.com/psf/black
+    rev: 24.1.0
+    hooks:
+    -   id: black
+
+-   repo: https://github.com/astral-sh/uv-pre-commit
+    # ensure the uv.lock file is up to date, it's important to update it when a dependency is updated
+    # by running `uv lock`
+    rev: 0.9.2
+    hooks:
+      - id: uv-lock

geovisio-2.11.0/.python-version

@@ -0,0 +1 @@
+3.13

{geovisio-2.10.0 → geovisio-2.11.0}/CHANGELOG.md

@@ -9,6 +9,30 @@ Before _1.6.0_, [Viewer](https://gitlab.com/panoramax/clients/web-viewer) was em
 
 ## [Unreleased]
 
+## [2.11.0] - 2025-12-12
+
+### Added
+
+- A way to delete an annotation (via `DELETE /api/annotations/<uuid:annotationId>` or `DELETE /api/collections/<uuid:collectionId>/items/<uuid:itemId>/annotations/<uuid:annotationId>`). Anyone authenticated can delete an annotation (and the changes are tracked in the history).
+- Added a new way to restrict who can view a sequence/picture, instead of the old `hidden` mechanism, we can now set a `visibility` field at the sequence/picture/upload_set level. This parameter can have (for the moment) the values:
+  - `anyone`: the sequence is visible to anyone
+  - `owner-only`: the sequence is visible to the owner and administrator only
+  - `logged-only`: the sequence is visible to logged users only
+  A default `visibility` can also be set at the `account` or instance level.
+- Change the permissions, now an instance administrator (and account that has the `admin` role), can see, edit and delete all sequences and pictures.
+- Display the collection semantics in the `/api/collections/<uuid:collectionId>/items` endpoint, to make it easier to be crawled by the metacatalog.
+- Add a new search capability with the query `/api/search?filter=semantics IS NOT NULL` to search for all items with some semantics (be it linked to the picture, its sequence or an annotation in the picture).
+- Add a way to know that the terms of service have been updated, and the users have read the latest changes.
+- Add an admin cli command to delete all the pictures of a user (`user <ACCOUNT_ID_OR_NAME> --delete-data`).
+
+### Changed
+
+- ⚠️ API breaking change ⚠️: we do not support anymore the `status` filter (and especially the `status='deleted'` filter) when querying the sequences, since it could leak information about some sequences with restricted visibility (since we treated those sequences as `deleted` to tell potential crawlers not to consider them anymore). This parameter is now replaced by a new `show_deleted` boolean parameter that makes the API return collections with only an `id` and a `deleted` status, without additional fields. Note that thus, when using this parameter, the response does no longer follow the STAC format for deleted collections.
+
+### Fixed
+
+- Use fully qualified path for the pictures_grid materialized view to avoid the `relation "pictures" does not exist` issue on some server.
+
 ## [2.10.0] - 2025-08-27
 
 ### Added
@@ -23,6 +47,7 @@ Before _1.6.0_, [Viewer](https://gitlab.com/panoramax/clients/web-viewer) was em
   * The route to create an annotation `/api/picture/<uuid:pictureId>/annotations` is now an alias of `/api/collections/<uuid:collectionId>/items/<uuid:itemId>/annotations`
 - Add a way to attach semantic tags to upload sets. Those tags will be transferred to all the collections associated to the upload set. This makes it possible to add semantic tags directly at the upload, without waiting for all the associated collections to be created.
 - Add a `relative_heading` parameter to the `/api/upload_sets/:id` route (for `POST` and `PATCH`), to update the relative heading of the upload set. If a `relative_heading` is set on the upload set, it will be applied when computeing the heading of all the associated collections.
+- Add a `/api/queryables` route to list the queryables for search and `/api/collections/queryables` to list the queryables for collection search.
 
 ### Changed
 
@@ -678,7 +703,8 @@ FLASK_APP="src" flask process-sequences
 - Viewer based on Photo Sphere Viewer automatically calling API to search and retrieve pictures
 - Dockerfile for easy server setup
 
-[Unreleased]: https://gitlab.com/panoramax/server/api/-/compare/2.10.0...develop
+[Unreleased]: https://gitlab.com/panoramax/server/api/-/compare/2.11.0...develop
+[2.11.0]: https://gitlab.com/panoramax/server/api/-/compare/2.10.0...2.11.0
 [2.10.0]: https://gitlab.com/panoramax/server/api/-/compare/2.9.0...2.10.0
 [2.9.0]: https://gitlab.com/panoramax/server/api/-/compare/2.8.1...2.9.0
 [2.8.1]: https://gitlab.com/panoramax/server/api/-/compare/2.8.0...2.8.1

{geovisio-2.10.0 → geovisio-2.11.0}/Dockerfile

@@ -14,7 +14,7 @@ LABEL org.opencontainers.image.url="https://panoramax.fr/"
 # and create a `geovisio` user, to run the app as non root user
 RUN apt update \
     && apt install -y git gettext make \
-    && pip install waitress gunicorn Babel \
+    && pip install waitress Babel \
     && rm -rf /var/lib/apt/lists/* \
     && mkdir -p /opt/geovisio /data/geovisio \
     && groupadd --gid 1000 geovisio \

{geovisio-2.10.0 → geovisio-2.11.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: geovisio
-Version: 2.10.0
+Version: 2.11.0
 Summary: GeoVisio API - Main
 Author-email: Adrien PAVIE <panieravide@riseup.net>, Antoine Desbordes <antoine.desbordes@gmail.com>
 Requires-Python: >=3.10
@@ -28,12 +28,13 @@ Requires-Dist: pygeofilter[backend-native] ~= 0.3.1
 Requires-Dist: python-dateutil ~= 2.9.0
 Requires-Dist: tzdata ~= 2025.2
 Requires-Dist: croniter ~= 6.0.0
-Requires-Dist: pydantic ~= 2.11
+Requires-Dist: pydantic ~= 2.12
 Requires-Dist: pydantic-extra-types ~= 2.7
 Requires-Dist: flask-babel ~= 4.0.0
 Requires-Dist: geojson-pydantic ~= 2.0.0
 Requires-Dist: email-validator ~= 2.2.0
 Requires-Dist: multipart>=1.2.1
+Requires-Dist: gunicorn ~= 23.0.0
 Requires-Dist: flit ~= 3.9.0 ; extra == "build"
 Requires-Dist: coverage ~= 7.9 ; extra == "dev"
 Requires-Dist: protobuf ~= 5.26 ; extra == "dev"

geovisio-2.11.0/bin/run_production_api.sh

@@ -0,0 +1,5 @@
+#!/usr/bin/env bash
+
+# script called by the Scalingo Procfile
+
+DB_CHECK_SCHEMA=false gunicorn --workers "${NB_API_WORKERS:-5}" --threads "${NB_API_THREADS:-4}" -b ":$PORT" 'geovisio:create_app()'

{geovisio-2.10.0 → geovisio-2.11.0}/docker/docker-entrypoint.sh

@@ -23,7 +23,7 @@ case $command in
     python3 -m waitress --port 5000 --threads=${NB_API_THREADS:-4} --call 'geovisio:create_app'
     ;;
 "gunicorn-api")
-    gunicorn --workers ${NB_API_WORKERS:-5} --threads ${NB_API_THREADS:-4} -b :5000 'geovisio:create_app()'
+    python3 -m gunicorn --workers ${NB_API_WORKERS:-5} --threads ${NB_API_THREADS:-4} -b :5000 'geovisio:create_app()'
     ;;
 "ssl-api")
     python3 -m waitress --port 5000 --threads=${NB_API_THREADS:-4} --url-scheme=https --trusted-proxy '*' --trusted-proxy-headers 'X-Forwarded-For X-Forwarded-Host X-Forwarded-Port X-Forwarded-Proto' --log-untrusted-proxy-headers --clear-untrusted-proxy-headers  --call 'geovisio:create_app'