<div dir="auto">Summer 2017 should see the release of 3.0. </div><div class="gmail_extra"><br><div class="gmail_quote">On Feb 3, 2017 12:36, "Kevin Grootendorst" <<a href="mailto:kgrootendorst@gmail.com">kgrootendorst@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>Good to know, thanks Dan. <br></div>So this leads to the question.... do you have a ballpark release date for GM3? <br></div>Cheers, Kevin<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 11:29 AM, Dan Little <span dir="ltr"><<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">It depends on what your timeframe is. One of our design goals was to make the dynamic addition/removal of layers from both the map and the catalog much easier in GM3. We're actually trying to keep things like interacting with CSW catalogs in mind.<div><br></div><div>Thus starts what will basically be the next year's of "But we can do that in GM3!!!"</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 2, 2017 at 7:25 PM, Kevin Grootendorst <span dir="ltr"><<a href="mailto:kgrootendorst@gmail.com" target="_blank">kgrootendorst@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Thanks for this feedback Jim.<br></div></div><div>Would the current GeoMoose version 2.9.2 support this endeavor or have features/functions been deprecated since then?<br></div>With respect to your second point, my client's GeoNetwork would not be harvesting data from other catalogs, only an internal database. I foresee less complexity in terms of needing mapfiles generated on-the-fly to deal with projection issues.<br></div>In hindsight though, do you think that the GeoMoose - GeoNetwork connection was worth your time and effort? Or do you believe that it makes more sense just to keep the two applications separate? Given the time and effort involved, I'm torn between the viability and feasibility of this, versus some sort of alternate solution.<br></div>Cheers,<br></div><div>Kevin<br><br></div></div><div class="m_-5567063717318564105m_-810388768160252157HOEnZb"><div class="m_-5567063717318564105m_-810388768160252157h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 2, 2017 at 10:46 AM, James Klassen <span dir="ltr"><<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>I wrote an extension connected GeoMoose to a CSW server (GeoNetwork) for a project maybe 5 years ago or so. I had intended to release it but never got around to cleaning it up enough to not be project specific. It would also take some work to bring it up to date with current GeoMoose.</div><div dir="auto"><br></div><div dir="auto">It was a tab that searched the catalog and then presented the results with options to view the metadata or if a WMS link was present in the metadata, add the layer to the map. A download button would be possible if it could be derived from the metadata, but don't remember if I had that working.</div><div dir="auto"><br></div><div dir="auto">Add to Map required some trickery:</div><div dir="auto">1) The Active/Visible layers extension was necessary to control the layers added from CSW. The regular Catalog tab still works as normal but didn't know anything about the new layers.</div><div dir="auto"><br></div><div dir="auto">2) (And this was the real stumbling block to me finishing the release.) Because the CSW server was cataloging many off site resources, I had no control over the WMS servers. As such many didn't support the projection used by GeoMoose (at the only commonly available WMS projection was 4326 which looks horrible on screen) so I wrote a ruby-mapscript program that generated a mapfile for MapServer on the fly (in RAM) that from the metadata info would connect to the remote WMS, find the best projection supoorted by the server, if necessary reproject it to the projection uses by GeoMoose and create a local WMS server that GeoMoose would use.</div><div dir="auto"><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Feb 2, 2017 8:23 AM, "Kevin Grootendorst" <<a href="mailto:kgrootendorst@gmail.com" target="_blank">kgrootendorst@gmail.com</a>> wrote:<br type="attribution"><blockquote class="m_-5567063717318564105m_-810388768160252157m_-3171646441508399855m_6129821016859212010quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Dear list,<br>I'm interested in using GeoMOOSE to ssearch and display layers from GeoNetwork. A user would be able to query GeoNetwork metadata from within GeoMOOSE, then have the option to display metadata, add the layer to the map, or download the layer. <br>I think I have to implement Catalog Web Services in GeoNetwork and have GeoMOOSE connect to these web services. I assume I'll have to write a JavaScript extension for GeoMOOSE, but JS is not my strength.<br>Does any one have any insight into how to develop this connection? I found a post from years ago that confirmed that the connection is possible, but there was no additional info. <br></div>Cheers,<br></div>Kevin<br></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></div></div>
</blockquote></div><br></div>
</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>
</blockquote></div><br></div>
</blockquote></div></div>