Add editing tools

[GoogleCodeExporter]

Overview:

The result of this enhancement will be to allow editing of approved datalayers 
with splitting and snapping tools.  Since splitting and snapping tool 
functionality is already available in the OpenLayers toolkit on which OLIVER is 
built this enhancement is relatively straightforward.  Layers which will be 
edited will be secured on the GeoServer backend by a username and password, an 
existing capability.  The editing tools need to be added to the OLIVER user 
interface.  If the edit does not successfully enter the database the user must 
be notified. 

Detailed Description:

For a particular OLIVER-based viewer, a specific configured layer (or layers) 
will need to be “editing-enabled”.  When the user wishes to start their 
editing session, the user will indicate an “area of interest” and a single 
layer of interest.  All editable features (and relevant features from any 
snapping layers) will be loaded into the browser to begin the editing session.  
Note that editing an area of interest with many large features may cause 
performance issues due to having a large number of vector features (or a small 
number of very large vector features) stored inside browser memory.  A sensible 
(but configurable) maximum will be configurable so that users can be presented 
with a warning message when they ask for more features (or more vertexes) than 
the maximum.

When editing attributes of a particular feature, OLIVER will not 
“pre-validate” the input.  This means that if a particular column in the 
database is an “integer” column and the user attempts to enter text into 
that column, the storage of the record will fail.  OLIVER will return as 
specific an error message about any data-storage failures as is possible based 
on information returned from the server.

Editing will consist of adding points, moving points, deleting points, creating 
new lines or polygons, extending existing lines or polygons by adding or 
removing vertexes, or by moving the line or polygon wholesale.

Splitting will consist of drawing a line feature which crosses another line 
feature, causing the crossed line feature to be split into two line features at 
the point of intersection.  Note that only line-crossing-line splitting will be 
available.

Snapping will be available as follows:
• Moved point features may be snapped to other points, other 
lines/polygon-edges or other line/polygon vertices.
• Moved line vertices may be snapped to other points, other 
lines/polygon-edges or other line/polygon vertices.
• Moved polygon vertices may be snapped to other points, other 
lines/polygon-edges or other line/polygon vertices.

Note that Snapping will not be available for translated or “dragged” 
polygons or lines.  Snapping will only apply to the movement of vertices, which 
may be part of a point line or polygon.  The snapping configuration involving 
which layers are snapped-to will be set in the server configuration only.  
Other than “enable/disable snapping” the configuration of the snapping 
functionality will not be user-configurable through the OLIVER web interface.

Once the user has completed their edits, they will click the “save edits and 
close editing session” button, which will attempt to persist their changes to 
the MassGIS WFS-T.  Any failure to persist the edits will be communicated to 
the user, along with any relevant error messages.

Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 21 Mar 2011 at 4:31

[GoogleCodeExporter]

Due June 30, 2011 from PeopleGIS

Original comment by Aleda.Fr...@state.ma.us on 21 Mar 2011 at 4:31

[GoogleCodeExporter]

Original comment by Aleda.Fr...@state.ma.us on 21 Mar 2011 at 4:32

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by Aleda.Fr...@state.ma.us on 21 Mar 2011 at 4:32

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by Aleda.Fr...@state.ma.us on 29 Jul 2011 at 3:29

• Changed state: Started

[GoogleCodeExporter]

Selecting features only works in the Custom basemap, otherwise no features are 
returned.

Edit select for Custom basemap is too sensitive - too many features are 
selected for the box drawn. (see attachment).

Original comment by Aleda.Fr...@state.ma.us on 30 Aug 2011 at 9:18

Attachments:

• edit_tool_too_sensitive.JPG

[GoogleCodeExporter]

HTTPS fails - both insert and WFS intersect (trying to select the preexisting 
point).

Original comment by Aleda.Fr...@state.ma.us on 30 Aug 2011 at 9:21

[GoogleCodeExporter]

I think the user/pass is not being sent with the post - the error is 401 
Unauthorized.

Original comment by Aleda.Fr...@state.ma.us on 30 Aug 2011 at 9:22

[GoogleCodeExporter]

Issue resolved as of r102

Original comment by its.s...@gmail.com on 13 Oct 2011 at 10:02

• Changed state: Fixed

[GoogleCodeExporter]

HTTPS problem has been entered as Issue 58

Original comment by Aleda.Fr...@state.ma.us on 4 Nov 2011 at 8:34

• Changed state: Verified