Maps in DHIS2 2.33 migrating from DHIS 2.27 or 2.30

jgaf1980 · 23 December 2019 17:20

Hello Community,

We are trying to migrate either from 2.27 or 2.30 to the latest version 2.33, but we are having problems migrating the polygons for our maps. Apparently there is a different way to represent the maps, we have coordinates from our 2.30 version and now the way DHIS2 handles maps appears to be different. Anyone has a step by step process on how to do this migration?

Thanks.

Knut_Staring · 23 December 2019 18:57

I think you could just export the orgunits in the old instance and import them, which should update the missing coordinates. But have not yet tried it.

jgaf1980 · 23 December 2019 19:26

Thank you Knut, we tried exporting the OU from old version and import them in the new one, but no map appear just the OU tree. I believe it has something to do on how the new version handles the polygons

pablodelmedico · 6 February 2020 16:45

Hi Jose,
The change related to OU and coordinates is done in the version 2.32.

github.com

dhis2/dhis2-releases/blob/master/releases/2.32/README.md

# 2.32 Upgrade Notes

## System Administration
- The *Server base URL* system setting has changed from being a system setting to a `dhis.conf` property. This is done because the server base URL typically follows the server and not the database. The setting key is `server.base.url`. See install guide for details.
- Most metadata database tables now use *8-bit int* data type for the primary key column. This migration happens automatically. For the migration to succeed it is recommended to increase the PostgreSQL max locks per transaction setting such as `max_locks_per_transaction = 96`. See install guide for details. Note that this migration can take several hours, and that the database size may increase substantially during the process.
- For Tomcat versions after 8.5, it is necessary to include a `relaxedQueryChars="[]"` attribute to allow for brackets in URLs in the `Connector` element in `server.xml`. See install guide for details.

## Data model
- The (unused) association between `Program` and `DataApprovalWorkflow` is removed.
- The (unused) `representative` association between `TrackedEntityInstance` and `TrackedEntityInstance` is removed.
- A Geometry (`Geometry, 4326`) field `geometry` is added replacing the `coordinates` and `featuretype` fields for `OrganisationUnit`.
- A Geometry (`Geometry, 4326`) field `geometry` is added replacing the `coordinates` columns for `OrganisationUnitGroup`.

## Database
- The `trackedentitydatavalue` table has been replaced by a PostgreSQL JSONB object/column in the `programstageinstance` table. 

## System
- The *Event capture* app is removed. It is replaced by the *Capture* app which offers all of its features and more.

## Process

This file has been truncated. show original

A Geometry ( Geometry, 4326 ) field geometry is added replacing the coordinates and featuretype fields for OrganisationUnit .
A Geometry ( Geometry, 4326 ) field geometry is added replacing the coordinates columns for OrganisationUnitGroup .

So, I believe, you’ll need to re-import the polygons/coordinates in the new field geometry.

Good luck

Karoline · 13 March 2020 14:45

Hi @jgaf1980,

I am going to mark @pablodelmedico’s post as the solution here, hopefully it did help you too?

Best regards,
Karoline

jgaf1980 · 13 March 2020 16:47

Thank you all for your help, we did solve the problem.

Lots of appreciation

Knut_Staring · 15 March 2020 19:43

Just to share how I did this in another context (though there may be better ways), namely I exported coordinates by using .geojson as extension in the URL, then converted this to GML using ogr2ogr and used the GML importer. I can give more details if needed.