Skip to Content

Advanced Map View - Grevlin Visualisation Suite

by
Odoo

$ 5.87

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Lines of code 1780
Technical Name grev_od_map_view
LicenseOPL-1
Websitehttps://www.grevlin.com
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Lines of code 1780
Technical Name grev_od_map_view
LicenseOPL-1
Websitehttps://www.grevlin.com

Advanced Map View

A first-class Odoo map view type — fullscreen, picture-in-picture, side list panel, road-snapped asset routes, click-to-create and a form-view field widget

✓ Odoo 19.0 Compatible ✓ Community & Enterprise ✓ No CDN dependency

Advanced Map View registers a brand-new grev_map view type alongside Odoo’s standard list, kanban and form views. Any model exposing latitude and longitude fields can be visualised on a Leaflet map — with fullscreen mode, a floating picture-in-picture window, a click-to-zoom side list, road-snapped origin→current→destination asset routes, drag-rectangle area zoom, a click-to-measure distance tool, and a one-click «Add asset on the map» mode. A companion grev_map_location field widget embeds the same map directly inside form views.

Core Features

🗺

Native View Type

Declare <grev_map> in any window action just like list or kanban — Odoo’s view switcher, breadcrumbs, pager and search panel work out of the box.

⛶

Fullscreen Mode

Expand the map to the entire viewport for war-room style monitoring, then collapse back into the standard Odoo layout in a single click.

🖼

Picture-in-Picture

Detach the map into a floating, draggable window so it stays visible while you work on forms, lists or reports in the main view.

🔍

Area Zoom

Drag a rectangle on the map to zoom precisely to a region — perfect for inspecting dense clusters of records without endless scroll-zooming.

🛣

Road-Snapped Routes

Set routing="1" with a timestamp field to draw an ordered path through records, snapped to real roads via OSRM — with a polyline fallback when the routing service is unavailable.

📏

Distance Tool

Click successive points on the map to measure distances using the haversine formula — with running totals shown live.

🎨

Color by Field

Use color_field to colour markers by a selection or many2one field — categorise records visually at a glance.

🗾

Multiple Tile Layers

Choose from CARTO Voyager, Positron, Dark Matter, OpenStreetMap or Humanitarian OSM — configurable per view via the tile_layer attribute.

🔗

Side List Panel

A built-in left panel lists every record on the map — click an item to fly to its location and open its popup. Toggle on/off from the toolbar.

🚛

Asset Routes

Declare origin and destination fields to render the done leg as a solid road-snapped line and the remaining leg as a dashed line through the asset’s current position.

📝

Map Field Widget

Embed a Leaflet map directly inside any form view with the grev_map_location widget — click-to-set editing, configurable height and tile layer, and the same asset route overlay.

📍

Click-to-Create

Hit the + New button, then click anywhere on the map — a form view opens with the latitude and longitude already prefilled. Honors the standard create attribute.

Built For Any Geo Model

🏢 Customers & Partners

Plot your res.partner records on a map by exposing their latitude and longitude — cluster prospects, route sales reps, visualise territories.

🚚 Fleet & Deliveries

Visualise vehicles, stops or shipments. Combine with the routing option to draw the actual delivery sequence on the map.

📡 IoT & Sensor Data

Display GPS pings, environmental sensors or asset positions in real time, with custom popup fields for telemetry data.

📍 Projects & Sites

Map project tasks, field service interventions, construction sites or rental locations — any business object with coordinates.

Add It To Any Model In Seconds

1. Basic map view 

<record id="view_partner_grev_map" model="ir.ui.view">
    <field name="name">res.partner.grev.map</field>
    <field name="model">res.partner</field>
    <field name="arch" type="xml">
        <grev_map lat_field="partner_latitude"
                  lng_field="partner_longitude"
                  color_field="category_id"
                  default_zoom="6"
                  panel_title="Partners">
            <field name="display_name"/>
            <field name="city"/>
            <field name="country_id"/>
        </grev_map>
    </field>
</record>

Then add grev_map to your action’s view_mode — a new map button appears in the view switcher next to list and kanban.

2. Asset routes — origin & destination 

<grev_map lat_field="current_lat"
          lng_field="current_lng"
          origin_lat_field="origin_lat"
          origin_lng_field="origin_lng"
          destination_lat_field="dest_lat"
          destination_lng_field="dest_lng"
          tile_layer="carto_voyager"
          panel_title="Fleet">
    <field name="display_name"/>
    <field name="state"/>
</grev_map>

Selecting a record in the side list draws its journey on the map — a solid road-snapped line from origin to current position (the done leg), and a dashed line from current position to destination (the remaining leg). The four origin_*_field / destination_*_field attributes are all optional and only kick in when the four are set together. OSRM is used for road-snapping, with an automatic straight-polyline fallback per leg if the routing service is unreachable.

3. Embed the map inside a form — grev_map_location widget 

