Hi Andrew,
in geotools we call this issue pixel is center vs pixel is corner.
OGC mandates the pixel is center interpretation as far as I know, see
also:
http://gis.stackexchange.com/questions/122670/is-there-a-standard-for-the-coordinates-of-pixels-in-georeferenced-rasters
Hi Mike,
I think that the only way to investigate into the issue is to debug the
code.
Do you have any chance to open a JIRA for this?
I think you can simply paste the explanations you provided in this email.
Please, also attach the sample zip, containing data (even fake pixels but
proper naming),
On Tue, Mar 31, 2015 at 10:48 PM, Martin Davis mtncl...@gmail.com wrote:
An update on this issue, which I think identifies the source of the
problem with the slow WFS query.
After experimenting with using the SDE Java API against the troublesome
table, I found that the order of API calls is
Hi,
A direct link for finding the issue faster:
http://jira.codehaus.org/browse/GEOS-6948
I tested the nightly build with Firefox 36.0.4 on Windows and fix seems to be
OK and the active area is only the check box.
However, an opposite issue that prevents changing the status of some check
Hi,
I believe that this is totally grey are in WCS 1.0.0 but for WCS 2.0 there
seems to be two papers which are not official standards but maybe sort of
recommendations:
https://portal.opengeospatial.org/files/?artifact_id=51141
https://portal.opengeospatial.org/files/?artifact_id=51142
From
Hi Mike,
have you already considered using REST PathMapping in GeoServer? It allows
you to change the REST base directory, keeping the same
workspace/coveragestore structure.
Here you may find more information:
- http://docs.geoserver.org/stable/en/user/webadmin/server/REST.html
-
Hi Andrea,
I'd suggest you to take this giant geometries and clip them on a regular
grid, separating polygon and outlines as two different shapefiles, just like
OSM did for the world countries layer, to avoid the very same problem you're
facing (geometries that are excessively large). And
On Wed, Apr 1, 2015 at 11:49 AM, Nachtigall, Jens (init)
jens.nachtig...@init.de wrote:
…and would it help to set the default meta tiling settings to 20x20
instead of 4x4 – or is this only relevant when GeoServer “asks” for tiles
but not for seeding?
Yes, I believe that would help, if you
On Tue, Mar 31, 2015 at 3:19 PM, Nachtigall, Jens (init)
jens.nachtig...@init.de wrote:
For OSM rendering with mapnik for same extent and much more features, it
took just a few days. So I really do not get it, why it takes weeks for a
damn simply Shapefile.
Hi Jens,
thanks a lot for
…and would it help to set the default meta tiling settings to 20x20 instead of
4x4 – or is this only relevant when GeoServer “asks” for tiles but not for
seeding?
Best,
Jens
--
Dive into the World of Parallel
On Wed, Apr 1, 2015 at 2:12 PM, Luís de Sousa luis.a.de.so...@gmail.com
wrote:
Dear all,
I am querying a GeoServer 2.4.3 instance with DescribeCoverage
requests using WCS version 1.1.0. But the response document refers to
WCS version 1.1.1, with an header like:
wcs:CoverageDescriptions
Hi Andrea, thank you for the swift reply.
If GeoServer does not support WCS 1.1.0, why is it responding to
requests? Shouldn't it issue an unsupported version message of some
sort?
I use OpenLayers and OWSLib and neither support WCS 1.1.1, only 1.1.0.
Would you have any suggestion on how to get
On Wed, Apr 1, 2015 at 2:55 PM, Luís de Sousa luis.a.de.so...@gmail.com
wrote:
Hi Andrea, thank you for the swift reply.
If GeoServer does not support WCS 1.1.0, why is it responding to
requests? Shouldn't it issue an unsupported version message of some
sort?
Yes and no... they are all
On Wed, Apr 1, 2015 at 4:03 PM, Nachtigall, Jens (init)
jens.nachtig...@init.de wrote:
Hi,
On Wed, Apr 1, 2015 at 11:49 AM, Nachtigall, Jens (init)
jens.nachtig...@init.de wrote:
…and would it help to set the default meta tiling settings to 20x20
instead of 4x4 – or is this only
Hi,
On Wed, Apr 1, 2015 at 11:49 AM, Nachtigall, Jens (init)
jens.nachtig...@init.demailto:jens.nachtig...@init.de wrote:
…and would it help to set the default meta tiling settings to 20x20 instead of
4x4 – or is this only relevant when GeoServer “asks” for tiles but not for
seeding?
Yes, I
Argh... that code snippet for the CORRECT use of spatial constraints
should read:
query = new SeQuery(conn, columns, construct);
query.prepareQuery();
query.setSpatialConstraints(...);
And agreed, it seems like it's unlikely that WFS alone uses a different
call order. As you say, it may
Hi Andrea,
Thanks for the links; those are incredibly helpful. We are asking since
we supporting a use case which involves imagery (pixel by area) and
elevation (pixel by point) together.
Just to make sure, it sounds like gdal's 'pixel by area' maps to 'pixel
is center', right?
Thanks
Hmmm... in ArcSDEQuery.calculateResultCount() start at line 615 I see:
[1] 615: query.setSpatialConstraints(searchOrder, calcMasks,
spatialFilters);
and then a few lines later in a code path that is executed only if the SDE
instance is versioned and backed by Oracle:
[2] 631:
Hello All,
I have multi-point time series data in postgis that I want to serve out
via geoserver for display using Open Layers. I would like to represent
the value at each point as a proportional symbol (circle) and animate
through each step in the time series. I did this in an earlier
Daniele,
I have spent about 5 hours today putting together an extensive set of test
data, indexer files, and cases for this to submit a JIRA ... but JIRA will
no longer let me submit issues for GeoServer under my account, even though
I have done so in the past. Have you guys locked down who can
On Wed, Apr 1, 2015 at 7:03 PM, Mike Pumphrey m...@boundlessgeo.com wrote:
Hi all. As part of the 2.7 release process I got to copyedit the new
color-blending docs, but not actually go through the example.
Hi all. As part of the 2.7 release process I got to copyedit the new
color-blending docs, but not actually go through the example.
http://docs.geoserver.org/2.7.0/user/styling/sld-extensions/composite-blend/example.html
I'm doing that now, and finding that the SLD as saved doesn't validate:
So there is still some work to do for Firefox.
Any problem back porting this change to stable?
--
Jody Garnett
On 1 April 2015 at 00:21, Rahkonen Jukka (MML)
jukka.rahko...@maanmittauslaitos.fi wrote:
Hi,
A direct link for finding the issue faster:
Just wanted to call this out - one of our groups recently got the okay to
open source an internally developed geoserver - elasticsearch datastore
plugin.
https://github.com/ngageoint/elasticgeo
Documentation is at:
Thanks for confirming. Drat, wishing I had just tested validation of the
existing SLD when I was copyediting.
Not being sure whether this is a GeoTools or GeoServer issue, where should I
ticket this?
Thanks,
Mike
Mike Pumphrey
User Advocate | Boundless
m...@boundlessgeo.com
That is cool Chris - do you (or the group responsible) want to do a guest
blog post for the geotools blog?
--
Jody Garnett
On 1 April 2015 at 15:09, Chris Bennight ch...@slowcar.net wrote:
Just wanted to call this out - one of our groups recently got the okay to
open source an internally
26 matches
Mail list logo