Re: [Dhis2-devs] [Bug 608318] [NEW] GIS hangs after deleting map

2010-07-23 Thread Jan Henrik Øverland
Not able to reproduce this one. Even deleted the map that was selected in the thematic map and then opened the thematic map panel, but no errors. More details? On Wed, Jul 21, 2010 at 5:42 PM, Knut Staring wrote: > Public bug reported: > > Using GeoJSON as map source and deleting a map triggers

[Dhis2-devs] [Bug 608320] Re: GIS Refreshing choropleth causes return to initial coordinates

2010-07-23 Thread Jan Henrik Øverland
** Changed in: dhis2 Assignee: (unassigned) => Jan Henrik Øverland (janhenrik-overland) ** Changed in: dhis2 Status: New => Fix Committed -- GIS Refreshing choropleth causes return to initial coordinates https://bugs.launchpad.net/bugs/608320 You received this bug notification becaus

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 1875: Fixed bug: [Bug 608320] [NEW] GIS Refreshing choropleth causes return to initial coordinates

2010-07-23 Thread noreply
Merge authors: Jan Henrik Øverland (janhenrik-overland) revno: 1875 [merge] committer: Jan Henrik Overland branch nick: trunk timestamp: Fri 2010-07-23 23:05:35 +0200 message: Fixed bug: [Bug 608320] [NEW] GIS Refreshing choropleth c

Re: [Dhis2-devs] Info on GIS development

2010-07-23 Thread Bob Jolliffe
In fact the xpath expression will be a bit tricky. xpath is not really well suited to this kind of data where the coordinates are not "proper" xml elements but are encoded in a string. In fact right the way through the process from gml to database we don't ever see the coordinates as numbers. (P

Re: [Dhis2-devs] Info on GIS development

2010-07-23 Thread Knut Staring
It obviously also depends a bit on the scale - if we are talking about world maps and just national borders, in my experience 2 decimals is more than enough. But for a subdistrict map I think you would at least want 3. k On Fri, Jul 23, 2010 at 10:11 PM, Knut Staring wrote: > There is probably s

Re: [Dhis2-devs] Info on GIS development

2010-07-23 Thread Knut Staring
There is probably some difference between polygons and points. For the location of health facilities (points), I think it makes sense to retain 4-5 decimals. Polygons (which obviously have a lot more coordinates) can probably do fine with 3-4. Let us settle for 4 overall for now, and then ppl like

Re: [Dhis2-devs] dhis14 import

2010-07-23 Thread Bob Jolliffe
Hi Ime On 23 July 2010 19:23, Ime Asangansi wrote: > Hi Bob, > > Mmmm..interesting. > > Just to be sure. > Were you reading from 1.4 and writing to 2.0? mysql or postgres? > > Were you writing the other way (to access)? Nothing so grand as any of the above. Though I am reading and writing acces

Re: [Dhis2-devs] Info on GIS development

2010-07-23 Thread Bob Jolliffe
2010/7/23 Knut Staring : > 2010/7/14 Lars Helge Øverland : >> >> We are in the process of changing the GIS module in terms of how the >> geographical information is persisted and presented. >> In the snapshot version we now store the coordinates in JSON format directly >> in the database on the Org

Re: [Dhis2-devs] dhis14 import

2010-07-23 Thread Ime Asangansi
Hi Bob, Mmmm..interesting. Just to be sure. Were you reading from 1.4 and writing to 2.0? mysql or postgres? Were you writing the other way (to access)? Thanks. Ime --- On Fri, 7/23/10, Bob Jolliffe wrote: > From: Bob Jolliffe > Subject: Re: [Dhis2-devs] dhis14 import > To: "Lars Helge Øv

Re: [Dhis2-devs] Info on GIS development

2010-07-23 Thread Jan Henrik Øverland
Having 15 decimals is of course ridiculous in our case. The surface distance per 1 degree change in latitude is approximately 111 km, so 15 decimals means an accuracy of 0.00111 mm. I think five decimals should be appropriate (1 meter) or even four (11 meter) or three (111 meter)? Could this be

Re: [Dhis2-devs] Info on GIS development

2010-07-23 Thread Knut Staring
2010/7/14 Lars Helge Øverland : > > We are in the process of changing the GIS module in terms of how the > geographical information is persisted and presented. > In the snapshot version we now store the coordinates in JSON format directly > in the database on the OrganisationUnit.coordinates proper

Re: [Dhis2-devs] dhis14 import

2010-07-23 Thread Bob Jolliffe
Alright writing is pretty slow. Writing 10million records take two hours. But reading is pretty darn quick. Iterating through 10million rows and dumping each row to stdout (redirected to /dev/null) takes about 1 minute +- 5 seconds. Throughout which memory use is constant and low: less than 1.

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 1874: Fixed ChartGenerationAction in Dashboard to support AggregationServcie Changes; Minor bug fixes i...

2010-07-23 Thread noreply
revno: 1874 committer: Bharath branch nick: trunk timestamp: Fri 2010-07-23 18:35:37 +0530 message: Fixed ChartGenerationAction in Dashboard to support AggregationServcie Changes; Minor bug fixes in reports & patient modules modified:

Re: [Dhis2-devs] dhis14 import

2010-07-23 Thread Bob Jolliffe
2010/7/22 Lars Helge Øverland : > > No doubt this looks much simpler. > Would be interesting to do a test with a large table (>10 mill) and see how > it performs in terms of memory usage. 10 million records is a lot of records! I have it whirring away in the background as I get on with other stuf

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 1873: Minor fix.

2010-07-23 Thread noreply
revno: 1873 committer: Tran Chau branch nick: trunk timestamp: Fri 2010-07-23 14:04:03 +0700 message: Minor fix. modified: dhis-2/dhis-web/dhis-web-commons-resources/src/main/webapp/dhis-web-commons/oust/oust.js dhis-2/dhis-web/d