<div><br></div>Couldn't you handle login at the Apache level?<div><br></div><div>TH<span></span><br><br>On Monday, April 25, 2016, Brent Fraser <<a href="mailto:bfraser@geoanalytic.com">bfraser@geoanalytic.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jim,<br>
<br>
Interesting ideas. I had considered views (I use them extensively with the old GeoMOOSE editing) for other purposed like styling, but I didn't want to push my luck with TinyOWS. It is implied in the TinyOWS doc that it will work with views (I'll test that).<br>
<br>
The more bigger issue is security. With the old GeoMOOSE editing mechanism, I handled security in the PHP. It checked the session to ensure the user was logged in and issued the SQL if they were. I guess I'll need to code some PHP to act as a proxy between TinyOWS and GeoMOOSE.<br>
<br>
Remind me how is WFS-T better? ;)<br>
<br>
Best Regards,<br>
Brent Fraser<br>
<br>
On 4/25/2016 9:48 AM, Jim Klassen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
An option for TinyOWS might be to do the attribute filtering in<br>
PostgreSQL with some combination of views/triggers/rules. You probably<br>
want to somehow enforce that clients can't view or update fields that<br>
they shouldn't.<br>
<br>
On 04/22/2016 01:34 PM, Brent Fraser wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Tanya,<br>
<br>
Lots of wanderings. I ran across <a href="http://featureserver.org/" target="_blank">http://featureserver.org/</a> while<br>
searching for a WFS-T server with more options for a data store<br>
back-end (like Spatialite). Looks like support has died out though...<br>
<br>
Best Regards,<br>
Brent Fraser<br>
On 4/22/2016 12:06 PM, TC Haddad wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Awesome,<br>
<br>
"exclude_items" was just what I was interested in. Thanks!<br>
<br>
Interesting topics all of this. I'm very interested in your WFS-T<br>
wanderings, even though I don't currently have a project to apply<br>
them to.<br>
<br>
thanks for continuing to prompt,<br>
<br>
Tanya<br>
<br>
On Fri, Apr 22, 2016 at 11:02 AM, Brent Fraser<br>
<<a>bfraser@geoanalytic.com</a> <mailto:<a>bfraser@geoanalytic.com</a>>> wrote:<br>
<br>
Tanya,<br>
<br>
There are a couple of things happening here with respect to<br>
attributes. As a GeoMOOSE implementer, I can limit the<br>
attributes in the Attribute Dialog by specifying only the ones I<br>
want to present to the user in the <mapsource> definition in the<br>
mapbook:<br>
<br>
<attribute name="geoid10" type="user" label="ID:"<br>
default-value="27999"/><br>
<attribute name="namelsad10" type="user" label="Name:"/><br>
<attribute name="classfp10" type="select" label=" Type:<br>
" default-value="C5"><br>
<option value="C1">C1</option><br>
<option value="C5">C5</option><br>
</attribute><br>
<br>
even though there could be an additional 10 attribute fields in<br>
the database for that feature type, the user will never see<br>
them. All good.<br>
<br>
The other thing is a little odd. In my Iceberg application I<br>
have a "created_time" that gets automatically populated by the<br>
Postgres database engine:<br>
<br>
created_time timestamp with time zone DEFAULT now(),<br>
<br>
In my testing, TinyOWS was generating an error regarding time<br>
formats, which was unexpected since I never listed the<br>
created_time attribute in the mapsource. It appears TinyOWS gets<br>
all the attributes by default. I was able to prevent this by<br>
adding a line in the TinyOWS config.xml:<br>
<br>
exclude_items="created_time,approved_time,deleted_time,obs_time"<br>
<br>
<br>
Best Regards,<br>
Brent Fraser<br>
<br>
On 4/22/2016 11:38 AM, TC Haddad wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Brent<br>
<br>
Just briefly skimming the TinyOWS config options:<br>
<br>
- XML:<br>
<a href="http://mapserver.org/tinyows/configfile.html#tinyows-configfile" target="_blank">http://mapserver.org/tinyows/configfile.html#tinyows-configfile</a><br>
- Mapfile: <a href="http://mapserver.org/tinyows/mapfileconfig.html" target="_blank">http://mapserver.org/tinyows/mapfileconfig.html</a><br>
<br>
I don't see a place where you can confine editing to only a<br>
specific few attributes. It seems like you make the layer<br>
editable or not (where editing includes geometry and all<br>
attributes).<br>
<br>
I don't know the WFS-T spec well enough to know if it is an<br>
option in the spec that is just not implemented in TinyOWS, or<br>
what. Interesting question, will try to look it up.<br>
<br>
But anyhow, circling back to GeoMoose, if we wanted to find a<br>
way for a user to "hide" fields from editing, it might have to<br>
be entirely on the GM side if not supported by TinyOWS.<br>
<br>
Tanya<br>
<br>
On Fri, Apr 22, 2016 at 10:11 AM, Brent Fraser<br>
<<a>bfraser@geoanalytic.com</a>> wrote:<br>
<br>
Interesting stuff. What did the layout of your attributes<br>
form end up looking like? What would we need to address in<br>
GeoMOOSE to make it usable in a project like yours?<br>
<br>
Thanks!<br>
<br>
Best Regards,<br>
Brent Fraser<br>
<br>
On 4/21/2016 11:43 PM, Raffaele Morelli wrote:<br>
<br>
On 21/04/16 at 05:21pm, Brent Fraser wrote:<br>
<br>
Hey all,<br>
<br>
I've been experimenting with Geomoose's WFS-T<br>
(feature editing). Any<br>
thoughts about allowing teh target of the attribute<br>
editing to be a tab<br>
instead of just a dialog?<br>
<br>
Recently I've been involved in a survey project,<br>
basically I was asked<br>
to allow ~4500 users to insert points on a map and fill<br>
a form (attributes).<br>
<br>
Attributes form was "huge", ie ~15 select lists (with<br>
multiple choice) and ~5 textbox, I<br>
would have liked to use GeoMOOSE but WFT-T issues (those<br>
recently pointed out to this ML)<br>
and your point made me give up and switch to<br>
Drupal+Openlayers.<br>
<br>
Must say I did not spent too much in digging into GM<br>
code for that attribute thing<br>
as my deadline was really close.<br>
<br>
Ciao<br>
/r<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a>Geomoose-users@lists.osgeo.org</a><br>
<mailto:<a>Geomoose-users@lists.osgeo.org</a>><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a>Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
</blockquote>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a>Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
</blockquote>
<br>
<br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a>Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a></blockquote></div>