Good point (this was in another app-schema related thread):
http://osgeo-org.1560.x6.nabble.com/Application-schema-plugin-and-filter-encoding-performance-concern-td5325806.html
The documentation just says that "... Joining is turned on by default ..." but
indeed it should only enable
itself for
Hi,
I'm confused, I thought Ben said it's active by default but there is also a
check
that the underlying store is a JDBC one, or it won't activate.
Have I misunderstood?
Cheers
Andrea
On Mon, Jul 24, 2017 at 3:00 PM, Nuno Oliveira <
nuno.olive...@geo-solutions.it> wrote:
> Ah yes joining is ac
Ah yes joining is activated by default, it can be deactivate with a Java
variable:
http://docs.geoserver.org/latest/en/user/data/app-schema/joining.html#configuration
On 07/24/2017 01:40 PM, Markus Jackenkroll wrote:
If someone is searching for the "Joining queries are only supported on
JDBC da
If someone is searching for the "Joining queries are only supported on
JDBC data stores"-error, have a look at
https://sourceforge.net/p/geoserver/mailman/message/35922112/.
You have to change the parameter "app-schema.joining" in the
WEB-INF/classes/app-schema.properties.
On Mon, 2017-07-24 at 14
Hey,
in the layer list there is one with the name "fmis:Fertilization" from
the store "fmis_Fertilization". The layer name seem to remain from my
older configurations. As you said, I published the layer again. Now
there is a layer "fmis:Crop". Requesting this I got the exception:
"Joining queries
The filenames don't influential the layers names.
The error you get (it seems to me) is that GeoServer is not finding the
fmis:Crop layer.
When you got t GeoServer list layers, what names do you see ?
When you got the app-schema store and lick on publish layer what do you see ?
On 07/20/2017 09:
I did so and get:
Feature type fmis:Crop unknown
I am not sure, but my directories and filenames are all named
"fmis_Fertilization". Do I have to change that?
Zitat von Nuno Oliveira :
The example request you show is targeting fmsi:Fertilization type:
http://mygeoserver.uni-hohenheim.de:8
Yes! Markus, please disregard my last email. I re-read your original
question and Nuno is correct.
Kind regards,
Ben.
On 20/07/17 08:51, Nuno Oliveira wrote:
The example request you show is targeting fmsi:Fertilization type:
http://mygeoserver.uni-hohenheim.de:8080/geoserver/wfs?service=WFS&Ve
Markus,
I think you need to change both targetElement and targetAttribute to
fmis:Fertilization.
Kind regards,
Ben.
On 20/07/17 08:12, Markus Jackenkroll wrote:
Hey,
you are right. I changed the target attribute of the ID mapping:
...
The example request you show is targeting fmsi:Fertilization type:
http://mygeoserver.uni-hohenheim.de:8080/geoserver/wfs?service=WFS&Version=1.1.0&Request=GetFeature&typeName=fmis:Fertilization
You probably want to use fmis:Crop as the type name parameter.
On 07/19/2017 09:12 PM, Markus Jackenk
Hey,
you are right. I changed the target attribute of the ID mapping:
...
fmis:Crop
ID
...
After restarting the tomcat
Markus,
sourceType must be the name of the source type (table or view name). If
you want fmis:Fertilization output, use
fmis:Fertilization; this element
specifies the output feature type.
Kind regards,
Ben.
On 18/07/17 02:24, Nuno Oliveira wrote:
Hi,
You are using fmis:Fertilization as th
Hi,
You are using fmis:Fertilization as the target element on the ID mapping.
When using the idExpression the target attribute must be an existing element
in this case it should be fmis:Crop.
Regards,
Nuno Oliveira
On 07/17/2017 03:07 PM, Markus Jackenkroll wrote:
Dear list,
I implemented my
Dear list,
I implemented my own application schema on geoserver. The user interface
shows workspace, store and layer as enabled. Next, I tried to request
the WFS by
http://mygeoserver.uni-hohenheim.de:8080/geoserver/wfs?service=WFS&Version=1.1.0&Request=GetFeature&typeName=fmis:Fertilization.
It
14 matches
Mail list logo
