Hi Geoserver Team,
I installed geoserver 2.14.0 version and whenever I am executing
OGC(CSW-2.0.2) test suite it will giving
Error 1: assertion failed:
The exception report must have @version = "1.2.0".
The reported version number is 1.0.0.
Please Help me what am I doing wrong?
--
Dipak
hi,
im using geoserver 2.11.0, with elasticsearch as datasource.
i also use leaflet vector tiles plugin to request the tiles.
i have noticed that when use leaflet map controller, in certain zooms the
geoserver doesn't return all geometries (in deeper zoom it shows more
geometries).
i checked w
Ciao Pedro,
I don't see anything strange from this info.
You might want to make this geotiff available for us to have a look at
(if/when we have time :) ).
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Sim
Hi, Simone.
The style:
http://www.opengis.net/sld";
xmlns:gml="http://www.opengis.net/gml"; xmlns:ogc="http://www.opengis.net/ogc";
xmlns:sld="http://www.opengis.net/sld";>
PrecipAnual-2016i
Hi,
May not be related to just this case, but if image mosaic is built from images
having different CRS then the calculated levels in the .properties file may
need manual fix. For example, if coverage is published in EPSG:3067 but
originals are either in EPSG:2393 or EPSG:3067, both having pixe
Le 31/10/2018 à 15:21, Andrea Aime a écrit :
Hum.. I cannot exclude it (but I'm not sure without checking the code).
Did you provide a TypeName in the indexer, to tell the mosaic which
table to use? Wondering if doing so might convince it to actually use
the table in question.
No, indeed. Exc
On Wed, Oct 31, 2018 at 3:16 PM Arnaud L. wrote:
> OK, I have a guess.
> In the FOLDER referenced by the index there are some GeoTIFFs whose
> level is 2.54.
> None of these GeoTIFFs are referenced in the index though.
> Could it be that the imagemosaic plugin does a scan on the entire
> folder,
Hi Arnaud,
I don't know what's happening there honestly, the property files that
GeoServer
generates normally match the gdalinfo output... but I haven't worked with a
simple, uniform
mosaic in a while (most of what comes my way these days is either
heterogeneous in resolutions
or has downright diff
Le 31/10/2018 à 14:59, Arnaud L. a écrit :
Why would the imagemosaic plugin guess that levels are 2.54 ? Is there
something wrong in the way I configured the imagemosaic ?
OK, I have a guess.
In the FOLDER referenced by the index there are some GeoTIFFs whose
level is 2.54.
None of these GeoT
Le 31/10/2018 à 14:03, Andrea Aime a écrit :
No, you are still supposed to let the mosaic configure itself. Never,
ever, generate
the mosaic property file manually, setup a indexer and a datastore
config files
and let the mosaic do its work, regardless of where the index is stored.
OK Andrea,
Hi,
This is almost definitely really niche but I thought I'd send the message in
case it is relevant for any reason. We have a view in our Oracle database which
takes a spatial table (source of GeoServer store) and joins it with non-spatial
data from another Oracle database which is not in our
Dear Pedro,
we need to see the styles and the output of gdalinfo --stats on this image
before saying anything.
Can you provide them?
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simog
On Mon, Oct 29, 2018 at 12:45 PM Nanaso via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:
> Hi,
> Thanks a lot Nuno for your reply.
> There are two issues:
> 1- The Geofence extention can satisfy my needs in the following way: I
> have an attribute in my layer called "user_name",
Hi,
I don't think the WFS-Insert could resolve the postgresql function
current_setting().
You should insert your user data with SQL.
GeoServers SQL View can resolve current_setting() and can combine/join
it with your user data to return only records the current myapp.user
should see.
Regards,
St
On Wed, Oct 31, 2018 at 1:04 PM Arnaud L. wrote:
> Hi Andrea
>
> Le 31/10/2018 à 13:00, Andrea Aime a écrit :
> > thanks for sharing! It would have been hard to guess that you had a
> > image mosaic without sample image,
> > those files are mandatory and manual generation of the mosaic setup is
>
Hi,
Thanks a lot Stefan for your perfect solution.
I have tested what you mentioned and it works pretty fine. But there is one
remaining issue. That is how to pass the current geoserver's username to the
database? I've a field in the geometries table called "user_name". It should
hold the owner
Hi Andrea
Le 31/10/2018 à 13:00, Andrea Aime a écrit :
thanks for sharing! It would have been hard to guess that you had a
image mosaic without sample image,
those files are mandatory and manual generation of the mosaic setup is
uncommon.
Is it ? But manual generation is mandatory when one us
Hi,
thanks for sharing! It would have been hard to guess that you had a image
mosaic without sample image,
those files are mandatory and manual generation of the mosaic setup is
uncommon.
Cheers
Andrea
On Wed, Oct 31, 2018 at 12:01 PM Arnaud L. wrote:
> Le 30/10/2018 à 14:04, Arnaud L. a écrit
On Wed, Oct 31, 2018 at 12:45 PM Johannes Weskamm
wrote:
> Maybe you could give me a hint where (files / classes) development for
> this should start off.
>
I don't have time to produce a list, but this commit added "nearest match"
for time in WMS, and it touches
many of the same files/classes th
Hi,
You are right, the queries itself could be fast. I identified my
SQL-View of the layer to be the problem.
When requesting the layer via WMS, the resulting SQL query made by
geoserver will always contain an AND filter for the timestamp, which
makes the service working fast.
But when requestin
Le 30/10/2018 à 14:04, Arnaud L. a écrit :
When there are granules in the bbox, even when they only partially cover
the area, the region where there is no granule is transparent.
But when there are really no granule to load at all, the resulting PNG
is fully black, with no transparency.
[...]
So
Hi,
there is indeed no way to configure GeoServer with static time domain
values (could be done, needs coding, preventive discussion on the
devel list and then implementation according to the published contribution
rules).
However, finding min and max should be fast if you have an index on the
time
I have already checked that, and tried the different options, sadly it
does not change the time it takes to generate the capabilities document.
I tried dynamic values and also hardcoded timestamps, the result is the
same (timeouts).
I think geoserver is still asking the database for the min and m
You can create a ticket (see standard footer on email), but please be aware
that this probably isn't a high priority right now.
Brad
-Original Message-
From: mikeluz
Sent: Wednesday, 31 October 2018 9:27 PM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Removin
How are you specifying the Default value strategy?
If you change that to Reference Value, you can use a form like
fromValue/toValue. It's also possible to use relative times like
P1M/PRESENT, but note that the reference value is copied verbatim into the
capabilities document, which might not be wh
Hi Brad,
yes, I figured that unpublished would not delete system files, but removing
story would. But as you said this is just not implemented... anyway, is
there anything I can do, create a ticket or to do something about it ? Was
this done deliberately, or just someone has forgotten about it ?
Hi list,
I am trying to configure the range of time my WMS-Time enabled Layer can
be used for.
The problem i have is, that requesting the capabilities document slows
down the machine for several minutes and i receive a timeout.
Diving deeper into the issue i realized that geoserver asks my data
Conceptually you should be removing the data store, not just unpublishing
the layer.
However from
https://github.com/geoserver/geoserver/blob/master/src/restconfig/src/main/j
ava/org/geoserver/rest/catalog/DataStoreController.java#L217 it looks like
the purge (deleteType) option didn't actually ge
Hi,
"Is it possible to decide which users can access which features in a layer?"
I'm using the following solution for postgis datastore/layer:
* set a Session startup SQL (and session close-up SQL) in the
datastore. This will set a variable with the current GeoServer user.
e.g. startup
Hi everyone,
I am have a bit problem with removing the SHP layer using the
it.geosolutions library, but I think it is general Geoserver REST API
problem. My question or problem is that when I unpublish/remove a layer
using:
/
publisher.unpublishFeatureType(WORKSPACE, STORE, layerName);
/
the laye
On Wed, Oct 31, 2018 at 10:07 AM Ian Turton wrote:
> It's been a while since I did this but I think I set the profile in the
> maven -> set maven profiles menu for the gs-web module. Though I use the
> built in maven in eclipse rather than eclipse:eclipse so it may not work
> for you.
>
Been a w
It's been a while since I did this but I think I set the profile in the
maven -> set maven profiles menu for the gs-web module. Though I use the
built in maven in eclipse rather than eclipse:eclipse so it may not work
for you.
Ian
On Tue, 30 Oct 2018 at 20:21, Olyster wrote:
> Hi,
>
> I have an
32 matches
Mail list logo