[GeoNode-devel] Q: collaborative mapping with custom data fields and workflow - is geonode the right tool?

[Ariel Nunez]

You would not have to reinvent wheels, just put the wheels together to make
a cart.

The missing links were:
https://github.com/makinacorpus/django-geojson
and what powers:
http://geojson.io/#map=2/20.0/0.0

-a

On Tue, Aug 25, 2015 at 5:32 PM, Karma Kolabor <collaborista at gmail.com>
wrote:

> Hi Ariel,
>
> wow, that was fast. Yes, I had the impression that geonode will be
> slightly overdose for this, thanks for the clarification!
>
> I am still evaluating other projects as I would not like to reinvent
> all wheels, so all hints are welcome.
>
> Ah, yes, and of course: thank you very much for your great open source
> project!
>
> Have a nice day,
> Karma
>
>
> On Wed, Aug 26, 2015 at 12:07 AM, Ariel Nunez <ingenieroariel at gmail.com>
> wrote:
> > Hello Karma,
> >
> > Your application sounds very simple and GeoNode is an overkill for it. If
> > you have a good idea of your data model layout and are familiar with
> Django
> > all you need is:
> >
> > 1) django-guardian for per row permission.
> > 2) A simple manual workflow, no need for a custom app
> > 3) Postgis as your data store
> > 4) Integration with a good geojson editor. Search our mailing lists for
> > posts from John Jediny, he has done similar things in the past.
> >
> > The use case GeoNode is good for, is when your users are the ones who are
> > going to upload the geospatial data afterwards, and you need to let
> people
> > with no GIS skills or tools be able to know what it is in that
> buildings.shp
> > layer that they got access to, who created it, when, who to contact for
> an
> > update.
> >
> > Good luck, django for geospatial apps is a safe bet.
> > -a
> >
> > On Tue, Aug 25, 2015 at 4:49 PM, Karma Kolabor <collaborista at gmail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> I would like to develop a web project that realizes collaborative
> >> mapping with custom data fields attached to the POIs, plus there
> >> should be a workflow that enables editors to review new additions
> >> before publishing them.
> >>
> >> I found the PGIS example of the cartaro.org project @
> >> http://demo.cartaro.org/collaborative-mapping to be quite near to what
> >> I would like to realize, however I would prefer django and python as a
> >> stack.
> >>
> >> From what I understand from the geonode docs and examples it seems to
> >> be more about cataloging of different maps - I only need one map and I
> >> can not find any references to any kind of workflow in geonode.
> >>
> >> As I know django, I am quite sure that custom fields (only some text
> >> and number fields needed here) attached to spatial data should be no
> >> problem, also I know there are some workflow solutions existing for
> >> django, however I would like to ask: will a usecase like this still be
> >> on par with the envisioned use cases for geonode or will I find myself
> >> using the wrong tool for the job quickly?
> >>
> >> If I am on the right track with geonode, it would be great if you
> >> could give me some hints in which direction to look - maybe even some
> >> examples?
> >>
> >> If there is nothing realized that comes near my planned project right
> >> now, but attaching custom fields to geodata and a workflow system
> >> sounds attractive to you, what directions would you take, if it would
> >> be a part of a future geonode? Do you have some experiences and
> >> recommendations for which way to go?
> >>
> >> Regarding custom fields: I know the django datamodel has a serious
> >> limitation with dynamic fields, see e.g. [1], but things like
> >> django-hstore [2] are actively developed and seem to be a good
> >> workaround, used in similar projects like nodeshot [3], which I am
> >> evaluating too. For the special case I am working on I will not need
> >> fields to be created dynamically by the user, so fixing them in the
> >> model definition is ok - however it would be interesting to read what
> >> you think about that scenario.
> >>
> >> Regarding workflow - seems like django-viewflow [4] atm is very
> >> popular [5] - has geonode some built in workflow capacity? I just need
> >> a very simple approval workflow, but how simple this ever might be, it
> >> needs some kind of permission management - and again there are too
> >> many things [6] out there for this, unfortunately. What would you
> >> recommend / prefer for perfect harmony with what you are planning for
> >> geonode?
> >>
> >> Thanks for your attention,
> >> have anice day,
> >> Karma
> >>
> >>
> >> [1] - http://www.slideshare.net/schacki/django-dynamic-models20130502
> >> [2] - https://github.com/djangonauts/django-hstore
> >> [3] - http://nodeshot.org/
> >> [4] - https://github.com/viewflow/viewflow
> >> [5] - https://www.djangopackages.com/grids/g/workflow/
> >> [6] - https://www.djangopackages.com/grids/g/perms/
> >> _______________________________________________
> >> geonode-devel mailing list
> >> geonode-devel at lists.osgeo.org
> >> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-devel
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20150825/6b402ef0/attachment-0001.html>