<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
Overall, it looks good to me. I have some minor
questions/clarifications:<br>
<br>
"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."<br>
<br>
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.<br>
<br>
<br>
<br>
Mapbook configuration: <br>
<br>
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?)<br>
<br>
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.<br>
<br>
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?<br>
<br>
<br>
<br>
Compatibility:<br>
<br>
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).<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 12/10/20 10:23 AM, Brent Fraser
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8d6d47726388402590ee639881e10e0e@geoanalytic.com">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div style="font-family: arial; font-size: 14px;">
<div fr-original-style="" style="box-sizing: border-box;">Hello
all GeoMoosers!</div>
<div fr-original-style="" style="box-sizing: border-box;"><br
fr-original-style="" style="box-sizing: border-box;">
</div>
<div fr-original-style="" style="box-sizing: border-box;"> I
present for your reading pleasure RFC 8 GM 3 - Vector Editing
<a fr-original-style=""
href="https://www.geomoose.org/rfc/rfc-8.html"
style="box-sizing: border-box; color: rgb(0, 102, 147);
text-decoration: underline; user-select: auto;"
target="_blank" rel="noopener noreferrer"
moz-do-not-send="true">https://www.geomoose.org/rfc/rfc-8.html</a>.
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.</div>
<div fr-original-style="" style="box-sizing: border-box;"><br
fr-original-style="" style="box-sizing: border-box;">
</div>
<div fr-original-style="" style="box-sizing: border-box;">Thanks!</div>
<div fr-original-style="" style="box-sizing: border-box;">Brent
Fraser</div>
<div fr-original-style="" style="box-sizing: border-box;"><br
fr-original-style="" style="box-sizing: border-box;">
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Geomoose-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/geomoose-users">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a>
</pre>
</blockquote>
<br>
</body>
</html>