bug #9124
Altitude feature should have [m] as measurement unit by default
100%
Description
This requires that measurement units are loaded before.
Update script needed
Related issues
Associated revisions
fix #9124 add meter to altitude (update script)
ref #9124 skip altitude adder if altitude feature does not yet exist
ref #9124 fix incorrect Altituded recommended measurement unit update script
ref #9124 fix taxeditor test H2
ref #9124 fix altitude recommended measurement units issue in vaadin
History
#1 Updated by Andreas Müller over 1 year ago
- Related to feature request #9043: Add feature "Altitude" added
#2 Updated by Andreas Müller about 1 year ago
- Priority changed from New to Highest
#3 Updated by Andreas Müller about 1 year ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
#4 Updated by Andreas Müller about 1 year ago
The first implementatin of the update script had a serious bug as it filled the table DefinedTermBase_StatisticalMeasure instead of DefinedTermBase_MeasurementUnit.
This is fixed and an update script for the wrong update is committed. The result can be checked by:
SELECT MN.feature_id, MN.recommendedstatisticalmeasures_id
FROM DefinedTermBase_StatisticalMeasure MN
INNER JOIN DefinedTermBase alt ON alt.id = MN.feature_id
INNER JOIN DefinedTermBase sm ON sm.id = MN.recommendedstatisticalmeasures_id
WHERE alt.uuid = '1a28ed59-e15f-4001-b5c2-ea89f0012671' AND sm.uuid = '8bef5055-789c-41e5-bea2-8dc2ea8ecdf6';
SELECT MN.REV, MN.feature_id, MN.recommendedstatisticalmeasures_id
FROM DefinedTermBase_StatisticalMeasure_AUD MN
INNER JOIN DefinedTermBase_AUD alt ON alt.id = MN.feature_id
INNER JOIN DefinedTermBase_AUD sm ON sm.id = MN.recommendedstatisticalmeasures_id
WHERE alt.uuid = '1a28ed59-e15f-4001-b5c2-ea89f0012671' AND sm.uuid = '8bef5055-789c-41e5-bea2-8dc2ea8ecdf6';
SELECT MN.feature_id, MN.recommendedmeasurementunits_id
FROM DefinedTermBase_MeasurementUnit MN
INNER JOIN DefinedTermBase alt ON alt.id = MN.feature_id
INNER JOIN DefinedTermBase sm ON sm.id = MN.recommendedmeasurementunits_id
WHERE alt.uuid = '1a28ed59-e15f-4001-b5c2-ea89f0012671' AND sm.uuid = '8bef5055-789c-41e5-bea2-8dc2ea8ecdf6';
SELECT MN.REV, MN.feature_id, MN.recommendedmeasurementunits_id
FROM DefinedTermBase_MeasurementUnit_AUD MN
INNER JOIN DefinedTermBase_AUD alt ON alt.id = MN.feature_id
INNER JOIN DefinedTermBase_AUD sm ON sm.id = MN.recommendedmeasurementunits_id
WHERE alt.uuid = '1a28ed59-e15f-4001-b5c2-ea89f0012671' AND sm.uuid = '8bef5055-789c-41e5-bea2-8dc2ea8ecdf6'
#5 Updated by Andreas Müller 11 months ago
- % Done changed from 50 to 90
I tested on test and integration. The result looks fine. But we should also run on production once after the release therefore I keep ticket open.
#6 Updated by Andreas Müller 11 months ago
- Target version changed from CDM UML 5.28 to Release 5.18
#7 Updated by Andreas Müller 11 months ago
- % Done changed from 90 to 100
I expect this to work so I close the ticket.
#8 Updated by Andreas Müller 11 months ago
- Status changed from Resolved to Closed
