I have tried with default templates and custom templates with the same
result. When I say "order" I mean column order as in PostGIS table DDL or in
Feature Type Details in Layer Properties. When you say "If you have not
specified a freemarker template for the request then I do not expect there
to
If you have not specified a freemarker template for the request then I do
not expect there to be any specific attribute order implied in the
getfeatureinfo specification. If you have to have a fixed order of some of
the attributes then a freemarker template is probably the best way to go.
Ian
On
Sorry, those were default templates. This is my custom setup:
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329630.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
So with the previous template with no Geofence rule limiting attribute
access, GetFeatureinfo request orders columns as they are listed in tabel or
layer property. With Geofence rule, they have no particular order, and
subsequent request can have even different order from previous requests.
--
I have tried with default templates and custom templates with the same
result. When I say "order" I mean column order as in PostGIS table DDL or in
Feature Type Details in Layer Properties. When you say "If you have not
specified a freemarker template for the request then I do not expect there
to
Dear Andera
I cant store the vector and raster output of wps in geoserver.
may you please explain the using of gs:Import.
thanks
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/how-to-store-geoserver-wps-raster-output-as-layer-in-geoserver-tp5329035p5329631.html
Sent from
Dear Jody Garnett
for each datastore that I selected the error occurred. I want to store my
result in store but I do not know what to do :(
may you please explain the using of gs:Import.
Regards
yousef
--
View this message in context:
Hello Andreas
1) Is Geoserver supposed to use the embedded data dir in the application
> server, too, maybe as fallback for missing configs or is that directory
> never used at all?
>
The embedded data dir should only be used if an external data dir is not
specified, or if the external data dir
Hi everyone
I'm having strange problems with GetFeatureinfo requests when restricting
access to some of layer attributes. After that column order in getfeaturinfo
request results is messed up - reordered. I could see that following
requests change that order again.
This kind of rule order
Hi Torben,
many thank for your response. And yes, the "point", "line", and "generic"
styles from the application server embedded data directory are also referenced
by the layers in our regular, external data directory, in many cases ("polygon"
is not because we only use polygons with custom
Hi,
I think this is a bug, probably in App Schema, but I want to ensure I'm not
doing something wrong before filing a report. I am using App Schema to
output GeodesyML for WFS requests. I noticed recently that Geoserver fails
to resolve one of my namespaces in GetFeature requests. This confused
But in freemarker a feature's attributes are stored in a map so there is no
expected order to them. If you require an order then you should define it.
Ian
On 28 Jul 2017 18:44, "dracic" wrote:
> Ok. I think I'm not clear enough. I do not want any specific order. I
>
Hi, Dylan,
I had some travis build issues, but it's built now. I asked torben to
kick-off a nightly build; it should be done in an hour or two.
Please give it a try when its done,
Dave
On Thu, Jul 27, 2017 at 12:16 PM, Dylan Parry wrote:
> That's excellent!
Ok. I think I'm not clear enough. I do not want any specific order. I would
like generic behavior - which is the one when Geofence rules don't apply
and that is that the attributes are ordered in the way they are listed in
database tables or in attribute list in geoserver layer properties. So that
Gavin,
both of these problems are likely caused by the lack of a secondary
namespace.
I saw the difference in encoding (the xmlns on the non-root element),
which is odd. Incremental improvements might have changed the
manifestation of the problem (no longer an exception), and
Can we compare the configuration of your new store+layer to the old
store+layer?
If you use the rest api, or look in the data directory at the xml files,
you should be able to see the configuration that is stored. We are trying
to spot a different, not all of the configuration is editable in the
Hi Ben,
That's probably what it is. I don't have a secondary namespace for gml.
Weird that it's not throwing an error when encoding the response.
With respect to your second question, we do see wfs:FeatureCollection and
wfs:ValueCollection when using App Schema. However, in the
I always disable gs:Import (since in a production instance I do not want to
let clients add content to my server).
I am looking for a reason your datastore is read-only:
a) it could be security - please check
http://docs.geoserver.org/latest/en/user/security/layer.html
b) it could be file
Dear Geoserver Users
I cant store the vector and raster output of wps in geoserver.
may you please explain the using of gs:Import.
thanks
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/storing-wps-results-in-geoserver-tp5329652.html
Sent from the GeoServer - User
19 matches
Mail list logo