Thank you, Ian (and Peter).
I had actually considered using gdal_merge.py to combine the GeoTiffs I'd
created, but thought the resulting mega-TIFF would be too large. However:
gdal_merge.py -o elevation.tif -co BIGTIFF=YES -co TILED=YES -co
COMPRESS=DEFLATE *.hgt.tif
worked fine. GeoServer
I have application where user draws arbitrary line over a map, and is presented
with cross-section of terrain from DTM under that line. At the moment, this is
supported by a custom DTM format to make this retrieval fast and memory
efficient (since can be dealing with very large high-resolution
Hey you guys,
I used a large gray image as a store, and then used tile caching to make
it display faster. Do the tile caches apply only to the gray image? I'm
guessing yes since the cached tiles are stored as PNG/GIF/JPG and not
GeoTiffs themselves, but wasn't sure. For example, it's
Hey
I put this question in stackexchange also, although here I think may be
the right place. I'll update either one accordingly when the solution comes
out.
My problem is with GeoServer recognizing a custom CRS. I append my custom
(WKT) projection to the file
Hi,
are you talking about the "queriable" checkbox right before the style
selection?
There should be a queryable element in the layer xml description, it may
not show up if the layer is queriable, as that's the default, e.g:
bmng_topo_bathy
RASTER
raster
http://www.w3.org/2005/Atom;
Hi,
I would expect an issue like that one if your footprints are vector, as the
vectors cannot scale
the same way as pixels (a pixel cannot be split in half, vector data scales
linearly).
If you're not already doing so, try to embed raster masks using gdal and
enable raster footprints.
If you're
Gabriel,
GeoServer 2.11 is not supported, you should give 2.15.x a spin instead.
Anyways, what if you try to open a single image with the JPEG2000 reader?
If it's not in the list of readers, then the GDAL extension needed to read
it, is not installed or its native libs not properly linked.
And oh,
Hi Olyster,
I saw it, but could not put toghether an answer in just a minute so kept on
delaying the answer.
Sorry, I'm overwhelmed with work beyond repair, only the mails that I can
answer super-quickly get answered.
Anyways, I can go for a short and direct response, since I still don't have
Hi,
I suggest to open a ticket at
https://osgeo-org.atlassian.net/projects/GEOS/summary
with a set of data and styles, and a request, that shows how to reproduce
the issue.
The simplest the example, the better
Cheers
Andrea
On Wed, May 22, 2019 at 4:10 PM Johannes Weskamm
wrote:
> This is not
True, but the MVT code should work even in that case, and return either a
404 (if the client can detect the valid range somehow)
or return an empty vector tile (the way I see it at least).
Cheers
Andrea
On Wed, May 22, 2019 at 4:01 PM Ian Turton wrote:
> The solution is to not request tiles
This is not a solution, as the client rendering the tiles does not know
what scaledenominators are set in the sld.
The behaviour should be to not serve any features in the tiles for that
specific layer, but not responding with an code 400.
As i am using a grouplayer, there is in fact a demand to
The solution is to not request tiles outside the specified range.
Ian
On Wed, 22 May 2019 at 14:06, Johannes Weskamm
wrote:
> Hi,
>
>
> Thanks, but the problem is, i do not generate that query by myself, its
> seems to be the code (GeoServer / GeoWebCache / MVT Vectortiles Extension).
>
> The
Either wait until the build server comes back on line fully (which should
be shortly if you have been following the list) or download the source and
build it yourself as the open source license allows you.
If neither of those is quick enough consider contacting a commercial
support provider
Hi,
Thanks, but the problem is, i do not generate that query by myself, its
seems to be the code (GeoServer / GeoWebCache / MVT Vectortiles Extension).
The layer is published as simple table from the database (also checked
if using an sql view differs, but its the same problem).
So the
Hi,
maybe you didn't get the time to read my reply. I don't want to bug you with
that issue but I just want to make sure if you consider it to be a bug.
If yes, should I make the modification as a quick fix to be released or
create an issue in bug tracker or I should maintain my own version of
Hi Guys,
I can`t download the JMS-cluster for version 2.15.1 or 2.14 from anywhere
and the link on the official geoserver website "https://build.geoserver.org/
geoserver/2.15.x/community-latest/"
is giving me nothing and I need this plugin urgently, what can I do ??
Johannes,
There's indeed a syntax problem in your SQL just between the 1st SELECT and
the 1st FROM : SQL expect a list of fields , or a " * "You must select
something...
SELECT FROM (SELECT * FROM osm_waterareas
) as "vtable" WHERE 0 = 1
Benoît DEGRÈVE
Risques sous-sols et
Hi Scott,
Are you setting the tileGrid property when creating the vector layer? If
so, remove it.
I think everyone copies this code off the Geoserver website:
var map = new ol.Map({
target: 'map',
view: new ol.View({
center: [0, 0],
zoom: 2
}),
layers: [new
Hi GeoServer Users!
We've upgraded from GeoMesa 2.2.0 to 2.3.0 and are experiencing an issue with
GeoServer (2.14.3) and the GeoMesa-Filesystem data store plugin now.
We're creating new layers using GeoServer's REST API as follows:
curl -X POST -d @ -H "Content-Type: application/json"
Hi,
First of all, thank you for such a quick reply.
Regarding the Swagger docs, some software stacks enable developers to
automatically generate them. This approach eliminates the need to
maintain documentation, and even serve the docs through a convenient
endpoint that also allows users to
On Wed, May 22, 2019 at 10:40 AM Rui Maciel wrote:
> Hi,
>
> First of all, thank you for such a quick reply.
>
> Regarding the Swagger docs, some software stacks enable developers to
> automatically generate them. This approach eliminates the need to
> maintain documentation, and even serve the
Hi all,
I have troubles getting Mapbox vectortiles from GeoServer in some
circumstances:
I am using a grouplayer with several layers from a PostGIS DB (Postgres
9.3 and PostGIS 2.1.2) in it.
The layer themselves are working fine when previewed / used as WMS.
But when i request the layer as
22 matches
Mail list logo
