On Tue, Feb 16, 2016 at 12:05 AM, Martin Davis wrote:
> Are you suggesting that GeoServer computes the scale at a single known
> point for all map request extents, no matter where on the globe they are
> located?Does the OGC standard specify this?
>
The OGC standard basically defines (brace
Hi Jonathan,
my guess is for some records the MY_DATE column is NULL... can you check?
On Fri, Feb 12, 2016 at 5:00 PM, Jonathan Moules <
jonathan-li...@lightpear.com> wrote:
> Hi List,
> (GeoServer 2.7.1)
> I'm trying to use the label feature to choose a label based
> on a date (newest
Hi Stefano,
that's my guess as well. Some years ago David made an effort to make most
filter functions null
safe (null in, null out, instead of thowing a NPE) but I guess this one was
not part of the lot
Cheers
Andrea
On Tue, Feb 16, 2016 at 9:48 AM, Stefano Costa <
stefano.co...@geo-solutions.it
First things first. Thanks for all the previous answers, especially to
Anrea...While playing with WFS settings, I noticed that In Services->WFS
pagethere is a combo with a name Workspace. It's empty. What's the use of this
combo?
There is a service level option I can select basic or transactiona
Hi,
I have an issue with starting multiple geoserver instances.
I have 3 geoservers (version 2.3.5) in 3 different tomcats, using java
version "1.6.0_45".
All 3 have the same geoserver_data_dir.
When geoservers starts up (all at the same time), one of the geoservers
keeps the datastore enable, an
The recommendation is not to have more than one GeoServer instance writing
to the data directory ever! The outcome is pretty much undetermined once
you do that. Look at using one of the clustering modules (
http://boundlessgeo.com/2013/04/geoserver-in-a-clustered-configuration-part-1/)
or the JDBC
Hi Brian,
I'm a bit short on time to help out at the minute. It sounds like you
have a pretty clear bug report.
I know the issue tracker is here:
https://osgeo-org.atlassian.net/projects/GEOS/issues. If you'd like to
report the bug yourself, you may need to ask for an account on this
list
Thanks. I've filed it.
https://osgeo-org.atlassian.net/browse/GEOS-7429
-Brian
On Tue, Feb 16, 2016 at 9:28 AM, Jim Hughes wrote:
> Hi Brian,
>
> I'm a bit short on time to help out at the minute. It sounds like you
> have a pretty clear bug report.
>
> I know the issue tracker is here:
> htt
Thanks, Andrea. I suspected this might be the cause of the issue.
Is there a way to view the scale computed for a map request? That might
let us correlate the client (geodetic) scale to "OGC scale", so we can
translate between the two.
On Tue, Feb 16, 2016 at 12:40 AM, Andrea Aime
wrote:
> On
On Tue, Feb 16, 2016 at 6:10 PM, Martin Davis wrote:
> Thanks, Andrea. I suspected this might be the cause of the issue.
>
> Is there a way to view the scale computed for a map request? That might
> let us correlate the client (geodetic) scale to "OGC scale", so we can
> translate between the t
Thanks for the advice - and for the warning. Sigh
On Tue, Feb 16, 2016 at 9:35 AM, Andrea Aime
wrote:
> On Tue, Feb 16, 2016 at 6:10 PM, Martin Davis wrote:
>
>> Thanks, Andrea. I suspected this might be the cause of the issue.
>>
>> Is there a way to view the scale computed for a map requ
Good news on this. Further experimentation revealed that it is possible
to get reasonably good agreement between scales in OpenLayers and GeoServer
using the following approach:
- use OpenLayers NON-geodesic (nominal) scale calculation
- set OpenLayers DOTS_PER_INCH to match the GeoServer value
12 matches
Mail list logo
