[Geomoose-users] General POLL: New functionality, WMS service/metadata export.

[TC Haddad]

Hi Bob,

Responding to just the first of your 3 items, I think what you are
proposing is a nice bit of functionality. The only app that I have seen
doing something like this is the (OpenLayers based) "Gulf of Mexico Data
Atlas" which has some pretty great "connect to these services" options
exposed under something they call "more information".

I think what they are doing is likely more like a GM extension that is
responsive to the specific layer being selected, as they seem to be able to
load quite a diverse number of informational items (metadata, links to
services, and download links). It's probably the most in-depth linking for
"more information" I have ever seen from a layer catalog type interface.
Check it out:

http://www.ncddc.noaa.gov/website/DataAtlas/atlas.htm

Tanya

On Wed, Mar 25, 2015 at 9:15 AM, Basques, Bob (CI-StPaul) <
bob.basques at ci.stpaul.mn.us> wrote:

>  All,
>
>
>
> I just had a thought on a new piece of functionality for GeoMOOSE, and I’m
> probably asking too soon (without thinking about it some more) but, what
> are peoples thoughts about setting up a layer control in the Catalog for
> spitting out a WMS connection string for a layer that is currently
> displayed in GeoMOOSE?
>
>
>
> I’m thinking a sort of ad-hoc metadata output for the layer, that shows
> the WMS service the feed is coming from, what the layer name is, and a
> complete link for the image in the current view.  This would obviously need
> to be filtered for WMS services only, but it could be another XML chunk in
> the mapbooks.
>
>
>
> So, why do we (I) need/want this?  Well, we’re actually seeing more and
> more applications, both Open and Commercial that are able to import
> services directly from WMS feeds.  I’ve been working with our traffic
> management folks on setting up some feeds for some of their commercial
> signalized intersection management software.  And I want to be able to let
> them choose which layers they want to use from the catalog that they want
> all on their own.
>
>
>
> I guess I’m talking about essentially a layer level popup type of
> capability that can be populated with items specific to a layer.  Our
> metadata services links would be a good thing to add to this for example.
> We’ve been assembling a Postgres metadata storage piece for a year or so
> now that could be included in all this at some future point as well.  With
> the popup mentality, we could set up things to startup QGIS or other
> applications right from the browser.
>
>
>
> Tangentially related to the above, is, has anyone done any work with
> trying to figure out how to register users of services.  The above might
> present a method for this.  We want to know for example who registers to
> use a service in their respective software so the service doesn’t get
> interrupted downstream without the admins being aware of or are able to
> warn the users before hand about a potential service downtime.
>
>
>
> Lastly, I’ve had  some thoughts for a while now (a couple of years) about
> GeoMOOSE installations being able to read each other’s WMS (OGC?)
> services.  This may be a spot in time where that kind of functionality
> might be easy to implement as well.  With a specific method of linking into
> a GEOMOOSE install for a GetCapabilities request, all of a sudden different
> layers can be used across servers, at least as WMS services, I know there
> are some Cross site scripting pieces, but, throwing the idea out there
> anyway.  This could be set up by layer, or as a composite WMS service from
> within the GeoMOOSE install.
>
>
>
> These topics probably should be separate threads, but I think there is
> enough overlap in the functions to include them together at this point.
>
>
>
> Thoughts?
>
>
>
> bobb
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20150325/a0b37336/attachment.html>