regarding expected
preconditions and/or conventions for on-the-fly mappings.
Best,
Matthias
From: Rahkonen Jukka (MML) [mailto:jukka.rahko...@maanmittauslaitos.fi]
Sent: Wednesday, June 15, 2016 2:42 PM
To: Matthias Müller; GeoServer Mailing List List
Subject: Re: [Geoserver-users] GML
, with different
mappings per service
The quickest solution for you is probably to setup a sql view that
amends the names and
ids so that they are compliant. This works as long as you don't have
to edit via WFS-T of course.
Cheers
Andrea
On Wed, Jun 15, 2016 at 10:58 AM, Matthias Müller
Hello everyone,
We are running a Geoserver instance with Postgres/PostGIS backend. Everything
seems to work fine so far, except for WFS with GML.
We have two specific issues here:
1) The auto-generated feature IDs (see [1]) do not comply with the QName
convention. We use UUIDs to identify our
Done.
https://jira.codehaus.org/browse/GEOS-6590
Regards,
Matthias
-Ursprüngliche Nachricht-
Von: simbo...@gmail.com [mailto:simbo...@gmail.com] Im Auftrag von Simone
Giannecchini
Gesendet: Dienstag, 22. Juli 2014 07:54
An: Matthias Müller
Cc: geoserver-users
Betreff: Re: [Geoserver
, Jul 16, 2014 at 9:01 PM, Matthias Müller
matthias_muel...@tu-dresden.de wrote:
Hi folks,
is there a way to let Geoserver handle a multi-band Geotiff as a
temporal mosaic? I have a large collection of GeoTiffs that each have
about 1000+ bands. The temporal reference is related to the bands
Hi folks,
is there a way to let Geoserver handle a multi-band Geotiff as a
temporal mosaic? I have a large collection of GeoTiffs that each have
about 1000+ bands. The temporal reference is related to the bands in the
following way:
data.tif#band1: 01-2006
data.tif#band2: 02-2006
Thanks for the hints, Andrea.
If we provide fixed values for time and spatial extent when creating the
layer - would that avoid the execssive data base queries?
Am 20.02.2013 16:26, schrieb Andrea Aime:
On Wed, Feb 20, 2013 at 3:46 PM, Matthias Müller
matthias_muel...@tu-dresden.de
Andrea Aime:
On Thu, Feb 21, 2013 at 1:19 PM, Matthias Müller
matthias_muel...@tu-dresden.de mailto:matthias_muel...@tu-dresden.de
wrote:
Thanks for the hints, Andrea.
If we provide fixed values for time and spatial extent when creating
the layer - would that avoid the execssive data
Hello list,
are there any best practices on offering a large number of WMS layers
with geoserver? We are operating a geoserver instance that has about 600
time-enabled vector layers (loaded from a postgres database) which
causes two problems:
1) The capabilities take a very long time (5
I see. We sometimes apply compression to some large data sets to avoid
excessive disk I/O (which was the main bottleneck in some cases). Of
course, the decision depends on the data and geoserver's hardware.
Cheers,
Matthias
Am 15.11.2011 08:33, schrieb Andrea Aime:
2011/11/14 Matthias Müller
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Matthias Müller
Dipl.-Geogr. | Research Associate
Technische Universität Dresden
Geoinformation Systems
01062 Dresden
Phone: +49 351 463-31953
Fax: +49 351 463-35879
Mail: matthias_muel...@tu-dresden.de
www: http://tu-dresden.de/fgh
Hi Akos,
gdaladdo doesn't generate any extra files - it just stores the pyramids
in the original tiff file. if you issue the command for the first time
you will notice an increased file size.
cheers,
matthias
Am 14.11.2011 14:35, schrieb Ákos Maróy:
Matthias,
This gdal command mosaics all
Hi Andrea,
I wasn't aware of that.
Is there also support for GeoTiff Compression Predictors in the 2.2.x?
GDAL supports predictive compression but Geoserver didn't like those
files when I tried it the last time.
Cheers,
Matthias
Am 14.11.2011 13:30, schrieb Andrea Aime:
2011/11/14 Matthias
Hi Christian,
thanks for the hint and appreciation for your work. I am planning to use
this module on a PostGIS Datastore - if you have a documentation I'd
really like to read it. Right now I am diving into the subtleties of
feature generalization.
Decimal degrees are a bit tricky as the real
14 matches
Mail list logo
