Re: [Dhis2-users] Update Category option combination

[Ifeanyi Okoye]

Dear Djibril,I actually don't think the issues are different. In our own case, 
we renamed category options but when you get to the form designer, what is 
showing up is the old name. Running maintenance did not help. Running data 
integrity showed that the changes made to some of the category option 
combinations did not take effect and we had to recreate all the ones that did 
not take effect.However, it wasn't until we removed the data element that had 
the category option combo (that wasn't changing) from the dataset, and then 
added it back, did the changes take effect. Not sure why this is happening, but 
give it a try and see what happens.

Warm Regards, 

Ifeanyi

Read DrMaestro's Blog
www.ifeanyiokoye.com
 

On Tuesday, November 28, 2017, 4:57:03 PM GMT+1, Djibril Dione 
 wrote:  
 
 Thanks Ifeanyi for the update.Our issue is a bit different here all is 
populating well on Data entry and people are capturing data. just that the 
category option combination names are not updated with the correct and we use 
those name in a complex completeness report script. 
Test step On Sierra Leon 2.27   
   -  I have renamed the dataelementcategoryoption "Improve access to clean 
water" to "IACW"
   -  then go to administration app > maintenance > select "Update category 
option combinations"  and click "perform maintenance".
   -  then I go to category option combination under maintenance (metadata) and 
search for "IACW" and could not find it but when you search for "Improve access 
to clean water" you get many that pop in. i.e: "AIDSRelief Consortium, Improve 
access to clean water" which supposes to be renamed to "AIDSRelief Consortium, 
IACW"
   - I create a sqlView that search on the categoryoptioncombo Table and I got 
the same result as the front end
so whenever you rename a categoryoption I believe that the category option 
combination name should also reflect the new name once an Update category 
option combinations is performed
On Tue, Nov 28, 2017 at 5:03 PM, Ifeanyi Okoye  wrote:

Just an update on this. 
Everything I tried initially did not work. I then went to the dataset editor 
window to remove the problematic data elements and once I filtered them, I 
found that each one of them had in parenthesis at the end of the name of the 
data element, the category option combo that was causing the issue. Once I 
removed and put it back, the issue was resolved.
I hope this helps somebody.
Thank you.

Warm Regards, 

Ifeanyi

Read DrMaestro's Blog
www.ifeanyiokoye.com
 

On Monday, November 27, 2017, 10:04:23 AM GMT+1, Ifeanyi Okoye 
 wrote:  
 
 Hello Lars,This is similar to the issue I raised on this platform last week.
What I noticed is that some data elements will carry the old category option 
combo even after it has been changed or updated. This affects the form designer 
and section forms. In our own case, everything refused to update. I ran 
maintenance severally with no effect whatsoever. 
I am posting the thread below as only one person weighed in on this:
Thread:

Hello Laura,Thank you for your response.
We are currently running the 22nd Nov (dbf5f18) build of version 2.27 which we 
upgraded to on Thursday, this past week but the issue is still persisting.
I have recreated the category option combination and applied it to the data 
element but the same issue is still persisting. When I do a metadata export 
from the API, the missing categories are not on the list. It is as though DHIS 
does not even create them for whatever reason.
I don't know if anyone can provide some insight on what we could do to fix this 
since upgrading did not help.
It's affecting our roll out plans.
Thank you once again.

Warm Regards, 

Ifeanyi

Read DrMaestro's Blog
www.ifeanyiokoye.com


On Tuesday, November 21, 2017, 10:21:58 PM GMT+1, Laura E. Lincks 
 wrote:

You may want to upgrade to the latest build. We had a similar problem with 2.27 
(on a build from August) and we just upgraded this very minute to the latest 
build 37edfc2 (Nov 8, 2017) and the problem appears fixed.

Laura E. Lincks
Database Manager/Developer
ICAP - Columbia University
Mailman School of Public Health
60 Haven Ave, Floor B1
New York, NY 10032
Tel: 212 304 7132


On Mon, Nov 20, 2017 at 1:13 PM, Ifeanyi Okoye   wrote:

Hello All,We are encountering this issue with the form designer where either 
the data element does not show up in the form designer i.e. after having been 
assigned to a dataset, or some of the category options do not show up.

In this instance I have a data element disaggregated by testing modalities, 
sex, and age (age categories <1,1-4,5-9,10-14,15-19,20-24, 
25-29,30-34,35-39,40-44,45-49, 50+).
The way it is showing up, a number of the age bands are missing in the form 
designer and it is not uniform. E.g. VCT has female 15-19, VCT is missing male 
15-19.
I have run maintenance, generated 

[Dhis2-users] questions about tracker (coordinates, attributes, visualization)

[Natalie Tibbels]

Hi all,

Looking for input on the tracker function. We are registering participants in 
community events using the android app in the field. Here are my questions 
about tracker:

  *   Why might a field for coordinates show up in the stages, but not in the 
main program enrollment screen if I have checked “yes” to capturing 
coordinates? (But the coordinates field DOES show up in tracker capture using a 
computer, just not on the app)
  *   What is the rationale for certain characteristics being attributes vs. 
data elements? If I want to be able to visualize all the data - total number 
enrolled, where, characteristics, stages - which should be attributes of the 
tracked entity and which should be data elements?
  *   In general I am having trouble visualizing tracked data - I made program 
indicators for certain elements, is that the best way to visualize tracker 
data? Tracker data elements are not even showing up in the data visualizer.

Another question is when I initially access the visualizer or pivot tables (as 
the admin), an error screen will pop up saying “No organization unit levels 
found” - any thoughts on what this means? I’m still able to see all my org 
units…

Thanks in advance for your help!

~Natalie T
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Update Category option combination

[Djibril Dione]

Thanks Ifeanyi for the update.
Our issue is a bit different here all is populating well on Data entry and
people are capturing data. just that the category option combination
names are not updated with the correct and we use those name in a complex
completeness report script.

Test step On *Sierra Leon 2.27*

   1.  I have renamed the dataelementcategoryoption "*Improve access to
   clean water*" to "*IACW*"
   2.  then go to administration app > maintenance > select "*Update
   category option combinations*"  and click "perform maintenance".
   3.  then I go to category option combination under maintenance
   (metadata) and search for "IACW" and could not find it but when you search
   for "Improve access to clean water" you get many that pop in. i.e:
"*AIDSRelief
   Consortium, Improve access to clean water" *which supposes to be renamed
   to *"AIDSRelief Consortium, IACW"*
   4. I create a sqlView that search on the categoryoptioncombo Table and I
   got the same result as the front end

so whenever you rename a categoryoption I believe that the category option
combination name should also reflect the new name once an Update category
option combinations is performed

On Tue, Nov 28, 2017 at 5:03 PM, Ifeanyi Okoye 
wrote:

> Just an update on this.
>
> Everything I tried initially did not work. I then went to the dataset
> editor window to remove the problematic data elements and once I filtered
> them, I found that each one of them had in parenthesis at the end of the
> name of the data element, the category option combo that was causing the
> issue. Once I removed and put it back, the issue was resolved.
>
> I hope this helps somebody.
>
> Thank you.
>
>
> Warm Regards,
>
> Ifeanyi
>
> Read DrMaestro's Blog
> www.ifeanyiokoye.com
>
>
> On Monday, November 27, 2017, 10:04:23 AM GMT+1, Ifeanyi Okoye <
> ifeanyiok...@yahoo.com> wrote:
>
>
> Hello Lars,
> This is similar to the issue I raised on this platform last week.
>
> What I noticed is that some data elements will carry the old category
> option combo even after it has been changed or updated. This affects the
> form designer and section forms. In our own case, everything refused to
> update. I ran maintenance severally with no effect whatsoever.
>
> I am posting the thread below as only one person weighed in on this:
>
> Thread:
>
>
> Hello Laura,
> Thank you for your response.
>
> We are currently running the 22nd Nov (dbf5f18) build of version 2.27
> which we upgraded to on Thursday, this past week but the issue is still
> persisting.
>
> I have recreated the category option combination and applied it to the
> data element but the same issue is still persisting. When I do a metadata
> export from the API, the missing categories are not on the list. It is as
> though DHIS does not even create them for whatever reason.
>
> I don't know if anyone can provide some insight on what we could do to fix
> this since upgrading did not help.
>
> It's affecting our roll out plans.
>
> Thank you once again.
>
>
> Warm Regards,
>
> Ifeanyi
>
> Read DrMaestro's Blog
> www.ifeanyiokoye.com
>
>
> On Tuesday, November 21, 2017, 10:21:58 PM GMT+1, Laura E. Lincks <
> laura.lin...@icap.columbia.edu> wrote:
>
>
> You may want to upgrade to the latest build. We had a similar problem with
> 2.27 (on a build from August) and we just upgraded this very minute to the
> latest build 37edfc2 (Nov 8, 2017) and the problem appears fixed.
>
> *Laura E. Lincks*
> Database Manager/Developer
> ICAP - Columbia University
> Mailman School of Public Health
> 60 Haven Ave, Floor B1
> 
> New York, NY 10032
> 
> Tel: 212 304 7132
>
> On Mon, Nov 20, 2017 at 1:13 PM, Ifeanyi Okoye 
>  wrote:
>
> Hello All,
> We are encountering this issue with the form designer where either the
> data element does not show up in the form designer i.e. after having been
> assigned to a dataset, or some of the category options do not show up.
>
>
> In this instance I have a data element disaggregated by testing
> modalities, sex, and age (age categories <1,1-4,5-9,10-14,15-19,20-24,
> 25-29,30-34,35-39,40-44,45-49, 50+).
>
> The way it is showing up, a number of the age bands are missing in the
> form designer and it is not uniform. E.g. VCT has female 15-19, VCT is
> missing male 15-19.
>
> I have run maintenance, generated resource tables, run analytics, removed
> the options from the category combo and put them back again, but still not
> showing up.
>
> We use custom forms a lot and this is not the first time we are
> encountering this, but then, not to this degree.
>
>
> Can anybody please help with this?
>
> We are running DHIS2 ver 2.27 Build revision: a8283e0 Build date:
> 2017-09-21 06:25
>
> Thank you.
>
>
>
>
> Warm Regards,
>
> Ifeanyi
>
> Read DrMaestro's Blog
> www.ifeanyiokoye.com
>
>
> On 

Re: [Dhis2-users] Update Category option combination

[Ifeanyi Okoye]

Just an update on this. 
Everything I tried initially did not work. I then went to the dataset editor 
window to remove the problematic data elements and once I filtered them, I 
found that each one of them had in parenthesis at the end of the name of the 
data element, the category option combo that was causing the issue. Once I 
removed and put it back, the issue was resolved.
I hope this helps somebody.
Thank you.

Warm Regards, 

Ifeanyi

Read DrMaestro's Blog
www.ifeanyiokoye.com
 

On Monday, November 27, 2017, 10:04:23 AM GMT+1, Ifeanyi Okoye 
 wrote:  
 
 Hello Lars,This is similar to the issue I raised on this platform last week.
What I noticed is that some data elements will carry the old category option 
combo even after it has been changed or updated. This affects the form designer 
and section forms. In our own case, everything refused to update. I ran 
maintenance severally with no effect whatsoever. 
I am posting the thread below as only one person weighed in on this:
Thread:

Hello Laura,Thank you for your response.
We are currently running the 22nd Nov (dbf5f18) build of version 2.27 which we 
upgraded to on Thursday, this past week but the issue is still persisting.
I have recreated the category option combination and applied it to the data 
element but the same issue is still persisting. When I do a metadata export 
from the API, the missing categories are not on the list. It is as though DHIS 
does not even create them for whatever reason.
I don't know if anyone can provide some insight on what we could do to fix this 
since upgrading did not help.
It's affecting our roll out plans.
Thank you once again.

Warm Regards, 

Ifeanyi

Read DrMaestro's Blog
www.ifeanyiokoye.com


On Tuesday, November 21, 2017, 10:21:58 PM GMT+1, Laura E. Lincks 
 wrote:

You may want to upgrade to the latest build. We had a similar problem with 2.27 
(on a build from August) and we just upgraded this very minute to the latest 
build 37edfc2 (Nov 8, 2017) and the problem appears fixed.

Laura E. Lincks
Database Manager/Developer
ICAP - Columbia University
Mailman School of Public Health
60 Haven Ave, Floor B1
New York, NY 10032
Tel: 212 304 7132


On Mon, Nov 20, 2017 at 1:13 PM, Ifeanyi Okoye  wrote:

Hello All,We are encountering this issue with the form designer where either 
the data element does not show up in the form designer i.e. after having been 
assigned to a dataset, or some of the category options do not show up.

In this instance I have a data element disaggregated by testing modalities, 
sex, and age (age categories <1,1-4,5-9,10-14,15-19,20-24, 
25-29,30-34,35-39,40-44,45-49, 50+).
The way it is showing up, a number of the age bands are missing in the form 
designer and it is not uniform. E.g. VCT has female 15-19, VCT is missing male 
15-19.
I have run maintenance, generated resource tables, run analytics, removed the 
options from the category combo and put them back again, but still not showing 
up.
We use custom forms a lot and this is not the first time we are encountering 
this, but then, not to this degree.

Can anybody please help with this?
We are running DHIS2 ver 2.27 Build revision: a8283e0 Build date: 2017-09-21 
06:25
Thank you.




Warm Regards, 

Ifeanyi

Read DrMaestro's Blog
www.ifeanyiokoye.com
 

On Sunday, November 26, 2017, 9:51:05 AM GMT+1, Lars Helge Øverland 
 wrote:  
 
 For data entry module, you might have to clean your browser cache.
regards,
Lars

On 25 November 2017 at 08:52, Djibril Dione  wrote:

Hi Lars,I did perform Update category option combinations as decrypt on my 
email but there was no change in the name.similarly, I renamed the category 
option "Improve Access to Improve access to clean water" on Sierra Leon demo 
2.27. but no change after performing maintenance.
On Fri, Nov 24, 2017 at 11:28 PM, Lars Helge Øverland  wrote:

Hi there,
try going to data administration app > maintenance > select "Update category 
option combinations"  and click "perform maintenance".
regards,
Lars

On 24 November 2017 at 15:01, Djibril Dione  wrote:

Dear DHIS2 community, We are setting up an aggregated system using Attribute 
option as part of the disaggregation. Some of the category option names were 
not correct and we have renamed them.
Now after updating the category option combination through data 
administration/Maintenance, the old combination name is still appearing on the 
category option combinations on the frontend and at the backend.
we have renamed some attribute option on Sierra Leon Demo 2.27 and still found 
the same issue.
Is there anyone experiencing the same issue.
we are using version 2.27 build:5c148f4
-- 


Kind Regards




Djibril Dione 

Database Specialist



Health Information Systems Program – SA

Cell: +27 71 711 5421

Skype: dione.djibril

Address: 66 Rigel Ave North, Waterkloof Ridge, 

Re: [Dhis2-users] gml import error

[Em Le Hong]

Hi,
There is a reported bug about GML import
https://jira.dhis2.org/browse/DHIS2-2521 You can check here, maybe it's the
same issue.

On Tue, Nov 28, 2017 at 2:55 PM, 林晓东  wrote:

> Hi,all,sir,
>
> what's wrong with this?
>
> I want import org boundary data into dhis2.  add some orgs, and  create a
> gml file as the user doc guided, file like:
>
>  
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://ogr.maptools.org/ main1.xsd"
>  xmlns:ogr="http://ogr.maptools.org/;
>  xmlns:gml="http://www.opengis.net/gml;>
>   
> 
>   102.8622570920001
> 30.7603155665
>   103.7439320390002
> 31.7195597506
> 
>   
>   
> 
>outerBoundaryIs>103.62481779500014,31.53714191353
> 103.62451709100016,31.53532277994 103.62466086100014,31.53097002984
> 103.62574409700014,31.52492020851 103.62562210100012,31.52406814583
> 103.62483881600016,31.52249621393 103.62077686800015,31.51701246758
> 103.6197319811,31.51681736351 103.61885734500011,31.51781958062
> 103.61829453100013,31.51772153185 103.61637853600016,31.51464278385
> 103.61620359500013,31.5137441396 103.61649060200013,31.5124504916
> 103.61566895300015,31.50981431195 103.61566493100015,31.50637683697
> 103.61484138700015,31.49996984588 103.6153018512,31.499406785000101
> 103.61599383400012,31.49690254955 103.61318011600015,31.49614242866
> 103.61142887600013,31.49496580753 103.6101844112,31.49335699581
> 103.60977310700015,31.4904224465 103.60906637200016,31.48911842951
> 103.60893561600012,31.48542411168 103.60917991400011,31.4850933837
> 103.60967881200015,31.48499942773 103.6102085713,31.48534817448
> 103.61641595100015,31.48663665473 103.61748375300013,31.48652317255
> 103.61787105200013,31.48613306157 103.61717549600016,31.48421133161
> 103.61726233100013,31.4801853096 103.61651247100015,31.47931925592
> 103.61584231600013,31.47781904482 103.61313264700013,31.47579892249
> 103.61083853700015,31.47276725586 103.60991132600016,31.47047121053
> 103.61002406600014,31.46934659894 103.60961751900012,31.46704933595
> 103.60977101700014,31.465334792000103 103.60906452600013,31.46436604687
> 103.60873138100013,31.46306497355 103.60811765500014,31.46232377272
> 103.6079265514,31.460626078000104 103.60494097100015,31.45717538699
> 103.60442228300016,31.45547427196 103.60524883900014,31.45419755082
> 103.60598188700011,31.45366863295 103.60651382700016,31.45253516196
> 103.60600907200013,31.45176076599 103.60612052700017,31.45098565678
> 103.60719168500012,31.44988112568 103.60752359700015,31.44861313273
> 103.60817147300016,31.448266954000101 103.60885253300013,31.446790817000103
> 103.60899751700012,31.44590226969 103.60872180100014,31.8638672
> 103.60894249700013,31.44293460083 103.60751983400016,31.44069406584
> 103.60536892300014,31.43820460174 103.60414868400012,31.43720914486
> 103.60112570300012,31.43611721692 103.5982057215,31.4361711298
> 103.59795814700013,31.43590900888 103.59921583300016,31.43536014347
> 103.59997440100013,31.43453643298 103.60082541100016,31.43426222397
> 103.60155007500012,31.43353779174 103.60171153800016,31.4324733275
> 103.60258477300012,31.431832749000101 103.60263035500017,31.4314864395
> 103.60358378200011,31.43128875103 103.60388956900013,31.4304424040001
> 103.60556251600015,31.42876994577 103.60590617600016,31.42741246792
> 103.6066871314,31.42781647564 103.60899487200012,31.42807958291
> 103.61083890700016,31.42658916074 103.61374410400012,31.42558017067
> 103.61409064800014,31.42466318475 103.61453828700014,31.42454317164
> 103.61540541500013,31.42357877177 103.61754784700015,31.42331836764
> 103.61901573400016,31.42259118744 103.61999370900017,31.42163313053
> 103.62208813500015,31.42076674887 103.62315267400012,31.41978751167
> 103.62367380800011,31.41833388056 103.62494224400015,31.41670041383
> 103.62494385100015,31.4154607208 103.62534657600015,31.41423765365
> 103.6262394160001,31.413092047000102 103.62714936400012,31.40911822475
> 103.62714712100014,31.40573143496 103.62808331600014,31.40434104459
> 103.62850161600014,31.4029621856 103.63011211800013,31.40114290879
> 103.63025119400011,31.39815125866 103.63075096800017,31.39665319581
> 103.63195545200014,31.39490297289 103.63220802200011,31.39286923888
> 103.63505027600014,31.39134145467 103.63624302900016,31.38929037969
> 103.63672949200017,31.38760080555 103.63693039200015,31.385826187000102
> 103.63576079100012,31.38407799891 103.63685864800013,31.38197123652
> 103.63664170600012,31.37934480091 103.63594054100015,31.37825762492
> 

[Dhis2-users] gml import error

[林晓东]

Hi,all,sir,


what's wrong with this?


I want import org boundary data into dhis2.  add some orgs, and  create a  gml 
file as the user doc guided, file like:


 
http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://ogr.maptools.org/ main1.xsd"
 xmlns:ogr="http://ogr.maptools.org/;
 xmlns:gml="http://www.opengis.net/gml;>
  

  
102.862257092000130.7603155665
  
103.743932039000231.7195597506


  

  103.62481779500014,31.53714191353
 103.62451709100016,31.53532277994 103.62466086100014,31.53097002984 
103.62574409700014,31.52492020851 103.62562210100012,31.52406814583 
103.62483881600016,31.52249621393 103.62077686800015,31.51701246758 
103.6197319811,31.51681736351 103.61885734500011,31.51781958062 
103.61829453100013,31.51772153185 103.61637853600016,31.51464278385 
103.61620359500013,31.5137441396 103.61649060200013,31.5124504916 
103.61566895300015,31.50981431195 103.61566493100015,31.50637683697 
103.61484138700015,31.49996984588 103.6153018512,31.499406785000101 
103.61599383400012,31.49690254955 103.61318011600015,31.49614242866 
103.61142887600013,31.49496580753 103.6101844112,31.49335699581 
103.60977310700015,31.4904224465 103.60906637200016,31.48911842951 
103.60893561600012,31.48542411168 103.60917991400011,31.4850933837 
103.60967881200015,31.48499942773 103.6102085713,31.48534817448 
103.61641595100015,31.48663665473 103.61748375300013,31.48652317255 
103.61787105200013,31.48613306157 103.61717549600016,31.48421133161 
103.61726233100013,31.4801853096 103.61651247100015,31.47931925592 
103.61584231600013,31.47781904482 103.61313264700013,31.47579892249 
103.61083853700015,31.47276725586 103.60991132600016,31.47047121053 
103.61002406600014,31.46934659894 103.60961751900012,31.46704933595 
103.60977101700014,31.465334792000103 103.60906452600013,31.46436604687 
103.60873138100013,31.46306497355 103.60811765500014,31.46232377272 
103.6079265514,31.460626078000104 103.60494097100015,31.45717538699 
103.60442228300016,31.45547427196 103.60524883900014,31.45419755082 
103.60598188700011,31.45366863295 103.60651382700016,31.45253516196 
103.60600907200013,31.45176076599 103.60612052700017,31.45098565678 
103.60719168500012,31.44988112568 103.60752359700015,31.44861313273 
103.60817147300016,31.448266954000101 103.60885253300013,31.446790817000103 
103.60899751700012,31.44590226969 103.60872180100014,31.8638672 
103.60894249700013,31.44293460083 103.60751983400016,31.44069406584 
103.60536892300014,31.43820460174 103.60414868400012,31.43720914486 
103.60112570300012,31.43611721692 103.5982057215,31.4361711298 
103.59795814700013,31.43590900888 103.59921583300016,31.43536014347 
103.59997440100013,31.43453643298 103.60082541100016,31.43426222397 
103.60155007500012,31.43353779174 103.60171153800016,31.4324733275 
103.60258477300012,31.431832749000101 103.60263035500017,31.4314864395 
103.60358378200011,31.43128875103 103.60388956900013,31.4304424040001 
103.60556251600015,31.42876994577 103.60590617600016,31.42741246792 
103.6066871314,31.42781647564 103.60899487200012,31.42807958291 
103.61083890700016,31.42658916074 103.61374410400012,31.42558017067 
103.61409064800014,31.42466318475 103.61453828700014,31.42454317164 
103.61540541500013,31.42357877177 103.61754784700015,31.42331836764 
103.61901573400016,31.42259118744 103.61999370900017,31.42163313053 
103.62208813500015,31.42076674887 103.62315267400012,31.41978751167 
103.62367380800011,31.41833388056 103.62494224400015,31.41670041383 
103.62494385100015,31.4154607208 103.62534657600015,31.41423765365 
103.6262394160001,31.413092047000102 103.62714936400012,31.40911822475 
103.62714712100014,31.40573143496 103.62808331600014,31.40434104459 
103.62850161600014,31.4029621856 103.63011211800013,31.40114290879 
103.63025119400011,31.39815125866 103.63075096800017,31.39665319581 
103.63195545200014,31.39490297289 103.63220802200011,31.39286923888 
103.63505027600014,31.39134145467 103.63624302900016,31.38929037969 
103.63672949200017,31.38760080555 103.63693039200015,31.385826187000102 
103.63576079100012,31.38407799891 103.63685864800013,31.38197123652 
103.63664170600012,31.37934480091 103.63594054100015,31.37825762492 
103.63627556800017,31.37601974264 103.63595001800016,31.37395775985 
103.63703826900016,31.372957416000101 103.63714782800015,31.37207504699 
103.63883346400016,31.37114899849 103.63937043100012,31.36915918851 
103.64016113100014,31.36834067445 103.63971725900014,31.36707862794