I apologize for offending you, but I still strongly disagree with being
called out for using "flamebait". I was addressing a technical capability,
not trying to offend a developer or critique what anybody has done or the
code they have written.
The word "disable" or "disabled" can also invoke
I disagree with the term "flaimbait". Definitely not my intention.
Perhaps something is being lost in translation?
I was attempting to emphasize that there is a very useful/powerful
construct in place (the advertised input classes in the SPIs) that
GeoServer isn't really taking advantage of and
access?
>>>> We are not that comfortable making our wiki publicly editable, and just
>>>> completed an activity removing inactive committers.
>>>> --
>>>> Jody Garnett
>>>>
>>>>
>>>> On Fri, 14 Feb 2020 at 21
publicly editable, and just
>>> completed an activity removing inactive committers.
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Fri, 14 Feb 2020 at 21:27, Josh Fix via Geoserver-devel <
>>> geoserver-devel@lists.sourceforge.net> wrote:
&
enough to allow wiki
> access?
> We are not that comfortable making our wiki publicly editable, and just
> completed an activity removing inactive committers.
> --
> Jody Garnett
>
>
> On Fri, 14 Feb 2020 at 21:27, Josh Fix via Geoserver-devel <
> geoserver-devel@lists
Thanks Andrea. Proposal is up (thanks Torben):
https://github.com/geoserver/geoserver/wiki/GSIP-188
On Fri, Feb 14, 2020 at 11:38 AM Andrea Aime
wrote:
> Hi Josh,
> not much to add, looks good to me
>
> Cheers
> Andrea
>
>
> On Thu, Feb 13, 2020 at 8:36 PM Josh
Hi all,
I'm looking to propose a new extension point in ResourcePool. The long and
short of it is, the ResourcePool attempts to instantiate
GridCoverageReaders and ImageInputStreams by analyzing the input object
passed to it. ImageInputStreams in particular advertise an "inputClass",
which is
Well my very simple idea did in fact just get very complicated! Thank you
very much for the detailed explanation. I'm not ready to give up on this,
but with very tight time constraints, I think I'll focus on the GDAL
virtual file system reader first and revisit this later.
On Thu, Jul 18, 2019
ndle that case, not sure how ready the GetFeatureInfo
>machinery is, along with the gml/json/text/html encoders. But it would sure
>be useful in some cases (e..g, I click on a mosaic image and get
> information about cloud cover, snow cover, off nadir and so on)
>
> Cheers
>
g the
> other granule properties at the same time, or is that already available
> - The handling of interpolation sounds a bit suspect, may be better to
> return the nearest neighbour FID and attributes
>
> --
> Jody Garnett
>
>
> On Wed, 17 Jul 2019 at 13:48, Josh Fix vi
I was interested in submitting a PR to enhance the GetFeatureInfo response
for image mosaics, but thought I would post here first.
When GetFeatureInfo is called on an image mosaic, the pixel values are
returned in a table. The first column of the table is "fid", but is never
populated. I would
11 matches
Mail list logo
