[ckan-dev] default beaviour of WMS viewer

Elena Camossi elena.camossi at ext.jrc.ec.europa.eu
Tue Dec 17 13:19:46 UTC 2013


Hi Armin,

 

CKAN version is 2.1, and the source catalogue is harvested as CSW.

 

Regards,

-Elena 

 

 

 

From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] On Behalf Of Armin
Retterath
Sent: martedì 17 dicembre 2013 12:41
To: CKAN Development Discussions
Subject: Re: [ckan-dev] default beaviour of WMS viewer

 

Hi Elena,

what version of ckan do you use? The catalogue that you harvest, is it a
ckan instance or a csw source?

Regards

Armin

 

2013/12/17 Elena Camossi <elena.camossi at ext.jrc.ec.europa.eu
<mailto:elena.camossi at ext.jrc.ec.europa.eu> >

Hi Alex,

thanks for replying.

I'm not sure to understand correctly your answer, or most likely I didn't
put my question clear enough.
My institution harvests the datasets from another catalogue that publishes
these layers with GeoServer, but I don't have any authorization to
re-organize the layers server side. I'm just trying, client side, after
harvesting, to clean up the metadata in my catalogue to visualize the
layers.
I'm trying to use and customize a little bit the WMS view, for what is
possible to arrange from the CKAN front end (without developing any code),
and I was wondering if it's possible to pass the request from CKAN in a
different way, in order to point directly to a specific layer, or if there
is some customization that I don't know for the WMS viewer.

Thanks a lot,
-Elena









> -----Original Message-----
> From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org
<mailto:ckan-dev-bounces at lists.okfn.org> ] On Behalf Of Alex
> (Maxious) Sadleir
> Sent: martedì 17 dicembre 2013 11:12
> To: CKAN Development Discussions
> Subject: Re: [ckan-dev] default beaviour of WMS viewer
>
> In GeoServer you can put layers in separate workspaces and each workspace
> has it's own WMS link that only contains layers from that workspace.
> So one way to handle this is create a workspace for each dataset and a
layer
> for each data file (if more than one) eg.
> http://data.gov.au/geoserver/geelong-roofprints-kml/wms accesses all
> (one) files from http://data.gov.au/dataset/geelong-roofprints-kml
>
> On Tue, Dec 17, 2013 at 8:54 PM, Elena Camossi
> <elena.camossi at ext.jrc.ec.europa.eu
<mailto:elena.camossi at ext.jrc.ec.europa.eu> > wrote:
> > Hi everyone,
> >
> > I'm trying to visualize in CKAN a dataset that contains several layers
> > in OpenLayers created with GeoServer using the WMS viewer.
> > The layers have been harvested as different datasets, each one is
> > correctly uploaded as WMS in CKAN, but since they point to the same
> > GetCapabilities request, when I open any of them I see always the same
> > layer in the preview (the first the in the GetCapabilities).
> >
> > That would not be that bad, because in theory you can choose
> > interactively the layers to visualize and even overlay different
> > layers... Unfortunately the list of available layers is truncated to
> > the first 14 layers (but there are many others that I cannot see).
> >
> > I have tried putting the GetMap request (pointing to the specific
> > layer) instead of the GetCapabilities in the dataset URL, but the
> > viewer doesn't work, the page remains empty with a Loading... message
> > (I don't get any error in the log, and the Development Console of the
> > broswer says HTTP 200 OK).
> > Anyway, this would not be a good solution in the end because you lose
> > the overlay functionality...
> > As last chance, I manage to visualize the image of the layer modifying
> > its format as a PNG, or GIF, but in this way you loose completely any
> > geospatial functionality.
> >
> > Is there any way to change the default behaviour of the viewer,
> > showing a different layer instead of the first one listed in the
> > GetCapability? Or to configure differently the viewer to show the layer
> using the GetMap request?
> >
> > Thanks in advance for any help.
> >
> > Kind regards,
> > -Elena
> >
> >
> >
> > _______________________________________________
> > ckan-dev mailing list
> > ckan-dev at lists.okfn.org <mailto:ckan-dev at lists.okfn.org> 
> > https://lists.okfn.org/mailman/listinfo/ckan-dev
> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org <mailto:ckan-dev at lists.okfn.org> 
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

_______________________________________________
ckan-dev mailing list
ckan-dev at lists.okfn.org <mailto:ckan-dev at lists.okfn.org> 
https://lists.okfn.org/mailman/listinfo/ckan-dev
Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20131217/16a8d536/attachment-0003.html>


More information about the ckan-dev mailing list