Changelog¶
Info
On 2024/12/18 we updated our service API and changed the domains where DVM gets its resources. Please make sure your services have allowlisted these domains. You can check these domains on the DVM requirements section.
2025-04-14¶
New versions for both map_viewer
and 3d_viewer
modules,
and the module manager, has been published.
Both modules have improved their compatibility with accessibility, mainly screen readers and keyboard navigation. To learn more about accessibility, please check the accessibility section. Between the new additions are:
- The viewers and its elements are focusable with the
tab
key, and clickable withspace
andenter
keys. - Better and more labeling of WAI-ARIA attributes.
- when
getThumbnail()
returns an image (not an url), the images includes dealt
andlang
attributes.
Here are the API changes:
Map Viewer
- Additions:
- New general method
setCurrentMapDescription
. - new interface method
setPoweredByLabel
. - New keyboard triggers, when the viewer is focused:
keydown
keyup
- New general method
3D Viewer
- Additions:
- New general method
setCurrentViewDescription
. - new interface method
setPoweredByLabel
. - new interface method
setNoViewLabel
. related_previews
plugin: New flagsautomatic_load
andautomatic_track
navigation
plugin: New flagautomatic_click_load
.- New keyboard triggers, when the viewer is focused:
keydown
keyup
- New general method
- Changes:
related_previews
plugin:generateRelatedPreview
method doesn't throw an error if the preview was already being tracked. Instead, it just prints a warning.
Breaking changes
related
,
related_previews
and
navigation
plugins now will always be loaded, and automatic basic
interaction will be added by default. That means that clicking a preview or a navigation node will trigger
a loadView3d
to its destination.
To prevent breaking integrations, If your integration was already including navigation
or related_previews
plugins (or the deprecated indoor
), this automatic
behavior will be disabled by default.
You can also enable/disable this automatic behavior with their corresponding automatic_load
/automatic_click_load
flags.
We still recommend to add these plugins manually and manage yourself any kind of interaction or loads.
Remember that although you can't use the loadView3d
promise because it's not called by your integration,
you can always use the load_success
and load_error
triggers to know when the load was successful or not.
2025-02-17¶
- Extended requirements section, with detailed CSP requirements and firewalls.
2024-10-31¶
map_viewer
:
- Now, instancing with a container it's optional (before it was mandatory).
getContainer()
related
plugingetNeighbors
quantity
parameter is now optional.- New initialization property
aliases
. - Nodes have a new property
aliases
.
3d_viewer
:- Now, instancing with a container it's optional (before it was mandatory).
- experimental space scene public API. This API may change in the future.
- new methods:
- new properties
:
2024-07-22¶
map_viewer
:- Nodes have a new property
description
.
- Nodes have a new property
3d-viewer
- Added
related_previews
plugin
- Added
2024-03-04¶
map_viewer
:- new triggers:
pre_load_start
load_start
- deprecated trigger:
start_load
(replaced with load_start for consistency)
- New methods:
- new triggers:
3d-viewer
fov
property.
map_viewer
getThumbnail()
and3d_viewer
getThumbnail()
share the same API.
2024-01-31¶
- added
camera_mode
property tolimits
.
2023-11-30¶
- Added map-viewer layers advanced API.
2023-11-27¶
- Added map_viewer
preserve_min_scaling_factor
flag.
2023-11-20¶
- Added 3d_viewer additional flags:
2023-11-16¶
- map-viewer goTo inputs updated.
2023-11-08¶
- Added some clarifications about when to use some flags:
2023-10-26¶
- General:
- Map Viewer module:
- 3d Viewer module: