request with FeatureID: ~210ms
Best Regards,
Bernhard
Von: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] Im Auftrag von Andrea
Aime
Gesendet: Montag, 05. März 2018 10:11
An: Bernhard Kiselka
Cc: Ian Turton; geoserver-users@lists.sourceforge.net
Betreff: Re: [Geoserver-users] GeoServer
/geoserver/medford/ows?service=WFS=1.0.0=GetFeature=medford:buildings=230
takes only 250ms
Best regards,
Bernhard
Von: Ian Turton [mailto:ijtur...@gmail.com]
Gesendet: Donnerstag, 01. März 2018 16:14
An: Bernhard Kiselka
Cc:
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.so
Hi list!
I did not do so much research as in https://gis.stackexchange.com/a/82305 but
as my data increased, my CQL_FILTER containing IDs that shall be rendered
increased from 600 to 1800 (20 kilobyte of filter string!) and GeoServer
response time increased from 1 second to 5 seconds.
Does
updating to 2.2.2 all works fine.
Cheers,
Bernhard
-Ursprüngliche Nachricht-
Von: Bernhard Kiselka
Gesendet: Donnerstag, 29. Oktober 2015 16:29
An: geoserver-users@lists.sourceforge.net
Betreff: Possible bug rendering postgis data?
Dear list!
I have some lines imported to postgres by osmosis
Dear list!
I have some lines imported to postgres by osmosis and rendering the data with
the default line style as wms in geoserver 2.7.1.1 fails for scales more zoomed
out than 1:70K (though working zoomed more in), failing with the following
message:
org.geotools.data.DataSourceException:
Hi List!
I upgraded from GeoServer 2.1.3 to 2.4.2 and experienced the following problems:
1) Changed Axis Ordering with WFS 1.1.0 Filtering using URN-Projections
Worked and works only in GeoServer 2.1.3: Provide coordinates as
latitude/longitude (y/x)
Example:
