view artifacts/doc/conf/rivermap.xml @ 8587:07c9ac22f611

(issue1755) Generalise BedQuality result handling The bedquality calculation now produces a result for each time period which has BedQualityResultValues for each specific result type. Formally this was split up in density, porosity and diameter classes with some bedload diameter classes mixed in for extra fun. The intent of this commit is to allow more shared code and generic access patterns to the BedQuality results.
author Andre Heinecke <andre.heinecke@intevation.de>
date Wed, 18 Mar 2015 18:42:08 +0100
parents 288ea098494c
children 308a0d822d18
line wrap: on
line source
<?xml version="1.0" encoding="UTF-8" ?>
<!--// configuration fragment for static river WMS //-->
<rivermap>
    <mapserver>
        <server path="http://localhost:8081/cgi-bin/"/>
        <mapfile path="${artifacts.config.dir}/../rivers.map"/>
        <templates path="${artifacts.config.dir}/mapserver/"/>
        <map-template path="river-mapfile.vm"/>
    </mapserver>

    <velocity>
        <logfile path="${artifacts.config.dir}/../rivermap_velocity.log"/>
    </velocity>

    <river name="Beispielfluss">
        <srid value="31467"/>
        <river-wms url="http://localhost:8081/cgi-bin/river-wms" layers="Beispielfluss"/>
        <background-wms url="http://osm.intevation.de/bfg/service?" layers="OSM-WMS-Dienst"/>
    </river>
</rivermap>

http://dive4elements.wald.intevation.org