<div dir="auto">Jim hit the nail on the head. <div dir="auto"><br></div><div dir="auto">Also, it's important to keep in mind you were ALWAYS publishing that data, as mapserver had access to it via through WMS AND its own protocols. It is best to limit which attributes are published if you're worried about privacy protection. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sep 22, 2017 18:23, "James Klassen" <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>A quick answer from the top of my head.<br><br>1) No, but it works around a bug in some versions of MapServer and generally makes life a little simpler. The data can still be stored in your favorite projection and it gets reprojected on the fly for the map.<br><br></div>2) GeoMoose 3 will display and identify features on WMS layers but it needs access to the vector features (WFS or GeoJSON) to do a lot of the cool new stuff (client side buffering, querying based on features in a layer, and IIRC the results grid to name a few).<br><br></div>Some options: <br>* Not allow vector access and live with the reduced feature set<br>* Allow vector access but filter it with MapServer to limit what features/attributes/etc. is exposed.<br><div><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 22, 2017 at 3:38 PM, Mark Volz <span dir="ltr"><<a href="mailto:MarkVolz@co.lyon.mn.us" target="_blank">MarkVolz@co.lyon.mn.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div class="m_-8052499751325672571m_4467966976873810975WordSection1">
<p class="MsoNormal">Hello, <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I am curious about a couple things regarding GeoMOOSE 3.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">First,<u></u><u></u></p>
<p class="MsoNormal">I have seen several emails referencing projection 4326. Is that the only supported projection or can we use our own?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Second,<u></u><u></u></p>
<p class="MsoNormal">Unlike GeoMOOSE 2.x, It appears that GeoMOOSE 3 relies heavily on OGC and GeoJSON. Does this imply that we have to have our underlying data exposed on a web server that could be accessed by clients other than GeoMOOSE, or can we still
keep the underlying data private?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank You!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Sincerely,<u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="color:#1f497d">Mark Volz, GISP</span></b><b><span style="font-size:12.0pt;color:#1f497d"><u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span style="color:#1f497d"><u></u> <u></u></span></b></p>
</div>
</div>
<br>______________________________<wbr>_________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geomoose-users</a><br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/geomoose-<wbr>users</a><br></blockquote></div></div>