Thanks very much for that. I am quite happy with a fixed axis order in returns
but my problem was trying to find out what axis order to use when assembling a
polygon cql filter in the client where the client cannot control what EPSG are
in use. I didn't realize the axis order could be part of
Hi Andrea, All,
I managed to install GeoFence and I think it's going to serve our needs.
However, I'm seeing an exception in a wfs GetFeature xml response and the
features (that were requested and served into OpenLayers just fine before I
installed GeoFence) do not display. Here's the exception
Thank you Andrea for the quick answer and help pointing me in the right
direction.
I had already read the online resource, and figured out that I would have to
look in the code to see what it does.
Unfortunately disabling the filter altogether breaks something and geoserver,
as when I reload
Thank you Erik,
After some further research another solution would be to customize the
content ftl/template to show only desired columns.I will try to implement
this solution
https://gis.stackexchange.com/questions/6009/how-to-select-
fields-returned-by-geoserver-wms-getfeatureinfo-request
On
Hi Andrea,
Thanks very much for this amount of detail! I'll try re-configuring the
service security and GeoFence and report back if I find a solution.
Best,
Todd
On Thu, Jun 28, 2018 at 6:23 AM, Andrea Aime
wrote:
> Hi Todd,
> I believe that is just not possible with the current code, at
Hi,
yes, there is indeed something going on there... but I have no idea why.
Please open a ticket at
https://osgeo-org.atlassian.net/projects/GEOS/summary , including a sample
dataset, style, and a request that makes it happen on that dataset.
And then be patient, we have very little time
Hi,
all you shared so far are debugging logs which might or might not be
related to an actual issue
(e.g., could be that the previous version of GeoServer was doing the same,
but had less logging statements).
Can you share the WMS request that makes it happen? The logs do not report
anything about
Hi Todd,
I believe that is just not possible with the current code, at least
concentrating on the data security.
In GeoServer we have two interfaces that can access data, FeatureSource,
read only,
and FeatureSore, read/write, this influenced also the implementation of the
security subsystem,
Dear all
I have some more info. In the logs I found
2018-06-28 10:57:20,788 DEBUG [org.geotools.referencing.factory] - Failure in
the primary factory: No code "EPSG:3857" from authority "European Petroleum
Survey Group" found for object of type "IdentifiedObject". Now trying the
fallback
Hi,
The axis order of EPSG:3031 seems to be officially easting-northing
http://epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::3031
while EPSG:2193 is using northing-easting order
http://epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::2193
In valid GeoJSON the coordinates are
10 matches
Mail list logo
