https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362006-07-24T21:37:12ZEcoinformatics RedmineMetacat - Bug #2180: Make it easier for admin to add new layershttps://projects.ecoinformatics.org/ecoinfo/issues/2180?journal_id=74492006-07-24T21:37:12ZMatthew Perryperry@nceas.ucsb.edu
<ul></ul><p>Just for reference, here are the general steps to configure a layer to be displayed in our web map. Each step varies in ease of automation/webification:</p>
<p>1. Upload the data to the server. This can be handled through metacat.</p>
<p>2. Configure the data store (paths, geographic projection, format, etc). This is best handled by Geoserver as they have already worked out an excellent interface for this step. This tells the WMS server how to <strong>access</strong> your data</p>
<p>3. Create that styles and classification filters. These are created using OGC standard SLD documents. Geoserver lacks a sophisticated editor for these docs.</p>
<p>4. Associate your data store with the styles and filters. Essentially this tells the WMS server how to <strong>style</strong> your data creating a "featuretype". Again geoserver handles this quite well already.</p>
<p>5. Once the feature type has been configured, it has to be added to your Web Map context (WMC) document which tells the web client how to request your data. There are now good interfaces (other than a text editor) for adding entries to a WMC.</p>
<p>Since geoserver already does so much of this so well, I would vote for keeping 2-4 in the geoserver web admin interface (perhaps contributing to the enhancement of <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: some required elements should be optional (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/3">#3</a>). All layers that are configured properly in geoserver can then appear in a metcat web mapping admin interface to handle step <a class="issue tracker-1 status-5 priority-5 priority-highest closed" title="Bug: mde won't load because of hardcoded image paths (Closed)" href="https://projects.ecoinformatics.org/ecoinfo/issues/5">#5</a>.</p> Metacat - Bug #2180: Make it easier for admin to add new layershttps://projects.ecoinformatics.org/ecoinfo/issues/2180?journal_id=74502006-07-27T21:01:10ZMatthew Perryperry@nceas.ucsb.edu
<ul></ul><p>There are some parts of the geoserver admin page that can be improved upon. Namely alot of the information it prompts for can be determined through the metadata document (the epsg, title, keywords, abstract, geographic bounds, etc)</p> Metacat - Bug #2180: Make it easier for admin to add new layershttps://projects.ecoinformatics.org/ecoinfo/issues/2180?journal_id=74512011-01-28T20:25:35Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>It's true that Geoserver does all of this except including the new layer in a rendered map in Metacat.We could include a configuration step that allows and admin user to select which layers should appear for any given skin's map.</p> Metacat - Bug #2180: Make it easier for admin to add new layershttps://projects.ecoinformatics.org/ecoinfo/issues/2180?journal_id=74522013-03-27T21:19:23ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 2180</p>