Ecoinformatics Redmine: Matthew Perryhttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362006-12-15T18:13:13ZEcoinformatics Redmine
Redmine Metacat - Bug #2691: Update knbweb module to use maphttps://projects.ecoinformatics.org/ecoinfo/issues/2691#change-93312006-12-15T18:13:13ZMatthew Perryperry@nceas.ucsb.edu
<p>The knbweb now uses the "thumbnail" map on the front page which links to the full interactive mapping application. Requires that spatial metacat (version 1.7+ ) is installed at /knb on the server.</p> Metacat - Bug #2551: Generalized spatial xpaths for mutliple schemashttps://projects.ecoinformatics.org/ecoinfo/issues/2551#change-87142006-12-14T00:42:21ZMatthew Perryperry@nceas.ucsb.edu
<p>Preliminary support for multiple spatial schemas in the same metacat instance has been added to cvs head.</p>
<p>This is configured entirely in metacat.properties and allows you to specify multiple spatial schemas and the 4 bounding coordinates for each. If the docname matches one of the spatial schemas, it will use the appropriate set of coordinate xpaths.</p>
<p>This should mean that FGDC and EML documents can sit side-by-side in the same metacat instance and both will be included in the spatial cache ( although this has not been tested yet :-)</p> Metacat - Bug #2692: Use .jsp and reduce token usage in skinshttps://projects.ecoinformatics.org/ecoinfo/issues/2692#change-93332006-12-13T21:56:12ZMatthew Perryperry@nceas.ucsb.edu
<p>This should be part of a larger, more systematic effort to eliminate ant tokens. It should not be a priority for the 1.7 release as there are more pressing issues to deal with.</p> Metacat - Bug #2695: Loading map message persists when a WMS is downhttps://projects.ecoinformatics.org/ecoinfo/issues/2695#change-93382006-12-13T19:09:33ZMatthew Perryperry@nceas.ucsb.edu
<p>Fixed. When image load fails, the layerCount is decremented so that mapbuilder will not display a waiting message unless it is actually waiting for an image. If a wms server is down, it puts a line-through the legend text for that layer.</p>
<p>The patch was suggested by John Pulles <john.pullesATgeodan.nl> on the mapbuilder mailing list and i'll be working with the mapbuilder team to get the patch in the next release.</p> Metacat - Bug #2695 (Resolved): Loading map message persists when a WMS is downhttps://projects.ecoinformatics.org/ecoinfo/issues/26952006-12-12T19:59:47ZMatthew Perryperry@nceas.ucsb.edu
<p>When an external WMS server goes down, mapbuilder will continue trying to load the layer.. or at least will continue showing a message stating "Loading 1 map layer". If the server is down, the message never goes away and this is very distracting.</p>
<p>Ideally we could implement a timeout whereby mapbuilder would remove the message after a reasonable amount of time (20 seconds) if it had not recieved a response yet. Also a notification such as "Layer X could not be loaded" would be helpful.</p>
<p>I spoke with the Mapbuilder team about this and no one has implemented a solution but they'd be interested in including a patch in the next release assuming we can develop a fix.</p>
<p>The relevant source file will likely be metacat/lib/spatial/mapbuilder/lib/widget/MapPane.js</p> Metacat - Bug #2548: Architecture for filtering features from WMS requestshttps://projects.ecoinformatics.org/ecoinfo/issues/2548#change-87052006-12-12T03:14:27ZMatthew Perryperry@nceas.ucsb.edu
<p>The initial architecture for dynamically generated sld filters is in place. The SLD Factory can now take a list of allowable docids and generate an SLD which, when appended to a WMS request, can limit which features are shown on the map.</p>
<p>The actual generation of the allowable docid list is currently very expensive so it is not implemented. Ideally the allowable docids could be determined based on session variables to avoid having to run expensive SQL queries on every map redraw.</p>
<p>Since this requires more extensive changes than I can commit to before the 1.7.0 release, I'm pushing this off to 1.8.</p> Metacat - Bug #2548: Architecture for filtering features from WMS requestshttps://projects.ecoinformatics.org/ecoinfo/issues/2548#change-87042006-12-12T03:09:31ZMatthew Perryperry@nceas.ucsb.edu
<p>correction to original bug description:</p>
<pre><code>Currently, all of the <strong>PUBLIC</strong> documents in the metacat database are stored in the spatial cache.</code></pre> Metacat - Bug #2689: Upgrade to Geoserver 1.4https://projects.ecoinformatics.org/ecoinfo/issues/2689#change-93262006-12-08T01:49:42ZMatthew Perryperry@nceas.ucsb.edu
<p>Due to time constraints, I've upgrade to geoserver 1.4.0 RC5. It's the final release candidate and should be virtually identical to 1.4.0 final when it comes out.</p>
<p>If 1.4.0 final is released in the next week, we'll incorporate that into the metacat 1.7 release. Otherwise, this version seems to work 100% and I don't see any reason to undertake another upgrade immediately before a release.</p> Metacat - Bug #2692 (Resolved): Use .jsp and reduce token usage in skinshttps://projects.ecoinformatics.org/ecoinfo/issues/26922006-12-07T00:38:40ZMatthew Perryperry@nceas.ucsb.edu
<p>The following skins (esa, nrs, obfs, nceas) should be updated to use .jsp and replace use of tokens as much as possible. If runSpatialOption is false, don't display the map.</p> Metacat - Bug #2691 (Resolved): Update knbweb module to use maphttps://projects.ecoinformatics.org/ecoinfo/issues/26912006-12-07T00:31:18ZMatthew Perryperry@nceas.ucsb.edu
<p>The knbweb module needs to be integrated with our mapbuilder interface.</p> Metacat - Bug #2690 (Resolved): Fully document the spatial optionhttps://projects.ecoinformatics.org/ecoinfo/issues/26902006-12-07T00:29:25ZMatthew Perryperry@nceas.ucsb.edu
<p>All aspects of installing, configuring and using the spatial option should be covered in the docs before the release.</p> Metacat - Bug #2689 (Resolved): Upgrade to Geoserver 1.4https://projects.ecoinformatics.org/ecoinfo/issues/26892006-12-07T00:27:42ZMatthew Perryperry@nceas.ucsb.edu
<p>The current (12/06/2006) cvs head uses an early beta of geoserver 1.4. Though it works flawlessly for our purposes, it would be best to upgrade to geoserver 1.4 final to resolve any outstanding bugs and make it easier to upgrade in the future and support.</p> Metacat - Bug #2670: Test Metacat version with updates does not link to the "create a new account...https://projects.ecoinformatics.org/ecoinfo/issues/2670#change-92732006-12-07T00:21:26ZMatthew Perryperry@nceas.ucsb.edu
<p>The knb skins included with metacat are not the official skins deployed on the knb website. The knbweb module contains the official skin and will not have this issue when deployed.</p> Metacat - Bug #2669: Mapbuilder incompatible w/ Safari, Operahttps://projects.ecoinformatics.org/ecoinfo/issues/2669#change-92712006-11-28T01:26:56ZMatthew Perryperry@nceas.ucsb.edu
<p>Added a javascript detection mechanism to the mapbuilder load sequence to detect the browser and redirect the user to an error page if their browser is not compatible.</p> Metacat - Bug #2554: Store the spatial data cache outside servlet contexthttps://projects.ecoinformatics.org/ecoinfo/issues/2554#change-87202006-11-28T01:04:18ZMatthew Perryperry@nceas.ucsb.edu
<p>An alternative solution was implemented: once the initial spatial harvest is completed, the "regenerateCacheOnRestart" metacat property is set to false so that the full cache regeneration only happens once (when you first install metacat).</p>
<p>So the cache will still need to regenerate on every re-install but at least restarting the servlet container doesn't require the expensive regeneration.</p>