← Back to team overview

dhis2-devs team mailing list archive

Re: [Bug 1171229] Re: GML Import - organizationunit table, uid and uuid are not created

 

What this implies, is that you have to start by creating the orgunit
hierarchy, and then later match with geometries.

I usually start by building the hierarchy layer by layer downwards from the
.dbf files that are in the shapefiles, since then the matching will be
easier (however, one must pay attention to uniqueness of names/codes).

The process is a bit cumbersome, and indeed we did have a way to build the
whole hiearchy from well-structured WHO shapefiles a couple of years ago,
but this is not there currently (and did require files to be in that
specific format).

Knut


On Mon, Apr 22, 2013 at 7:13 AM, Lars Helge Øverland <larshelge@xxxxxxxxx>wrote:

> Hi Roshan, the gml import is not intended to import the relationships
> between org units, ie the hierarchy. Its a good idea to do so, but not a
> bug...
>
> Lars
> On Apr 22, 2013 5:40 AM, "jason.p.pickering" <1171229@xxxxxxxxxxxxxxxxxx>
> wrote:
>
>> You must access the "Organisation unit level" dialog to generate the new
>> levels.
>>
>> UIDs, UUIDs are generated upon restarting the server.
>>
>> If you use DXF2 instead of GML, you can prepopulate the XML with uids
>> and uuids, so that they are imported into the system, and therefore do
>> not need to be regenerated on startup.
>>
>> Not really so sure this is a bug?
>>
>> --
>> You received this bug notification because you are a member of DHIS 2
>> developers, which is subscribed to DHIS.
>> https://bugs.launchpad.net/bugs/1171229
>>
>> Title:
>>   GML Import - organizationunit table, uid and uuid are not created
>>
>> Status in DHIS 2 - District Health Information Software:
>>   New
>>
>> Bug description:
>>   Version:
>>       2.11
>>   Build revision:
>>       10480
>>   Build date:
>>       2013-04-21 18:06
>>
>>   When GML Import function is attempted a flat organization hiararchy is
>> created.
>>   Appropriate organization level is not created in orgunitlevel table.
>>   So, in Hiarachi Operations, 'Select the new parent organisation unit
>> for the one to move' is disabled.
>>
>>   Also, organisationunit table has no uid, uuid etc.
>>   Coordinates can not be regtrieved by GIS map.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/dhis2/+bug/1171229/+subscriptions
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
http://dhis2.org

Follow ups

References