feat: support fallback coordinates in event layers [DHIS2-8165]
Implements:
- https://dhis2.atlassian.net/browse/DHIS2-8165
Requires:
- https://dhis2.atlassian.net/browse/DHIS2-13528
Description
Test datasets:
Alternative coordinates:
- Event coordinate
- Enrollment coordinate *
- Tracked entity coordinate *
- Program stage data elements of type coordinates
- Program tracked entity attributes of type coordinate *
* Only for programs with enrollment
Fallback mechanism:
- None
- Single coordinate
- Cascade: Enrollment > event > tracked entity > org unit coordinate
References:
Frontend:
- https://github.com/dhis2/maps-app/pull/2236
- https://github.com/dhis2/maps-app/pull/2575
Backend:
- https://github.com/dhis2/dhis2-core/pull/11384
- https://github.com/dhis2/dhis2-core/pull/11911
- https://github.com/dhis2/dhis2-core/pull/11934
- https://github.com/dhis2/dhis2-core/pull/13153
We are supporting these parameters:
coordinateField. We are supporting all previous type plus pigeometry, psigeometry, teigeometry and ougeometry. Do not forget that teigeometry is valid only for registration program,
fallbackCoordinateField: it is hard fallback. We are supporting “pigeometry“, “psigeometry“, “teigeometry“ and “ougeometry“ as well as data elements and tracked attributes. Do not forget that teigeometry is valid only for registration program,
defaultCoordinateFallback (true/false).
When fallbackCoordinateField is null and defaultCoordinateFallback is true (default), a cascade fallback is applied (pigeometry -> psigeometry -> teigeometry -> ougeometry)
TODO
- [ ] Dashboard tested
- [ ] Tests added (Cypress and/or Jest)
- [ ] Docs added
- [ ] Update dependencies to not point to d2-ci
- [ ] todo
Known issues
- [ ] issue
Screenshots
supporting images
🚀 Deployed on https://pr-3468.maps.netlify.dhis2.org