Re: [Geoserver-users] WFS GetCapabilities failures

yes indeed. i create H2 database tables, some w/ and others w/o a geometry column. after publishing the first geometry-less one as a layer, the WFS GetCapabilities calls for both 1.0.0 and 1.1.0 versions fail. you are also correct in pointing out the UI does not allow geometry-less layers.

[Geoserver-users] Unable to update 'cached' image mosaic image

Hi all I'm using Geoserver 2.9, and I'm wondering about how Geoserver caches the image mosaic images. My set up 1. in the Database, I use the field 'dataset_id' to uniquely identify the image, and the path to the image is also stored. 2. I try to view the image like this

Re: [Geoserver-users] WFS will not read the same date that it stores

I am pretty sure that was me. But I'll check tomorrow. Ian On 13 Oct 2016 19:54, "Andrea Aime" wrote: > Ian, going by memory and answering from my tablet... didn't someone > contribute a patch to make > dates timezone independent? With a system variable to set

Re: [Geoserver-users] WFS will not read the same date that it stores

Ian, going by memory and answering from my tablet... didn't someone contribute a patch to make dates timezone independent? With a system variable to set that? Cheers Andrea On Thu, Oct 13, 2016 at 8:22 PM, Ian Turton wrote: > That sounds like a regression to me, when I'm

Re: [Geoserver-users] WFS will not read the same date that it stores

That sounds like a regression to me, when I'm back at my desk, I'll dig out the previous tests and check how that slipped in. Can you raise a bug in the meantime so I don't forget. Ian On 13 Oct 2016 16:28, "Walter Stovall" wrote: > Thanks for the advice.

Re: [Geoserver-users] WFS GetCapabilities failures

So are you configuring geometryless layers via the REST interface? The UI should not allow null bounding boxes even on geometryless layers. Cheers Andrea On Thu, Oct 13, 2016 at 6:45 PM, Raif S. Naffah wrote: > i believe what i'm seeing is explained by > >

Re: [Geoserver-users] WFS GetCapabilities failures

i believe what i'm seeing is explained by https://osgeo-org.atlassian.net/browse/GEOS-7216 On Wed, 28 Sep 2016 12:32:57 +1000, Raif S. Naffah wrote: > hi all, > > working w/ GeoServer 2.8.5 i'm getting sporadic failures when > requesting WFS capabilities. the failures show up in the >

Re: [Geoserver-users] WFS will not read the same date that it stores

Thanks for the advice. Unfortunately following that path does not work for me. I still end up with dates that are one-behind. This was discovered with a more complicated arrangement, but I have this problem in my simple test environment where my geoserver is deployed to a local tomcat 8 on my

Re: [Geoserver-users] WFS will not read the same date that it stores

The GeoTools/GeoServer data handler should use the timezone of the server (so if that is set to GMT then you need to convert before sending). This allows for servers where clients can be in multiple timezones and need to agree a fixed timezone when communicating with the server. If you are the

[Geoserver-users] WFS will not read the same date that it stores

Using GeoServer2.8 I'm having a very basic problem with WFS-T inserting a feature that has date fields. When I do a GetFeature to retrieve the date I inserted, I get a value that's one-day prior to the date I inserted. This appears to be related to the GeoTools xsDateTimeFormat class used to