view artifacts/doc/conf/rivermap.xml @ 8755:30b1ddadf275

(issue1801) Unify reference gauge finding code The basic way as described in the method comment of the determineRefGauge method is now used in the WINFOArtifact, MainValuesService and RiverUtils.getGauge method. RiverUtils.getGauge previously just returned the first gauge found. While this is now a behavior change I believe that it is always more correct then the undeterministic behavior of the previous implmenentation.
author Andre Heinecke <andre.heinecke@intevation.de>
date Wed, 24 Jun 2015 14:07:26 +0200
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