[19.0][MIG] base_geoengine: migrate to 19.0#446
Conversation
|
Nice work, thanks for taking care of the 19.0 migration 🙌 Small suggestion before merge: could you please redo it following the official OCA migration steps so the full commit history from 18.0 is preserved? Also, could you include PR #449 in this migration as well so 19.0 stays aligned with the previous stable branch? Thanks! |
…lways need to zoom out to get useful informations
…rch drop down list
Implement propotional Improve alpha channel management (everythong is ready to enable its configuration on the raster layer)
Currently translated at 100.0% (168 of 168 strings) Translation: geospatial-17.0/geospatial-17.0-base_geoengine Translate-URL: https://translation.odoo-community.org/projects/geospatial-17-0/geospatial-17-0-base_geoengine/it/
Currently translated at 100.0% (168 of 168 strings) Translation: geospatial-17.0/geospatial-17.0-base_geoengine Translate-URL: https://translation.odoo-community.org/projects/geospatial-17-0/geospatial-17-0-base_geoengine/zh_CN/
…eble) openlayers JS library (ol.js) could not be minified by Odoo minifier, because it is already minified. Thus, load it separately without minification (do not include in bundle)
Updated field label from "Params" to "Params WMS" of params_wms
attribute_field_id domain is updated to use values based on geo_field_id.model_id
Added edit button in popup of record shown in geoengine view which allows user to edit values of record from geoengine view.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: geospatial-18.0/geospatial-18.0-base_geoengine Translate-URL: https://translation.odoo-community.org/projects/geospatial-18-0/geospatial-18-0-base_geoengine/
Currently translated at 100.0% (169 of 169 strings) Translation: geospatial-18.0/geospatial-18.0-base_geoengine Translate-URL: https://translation.odoo-community.org/projects/geospatial-18-0/geospatial-18-0-base_geoengine/it/
…dient customization - Introduced `intermediate_colors` field to `geoengine.vector.layer` model, allowing users to specify comma-separated hex color values for intermediate gradient stops. - Updated the GeoengineRenderer to utilize the new field for dynamic gradient generation. - Modified relevant views and documentation to reflect the new feature.
- Version bump to 19.0.1.0.1 - JS modernization: ESM modules, OWL components - Library updates: OpenLayers 10.5.0, Chroma.js 3.1.2, Geostats 2.1.0 - ORM compatibility: monkey-patch Field._condition_to_sql for geo operators - Add domains.py for extended domain handling with geo operators - OCA compliance: license headers, readme updates, typo corrections - Replace deprecated Python 3.10+ syntax for compatibility - Update tests with add_to_registry pattern Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… renderer Add geoengine_swisstopo module providing: - proj4js support for non-standard SRIDs (EPSG:2056, EPSG:21781, etc.) - Swisstopo raster layer type for Swiss national map backgrounds - Automatic SRID detection from geo fields for correct projection handling - Patched GeoEngine renderer for multi-projection workflows - CI config update for PostGIS-enabled PostgreSQL image Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Hi @zamberjo, thanks for the review and the useful feedback! I've reworked the PR following the official OCA migration steps:
CI is green. Let me know if anything else needs adjusting! |
zamberjo
left a comment
zamberjo
left a comment
There was a problem hiding this comment.
The geoengine_swisstopo module should be in a separate pull request
| services: | ||
| postgres: | ||
| image: postgres:13 | ||
| image: postgis/postgis:14-3.5 |
There was a problem hiding this comment.
This is defined in the template and should not be modified manually.
There was a problem hiding this comment.
Thanks. base_geoengine requires PostGIS for its test database.
The module already creates the extension in its pre-init hook, but that only works if the PostgreSQL service image has PostGIS installed.
Since .github/workflows/test.yml is template-managed, what is the preferred OCA way to handle this for the repository? Should this be done through the template/repo configuration instead of a manual workflow change?
remove geoengine_swisstopo from [19.0][MIG] base_geoengine: migrate to 19.0#446 and submit it in a separate PR for the geoengine_swisstopo module.
|
20 participants
Summary
base_geoenginemodule to Odoo 19.0Changes in this PR
OCA Compliance fixes
models/__init__.py: Replace old-style verbose GPL header with standard OCA# Copyright / # License AGPL-3.0format__init__.py(root): Add missing license headerdomains.py: Add missing license headerreadme/HISTORY.md: Add 19.0.1.0.1 changelog entryreadme/INSTALL.md: Fix RST syntax (.. code-block:: bash) mixed with Markdown, fix typo "documenation"readme/DESCRIPTION.md: Fix typo "PostgGIS" → "PostGIS"readme/CONTRIBUTORS.md: Remove empty email brackets for contributor entryexpressions.py: Replace Python 3.10+match/casewith dict-based dispatch for pre-commit compatibilityCore migration (already done before this PR)
.esm.js) with OWL componentsDomainConditionmonkey-patching)fields.Field._condition_to_sqlextended for geo operatorsadd_to_registry/_setup_models__(Odoo 19 API)Pre-commit validation
All hooks pass:
pre-commit run --all-files✅Test plan
odoo-bin -d test_db -i base_geoengine --test-enable --stop-after-init