dhis2-devs team mailing list archive

[Sergio Valenzuela <sergio.valenzuela@xxxxxxxx>]

Hi Lars,

I was about to answer Jason explaining use cases, but with your last
message all my questions are now solved.

First of all, I was wrong with the thematic layer issue, I thought you were
basing the thematic mapping on event coordinates so I thought that in order
to render the (for example) number of malaria diagnosis for each district I
had to force the clerks to introduce event coordinates for each event they
registered, otherwise the events would not count on the aggregation. I
understand that it is the same for the Facility Layer, right? The program
indicators appearing for each facility are aggregated with the facility
coordinates, not the event coordinates.

And for the clustering of events It makes total sense to me the blueprint
you just have created. This is what I was asking for in the first place. An
example for this, is that we want to create a map with the number of deaths
clustered at different levels (province, district, facility ...), so with
this new option we won't need to capture coordinates for each event
separately.

Thanks for your help,


*Sergio Valenzuela*
Fundación EHAS
Telemedicina para países en desarrollo -* www.ehas.org
<http://www.ehas.org/>*
E.T.S.I. de Telecomunicación A.101-9L. Ciudad Universitaria 30, 28040
Madrid - España
Tlfno. (+34) 91 488 87 41: (+34) 687 67 17 62



2016-05-23 12:44 GMT+02:00 Lars Helge Øverland <lars@xxxxxxxxx>:

> Hi Sergio,
>
> thanks for raising this.
>
> For the GIS app, we do in fact not base the thematic mapping on event
> coordinates at all. In later versions you can render aggregated data from
> program-based data elements as thematic layers, however that aggregation is
> based on the org unit (e.g. facility) of the events, not the coordinates.
>
>
> [image: Inline image 1]
>
>
> However, for the event layer, we do of course render events based on the
> event coordinates. We have been thinking about supporting a an option in
> GIS where you could base the clustering on the coordinate of the org unit
> (facility) instead of the event itself. This makes sense and will not be
> very hard to do. Blueprint for 2.25 here:
>
>
> https://blueprints.launchpad.net/dhis2/+spec/event-analytics-clustering-based-on-org-unit-coordinates
>
> Note that in my mind this really only makes sense for clustering of events
> - for rendering of non-clustered events, you will basically end up with one
> single point hiding a large number of points at the location of the
> facility ;)
>
> Let me know if this makes sense to you.
>
> best regards,
>
> Lars
>
>
>
>
>
>
>
> On Mon, May 23, 2016 at 12:18 PM, Sergio Valenzuela <
> sergio.valenzuela@xxxxxxxx> wrote:
>
>> Hi devs,
>>
>> Using *GIS app* you need to have coordinates on each event most of the
>> time in order to use* Thematic Layer and/or Event Layer* on maps and in
>> the case we consider all the events take place at the facility where the
>> events get registered, It would be helpful for the clerks who introduce the
>> events data into the system to not have to introduce the same coordinates
>> over and over for each patient they register. So my question is, is there
>> any way (maybe using custom forms??) to make the facility coordinates as a
>> default value for the event coordinates?
>>
>> Any suggestion to achieve this will be appreciated.
>>
>> Regards.
>>
>>
>> *Sergio Valenzuela*
>> Fundación EHAS
>> Telemedicina para países en desarrollo -* www.ehas.org
>> <http://www.ehas.org/>*
>> E.T.S.I. de Telecomunicación A.101-9L. Ciudad Universitaria 30, 28040
>> Madrid - España
>> Tlfno. (+34) 91 488 87 41: (+34) 687 67 17 62
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> lars@xxxxxxxxx
> http://www.dhis2.org <https://www.dhis2.org/>
>
>