[Geomoose-users] Announcing RFC 8 GM 3 - Vector Editing

Brent Fraser bfraser at geoanalytic.com
Mon Dec 14 13:26:42 PST 2020


Jim,

Some somewhat terse answers to your questions:

CORS support:
CORS tricks may work; proxy will work.

Editing without saving option:
A rare workflow, but might be useful.

Useful to be able to use geometry other than a point to select feature for edit?
A future enhancement if requested.

Overloading query-as:
We may use an "edit-as" tag; TBD in Development.

Both WMS and WFS layers editable?
Since we are using standard OGC protocols, WMS is not used for editing.  But since both layers point to the same dataset (using different protocols), the WMS will be updated, via WFS-T.  In fact it will be necessary for GM to refresh the WMS layer (or the WFS layer) after a WFS-T edit.

Compatibility with other protocols:
Hopefully Dan will take this into account in the design.

Best regards,
Brent

----------------------------------------

From: Jim Klassen <klassen.js at gmail.com>
Sent: 12/10/20 11:15 AM
To: geomoose-users at lists.osgeo.org
Subject: Re: [Geomoose-users] Announcing RFC 8 GM 3 - Vector Editing

Overall, it looks good to me.  I have some minor questions/clarifications:

"Proxying the WFS-T server will be necessary if the GeoMoose JavaScript is delivered from an address different from the WFS-T server. This can be configured on the GeoMoose web server."

Do the normal WFS CORS tricks not work?  Although, I'd understand for clarity of the documentation that recommending using proxy it is simpler than explaining how to setup CORS correctly.

Mapbook configuration: 

How does GeoMoose know "editing" or more specifically saving is supported by a layer?  Is there any use case allowing the user to edit a non-savable layer?  IIRC: The existing editing tools aren't specific to the Sketch layer, but "work" on any vector layer.  This could be useful maybe to have a layer that provides predefined, but editable polygons that could be used as input to a select service.  Would it make sense to have an attribute for this (or have a "wfs-t" layer type)?  (Or is this what "draw-edit" does?)

Are we re-using "query-as" in the WMS layer for "edit-as"?  Would we ever want to separate the two concepts?  I'm saying this is a problem, just asking.

Is the intent that the WMS (with query-as/edit-as) and WFS layer in the catalog are both editable?  Are they simply provided as two separate examples of what is possible or do both need to be in the catalog for editing to work?

Compatibility:

Please keep the potential for other editable layer types in mind (I'm thinking of WFS3/OGC API Features, or maybe someone wants to implement a custom GeoJSON/REST layer type specific to their environment) so we don't box ourselves out of implementing them sometime in the future (not as part of this RFC).

On 12/10/20 10:23 AM, Brent Fraser wrote:

Hello all GeoMoosers!

I present for your reading pleasure RFC 8 GM 3 - Vector Editing https://www.geomoose.org/rfc/rfc-8.html.   Please read and feel free to comment, ask questions, etc. via this mailing list.    If the review goes well, I'll call for a vote Monday and hopefully proceed with development in the next week or two.

Thanks!
Brent Fraser

_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geomoose-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20201214/6b4e6984/attachment.html>


More information about the Geomoose-users mailing list