test-base-geoengine
auto_awesome What this module does
AI-generated from the code · Odoo 13.0This is a technical test module for the geospatial engine; it adds no business features for end users. It only creates sample records with map fields to verify that geographic data types and map views work correctly.
This module is a test module, not a business feature. It exists to check that the geospatial engine works, so it does not add anything useful to day-to-day work.
What it creates:
- Sample data models with geographic fields: a point, a multi-polygon and a line, plus a related multi-polygon copied from another record.
- A map view for the test.dummy model and another map view for test.dummy.related, showing records on a map.
- A form view for test.dummy with a "Geometry" tab where the multi-polygon can be drawn and edited on a map.
Access rights are granted to all internal users for the three sample models, so they can read, create, edit and delete these test records.
No menus, no reports, no emails, no scheduled jobs and no business rules are added. The module depends on base_geoengine and only works as a demonstration and verification of geographic field types and map widgets. It should normally be installed only on test or development databases.
Depends on
Models and fields (4)
- test.dummy · new modelname, geo_point, geo_multipolygon
- test.dummy.related · new modeldummy_test_id (Dummy test), dummy_geo_multipolygon (Related Geom)
- test.abstract.dummy · new modelgeo_line (Line)
- test.dummy.from_abstract · new modelname
Text generated by AI (DeepSeek) from reading the Odoo 13.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/geospatial.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.