<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
x/y status bar can be in anything you like it is now independent of
the map. See "Configure Coordinate Display" in the workshop [1]<br>
<br>
Air photo background shouldn't be a problem as it is WMS. IIRC the
bug had something to do with identify or select features over WFS.
I don't remember the details of what versions were affected.<br>
<br>
Open Data, particularly from governments, seems to be the trend at
least in MN, [2], [3], etc. That said, you are correct, GeoMoose
2.x does more of the processing (most notably select and search) on
the server in PHP scripts vs using directly querying WFS so it does
hide the source data a bit better from the end user, but even with
just WMS you can reconstruct the vectors from the image with a
little effort. You could theoretically replicate the PHP model with
GeoMoose 3.x but it would take some effort.<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://geomoose.github.io/gm3/workshop/">http://geomoose.github.io/gm3/workshop/</a><br>
<br>
[2] <a class="moz-txt-link-freetext" href="https://gisdata.mn.gov/organization">https://gisdata.mn.gov/organization</a><br>
[3]
<a class="moz-txt-link-freetext" href="http://www.twincities.com/2014/02/10/ramsey-county-gis-data-will-soon-be-free/">http://www.twincities.com/2014/02/10/ramsey-county-gis-data-will-soon-be-free/</a><br>
<br>
<div class="moz-cite-prefix">On 09/27/2017 02:35 PM, Mark Volz
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:36CA828A36E29F45B7CF0A1766E5DFA37C3C5403@swmail01.r8nssis.local">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dan
and Jim,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank
you for your reply.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Regarding
projections, I would still like to use county coordinates
for the x/y status bar, underlying data, air photo
background, etc. I have no desire to use Google or Mapnik
boundaries. Therefore I would like to continue using my
county coordinates if possible. Is there a way that I can
verify which version of Mapserver / MS4W has the projection
bug so that I can avoid that version of Mapserver / MS4w if
I choose to use my own projection?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Regarding
sharing data through WMS, WFS, and GeoJson. Our county does
not have an “Open Data” Policy yet. Therefore I think I
should do my due diligence to try to protect users from
downloading the parcels in a vector format through an open
WFS or GeoJSON endpoint – even if it is just the outline and
Parcel Identification Number. So it sounds like my choices
right now are 1) Adopt an Open data Policy. 2) Use GeoMOOSE
3.x, but without the cool features, or 3) Use GeoMOOSE 2.x.
Is that correct? If so perhaps there might be more interest
in adopting an open data policy.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank
You!<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Mark
Volz, GISP</span></b><b><span
style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Dan
Little [<a class="moz-txt-link-freetext" href="mailto:theduckylittle@gmail.com">mailto:theduckylittle@gmail.com</a>]
<br>
<b>Sent:</b> Friday, September 22, 2017 6:27 PM<br>
<b>To:</b> Jim Klassen <a class="moz-txt-link-rfc2396E" href="mailto:klassen.js@gmail.com"><klassen.js@gmail.com></a><br>
<b>Cc:</b> Mark Volz <a class="moz-txt-link-rfc2396E" href="mailto:MarkVolz@co.lyon.mn.us"><MarkVolz@co.lyon.mn.us></a>;
GeoMOOSE Users List <a class="moz-txt-link-rfc2396E" href="mailto:geomoose-users@lists.osgeo.org"><geomoose-users@lists.osgeo.org></a><br>
<b>Subject:</b> Re: [Geomoose-users] GM3: Different
Projections, securing underlying data?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Jim hit the nail on the head. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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. <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Sep 22, 2017 18:23, "James Klassen"
<<a href="mailto:klassen.js@gmail.com"
moz-do-not-send="true">klassen.js@gmail.com</a>>
wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">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.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">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).<o:p></o:p></p>
</div>
<p class="MsoNormal">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.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Sep 22, 2017 at 3:38 PM,
Mark Volz <<a
href="mailto:MarkVolz@co.lyon.mn.us"
target="_blank" moz-do-not-send="true">MarkVolz@co.lyon.mn.us</a>>
wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid
#CCCCCC 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hello,
<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I
am curious about a couple things regarding
GeoMOOSE 3.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">First,<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I
have seen several emails referencing
projection 4326. Is that the only supported
projection or can we use our own?<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Second,<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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?<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Thank
You!<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">Sincerely,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="color:#1F497D">Mark Volz, GISP</span></b><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="color:#1F497D"> </span></b><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org"
target="_blank" moz-do-not-send="true">Geomoose-users@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/geomoose-users"
target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org"
moz-do-not-send="true">Geomoose-users@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/geomoose-users"
target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>