We should probably add validation of coordinates vis a vis the parent
coordinates (given that we have parent coordinates...otherwise perhaps
grandparent etc.). It would probably be quickest now to do this on the
client, though in the longer term we might want to add GIS Java
libraries such as
While on unexplainable reasons, the 2.5 release had a few serious bugs
which have been fixed:
- DHIS represents coordinates as longitude/latitude pairs. The add and
update organisation unit screen had gotten it wrong and saved
coordinates the other way around.
- Data visualizer module did not
2 matches
Mail list logo