<field name="current_lat" widget="grev_map_location"
       options="{
           'lng_field':              'current_lng',
           'zoom':                   14,
           'tile_layer':             'carto_voyager',
           'height':                 360,
           'origin_lat_field':       'origin_lat',
           'origin_lng_field':       'origin_lng',
           'destination_lat_field':  'dest_lat',
           'destination_lng_field':  'dest_lng',
       }"/>

The grev_map_location widget is bound to the latitude field; the longitude companion is passed via the lng_field option. When the field is editable, clicking the map updates both coordinates on the record. The four optional origin_* / destination_* options paint the same done/remaining route overlay as the map view, so a single field turns any form into a tracking dashboard.

Screenshots

Loading the grev_map view from the view switcher

The grev_map view loads alongside list and kanban — one click in the view switcher and your records are on the map.

grev_map_location widget rendered inside a form view

The grev_map_location field widget embeds a Leaflet map directly inside the form view — coordinates, marker and the optional origin/destination route overlay, all in place.

Compatibility

✓ Odoo 19.0 Community
✓ Odoo 19.0 Enterprise

✓ Depends only on base, web
✓ No Enterprise-only modules required

Changelog

Version 19.0.1.5.0

  • Asset routes are now road-snapped via leaflet-routing-machine and OSRM
  • Each leg (done / remaining) is rendered as its own routed segment with the original solid / dashed styling
  • Automatic polyline fallback when the routing service is unavailable, per-leg

Version 19.0.1.4.0

  • New + New toolbar button: click on the map to drop a pin and open a form prefilled with latitude and longitude
  • Standard create arch attribute is honored to gate the action

Version 19.0.1.3.0

  • New grev_map_location field widget for embedding a Leaflet map inside form views
  • Optional click-to-set editing, configurable height and tile layer
  • Carries the same origin / current / destination route overlay

Version 19.0.1.2.0

  • Selecting a record from the side list now draws the asset’s done (solid) and remaining (dashed) route through the current position
  • New origin_lat_field, origin_lng_field, destination_lat_field, destination_lng_field arch attributes
  • Active item is highlighted in the side list

Version 19.0.1.1.0

  • New side list panel for multi-record views: click an item to fly the map to its marker and open its popup
  • Map now stretches to the full canvas height instead of a fixed minimum
  • Modernized OWL component layout to align with Odoo 19 conventions

Version 19.0.1.0.0 — Initial Release

  • New grev_map view type registered with Odoo’s view registry
  • Fullscreen mode and detachable picture-in-picture window
  • Drag-rectangle area zoom and click-to-measure distance tool
  • Ordered route polylines through timestamped records
  • Color-by-field markers and rich popup field declarations
  • Five built-in tile layers (CARTO Voyager, Positron, Dark Matter, OSM, OSM HOT)

Need Help?

For support, contact us at odoo@grevlin.com

Follow us on X: @GrevlinGlobal

✨ 30 days free support included

Advanced Map View - Documentation

A first-class Odoo view type that renders any model with latitude and longitude fields on an interactive Leaflet map &mdash; with fullscreen, picture-in-picture, area zoom, ordered route polylines and a click-to-measure distance tool.

Overview

Advanced Map View registers a new grev_map view type alongside Odoo's standard list, kanban and form views. It plugs into the view-switcher, breadcrumbs, search panel and pager exactly like a native view, so any model that exposes geographic coordinates can gain a fully featured map UI without a single line of JavaScript.

The module ships only the view type itself &mdash; it has no opinions about which records you map. Point it at customers, fleet vehicles, deliveries, sensors, project sites, rental assets or any custom model.

Key Features

  1. Native ``grev_map`` view type &mdash; declared like list or kanban in any ir.actions.act_window view mode
  2. Fullscreen mode &mdash; expand the map to the entire viewport for monitoring
  3. Picture-in-picture &mdash; detach the map into a floating window that stays visible while you work elsewhere in Odoo
  4. Side list panel &mdash; built-in left panel listing every record on the map; click an item to fly to its marker and open its popup
  5. Click-to-create &mdash; hit :guilabel:`+ New` and click on the map to open a form prefilled with the latitude and longitude of that point
  6. Area zoom &mdash; drag a rectangle to zoom precisely to a region
  7. Distance tool &mdash; click successive points to measure distances using the haversine formula, with running totals
  8. Route polylines &mdash; draw an ordered path through records using a timestamp field
  9. Asset routes (origin &rarr; current &rarr; destination) &mdash; declare origin and destination fields to render the done leg as a solid road-snapped line and the remaining leg as a dashed line through the asset's current position; powered by leaflet-routing-machine and OSRM, with a per-leg straight-polyline fallback
  10. Color by field &mdash; colour markers by a selection or many2one field
  11. Rich popups &mdash; declare <field> children to render contextual information for each record both in the side panel and the marker popup
  12. Form-view field widget &mdash; the companion grev_map_location widget embeds a Leaflet map directly inside any form view, with optional click-to-set editing and the same asset-route overlay
  13. Five built-in tile layers &mdash; CARTO Voyager, Positron, Dark Matter, OpenStreetMap and OpenStreetMap HOT

Note

This module is compatible with both Odoo Community and Odoo Enterprise editions. It depends only on base and web &mdash; there is no Enterprise-only requirement and no CDN dependency for the Leaflet library.

