Mercurial > dive4elements > river
comparison flys-artifacts/ChangeLog @ 1774:092e1e5020bc
Added a new MapGenerator which only returns a map configuration document at the moment (work still in progress).
flys-artifacts/trunk@3095 c6561f87-3c4e-4783-a992-168aeb5c3f6f
author | Ingo Weinzierl <ingo.weinzierl@intevation.de> |
---|---|
date | Fri, 28 Oct 2011 05:54:25 +0000 |
parents | 9be01e2e6897 |
children | 0156105222c9 |
comparison
equal
deleted
inserted
replaced
1773:9be01e2e6897 | 1774:092e1e5020bc |
---|---|
1 2011-10-28 Ingo Weinzierl <ingo@intevation.de> | |
2 | |
3 * src/main/java/de/intevation/flys/utils/GeometryUtils.java: Added new | |
4 method gerRiverBoundary() which returns an Envelope object (which | |
5 represents the bounding box of a Geometry) of a riveraxis specified by its | |
6 rivername. | |
7 | |
8 * src/main/java/de/intevation/flys/artifacts/states/RiverAxisState.java: Use | |
9 Geometry.getRiverBoundary() to determine the max extent of a river. | |
10 | |
11 * src/main/java/de/intevation/flys/wsplgen/FacetCreator.java, | |
12 src/main/java/de/intevation/flys/artifacts/model/WMSLayerFacet.java: Use | |
13 JTS Envelope to save the bounding boxes of WMS layers. | |
14 | |
15 * src/main/java/de/intevation/flys/artifacts/services/MapInfoService.java: | |
16 Adapted the code to apply the changes in GeometryUtils (use Envelope to | |
17 determine the max extent of the river axis). | |
18 | |
19 * src/main/java/de/intevation/flys/exports/MapGenerator.java: New (work in | |
20 progress). This Generator will currently return a map configuration in XML | |
21 which consists of parameters required by OpenLayers to create a map. | |
22 | |
23 * doc/conf/conf.xml: Registered the new MapGenerator. | |
24 | |
1 2011-10-27 Felix Wolfsteller <felix.wolfsteller@intevation.de> | 25 2011-10-27 Felix Wolfsteller <felix.wolfsteller@intevation.de> |
2 | 26 |
3 * doc/conf/meta-data.xml: Do not recommend historical data to load | 27 * doc/conf/meta-data.xml: Do not recommend historical data to load |
4 when having computational discharge curves. | 28 when having computational discharge curves. |
5 | 29 |