...
The spatial editing extension for Weave provides a means to edit geometry and attributes for an entity.
Features:
- Simple to setup for basic operation
Configure the id, label and entity and Weave will do the rest. - Customisable for advanced operation
- Supports transparent editing on an entity with multiple spatial layers
- Can be initiated from URL parameters
Limitations:
- for advanced operation
Refine geometry setting and input parameters, and provide pre-defined lists of values for input. - Supports editing on an entity with multiple spatial layers
A single entity that is composed of separate point, line and/or polygon tables is transparently handled by Weave. - Creation and updating on an entity in the client can be initiated from URL parameters
The Weave client can be started with parameters in the URL to immediately begin the editing process for a specific entity for the user. - Auditing of editing operations
Custom auditing can be setup to write a new log records to a database table for each edit operation performed by a user. - I18n support
All of the text/labels for the editing components can be customized for multiple languages or even just having the default text changed. - "Identity" columns
It's possible to specify that an attribute for a new record is based on incrementing the previous highest value of the column, or that the column will be automatically generated by the underlying database system. - Read-only columns
It's possible to specify that an attribute can be displayed but not changed (readonly), can only be changed when the entity is created (readonlyonupdate) or can only be changed when an entity is updated (readonlyoncreate). - Hidden columns
It's possible to specify attributes that aren't visible to the user but are still written when an edit is performed, using either a fixed value or one of a number of supported functions. - Formula columns
It's possible to specify a number of in-built formulas as the value for a column, including things like userid(), datetime(), entity(), area() and length(). These can be used for both the spatial and audit tables.
Limitations:
- Currently only attributes directly attached to the spatial table can be edited
Weave will only write to the spatial table when editing an entity, currently having some attributes written to the spatial table and other attributes written to separate database tables is not supported. Audit tables may provide enough functionality to support the required workflow though. - Spatial mapper for entity must have <dynamic> set to true and <cache> set to false
But this is generally the case for any entity that can have it's underlying data altered on the flyCurrently only attributes directly attached to the spatial table can be edited.
Installation
Currently the Weave editing sub-system is provided as a single bundle, com.cohga.spatial.edit, but this may change before release.
This bundle must be copied to the weave\platform\plugins directory and the server restarted for it to be available.
...