Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362006-12-12T19:59:47ZEcoinformatics Redmine
Redmine 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> Bug #2669 (Resolved): Mapbuilder incompatible w/ Safari, Operahttps://projects.ecoinformatics.org/ecoinfo/issues/26692006-11-14T19:48:00ZMatthew Perryperry@nceas.ucsb.edu
<p>Mapbuilder, our current web mapping client, uses the browser to do XSLT transforms on the client side. A number of browsers do not allow XSLT to be accessed from javascript, most notably Safari, Opera and Konqueror.</p>
<p>See <a class="external" href="http://developer.apple.com/internet/safari/faq.html#anchor21">http://developer.apple.com/internet/safari/faq.html#anchor21</a></p>
<p>This is a fundamental problem and the mapbuilder developers have stated that they have no plans to support browsers without javascript XSLT.</p>
<p>We have two options to remedy this:</p>
<p>- Switch to a different web mapping client<br />- Detect the browser and alert the user when their browser is not compatible (and don't display the broken map of course).</p> Bug #2551 (Resolved): Generalized spatial xpaths for mutliple schemashttps://projects.ecoinformatics.org/ecoinfo/issues/25512006-09-11T22:16:43ZMatthew Perryperry@nceas.ucsb.edu
<p>The spatial harvester is currently generic enough to handle any xml document with west,east,north and south xpaths. These are configured in metacat.properties.</p>
<p>However, they are single values and thus a metacat instance can only support spatial options for one schema at a time.</p>
<p>We need to make this generic enough so that multiple supported schemas can be in the same database, their geographic coverages all represented in the spatial cache.</p> Bug #2550 (Resolved): Dateline and polar handling for pointshttps://projects.ecoinformatics.org/ecoinfo/issues/25502006-09-11T22:08:15ZMatthew Perryperry@nceas.ucsb.edu
<p>Unfortunately for cartographers the world is not flat. When a feature crosses the dateline or the polar regions, the cartesian coordinate system and all the assumptions that go with it are invalid. For instance the west bounding coordinate would be greater than the east bounding coordinate for a bounding box that crossed the international date line.</p>
<p>This is taken care of in the polygon code by splitting such polygons into multi-polygons.</p>
<p>We need to update the point centroid generation code to reflect this reality as well.</p> Bug #2549 (Resolved): Limit spatial cache to public documentshttps://projects.ecoinformatics.org/ecoinfo/issues/25492006-09-11T22:02:20ZMatthew Perryperry@nceas.ucsb.edu
<p>Until we implement a feasible wms feature filter ( bug 2548 ) we must only put publically readable documents in the spatial cache.</p> Bug #2511 (Resolved): Include an optional spatial dataset packagehttps://projects.ecoinformatics.org/ecoinfo/issues/25112006-08-09T23:54:12ZMatthew Perryperry@nceas.ucsb.edu
<p>For users who can't rely on external WMS servers for their data, it would be nice to have some global datasets that they could store locally and use as a base map. The issue is size.. 32 MB for a world borders dataset of acceptable quality.</p>
<p>So we'll make this an optional data package that can be added on after the metacat install (For the CD distributiuons, we could incude it by default).</p>
<p>The trick will be configuring geoserver:</p>
<p>For the 1.7 release, we'll have to resort to an instruction set for how to edit the necessary config files. We should have the entries already constructed but commented out to make this as easy as possible.</p>
<p>For the 1.9 release, we should make this tightly integrated with the spatial admin page so that it is a few painless clicks. ( see bug 2180 and bug 2190 )</p> Bug #2503 (Resolved): Metacat Servlet action=spatial_query returns incorrect resultshttps://projects.ecoinformatics.org/ecoinfo/issues/25032006-07-31T19:55:05ZMatthew Perryperry@nceas.ucsb.edu
<p>It appears that the metacat spatial query (metacat?action=spatial_query) does not return correct results. Based on a few test cases, it appears that only spatial queries which intersect the north-west corner of the geographic coverage return a correct result. This indicates a rather serious error in the spatial intersection logic.</p> Bug #2437 (Resolved): Cleaner install for spatial componentshttps://projects.ecoinformatics.org/ecoinfo/issues/24372006-05-16T16:46:47ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Make geoserver install possible from metacat build file and easier integration into the skins.</p> Bug #2190 (Resolved): Metacat Spatial Option Admin Pagehttps://projects.ecoinformatics.org/ecoinfo/issues/21902005-09-06T17:17:11ZJohn Harrisharris@nceas.ucsb.edu
<p>The Metacat Spatial Option needs an admin page so that the Metcat administrator<br />can administer the configuration of the spatial options. The admin page should<br />include:</p>
<p>upload GIS elements (georef'd images, shapefiles etc..)<br />set which elements should be available to end-user<br />set projections<br />set the geographic presentation info to be displayed (scale bars, titles etc..)</p> Bug #2186 (Resolved): Customizable web map clienthttps://projects.ecoinformatics.org/ecoinfo/issues/21862005-09-06T17:05:38ZJohn Harrisharris@nceas.ucsb.edu
<p>Currently, the spatial elements displayed within the Metacat spatial viewer are<br />lacking the standard information needed for geographic presentations. The<br />information below should be available for display within the Metacat spatial viewer:</p>
<p>Title<br />Legend<br />Scale<br />Contour Intervals<br />Source</p>
<p>... and there are probably others.</p> Bug #2184 (Resolved): Integrate into skins systemhttps://projects.ecoinformatics.org/ecoinfo/issues/21842005-09-06T16:55:49ZJohn Harrisharris@nceas.ucsb.edu
<p>The Metacat spatial option(s) should be easily included in any skin, so that<br />individuals and organizations may easily customize their sites.</p> Bug #2182 (Resolved): Identifying point goes direct to metadata displayhttps://projects.ecoinformatics.org/ecoinfo/issues/21822005-09-06T16:44:57ZJohn Harrisharris@nceas.ucsb.edu
<p>The user should be able to click on a point (and maybe a polygon) with in the<br />map viewer and have the metdata be displayed for that selected element.</p> Bug #2181 (Resolved): Footprint based queryhttps://projects.ecoinformatics.org/ecoinfo/issues/21812005-09-06T16:43:32ZJohn Harrisharris@nceas.ucsb.edu
<p>Currently, there is no way to submit a query based on a selected region of a<br />map. We need to be able to draw a box (rubberband) as a query that should<br />return metacat result page.</p> Bug #2179 (Resolved): Fix harvesting script to get all points and boxeshttps://projects.ecoinformatics.org/ecoinfo/issues/21792005-09-06T16:25:53ZJohn Harrisharris@nceas.ucsb.edu
<p>Currently, the code that extracts spatial information from EML documents stored<br />in Metacat only grabs points and does not create polygons that better represent<br />the bounding boxes expressed in EML. Also, the code grabs the first of the<br />geographicCoverage sections, instead it should grab all.</p> Bug #2178 (Resolved): Evaluate java-based web mapping applinactionshttps://projects.ecoinformatics.org/ecoinfo/issues/21782005-09-06T15:55:15ZJohn Harrisharris@nceas.ucsb.edu
<p>Currently, Metacat works with MapServer <a class="external" href="http://mapserver.gis.umn.edu/">http://mapserver.gis.umn.edu/</a>, an<br />application that is used to display spatial elements stored in Metacat. To ease<br />the incorporation of a map server into Metacat, we should evaluate the map<br />servers that are implemented as java servlets. Requirements for these<br />mapservers are that they can read/write ESRI shapefiles and read raster data.</p>