at gn prefix is missing after CreateStoredQuery POST, i
added it manually in data_dir/wfs/query/querydefinition.xml, but the result
is the same. XML header does not contain gn prefix. Am I missing something
here or this could possibly be a Bug?
Best regards
Davor
uto, 30. lis 2018. u 07:56 Davor
Hi,
just tried POST-ing with returnFeatureTypes="" and it worked. xmlns:gn="
http://inspire.ec.europa.eu/schemas/gn/4.0; is stripped from query
definition in data dir.
Best regards
Davor
pon, 29. lis 2018. u 20:35 Davor Racic napisao je:
> Just an explanation where I
ied with CreateStoredQuery to catch some errors on Geoserver, but
that one was the least expected.
Best regards
Davor
pon, 29. lis 2018. u 19:47 Davor Racic napisao je:
> Hi Andrea,
>
> I tried with that few minutes after posting:
>
> xmlns="http://www.opengis.net/wfs/2.0;
> xm
Hi Andrea,
I tried with that few minutes after posting:
http://www.opengis.net/wfs/2.0;
xmlns:wfs="http://www.opengis.net/wfs/2.0;
xmlns:gml="http://www.opengis.net/gml/3.2;
xmlns:fes="http://www.opengis.net/fes/2.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
ArcSDE 10.3 doesn't exist. You can only connect directly to enterprise
geodatabase, so I'm not sure that ArcSDE plugin which used ArcSDE
middleware or direct ArcSDE database connection is going to work with
Enterprise Geodatabases. They had upgrade database tool:
Hi everyone.
After upgrade 2.11.x -> 2.12.x, geoserver page redirects me to /gwc page
instead of /web, and when I try to go to "Seed->truncate" in Geoserver GUI
i'm getting HTTP 404:
No mapping found for HTTP request with URI
[/geoserver/gwc/rest/seed/workspacename:layername] in
Does anyone have experience with upgrading Geoserver 2.11 + Geofence 3.2 to
Geoserver 2.12. It's not fully clear from docs whether I need Geofence 3.3,
and is it possible to upgrade old db.
I tried with Geofence 3.2 branch, but getting errors in geoserver log:
2018-01-03 20:47:48,854 ERROR
d). Recursive implementations will then use
> O(n**2) time and stack.
>
> Heapsort is often preferred because its worst-case performance is O(n
> log n):
> https://en.wikipedia.org/wiki/Heapsort
>
> Kind regards,
> Ben.
>
> On 20/12/17 03:41, Davor Racic wrote:
> > I'm
I'm using Geoserver 2.11.dev and app-schema plugin. WFS max request limit
is set to 1mil features. When serving large WFS 2.0 requests (over 10
fetures) from app-schema store (PostGIS backend) requests fail with error:
19 pro 09:49:48 ERROR [geoserver.ows] -
java.lang.StackOverflowError
