Page Comparison

The spatial editing extension for Weave provides a means to edit geometry and attributes for an entity.

Features:

...

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
  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.
• Snapping of geometry
  Configurable snapping is available to help with drawing geometry.
• 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.
• Restrictions on the number and types of geometry
  Geometry input can be constrained to indicate a minimum and maximum number of geometries that can be entered when creating an entity and the types of geometries can be specified.
• Customization of client view
  The display of the input panel can be customized via the configuration. Some things that can be customized are if text and/or icons are display in buttons, which buttons are displayed (hiding the polygon button for example) and the locations of some of the buttons.

...

A few things to not about the properties that can be applied to parameters:

• column is optional, if not provided then the field will still appear, but an attempt to write the entered value into the underlying spatial table will not be made. The user entered value can still be used by other means that will be covered later.
• The controltype now supports 'textarea' which isn't available for search fields, it provides a multi-line text input field.
• readonly, readonlyoninsert and readonlyonupdate aren't available for search field either, they're special marker markers that allow you to alter the ability of the user to change the value in a field. These are client-side flags, and if set alter alters the display of the field so that the user cannot change the value, the field is still displayed, just not editable.
• updatable specifies that one a value is set it can't be changed, this is similar to readonlyonupdate, and in fact readonlyonupdate will be set to true if updatable is set to false, but it also provides additional checks on the server to ensure that the value is not updated.
• value can be used to set a value explicitly by directly supplying the value, or there are a number of formulas that are available.
  • entity() The name of the entity type being edited.
  • userid() The current username.
  • ip() The current users IP address.
  • datetime() The current date/time.
  • operation() The type of operation being perform, performed will be one of the strings 'create', 'update' or 'delete'.
  • nextval() The value used for the column will be the previous largest value from the column plus one, the underlying column must be numeric.
  • geometry() A WKT (Well Known Text) representation of the geometry if available, otherwise null.
  • id() The value for the key field for the spatial table will be used if available, otherwise null.
  • auto() The value for the field is auto-generated by the database.
  • count() The number of geometry objects.
  • area() The area of the geometry.
  • length() The length of the geometry.

...