Release Notes 1.2
What’s New
Direct creation of geometries
In the dialog for geometry editing, a tool suitable for the respective geometry of the map layer is now available, with which e.g. a polygon can be drawn directly. Thus, it is no longer always necessary to create an auxiliary geometry first for new geometries. Due to the already existing possibility to hide the helper geometries completely from the user interface, a very simple editing workflow can be created.
API for integrating the editing tools into own implementations
An external API now provides interfaces for creating and editing objects (features of a map layer) and independent geometries (which are e.g. assigned to a map layer only in a later work step). With the help of these interfaces, e.g. editing can be started from own workflows. It also allows you to prevent the user-created object from being saved directly to a map layer and instead, for example, first open a separate dialog with complex attribute editing, plausibility checks, or the like.
Changelog
1.2.1
Fixed Issues
|
Editing.js missing in module.js |
|
Error when trying to delete object after clearing geometry |
|
Exception when opening edit widget directly on app start |
|
Geometries uploaded with map.apps ETL cannot be snapped |
|
Layers are not listed in add feature dialog when placed in group layer |
|
Promise not resolved with error message when user cancels createGeometry workflow |
|
Snapping on MapService layers not possible for layers inside of group layers |
|
Snapping still active when group layer is deactivated |
|
Zoom to feature not working for point geometries |
1.2.0
New Features
|
Add tool and construction infos to construct a new object directly |
|
Allow to hide attachment tab |
|
Allow to hide attribute editing tab |
|
Ensure that editor window does not overlap editing object on zoom |
|
Provide external API to start editing and get resulting feature |