...
The most basic edit configuration interrogates the underlying spatial tables for the information it requires. (e.g. to determine what attributes are associated with the entity or what spatial geometries (point, line or polygon) the user is allowed to create.)
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="UTF-8"?>
<config xmlns="urn:com.cohga.server.config#1.0" xmlns:edit="urn:com.cohga.spatial.edit#1.0">
<edit:config id="simple.edit">
<entity>graffiti</entity>
<label>Graffiti</label>
<description>Report graffiti for removal</description>
</edit:config>
</config>
|
This provides a simple way to setup editing for an entity , allowing and allow the user to directly edit the attributes that are attached to the entity in the underlying spatial table.
| Tip |
|---|
The edit configuration has a |
...
The basic edit configuration offers no options to customise what attributes are enables all attributes available for editing, they all are, or . Also, the basic configuration does not provide an option to customise how the user will be able to edit those values, which will be determined by the underlying column type in the spatial table and be limited to simple field types (text fields for string and numbers, calendar field for dates, etc).
...
What types of geometry the user will be able to create /or edit will also be determined by the underlying spatial table, if the spatial table contains polygons then the user will only be able to create polygons , and they will not be able to create points or lines. If however the entity is linked to two spatial tables, one containing polygons and the other containing points then the user will be able to edit both points and polygons.
Further there There is differentiation between spatial layers that contain single instance geometry and those that contain multi-instance geometry. That is, that is if the spatial table contains multipolygons, as opposed to just polygons, then the user will be allowed to create more than one polygon shape when editing the entity, when . When the spatial table contains polygons the user will be limited to a single polygon object. The same applies to points /or multipoints and line/lines or multilines.
Finally the The requirement for the user to actually create geometry is also determined by the underlying spatial table, if . If the spatial table allows nil geometry then the user will not be forced to create a geometry when creating a new entity , however if the spatial table doesn't allow nil geometries then the user will be required to create a geometry before they 'll will be able to complete the edit.
...
The things that you can override are the parameters that the user can edit, the maximum number of geometry items the user can create, and the required number of geometry items the user must create.
...