Installation

  1. Copy the grev_od_map_view module into your Odoo addons path
  2. Update the apps list from :menuselection:`Apps --> Update Apps List`
  3. Search for Advanced Map View and click :guilabel:`Install`

Usage

Declaring a Map View

Create an ir.ui.view record whose architecture root is <grev_map> and reference it from any window action. The two attributes lat_field and lng_field are required.

<record id="view_partner_grev_map" model="ir.ui.view">
    <field name="name">res.partner.grev.map</field>
    <field name="model">res.partner</field>
    <field name="arch" type="xml">
        <grev_map lat_field="partner_latitude"
                  lng_field="partner_longitude"
                  color_field="category_id"
                  default_zoom="6"
                  panel_title="Partners">
            <field name="display_name"/>
            <field name="city"/>
            <field name="country_id"/>
        </grev_map>
    </field>
</record>

Then add grev_map to the action's view_mode:

<record id="action_partner_map" model="ir.actions.act_window">
    <field name="name">Partners on Map</field>
    <field name="res_model">res.partner</field>
    <field name="view_mode">grev_map,list,form</field>
</record>

Supported Attributes

The <grev_map> root tag accepts the following attributes:

Attribute Required Description
lat_field Yes Float field holding the latitude of each record
lng_field Yes Float field holding the longitude of each record
timestamp_field No Date/datetime field used to order records when routing="1"
color_field No Selection or many2one field driving the marker colour
routing No Set to "1" to draw a polyline through ordered records
default_zoom No Initial Leaflet zoom level (default 13)
tile_layer No One of carto_voyager (default), carto_positron, carto_dark, osm, osm_hot
panel_title No Title shown at the top of the side panel
limit No Page size for the side panel (default 200)
hide_list No Set to "1" to hide the side list panel even on multi-record views
origin_lat_field No Float field with the asset's origin latitude (asset-route overlay)
origin_lng_field No Float field with the asset's origin longitude (asset-route overlay)
destination_lat_field No Float field with the asset's destination latitude (asset-route overlay)
destination_lng_field No Float field with the asset's destination longitude (asset-route overlay)

<field> children declared inside <grev_map> are loaded with the records and shown both in the side panel and in the marker popup.

Note

The four origin_*_field / destination_*_field attributes work as a set: the asset-route overlay only renders when the four are configured together and all four fields hold numeric values on the active record.

Asset Routes (Origin &rarr; Current &rarr; Destination)

When origin and destination fields are declared, selecting a record in the side list paints its journey on the map:

  • A solid road-snapped line from origin to current position &mdash; the done leg.
  • A dashed road-snapped line from current position to destination &mdash; the remaining leg.

Routing uses the public OSRM service via leaflet-routing-machine. If the service is unreachable for a leg, that leg falls back to a straight polyline in the same colour and dash pattern.

Form-View Field Widget &mdash; grev_map_location

The module also registers a field widget called grev_map_location that embeds a Leaflet map directly inside a form view. The widget is bound to the latitude field; the longitude companion is provided through options.

<field name="current_lat" widget="grev_map_location"
       options="{
           'lng_field':              'current_lng',
           'zoom':                   14,
           'tile_layer':             'carto_voyager',
           'height':                 360,
           'origin_lat_field':       'origin_lat',
           'origin_lng_field':       'origin_lng',
           'destination_lat_field':  'dest_lat',
           'destination_lng_field':  'dest_lng',
       }"/>

Supported widget options:

Option Required Description
lng_field Yes Companion float field holding the longitude
zoom No Initial zoom level (default 13)
tile_layer No One of carto_voyager (default), carto_positron, carto_dark, osm
height No Map height in pixels (default 320)
origin_lat_field / origin_lng_field No Origin coordinates &mdash; required as a pair to enable the route overlay
destination_lat_field / destination_lng_field No Destination coordinates &mdash; required as a pair to enable the route overlay

Tip

When the latitude field is editable on the form, clicking anywhere on the map updates both the latitude and the longitude on the record. In read-only contexts the click handler is disabled and the map becomes a pure visualisation.

Click-to-Create

The toolbar includes a :guilabel:`+ New` button that activates a single-shot drop a pin mode. The next click on the map opens the model's standard form view with the latitude and longitude fields prefilled at the clicked point. The button respects the standard create arch attribute, so you can disable it on read-only dashboards via <grev_map create="0" ...>.

Map Toolbar

Once a grev_map view is open, the floating toolbar offers:

Tip

The picture-in-picture window survives navigation, so you can keep an eye on live records while editing forms in another tab of the same Odoo session.

Compatibility

  • Odoo: 19.0 (Community and Enterprise)
  • Dependencies: base, web
  • Vendored library: Leaflet (no external CDN required at runtime &mdash; tile layers are fetched from CARTO and OpenStreetMap public endpoints)

Support

For questions, bug reports or feature requests, contact odoo@grevlin.com or follow @GrevlinGlobal on X.

Thirty days of free support are included with every purchase.

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.