On Fri, Nov 23, 2012 at 2:48 AM, cmaul christian.m...@dse.vic.gov.auwrote:
Paul,
as far as I see your data are static. You will not need them once you have
created the tiles.
My experience is that databases require 4 -10 times more time to render a
layer than local shape files.
My
Hi,
I've read the geoserver topic, maybe XY has to be inverted, but whatever it
should be inverted in all situation ? i mean in the GetFeatureResponse, and
in my filterRequest.
For exemple :
?xml version=1.0 encoding=UTF-8?
GetFeature
version=2.0.0
service=WFS
Hi,
Clearly EPSG:4258 should use lat-lon (north-east) order in all places if it is
GML3. Thus your filter is right and the response wrong.
The patch is ready but it involves also Geotools;
Looking for solutions I found different aspects on the WPS complex data
management to improve so the patch grew a bit in different directions.
I'm wondering which is the best way to share a draft solution and to agree
on the improvements (please
On Fri, Nov 23, 2012 at 11:56 AM, Fabrizio Tringali ftring...@gmail.comwrote:
The patch is ready but it involves also Geotools;
Looking for solutions I found different aspects on the WPS complex data
management to improve so the patch grew a bit in different directions.
I'm wondering which
Hi again,
I solved the problem. In the whole inconvenient XML jungle you have to
deal with I just overlooked the fact that additionally to the srs tag
there is also the nativeCRS tag which *must* be set in order to have
the layer being published properly. After I added that tag it worked.
All
On Fri, Nov 23, 2012 at 2:21 PM, Matthias Uden matthias.u...@gmail.comwrote:
Hi again,
I solved the problem. In the whole inconvenient XML jungle you have to
deal with I just overlooked the fact that additionally to the srs tag
there is also the nativeCRS tag which *must* be set in order to
Hi,
I'm trying to define a pointsymbolizer with different rules for the vector
shape and the fill color.
Is there a way to define them independently based to the different point
features?
Thanks,
Alfredo
--
Monitor
Even we use currently only mainly output via references I would also expect to
receive binary data in XML in this case. It's nice if you can trust standards
;-)
Von: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Gesendet: Freitag, 23. November 2012 12:10
An: Fabrizio Tringali
Cc:
On Fri, Nov 23, 2012 at 3:24 PM, thomas.wande...@dlr.de wrote:
Even we use currently only mainly output via references I would also
expect to receive binary data in XML in this case. It’s nice if you can
trust standards ;-)
I agree. At the same time code does not write itself (at least, not
I'm running the latest nightly build and I can't get the format_options=DPI
working. No matter what I input, I always get the same image size...
i.e. requests
Hi,
DPI is a hint for the printing software to print the image with a certain
resolution.
http://docs.geoserver.org/latest/en/user/services/wms/vendor.html
In your case for doupling the resotution you must first request more pixels by
using the same BBOX but width=200height=200. Now without
Yeah I totally missinterpreted the meaning. I though if I use a bigger DPI,
the image would automatically be resized. But the DPI is actually used, as
far as I can see - for styling, labeling, etc...To keep them coherent with
the image size. So I have to increase the image size manually through a
Hi list,
I am using the imagemosaic plugin to serve geotiff's produced daily (the store
index gets rebuild after a new image gets added - that works fine).
If i query for a particular date which doesn't exist in the index, an empty
image gets returned - to my mind it should return a 404.
14 matches
Mail list logo
