[Geomoose-users] GM3: Different Projections, securing underlying data?

[James Klassen]

A quick answer from the top of my head.

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.

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).

Some options:
* Not allow vector access and live with the reduced feature set
* Allow vector access but filter it with MapServer to limit what
features/attributes/etc. is exposed.



On Fri, Sep 22, 2017 at 3:38 PM, Mark Volz <MarkVolz at co.lyon.mn.us> wrote:

> Hello,
>
>
>
> I am curious about a couple things regarding GeoMOOSE 3.
>
>
>
> First,
>
> I have seen several emails referencing projection 4326.  Is that the only
> supported projection or can we use our own?
>
>
>
> Second,
>
> 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?
>
>
>
> Thank You!
>
>
>
> Sincerely,
>
> *Mark Volz, GISP*
>
>
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20170922/7da2662a/attachment.html>