rckrdmrd/workspace-v1
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
workspace-v1/shared/knowledge-base/reference/odoo/odoo-18.0/addons/base_geolocalize
History
rckrdmrd 66161b1566 feat: Workspace-v1 complete migration with NEXUS v3.4 
Sistema NEXUS v3.4 migrado con:

Estructura principal:
- core/orchestration: Sistema SIMCO + CAPVED (27 directivas, 28 perfiles)
- core/catalog: Catalogo de funcionalidades reutilizables
- shared/knowledge-base: Base de conocimiento compartida
- devtools/scripts: Herramientas de desarrollo
- control-plane/registries: Control de servicios y CI/CD
- orchestration/: Configuracion de orquestacion de agentes

Proyectos incluidos (11):
- gamilit (submodule -> GitHub)
- trading-platform (OrbiquanTIA)
- erp-suite con 5 verticales:
  - erp-core, construccion, vidrio-templado
  - mecanicas-diesel, retail, clinicas
- betting-analytics
- inmobiliaria-analytics
- platform_marketing_content
- pos-micro, erp-basico

Configuracion:
- .gitignore completo para Node.js/Python/Docker
- gamilit como submodule (git@github.com:rckrdmrd/gamilit-workspace.git)
- Sistema de puertos estandarizado (3005-3199)

Generated with NEXUS v3.4 Migration System
EPIC-010: Configuracion Git y Repositorios
2026-01-04 03:37:42 -06:00
..
i18n feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00
models feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00
security feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00
tests feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00
views feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00
__init__.py feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00
__manifest__.py feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00
README.md feat: Workspace-v1 complete migration with NEXUS v3.4 2026-01-04 03:37:42 -06:00

README.md

Partner geolocalize

Contacts geolocation API to convert partner addresses into GPS coordinates.

Configure

You can configure in General Settings the default provider of the geolocation API service.

A method _call_<service> should be implemented in object base.geocoder that accepts an address string as parameter and return (latitude, longitude) tuple for this to work. If no default provider is set, the first one will be used by default.

An optional method _geo_query_address_<service> which takes address fields as parameters can be defined to encode the query string for the provider.