[GeoNode-users] default workspace for geosites

Jeffrey Johnson ortelius at gmail.com
Wed Jan 18 06:51:43 PST 2017


My understanding and the documentation seem to be out of sync. I will have
to dig through this code. I've also cc'd Matt Hanson who worked on this and
he may have some insight.

On Wed, Jan 18, 2017 at 12:25 AM, Eugenio Trumpy <frippe12573 at hotmail.com>
wrote:

> Hi Jeffrey,
>
>
> as you wrote geosites does not use geoserver workspace.
>
> In the documentation (http://docs.geonode.org/en/
> master/reference/developers/geosites.html)
>
> I see:
>
> [...]To keep data organized each site specifies a default workspace
> (DEFAULT_WORKSPACE) that GeoServer will use to partition the data depending
> on which site uploaded the data. [...], however it provides at least some
> organization of the data based on the initial site.
>
> I guess the documentation is not correct, isn't it?
>
>
> Is there a way to distinguish the layer uploaded from one site to the
> others uploaded from different sites? If yes where it can be setup?
>
>
> Eugenio
>
>
>
> ------------------------------
> *Da:* Jeffrey Johnson <ortelius at gmail.com>
> *Inviato:* venerdì 13 gennaio 2017 15.26
> *A:* Eugenio Trumpy
> *Cc:* Simone Dalmasso; Alessio Fabiani; geonode-users at lists.osgeo.org
> *Oggetto:* Re: [GeoNode-users] default workspace for geosites
>
> Just to clarify.
>
> CASCADE_WORKSPACE Is used by Remote services for cascading WMS.
>
> The geosites functionality does NOT use geoserver workspaces.
>
> On Fri, Jan 13, 2017 at 3:04 AM, Eugenio Trumpy <frippe12573 at hotmail.com>
> wrote:
> > The suggested way to store the layers belonging different geosites in
> > geoserver It seemed nice to me.
> >
> > I read it here:
> > https://geonode.readthedocs.io/en/2.0/tutorials/admin/multi-tenancy.html
> GeoSites: GeoNode Multi-Tenancy — GeoNode 2.0 documentation
> <https://geonode.readthedocs.io/en/2.0/tutorials/admin/multi-tenancy.html>
> geonode.readthedocs.io
> GeoSites: GeoNode Multi-Tenancy¶ GeoSites is an approach to support
> multiple websites with GeoNode. Each GeoSite can have different templates,
> apps, and data ...
>
>
> >
> > I wondered how I should create the workspace in geoserver.
> >
> > I presume by hand from geoserver interface, then second question was
> where I
> > have to
> >
> > set the workspace for the geosite since in the global setting.py I have:
> >
> > DEFAULT_WORKSPACE
> >
> > and
> >
> > CASCADE_WORKSPACE (what does it means? What is it?)
> >
> >
> > I suppose the master site has to have DEFAULT_WORKSPACE = 'geonode'
> >
> > whereas the site DEFAULT_WORKSPACE = 'geosite', so loading a layer from
> the
> > site it should use such workspace, is that right?
> >
> > Why it does not work?
> >
> >
> > I understand that could be a second way (i.e. the way suggested by
> Simone),
> > could you give me an example? I guess you act layer by layer adding new
> > rules in geoserver 'Data security'.
> >
> >
> > ciao
> >
> >
> > Eugenio
> >
> >
> >
> >
> > ________________________________
> > Da: Simone Dalmasso <simone.dalmasso at gmail.com>
> > Inviato: venerdì 13 gennaio 2017 11.45
> > A: Alessio Fabiani
> > Cc: Eugenio Trumpy; geonode-users at lists.osgeo.org
> > Oggetto: Re: [GeoNode-users] default workspace for geosites
> >
> > Not sure about the default workspace it might be a geonode bug. But I
> leave
> > the layers in the "geonode" one and it works well. Layers are managed
> > respecting permissions, and it works well in the instances I have.
> >
> > 2017-01-13 10:59 GMT+01:00 Alessio Fabiani
> > <alessio.fabiani at geo-solutions.it>:
> >>
> >> Not sure but I'm afraid geonode has currently a lot of hardcoded stuff.
> It
> >> is quite premature speaking about multi-tenancy on GeoNode.
> >>
> >> Best Regards,
> >> Alessio Fabiani.
> >>
> >> ==
> >> GeoServer Professional Services from the experts!
> >> Visit http://goo.gl/it488V for more information.
> GeoSolutions Enterprise Services <http://goo.gl/it488V>
> goo.gl
> GeoSolutions offers enterprise support services to help you building
> enterprise-class Spatial Data Infrastructures leveraging on best-of-breed
> Open Source
>
>
> >> ==
> >>
> >> Ing. Alessio Fabiani
> >> @alfa7691
> >> Founder/Technical Lead
> >>
> >> GeoSolutions S.A.S.
> >> Via di Montramito 3/A
> >> 55054  Massarosa (LU)
> >> Italy
> >> phone: +39 0584 962313 <+39%200584%20962313>
> >> fax:     +39 0584 1660272 <+39%200584%20166%200272>
> >> mob:   +39 331 6233686 <+39%20331%20623%203686>
> >>
> >> http://www.geo-solutions.it
> <http://www.geo-solutions.it/>
> GeoSolutions <http://www.geo-solutions.it/>
> www.geo-solutions.it
> GeoSolutions Enterprise Support and Development Services. GeoSolutions off
> ers enterprise support and development services to help organizations
> building enterprise ...
>
>
> >> http://twitter.com/geosolutions_it
> GeoSolutions (@geosolutions_it) | Twitter
> <http://twitter.com/geosolutions_it>
> twitter.com
> The latest Tweets from GeoSolutions (@geosolutions_it). GeoSpatial
> solutions based on #GeoServer, #GeoTools, #MapStore, #GeoNetwork,
> ImageIO-Ext, JAI, ImageIO and other Geospatial Opens Source projects in
> general. Lucca, Italy
>
>
> >>
> >> -------------------------------------------------------
> >>
> >> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> >>
> >> Le informazioni contenute in questo messaggio di posta elettronica e/o
> >> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro
> >> utilizzo è consentito esclusivamente al destinatario del messaggio, per
> le
> >> finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio
> >> senza esserne il destinatario, Vi preghiamo cortesemente di darcene
> notizia
> >> via e-mail e di procedere alla distruzione del messaggio stesso,
> >> cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo
> >> anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per
> >> finalità diverse, costituisce comportamento contrario ai principi
> dettati
> >> dal D.Lgs. 196/2003.
> >>
> >>
> >>
> >> The information in this message and/or attachments, is intended solely
> for
> >> the attention and use of the named addressee(s) and may be confidential
> or
> >> proprietary in nature or covered by the provisions of privacy act
> >> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> >> Code).Any use not in accord with its purpose, any disclosure,
> reproduction,
> >> copying, distribution, or either dissemination, either whole or
> partial, is
> >> strictly forbidden except previous formal approval of the named
> >> addressee(s). If you are not the intended recipient, please contact
> >> immediately the sender by telephone, fax or e-mail and delete the
> >> information in this message that has been received in error. The sender
> does
> >> not give any warranty or accept liability as the content, accuracy or
> >> completeness of sent messages and accepts no responsibility  for changes
> >> made after they were sent or for other risks which arise as a result of
> >> e-mail transmission, viruses, etc.
> >>
> >> ---------------------------------------------------------------------
> >>
> >>
> >> On Fri, Jan 13, 2017 at 10:44 AM, Eugenio Trumpy <
> frippe12573 at hotmail.com>
> >> wrote:
> >>>
> >>> Dear all,
> >>>
> >>>
> >>> I setup geosites in my geonode instance.
> >>>
> >>>
> >>> I'm now testing the geosite I created. I tried to upload a SHP from my
> >>> new geosite and the procedure went well.
> >>>
> >>> However in geoserver, I see the new layer under the workspace named
> >>> 'geonode', which was created by the master site (for master site I
> mean the
> >>> one we have with the default installation of geonode). Since i
> inserted the
> >>> variable DEFAULT_WORKSPACE='mynewgeosite' in the settings.py placed
> in the
> >>> folder of my new geosite, I was expected to have the new SHP in the new
> >>> geoserver workspace.
> >>>
> >>> Where am I wrong?
> >>>
> >>>
> >>> Moreover, after the layer upload I can see it in the layer list, but in
> >>> the 'type' filter I see the vector layer loaded over all the others
> layers
> >>> loaded in the master site.
> >>>
> >>> I was expected to have only 1 layer. Is that correct or it is due to a
> >>> somehow miss-configuration?
> >>>
> >>>
> >>> Thanks in advance
> >>>
> >>>
> >>> Eugenio
> >>>
> >>>
> >>> _______________________________________________
> >>> geonode-users mailing list
> >>> geonode-users at lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/geonode-users
> geonode-users Info Page - Open Source Geospatial Foundation
> <http://lists.osgeo.org/mailman/listinfo/geonode-users>
> lists.osgeo.org
> GeoNode users discussion. To see the collection of prior postings to the
> list, visit the geonode-users Archives. Using geonode-users
>
>
> >>>
> >>
> >>
> >> _______________________________________________
> >> geonode-users mailing list
> >> geonode-users at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/geonode-users
> geonode-users Info Page - Open Source Geospatial Foundation
> <http://lists.osgeo.org/mailman/listinfo/geonode-users>
> lists.osgeo.org
> GeoNode users discussion. To see the collection of prior postings to the
> list, visit the geonode-users Archives. Using geonode-users
>
>
> >>
> >
> >
> >
> > --
> > Simone
> >
> > _______________________________________________
> > geonode-users mailing list
> > geonode-users at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/geonode-users
> geonode-users Info Page - Open Source Geospatial Foundation
> <http://lists.osgeo.org/mailman/listinfo/geonode-users>
> lists.osgeo.org
> GeoNode users discussion. To see the collection of prior postings to the
> list, visit the geonode-users Archives. Using geonode-users
>
>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20170118/26abe272/attachment-0001.html>


More information about the geonode-users mailing list