[STDM-user] Example setup

Olivier Dalang olivier.dalang at gmail.com
Wed Jan 7 04:25:45 PST 2015


Hi John,

Sorry to insist, but if you're still OK with it, could you share your UML
models ?

Thanks,

Olivier Dalang
*urbaMonde*


2014-12-19 12:50 GMT+01:00 Olivier Dalang <olivier.dalang at gmail.com>:

> Dear John,
>
> Thanks for your answer.
>
> I'd love to see the UML schemas.
>
> Actually I'm quite stuck about how to start. I managed to install the
> plugin with the standard modules (thanks to you answer in the other
> thread), and am now able to enter some data :
>
> *Parties*
> I get how to enter data in the "party" table, which is quite clear.
>
> *Households*
> Then, there is the "household" table, which I don't really understand.
> There seem to be no relation between "party" and "household" ?
>
> *Social Tenure Relationship*
> At some point, I try to add a new Social Tenure Relationship. I can choose
> from the list one of the parties that I created, but then have to choose a
> property. At this point I found nothing referring to properties in the UI,
> and the properties list is empty.
>
> I tried to create some polygons in the spatial_unit table (manually added
> to the QGIS project from the postgis database), expecting those to appear
> as "properties" in the social tenure relationship form, but they didn't.
> I just realized afterwards that once the layer was added, I could use the
> "Create spatial unit" button instead of the native QGIS create polygon. But
> when finishing the polygon, I get a python exception :
>
>> NameError: global name 'spatial_editor_widgets' is not defined
>
>
> *Supporting documents*
> I guess those enter in the game at the moment where a social tenure
> relationship is defined, so I didn't enter any yet.
>
>
>
>
> I understand that the default setup is not really intended to be used as
> is, since the idea is to customize the tool to match specific needs. But it
> would really help if it was possible to see the tool in action using the
> default setup.
>
> Then, I'd have some additional questions :
>
> - Does the tool allow for some database level enforcement of
> administrative constraints ? (for instance : you can't modify
> information/shape about a property as long the issued document for this lot
> hasn't been unvalidated)
>
> - Does the tool implement a revision history or other strategy to watch
> each agent's activity and detect or rollback frauds/mistakes ? (store
> timestamp, author and content of each modification)
>
>
> Thanks again,
>
> Olivier Dalang
> *urbaMonde*
>
>
>
>
>
>
>
>
>
> 2014-12-19 9:37 GMT+01:00 John Gitau <John.Gitau at unhabitat.org>:
>>
>> Hi Chris and Olivier,
>>
>> Unfortunately, the sample data we use for each context is copyrighted and
>> as such distribution is restricted. However, we are working on preparing a
>> comprehensive set of training data for the different contexts including
>> source codes for some of these implementations. If its of interest to you,
>> we have the data models in UML for some of the respective implementations,
>> which we can share on request.
>>
>> Cheers,
>>
>> John Gitau
>> Land and GLTN Unit,  Urban Legislation, Land and Governance Branch |
>> UN-HABITAT
>> NOF Block 3 Level 3 South Wing I  P.O. Box 30030-00100  Nairobi,  Kenya
>> Tel: + 254 20 762 3032 | +254 (0)722 945 556
>> Website: www <http://www.unhabitat.org>.unhabitat.org
>> <http://www.unhabitat.org>  | Partners' website: www
>> <http://www.gltn.net>.gltn.net <http://www.gltn.net>
>>
>>
>> -----stdm-user-bounces at lists.osgeo.org wrote: -----
>> To: Olivier Dalang <olivier.dalang at gmail.com>
>> From: Chris Berens
>> Sent by: stdm-user-bounces at lists.osgeo.org
>> Date: 12/19/2014 11:25AM
>> Cc: stdm-user at lists.osgeo.org
>> Subject: Re: [STDM-user] Example setup
>>
>>
>> Agreed, there is a limited knowledge base and user group which makes
>> implementation risky for us at this stage.  Where projects are referred to
>> the story is thin on day to day information management as well as setup and
>> running costs. We are considering a simplified version of QGIS on the
>> ground with cloud backups and using the power of the Atlas function.
>>
>> Chris Berens
>> www.mapland.co.za
>> +27 (0)82 567 9322
>>
>>
>> On 18 December 2014 at 16:30, Olivier Dalang < olivier.dalang at gmail.com>
>> wrote:
>>>
>>> Dear list,
>>>
>>> I'm a GIS developer currently evaluating the opportunity of using the
>>> STDM plugin for a project in Dakar, Senegal [1].  I managed to install the
>>> QGIS plugin and the PostGIS database without problems, and am now starting
>>> to look at the tool in detail.
>>>
>>> Could someone by any chance provide a populated database to see the tool
>>> in action with some more or less typical use case ?
>>> Since the tool seems very flexible, when starting from scratch, it's not
>>> easy to have a quick overview on how day to day workflow is supposed to
>>> work.
>>> A dump (or partial dump) would really be great in understand how
>>> powerful the plugin is.
>>>
>>> Or do you know if any implementation-specific documentation exists
>>> (aimed at local people working with the tool for one specific project,
>>> rather than developers or administrators).
>>>
>>> From the "applications" page on the website, I see the tool is used in
>>> several projects. Are there some detailed reports or use case documentation
>>> produced from those implementations ?
>>>
>>> Thanks a lot in advance,
>>>
>>>  Olivier Dalang
>>> *urbaMonde*
>>>
>>>
>>>
>>>
>>>
>>> [1] :  http://urbamonde.org/site/fr/urbadtk-s%C3%A9n%C3%A9gal
>>>
>>>
>>> _______________________________________________
>>> STDM-user mailing list
>>> STDM-user at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/stdm-user
>>>
>>>  _______________________________________________
>> STDM-user mailing list
>> STDM-user at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/stdm-user
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/stdm-user/attachments/20150107/8550342e/attachment.html>


More information about the STDM-user mailing list