Is there any work in progress or planned for supporting MySQL 8?
I am getting below exception with MySQL 8.0.13 and GeoServer 2.14.2 on
clicking LayerPreview.
Caused by: java.sql.SQLSyntaxErrorException: FUNCTION nyosm.asWKB does not
exist
at
hi all,
is it possible to write a WFS filter that intersects a subset of the
geometry from one layer with a subset of the geometry from another layer?
This is mainly for performance reasons.
In the below query I am intersecting a subset of geometry over the whole
base layer. Instead, can I first
Hi Norman.
Usually in Store factories it's used an URL typed parameter to parse the
"url" user input as we see on Shapefile one:
public static final Param URLP =
new Param(
"url", URL.class, "url to a .shp file", true, null, new
KVP(Param.EXT,
Hi,
I actually read the question the other way around... WMS is fine, WFS
output is problematic.
If that's the case, I'm wondering if it may be a case of number of decimals
in the layer configuration?
I think the default, if no value is provided, or if a value <= 0 is set, is
like 6 decimals,
Hi,
We developed a Geoserver extension to provide real time raster image
data from IBM PAIRS (ibmpairs.mybluemix.net) repository.
As part of the cleaning up of our extension, we would like to introduce a
custom Connection schema ( "ibmpairs") specific to our plugin. This schema
would appear
Did you turn off "Support on the fly geometry simplification" in your
postgis store? Otherwise you will see the simplification you see by default.
Ian
On Mon, 21 Jan 2019 at 14:06, Vanda A. Marcos
wrote:
> Hello,
>
>
>
>
>
> We are dealing with some problems in some of our WFS. The geometry
Hello,
We are dealing with some problems in some of our WFS. The geometry that is
shown, doesn't correspond to the original geometry.
As you can see in the image, the blue line is the correct geometry in a WMS,
the red line is the wrong geometry in the WFS. It seems a kind of
generalization
Thanks Nuno
I solved the issue.
Different wfs settings (global vs workspaces)
Bart
From: Nuno Oliveira
Sent: zaterdag 19 januari 2019 0:32
To: Verbeeck Bart (AIV) ;
geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] srsName OGC HTTP URI storedquery
Hi,
I have tried to
Great, thank you for the feedback !
On Mon, 2019-01-21 at 12:20 +, Verbeeck Bart (AIV) wrote:
> Thanks Nuno
>
> I solved the issue.
> Different wfs settings (global vs workspaces)
>
> Bart
>
> From: Nuno Oliveira
> Sent: zaterdag 19 januari 2019 0:32
> To: Verbeeck Bart (AIV) ;
Dear all,
In order to full fit inspire WFS requirements we need to create stored queries.
The problem is that we have several workspaces in GeoServer and it only works
for the first workspace introduced in the "code". We don't know if it is
anything bad in the peace of code or if that isn't
>
> You lose a lot of flexibility, but that's the only solution that
> worked 100% of the time for me.
I'm using the label-on-point approach as well right now, but as you've
correctly noted, it is less flexible than it could be with label-on-polygon
one.
Apart from the afore-mentioned necessity
Hi,
for those having WPS plugged in there is also a better polygon label
function called "labelPoint":
http://docs.geotools.org/latest/userguide/library/main/function_list.html#labelpoint-polygon-tolerance-labelpoint
I don't know what the tolerance parameter means though. Ian (cc'ed) do you
Le 21/01/2019 à 10:37, Eugene Podshivalov a écrit :
Sorry, yes, your are right, it does work but with point (centroid)
labeling you lose the possibility to render the label relative to the
polygon size. You will need to define the arae-zoom ranges manually in
the style, won't you?
Yes
Sorry, yes, your are right, it does work but with point (centroid) labeling
you lose the possibility to render the label relative to the polygon size.
You will need to define the arae-zoom ranges manually in the style, won't
you?
Cheers,
Eugene
пн, 21 янв. 2019 г. в 12:09, Arnaud L. :
> Hi
Hi Eugene
Le 21/01/2019 à 09:57, Eugene Podshivalov a écrit :
That solution works only for un-tiled requests.
Maybe I haven't understood you requirements then, because I use this
'trick' on some tiled wms request and it works great for me.
It guarantees a single label location, however you
Hi Arnaud,
That solution works only for un-tiled requests.
Cheers,
Eugene
пн, 21 янв. 2019 г. в 11:06, Arnaud L. :
> Hi Eugene
>
> Le 20/01/2019 à 18:52, Eugene Podshivalov a écrit :
> > Meta-tiling resolves most of the issues with duplicated labels but they
> > are still happening on
GeoWave + GeoServer plugin have a great managing raster timeseries. GeoWave
digests imagery from several raster datasources (Landsat8, Sentinel-2,
THEIA...).
There are two articles about this topic could be interesting for you:
GeoWave also advertises support for GeoServer
(https://locationtech.github.io/geowave/userguide.html#geoserver-2)
Best is an impossible question to answer though - it depends on your precise
needs. If your needs are proprietary and real time, perhaps WFS is not going
to be a good fit.
Hi Eugene
Le 20/01/2019 à 18:52, Eugene Podshivalov a écrit :
Meta-tiling resolves most of the issues with duplicated labels but they
are still happening on geometries which cover several meta-tiles. You
can see that illustrated on the diagram below.
Would it be possible to resolve it by
19 matches
Mail list logo
