diff --git a/CHANGELOG.md b/CHANGELOG.md
index 87e7364ca..17cebf04b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,9 +4,68 @@ All notable changes to this project will be documented in this file. Dates are d
Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
+#### [v2.1.12](https://github.com/KomMonitor/web-client/compare/v2.1.11...v2.1.12)
+
+- implement prefilling of role based access data tables; prefilled with roles of currently loggid in user in order to guarantee that he/she has access rights [`00d9df3`](https://github.com/KomMonitor/web-client/commit/00d9df380d1e39f96d943f47cc095f5e5bcda8eb)
+- add version info for version 2.1.12 [`a2868f3`](https://github.com/KomMonitor/web-client/commit/a2868f3440ef11df13bc402316e26868722d9e8f)
+
+#### [v2.1.11](https://github.com/KomMonitor/web-client/compare/v2.1.10...v2.1.11)
+
+> 21 March 2023
+
+- fix issues with data grid tables where false datasets were opened after editing other datasets; fixes #40 [`#40`](https://github.com/KomMonitor/web-client/issues/40)
+- add version info for v.2.1.11 [`21a8b9a`](https://github.com/KomMonitor/web-client/commit/21a8b9ab70f984f3891f0f7bc3fd506dbb4414ed)
+- Release 2.1.11 [`94fd844`](https://github.com/KomMonitor/web-client/commit/94fd8446088dac9630fd6995ed270f21c814839c)
+
+#### [v2.1.10](https://github.com/KomMonitor/web-client/compare/v2.1.9...v2.1.10)
+
+> 20 March 2023
+
+- fix bug in points in polygon analysis causing found POI features to not be displayed on map; fixes #39 [`#39`](https://github.com/KomMonitor/web-client/issues/39)
+- add version info for v2.1.10 [`798da1e`](https://github.com/KomMonitor/web-client/commit/798da1e7b3f929728533ab187dbc70d2aa91a8a1)
+- Release 2.1.10 [`450e94d`](https://github.com/KomMonitor/web-client/commit/450e94d9f3384bbdc64173e40f38b0b82aa823df)
+
+#### [v2.1.9](https://github.com/KomMonitor/web-client/compare/v2.1.8...v2.1.9)
+
+> 20 March 2023
+
+- fix georesource export due to additional / in path to logo; fixes #36 [`#36`](https://github.com/KomMonitor/web-client/issues/36)
+- fix various field issues with batch update wrt converter encoding and mimeType not being processed properly; fixes #38 [`#38`](https://github.com/KomMonitor/web-client/issues/38)
+- add version info for v 2.1.9 [`77015d5`](https://github.com/KomMonitor/web-client/commit/77015d5676df340bb0ac835b9e824d47a354781d)
+- Release 2.1.9 [`973a987`](https://github.com/KomMonitor/web-client/commit/973a987f4e6742d35ecb951c4506402d675af72a)
+
+#### [v2.1.8](https://github.com/KomMonitor/web-client/compare/v2.1.7...v2.1.8)
+
+> 5 March 2023
+
+- fix bug in regression diagram when x and y axis have different number of displayable features, fixes #37 [`#37`](https://github.com/KomMonitor/web-client/issues/37)
+- add version info for v 2.1.8 [`c432aef`](https://github.com/KomMonitor/web-client/commit/c432aef8854bb3fb4defddf5f406ec428f4bb889)
+- Release 2.1.8 [`6d4e1aa`](https://github.com/KomMonitor/web-client/commit/6d4e1aae9a89e111d852f7340b1dfb5b9c52d230)
+
+#### [v2.1.7](https://github.com/KomMonitor/web-client/compare/v2.1.6...v2.1.7)
+
+> 2 March 2023
+
+- fix bug where admin data tables did not show up when switching between admin and map interface while staying logged in, fixes #35 [`#35`](https://github.com/KomMonitor/web-client/issues/35)
+- fix bug in batch update where HTTP URL field and INLINE PAYLOAD fields where not properly taken into account when exporting batch list and performing batch update itself, fixes #34 [`#34`](https://github.com/KomMonitor/web-client/issues/34)
+- apply version info for version 2.1.7 [`60f0cb9`](https://github.com/KomMonitor/web-client/commit/60f0cb934049edabe5aa60ae24c42eaa811de09f)
+- prevent loading screen of regression and radar charts to overlap other sidebar content and thus allow menu clicking [`db4431f`](https://github.com/KomMonitor/web-client/commit/db4431f39133d119ff77330157603df2606ea5a6)
+- ensure collapse trigger logic for georesources topic hierarchy [`64e0faf`](https://github.com/KomMonitor/web-client/commit/64e0faf79c1b578aad33c3d6a93416fc7cb0660c)
+
+#### [v2.1.6](https://github.com/KomMonitor/web-client/compare/v2.1.5...v2.1.6)
+
+> 6 February 2023
+
+- update package-lock [`5b9486b`](https://github.com/KomMonitor/web-client/commit/5b9486b8cdcfbd010e8b6ae9b2b9b4c5412911af)
+- improve spatial unit fitler and also improve visuals [`a0d496f`](https://github.com/KomMonitor/web-client/commit/a0d496fc66fc624bf0ab74554204d61657cb2ed2)
+- add version info for v 2.1.6 [`1d10d73`](https://github.com/KomMonitor/web-client/commit/1d10d7306961c8107e01e126d64adc46a282e2db)
+
#### [v2.1.5](https://github.com/KomMonitor/web-client/compare/v2.1.4...v2.1.5)
+> 21 November 2022
+
- add version info 2.1.5 [`79255ad`](https://github.com/KomMonitor/web-client/commit/79255ade5c0ff7a946749e1bb2b9619361bed8f2)
+- Release 2.1.5 [`95e32d1`](https://github.com/KomMonitor/web-client/commit/95e32d1241dfa39858d614d375e9672053bd1b64)
- when renaming spatial units ensure that indicator metadata is fetched as well, as joins between indicators and spatial units may have been modified [`7419534`](https://github.com/KomMonitor/web-client/commit/741953473460831212f135cc9b6794b63d506479)
#### [v2.1.4](https://github.com/KomMonitor/web-client/compare/v2.1.3...v2.1.4)
diff --git a/Gruntfile.js b/Gruntfile.js
index e4e2bea81..c1f2f9708 100644
--- a/Gruntfile.js
+++ b/Gruntfile.js
@@ -192,7 +192,8 @@ module.exports = function (grunt) {
'icons/**/*',
'logos/**/*',
'components/**/*.template.html',
- 'config/**/*'
+ 'config/**/*',
+ 'favicon.ico'
],
// babel: {
diff --git a/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceAddModal/georesource-add-modal.component.js b/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceAddModal/georesource-add-modal.component.js
index 57f174330..2fbe041b2 100644
--- a/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceAddModal/georesource-add-modal.component.js
+++ b/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceAddModal/georesource-add-modal.component.js
@@ -112,7 +112,7 @@ angular.module('georesourceAddModal').component('georesourceAddModal', {
});
function refreshRoles() {
- $scope.roleManagementTableOptions = kommonitorDataGridHelperService.buildRoleManagementGrid('georesourceAddRoleManagementTable', $scope.roleManagementTableOptions, kommonitorDataExchangeService.accessControl, null);
+ $scope.roleManagementTableOptions = kommonitorDataGridHelperService.buildRoleManagementGrid('georesourceAddRoleManagementTable', $scope.roleManagementTableOptions, kommonitorDataExchangeService.accessControl, kommonitorDataExchangeService.getCurrentKomMonitorLoginRoleIds());
}
$scope.georesourceTopic_mainTopic = undefined;
diff --git a/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceBatchUpdateModal/georesource-batch-update-modal.template.html b/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceBatchUpdateModal/georesource-batch-update-modal.template.html
index feec46a63..a8c9a6711 100644
--- a/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceBatchUpdateModal/georesource-batch-update-modal.template.html
+++ b/app/components/kommonitorAdmin/adminGeoresourcesManagement/georesourceBatchUpdateModal/georesource-batch-update-modal.template.html
@@ -35,6 +35,7 @@
Wichtige Informationen zu KomMonitor - Version 2.1.5
+
Wichtige Informationen zu KomMonitor - Version 2.1.12
diff --git a/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.component.js b/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.component.js
index fe90b74c4..39a8ea4fb 100644
--- a/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.component.js
+++ b/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.component.js
@@ -20,6 +20,9 @@ angular
// initialize any adminLTE box widgets
$('.box').boxWidget();
+ $scope.considerAllowedSpatialUnitsOfCurrentIndicator = true;
+ $scope.loadingData = false;
+
$scope.rangeSliderForFilter;
$scope.valueRangeMinValue;
$scope.valueRangeMaxValue;
@@ -59,21 +62,46 @@ angular
};
- $scope.setupSpatialUnitFilter = function(indicatorMetadataAndGeoJSON, spatialUnitName, date){
+ $scope.setupSpatialUnitFilter = function(indicatorMetadataAndGeoJSON, spatialUnitName, date){
+
+ $scope.loadingData = true;
+
+ let allowedSpatialUnitIds = indicatorMetadataAndGeoJSON.applicableSpatialUnits.map(spatialUnitEntry => {
+ return spatialUnitEntry.spatialUnitId;
+ });
$scope.higherSpatialUnits = JSON.parse(JSON.stringify(kommonitorDataExchangeService.availableSpatialUnits));
- let targetIndex = 0;
+
+ // only show those spatial units that are actually visible according to keycloak role
+ // and associated to the current indicator as well
for (let index = 0; index < $scope.higherSpatialUnits.length; index++) {
const spatialUnitMetadata = $scope.higherSpatialUnits[index];
- if(spatialUnitMetadata.spatialUnitLevel == spatialUnitName){
- targetIndex = index;
+ // remove if it is not applicable for current indicator OR
+ // remove if it is the currently displayed spatial unit to show only hierarchically higher spatial units
+ if($scope.considerAllowedSpatialUnitsOfCurrentIndicator && ! allowedSpatialUnitIds.includes(spatialUnitMetadata.spatialUnitId)){
+
+ // only remove the current element
+ // which represents a spatial unit that is
+ // not supported by the current indicator
+ $scope.higherSpatialUnits.splice(index, 1);
+ }
+
+ // since we query through a hierarchically sorted array of ALL spatial units
+ // we have to stop when we identify the currently displayed spatial unit
+ // in that case we have to remove that from the list of upper
+ if (spatialUnitName == spatialUnitMetadata.spatialUnitLevel){
+ // remove current all all remaining elements from array
+ // (which are lower hierarchy spatial units)
+ $scope.higherSpatialUnits.splice(index);
break;
}
}
- $scope.higherSpatialUnits.splice(targetIndex);
+ // $scope.higherSpatialUnits.splice(targetIndex);
$scope.selectedSpatialUnitForFilter = $scope.higherSpatialUnits[$scope.higherSpatialUnits.length - 1];
+
+ $scope.loadingData = false;
};
$scope.inputNotValid = false;
@@ -395,12 +423,20 @@ angular
};
$scope.updateSelectableAreas = async function(selectionType) {
+ $scope.loadingData = true;
//send request to datamanagement API
let selectedSpatialUnit = kommonitorDataExchangeService.selectedSpatialUnit;
let selectedSpatialUnitId = selectedSpatialUnit.spatialUnitId;
- let upperSpatialUnitId;
- if (selectionType === "byFeature") {
- upperSpatialUnitId = $scope.selectedSpatialUnitForFilter.spatialUnitId;
+ let upperSpatialUnitId = undefined;
+
+ // spatial filter not applicable since no upper spatial unit is available or selected
+ if(! $scope.selectedSpatialUnitForFilter){
+ $scope.loadingData = false;
+ return;
+ }
+
+ if (selectionType === "byFeature" && $scope.selectedSpatialUnitForFilter) {
+ upperSpatialUnitId = $scope.selectedSpatialUnitForFilter.spatialUnitId;
}
let selectedIndicatorId = kommonitorDataExchangeService.selectedIndicator.indicatorId;
@@ -443,6 +479,8 @@ angular
let dataArray = kommonitorDataExchangeService.createDualListInputArray(areaNames, "name", "id");
$scope.selectionByFeatureSpatialFilterDuallistOptions.items = dataArray;
}
+ $scope.loadingData = false;
+ $scope.$digest();
});
};
diff --git a/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.template.html b/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.template.html
index ef654a3f4..2af32716b 100644
--- a/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.template.html
+++ b/app/components/kommonitorUserInterface/kommonitorControls/kommonitorFilter/kommonitor-filter.template.html
@@ -121,17 +121,44 @@
Wähle untergeordnete Raumeinheiten innerhalb der selektierten Raumeinheit
-
+
-
+
+
+
+
+
+
+
+
+
+
Auswahl bei derzeitig visualisierter Raumebene nicht möglich - keine übergeordneten Raumebenen vorhanden
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Wähle untergeordnete Raumeinheiten innerhalb der selektierten RaumeinheitSelektion zurücksetzen
-
Manuelle Selektion anzuzeigender Features
diff --git a/app/components/kommonitorUserInterface/kommonitorControls/kommonitorReachability/kommonitor-reachability.component.js b/app/components/kommonitorUserInterface/kommonitorControls/kommonitorReachability/kommonitor-reachability.component.js
index 646065087..9a304a710 100644
--- a/app/components/kommonitorUserInterface/kommonitorControls/kommonitorReachability/kommonitor-reachability.component.js
+++ b/app/components/kommonitorUserInterface/kommonitorControls/kommonitorReachability/kommonitor-reachability.component.js
@@ -1479,7 +1479,8 @@ angular
nextKey = keyIter.next();
}
- poi.geoJSON = pointsPerIsochroneRangeMap.get(largestRange);
+ // map stores keys as string
+ poi.geoJSON = pointsPerIsochroneRangeMap.get("" + largestRange);
return poi;
}
@@ -1528,7 +1529,7 @@ angular
var map = new Map();
for (const feature of $scope.currentIsochronesGeoJSON.features) {
- map.set(feature.properties.value, null);
+ map.set("" + feature.properties.value, null);
}
return map;
diff --git a/app/components/kommonitorUserInterface/kommonitorControls/poi/poi.component.js b/app/components/kommonitorUserInterface/kommonitorControls/poi/poi.component.js
index a0f41a8b2..f36b97055 100644
--- a/app/components/kommonitorUserInterface/kommonitorControls/poi/poi.component.js
+++ b/app/components/kommonitorUserInterface/kommonitorControls/poi/poi.component.js
@@ -65,6 +65,31 @@ angular
// });
}, 3000);
+ var addClickListenerToEachCollapseTrigger = function(){
+ setTimeout(function(){
+ $('.list-group-item > .collapseTrigger').on('click', function() {
+ $('.glyphicon', this)
+ .toggleClass('glyphicon-chevron-right')
+ .toggleClass('glyphicon-chevron-down');
+
+ // manage uncollapsed entries
+ // var clickedTopicId = $(this).attr('id');
+ // if ($scope.unCollapsedTopicIds.includes(clickedTopicId)){
+ // var index = $scope.unCollapsedTopicIds.indexOf(clickedTopicId);
+ // $scope.unCollapsedTopicIds.splice(index, 1);
+ // }
+ // else{
+ // $scope.unCollapsedTopicIds.push(clickedTopicId);
+ // }
+ });
+ }, 500);
+ };
+
+ $(document).ready(function() {
+
+ addClickListenerToEachCollapseTrigger();
+ });
+
$scope.onChangeShowPOI = function(){
if ($scope.showPOI){
$scope.showPOI = false;
diff --git a/app/components/kommonitorUserInterface/kommonitorControls/regressionDiagram/regression-diagram.component.js b/app/components/kommonitorUserInterface/kommonitorControls/regressionDiagram/regression-diagram.component.js
index 1b66ad374..7418e3107 100644
--- a/app/components/kommonitorUserInterface/kommonitorControls/regressionDiagram/regression-diagram.component.js
+++ b/app/components/kommonitorUserInterface/kommonitorControls/regressionDiagram/regression-diagram.component.js
@@ -56,7 +56,7 @@ angular
const defaultBorderColorForOutliers_low = __env.defaultBorderColorForOutliers_low;
const defaultFillOpacityForOutliers_low = __env.defaultFillOpacityForOutliers_low;
- $scope.setupCompleted = false;
+ $scope.setupCompleted = true;
//$scope.allIndicatorProperties;
$scope.selection.selectedIndicatorForXAxis;
@@ -98,6 +98,18 @@ angular
var wait = ms => new Promise((r, j)=>setTimeout(r, ms));
+ $scope.$on("allIndicatorPropertiesForCurrentSpatialUnitAndTime setup begin", async function (event) {
+
+ await wait(130);
+ $scope.setupCompleted = false;
+
+
+ $timeout(function(){
+ $scope.$digest();
+ }, 500);
+
+ });
+
$scope.$on("allIndicatorPropertiesForCurrentSpatialUnitAndTime setup completed", async function (event) {
await wait(100);
@@ -300,6 +312,42 @@ angular
return color;
};
+ function mapRegressionData(indicatorPropertiesArray, timestamp, map, axisValueName){
+
+ for (const indicatorPropertiesEntry of indicatorPropertiesArray) {
+ let featureName = indicatorPropertiesEntry[__env.FEATURE_NAME_PROPERTY_NAME];
+ let indicatorValue;
+
+ if (kommonitorDataExchangeService.indicatorValueIsNoData(indicatorPropertiesEntry[DATE_PREFIX + timestamp])){
+ indicatorValue = null;
+ }
+ else{
+ indicatorValue = kommonitorDataExchangeService.getIndicatorValue_asNumber(indicatorPropertiesEntry[DATE_PREFIX + timestamp]);
+ }
+
+ if(map.has(featureName)){
+ let oldObject = map.get(featureName);
+ oldObject[axisValueName] = indicatorValue;
+ map.set(featureName, oldObject);
+ }
+ else{
+ let color = getColor(featureName);
+ let regressionObject = {
+ name: featureName,
+ itemStyle: {
+ color: color
+ }
+ };
+
+ regressionObject[axisValueName] = indicatorValue;
+ map.set(featureName, regressionObject);
+ }
+
+ }
+
+ return map;
+ }
+
$scope.buildDataArrayForSelectedIndicators = async function(){
$scope.data = new Array();
$scope.dataWithLabels = new Array();
@@ -316,38 +364,43 @@ angular
var timestamp_xAxis = $scope.selection.selectedIndicatorForXAxis.selectedDate;
var timestamp_yAxis = $scope.selection.selectedIndicatorForYAxis.selectedDate;
- for (var i=0; i cope with that and only preserve those result objects that have both timestamp values
+ for x and y axis
+ */
+
+ // store data in a map to check above prerequesits
+ // key = ID,
+ // value = regressionObject = {
+ // name: featureName,
+ // itemStyle: {
+ // color: color
+ // },
+ // xAxisName: indicatorValue_x,
+ // yAxisName: indicatorValue_y
+ //}
+ let xAxisName = "xValue";
+ let yAxisName = "yValue";
+ let dataCandidateMap = mapRegressionData(indicatorPropertiesArrayForXAxis, timestamp_xAxis, new Map(), xAxisName);
+ dataCandidateMap = mapRegressionData(indicatorPropertiesArrayForYAxis, timestamp_yAxis, dataCandidateMap, yAxisName);
+
+ // now iterate over map and identify those objects that have both indicator axis values set
+ // put those into resulting lists
+
+ dataCandidateMap.forEach(function(regressionObject, key, map){
+ // $scope.data.push([xAxisDataElement, yAxisDataElement])
+ if (regressionObject[xAxisName] && regressionObject[yAxisName]){
+ $scope.data.push([regressionObject[xAxisName], regressionObject[yAxisName]]);
+
+ regressionObject.value = [regressionObject[xAxisName], regressionObject[yAxisName]];
+
+ $scope.dataWithLabels.push(
+ regressionObject
+ );
}
-
- if (kommonitorDataExchangeService.indicatorValueIsNoData(indicatorPropertiesArrayForYAxis[i][DATE_PREFIX + timestamp_yAxis])){
- yAxisDataElement = null;
- }
- else{
- yAxisDataElement = kommonitorDataExchangeService.getIndicatorValue_asNumber(indicatorPropertiesArrayForYAxis[i][DATE_PREFIX + timestamp_yAxis]);
- }
-
- $scope.data.push([xAxisDataElement, yAxisDataElement]);
-
- var featureName = indicatorPropertiesArrayForXAxis[i][__env.FEATURE_NAME_PROPERTY_NAME];
- var color = getColor(featureName);
- $scope.dataWithLabels.push({
- name: featureName,
- value: [xAxisDataElement, yAxisDataElement],
- itemStyle: {
- color: color
- }
- });
- }
+ });
return $scope.data;
};
diff --git a/app/components/kommonitorUserInterface/kommonitorControls/versionInfo/version-info.template.html b/app/components/kommonitorUserInterface/kommonitorControls/versionInfo/version-info.template.html
index 09f669e96..19badb8bd 100644
--- a/app/components/kommonitorUserInterface/kommonitorControls/versionInfo/version-info.template.html
+++ b/app/components/kommonitorUserInterface/kommonitorControls/versionInfo/version-info.template.html
@@ -1,5 +1,280 @@
+
+
+
+
Neuerungen in KomMonitor V2.1.12
+
+
+
+
+
+
+
+
+ Anpassungen in der Admin-Ansicht
+
+
+ Zugriffsschutz beim Anlegen neuer Ressourcen
+
+ Beim Anlegen neuer Ressourcen werden nun standardmäßig die Rollen des eingeloggten Nutzers verwendet,
+ um die daraus verknüpften Organisationen und Rechtestufen vorauszufüllen.
+ Dies stellt sicher, dass eingeloggte User den Zugriff auf die Ressource bekommen.
+
+
+
+
+ Anpassungen in der Kartenapp
+
+
+ keine
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Neuerungen in KomMonitor V2.1.11
+
+
+
+
+
+
+
+
+ Anpassungen in der Admin-Ansicht
+
+
+ Fehlerbehebung bei Datenverwaltungstabellen
+
+ Bei der Editierung von Ressourcen wurde ein Problem behoben, das falsche Datensätze geöffnet wurden, nachdem einzelne Datenzeilen editiert wurden.
+
+
+
+
+
+ Anpassungen in der Kartenapp
+
+
+ keine
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Neuerungen in KomMonitor V2.1.10
+
+
+
+
+
+
+
+
+
+ Anpassungen in der Admin-Ansicht
+
+
+ keine
+
+
+
+
+
+ Anpassungen in der Kartenapp
+
+
+ Punktobjekte im Einzugsgebiet
+
+ Die Analyse Punktobjekte im Einzugsgebiet als nachgelagerte Operation einer Erreichbarkeitsanalyse stellt nun wieder
+ die gefundenen Punktobjekte richtig auf der Karte dar.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Neuerungen in KomMonitor V2.1.9
+
+
+
+
+
+
+
+
+
+ Anpassungen in der Admin-Ansicht
+
+
+ Fehlerbehebung in Batch-Update Funktionen
+
+ Die Parameter Encoding und Quellformat im Batch Update Menü wurden fehlerhaft exportiert und weiterverarbeitet.
+ Beide Probleme wurden nun behoben.
+
+
+
+
+ Anpassungen in der Kartenapp
+
+
+ Export von Georessourcen
+
+ EIn Fehler wurde behoben, der den Export von Georessourcen verhinderte.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Neuerungen in KomMonitor V2.1.8
+
+
+
+
+
+
+
+
+
+ Anpassungen in der Admin-Ansicht
+
+
+ keine
+
+
+
+
+ Anpassungen in der Kartenapp
+
+
+ Fehlerbehbung im Regressionsdiagramm
+
+ Haben Indikatoren auf der X- und Y-Achse des Regressionsdiagramms eine unterschiedliche Anzahl darstellbarer Raumobjekte,
+ so werden diese nun korrekt verarbeitet und das Diagramm dargestellt.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Neuerungen in KomMonitor V2.1.7
+
+
+
+
+
+
+
+
+
+ Anpassungen in der Admin-Ansicht
+
+
+ Fehlerbehbung im Batch Update von Indikatoren und Georessourcen
+
+ Datensätze via HTTP URL oder als INLINE PAYLOAD werden nun korrekt verarbeitet und exportiert.
+
+
+ Laden aller Datentabellen sichergestellt
+
+ Im eingeloggten Zustand wird nun beim Wechsel zwischen Kartenapp und Administrator-Oberfläche nun sichergestellt,
+ dass die Datentabellen zur Verwaltung der Ressourcen korrekt geladen werden.
+
+
+
+
+ Anpassungen in der Kartenapp
+
+
+ Anwendung kann nun bedient werden, auch wenn noch kein Indikator geladen werden kann
+ Die linksseitigen Menüs sind nun bedienbar, auch wenn noch kein Indikator-Datensatz dargestellt werden kann (insbesondere Georessourcen-Menü).
+ (Indikatorenbezogene Menüs erlauben dennoch keine sinnvolle Interaktion, da keine Daten verfügbar sind)
+
+
+ Fehlerbehbung bei Datenexporten, wenn die KomMonitor-URL einen Kontextpfad enthält
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Neuerungen in KomMonitor V2.1.6
+
+
+
+
+
+
+
+
+
+ räumliche Filter können nun dahingehend konfiguriert werden, ob alle verfügbaren hierarchisch
+ höheren Raumeinheiten angezeigt werden, oder nur solche, die für den derzeitigen Indikator gültig sind.
+
+
+ bei räumlichen Filtern wird nun ein Ladebildschirm angezeigt, sobald die Raumeinheit selektiert wird, um die Augenblicke
+ zu überbrücken, die das Laden der möglichen Feature-Namen beansprucht.
+