<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Tanya,<br>
    <br>
      Lots of wanderings.  I ran across <a class="moz-txt-link-freetext" href="http://featureserver.org/">http://featureserver.org/</a> while
    searching for a WFS-T server with more options for a data store
    back-end (like Spatialite).  Looks like support has died out
    though...<br>
    <br>
    <pre class="moz-signature" cols="72">Best Regards,
Brent Fraser</pre>
    <div class="moz-cite-prefix">On 4/22/2016 12:06 PM, TC Haddad wrote:<br>
    </div>
    <blockquote
cite="mid:CAFVrPygkGmpJeHmGKzghBnSRsp=FhUbWU_euVqjeRxi1PuVdig@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div><br>
              </div>
              Awesome, <br>
              <br>
              "exclude_items" was just what I was interested in. Thanks!<br>
              <br>
            </div>
            Interesting topics all of this. I'm very interested in your
            WFS-T wanderings, even though I don't currently have a
            project to apply them to.<br>
            <br>
          </div>
          thanks for continuing to prompt,<br>
          <br>
        </div>
        Tanya<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Fri, Apr 22, 2016 at 11:02 AM, Brent
          Fraser <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"> Tanya,<br>
              <br>
                There are a couple of things happening here with respect
              to attributes.  As a GeoMOOSE implementer, I can limit the
              attributes in the Attribute Dialog by specifying only the
              ones I want to present to the user in the
              <mapsource> definition in the mapbook:<br>
              <br>
              <tt>        <attribute name="geoid10"    type="user"
                label="ID:" default-value="27999"/></tt><tt><br>
              </tt><tt>        <attribute name="namelsad10"
                type="user" label="Name:"/></tt><tt><br>
              </tt><tt>        <attribute name="classfp10" 
                type="select" label=" Type: "      
                default-value="C5"></tt><tt><br>
              </tt><tt>            <option
                value="C1">C1</option></tt><tt><br>
              </tt><tt>            <option
                value="C5">C5</option></tt><tt><br>
              </tt><tt>        </attribute></tt><br>
              <br>
              even though there could be an additional 10 attribute
              fields in the database for that feature type, the user
              will never see them.  All good.<br>
              <br>
              The other thing is a little odd.  In my Iceberg
              application I have a "created_time" that gets
              automatically populated by the Postgres database engine:<br>
              <br>
                  <tt>created_time timestamp with time zone DEFAULT
                now(),</tt><br>
              <br>
              In my testing, TinyOWS was generating an error regarding
              time formats, which was unexpected since I never listed
              the <br>
              created_time attribute in the mapsource.  It appears
              TinyOWS gets all the attributes by default.  I was able to
              prevent this by adding a line in the TinyOWS config.xml:<br>
              <br>
              <tt>      
                exclude_items="created_time,approved_time,deleted_time,obs_time"</tt><br>
              <br>
              <br>
              <pre cols="72">Best Regards,
Brent Fraser</pre>
              <div>
                <div class="h5">
                  <div>On 4/22/2016 11:38 AM, TC Haddad wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div>
                        <div>
                          <div>
                            <div>
                              <div>
                                <div>
                                  <div>Hi Brent<br>
                                    <br>
                                  </div>
                                  Just briefly skimming the TinyOWS
                                  config options:<br>
                                  <br>
                                </div>
                                - XML: <a moz-do-not-send="true"
                                  href="http://mapserver.org/tinyows/configfile.html#tinyows-configfile"
                                  target="_blank">http://mapserver.org/tinyows/configfile.html#tinyows-configfile</a><br>
                              </div>
                              - Mapfile: <a moz-do-not-send="true"
                                href="http://mapserver.org/tinyows/mapfileconfig.html"
                                target="_blank">http://mapserver.org/tinyows/mapfileconfig.html</a><br>
                              <br>
                            </div>
                            I don't see a place where you can confine
                            editing to only a specific few attributes.
                            It seems like you make the layer editable or
                            not (where editing includes geometry and all
                            attributes).<br>
                            <br>
                          </div>
                          I don't know the WFS-T spec well enough to
                          know if it is an option in the spec that is
                          just not implemented in TinyOWS, or what.
                          Interesting question, will try to look it up.<br>
                          <br>
                        </div>
                        But anyhow, circling back to GeoMoose, if we
                        wanted to find a way for a user to "hide" fields
                        from editing, it might have to be entirely on
                        the GM side if not supported by TinyOWS.<br>
                        <br>
                      </div>
                      Tanya<br>
                    </div>
                    <div class="gmail_extra"><br>
                      <div class="gmail_quote">On Fri, Apr 22, 2016 at
                        10:11 AM, Brent Fraser <span dir="ltr"><<a
                            moz-do-not-send="true"
                            href="mailto:bfraser@geoanalytic.com"
                            target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:bfraser@geoanalytic.com">bfraser@geoanalytic.com</a></a>></span>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">Interesting stuff. 
                          What did the layout of your attributes form
                          end up looking like?  What would we need to
                          address in GeoMOOSE to make it usable in a
                          project like yours?<br>
                          <br>
                          Thanks!<br>
                          <br>
                          Best Regards,<br>
                          Brent Fraser<span><br>
                            <br>
                            On 4/21/2016 11:43 PM, Raffaele Morelli
                            wrote:<br>
                            <blockquote class="gmail_quote"
                              style="margin:0 0 0 .8ex;border-left:1px
                              #ccc solid;padding-left:1ex"> On 21/04/16
                              at 05:21pm, Brent Fraser wrote:<br>
                              <blockquote class="gmail_quote"
                                style="margin:0 0 0 .8ex;border-left:1px
                                #ccc solid;padding-left:1ex"> Hey all,<br>
                                <br>
                                   I've been experimenting with
                                Geomoose's WFS-T (feature editing). Any<br>
                                thoughts about allowing teh target of
                                the attribute editing to be a tab<br>
                                instead of just a dialog?<br>
                              </blockquote>
                              Recently I've been involved in a survey
                              project, basically I was asked<br>
                              to allow ~4500 users to insert points on a
                              map and fill a form (attributes).<br>
                              <br>
                              Attributes form was "huge", ie ~15 select
                              lists (with multiple choice) and ~5
                              textbox, I<br>
                              would have liked to use GeoMOOSE but WFT-T
                              issues (those recently pointed out to this
                              ML)<br>
                              and your point made me give up and switch
                              to Drupal+Openlayers.<br>
                              <br>
                              Must say I did not spent too much in
                              digging into GM code for that attribute
                              thing<br>
                              as my deadline was really close.<br>
                              <br>
                              Ciao<br>
                              /r<br>
                              <br>
                              <br>
                            </blockquote>
                            <br>
                            <br>
                          </span>
                          <div>
                            <div>
                              _______________________________________________<br>
                              Geomoose-users mailing list<br>
                              <a moz-do-not-send="true"
                                href="mailto:Geomoose-users@lists.osgeo.org"
                                target="_blank">Geomoose-users@lists.osgeo.org</a><br>
                              <a moz-do-not-send="true"
                                href="http://lists.osgeo.org/mailman/listinfo/geomoose-users"
                                rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a></div>
                          </div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>