[Geomoose-users] Projection Issues, Extent Issues, Limit Buffer Size, Security

[Fischer, Brian]

Hey Mark,

 

Jim already addressed a few of these but I thought I would try to
address the rest.  See comments below...

 

From: geomoose-users-bounces at lists.sourceforge.net
[mailto:geomoose-users-bounces at lists.sourceforge.net] On Behalf Of Mark
Volz
Sent: Wednesday, May 07, 2008 2:45 PM
To: geomoose-users at lists.sourceforge.net
Subject: [Geomoose-users] Projection Issues, Extent Issues, Limit Buffer
Size,Security

 

This message covers a couple questions I have within Geomoose including

#Projection Issues

#Extent Issues

#Limit Buffer Size

#Security

 

#Projection Issues:

 

What I would like to do is:

 

a) Include data in either UTM or Lyon County Coordinates - including the
ability to utilize the LMIC WMS Server which is in UTM. 

b) Have the XY location on the bottom of the map to display Lyon County
Coordinates, the latitude and longitude must be accurate for the
pictometry tool. 

 

Currently my data is in UTM so that it matches the LMIC imagery.  The XY
location of also is in UTM.  The highway department expressed interest
in having the XY location display in County Coordinates.  To fix this, I
changed the Coordinate system in the .js file from UTM to MN-COUNTY
LYON.  The XY location did display our county coordinates and the
measurements were correct; however, the latitude and longitude are no
longer valid.

 

I would like to keep using the LMIC UTM image server, however, we do
need the XY location in county coordinates and the latitude and
longitude to be correct.  The GIS data could be in county coordinates or
UTM.  For my own curiosity I would like to know how to get the county
coordinates to work, I also think it might save time dealing with
updates - and yes I understand that there will be a performance hit if
mapserver reprojects on the fly, however I can always switch back if I
think its too slow.  Perhaps someone could send me a .map file using
county coordinates as an example.

 

I agree with Jim, I would put all your data in Lyon County cords and
then reproject the LMIC WMS on the fly to county cords.  I have an
example mapfile of doing this exact thing for another county if you want
it, just let me know.

 

#Extent Issue

 

Next, I am having some issues with the extent.  What I would like to do
is display only a portion of the data by using a top bottom left right
box area instead of a query.  However when I assign to small of an area
the entire layer does not draw.  Can I use the extent to limit the
displayed area, or is this not possible?

 

I don't believe this is possible, at least not that I can think of a way
to do it with MapServer or GeoMOOSE.  I would just clip your data set,
it will perform better any way.

 

#Select by Buffer

On the select by buffer tool I noticed that If I typed in a ridicules
number such as "buffer parcels within 900 miles" The server obviously
could not handle the request and crashed.  Is there a way to limit the
buffer size?

 

We do have the capability of specifying a form validation on an input
parameter, but I'm afraid it is undocumented and has never been tried
with the buffer tool.  You could always right your own javascript to do
this, but you would need to dig into the GeoMOOSE code for that.

 

#Security question

Last,  

We need the ability for some users to log in to get access to more
secure data.  For example a we need a public and internal site or
perhaps one where users log in i.e. The Sheriff might want a "crime map"
whereas only the sheriff and deputies have access to that information.
Does anyone have any ideas on how this could be done though geomoose?

 

I do this all the time for clients.  It is not a feature of GeoMOOSE or
MapServer.  Rather it is handled in the server admin side of things.  If
your running IIS you can use the windows authentication to restrict
people to a folder or file.  You can also do that same thing with Apache
using the httpd.conf file.

 

 

Mark Volz

GIS Specialist

Lyon County, MN

(507) 532-8218

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20080511/f765f9f9/attachment.html