dhis2-devs team mailing list archive

[Jan Henrik Øverland <janhenrik.overland@xxxxxxxxx>]

First of all, I was just talking about the geojson store folder, not
DHIS2_HOME/geojson where the GIS application is looking for files.

On Fri, Sep 11, 2009 at 3:59 PM, Jason Pickering <
jason.p.pickering@xxxxxxxxx> wrote:

> Possibly but IMHO, for more complex use cases, you would probably want to
> use something like Geoserver to automatically generate the GeoJSON for you
> possibly on the fly.
>
> Creating this type of directory structure, for say, the entire world would
> be daunting and a real pain to maintain. What I tried to do with the geodata
> at WHO for instance, was to flatten everything into a single layer, and then
> let Geoserver sort it out with the use of filters of WFS posts in order to
> get what you actually need. From a geodatabase management standpoint, it is
> much, much easier than having to maintain separate files in many different
> directories. However if most users of DHIS2 would be working only with a few
> files (admin1-4, PHU) maybe just a flat directory is enough.
>
> The ability of the client to be able to consume a GeoJSON stream from a
> server would probably be a better feature to focus on, with the client being
> able to connect to a WMS server and parse a GetFeatureRequest in order to
> allow either 1) population of the organization unit hierarchy (Knut's
> request) or 2) simply downloading of the GeoJSON file for an already
> populated hierarchy. A refresh feature would be good, as data can change.
> Otherwise, maybe the code could be altered at some point to allow the
> Mapping client to download the GeoJSON files directly from Geoserver without
> having to maintain the GeoJSON files locally. Maintenance of these GeoJSON
> files is going to be a bit of a headache for installations with many layers,
> or maybe people simply do not want to bother with it but would prefer to
> connect to other WMS servers out there to get their data.


No 2 is exactly what it was like a couple of months ago. We decided to read
local GeoJSON files instead, because we wanted to leave out Geoserver to get
rid of those ~50 mb. It is also a lot easier for nontechnicals to receive a
GeoJSON file and make use of it compared to getting a set of shapefiles and
not being familiar with Geoserver.

Is it possible to dynamically produce a list of shapefiles currenty
available in your Geoserver installation? Like the new combo box lists the
available files in DHIS2_HOME/geojson ?


>
> I was primarily suggesting that directory structure however for the
> contribution of the static GeoJSON files on Launchpad, so that they would
> will be available to others.
>
> However you should probably send your shape files to Knut at WHO, so that
> he can upload them to the WHO Geoserver. :)
>
> Best regards,
> Jason
>
>
>
> On Fri, Sep 11, 2009 at 10:33 AM, Jan Henrik Øverland <
> janhenrik.overland@xxxxxxxxx> wrote:
>
>> On Tue, Sep 8, 2009 at 3:39 PM, Jason Pickering <
>> jason.p.pickering@xxxxxxxxx> wrote:
>>
>>> Bump on this one. More of a feature request than bug, but I do agree.
>>>
>>> We had mentioned about having a contrib folder. I think this would be a
>>> good place for this type of data that would be potentially useful for
>>> different parties.
>>>
>>> How about this structure, and then maybe the devs can fix the code around
>>> it at some point?
>>>
>>> /contrib/geodata/iso2code/geojson/
>>>
>>> where the iso2code would be for a particular country.
>>
>>
>> Right now the folder structure is simply /resources/geojson/. A more
>> complex structure, like Jason suggested, might be needed eventually?
>>
>>
>>>
>>>
>>> On Tue, Sep 8, 2009 at 10:05 AM, Ola Hodne Titlestad <olatitle@xxxxxxxxx
>>> > wrote:
>>>
>>>> Public bug reported:
>>>>
>>>> Currently all the map files (geojson) needed for the GIS module are
>>>> stored in mapping/geojson in the dhis webapps folder.
>>>> I can see the benefit from distributing these files together with the
>>>> source code and inside war files, but often you will create these files
>>>> locally and put them manually into webapps/dhis. These files are then easily
>>>> lost when updating dhis to a new version (since you then have to delete
>>>> webapps/dhis). Would it be possible to keep these files in a
>>>> DHIS2_HOME/mapping/geojson folder in stead? Or if possible, fetch map files
>>>> match from both locations so that you get the best of both sides, both
>>>> distribution inside war files and a safe place to put additional maps?
>>>>
>>>> ** Affects: dhis2
>>>>     Importance: Medium
>>>>         Status: New
>>>>
>>>> ** Changed in: dhis2
>>>>   Importance: Undecided => Medium
>>>>
>>>> ** Changed in: dhis2
>>>>    Milestone: None => 2.0.3
>>>>
>>>> --
>>>> Move mapping/geojson folder out of webapps/dhis?
>>>> https://bugs.launchpad.net/bugs/426142
>>>> You received this bug notification because you are a member of DHIS 2
>>>> developers, which is subscribed to DHIS.
>>>>
>>>> Status in DHIS 2: New
>>>>
>>>> Bug description:
>>>> Currently all the map files (geojson) needed for the GIS module are
>>>> stored in mapping/geojson in the dhis webapps folder.
>>>> I can see the benefit from distributing these files together with the
>>>> source code and inside war files, but often you will create these files
>>>> locally and put them manually into webapps/dhis. These files are then easily
>>>> lost when updating dhis to a new version (since you then have to delete
>>>> webapps/dhis). Would it be possible to keep these files in a
>>>> DHIS2_HOME/mapping/geojson folder in stead? Or if possible, fetch map files
>>>> match from both locations so that you get the best of both sides, both
>>>> distribution inside war files and a safe place to put additional maps?
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>