Looking forward to seeing everyone next week, following up to our meeting
we have established a couple of GeoServer activities to look forward to at
FOSS4G.
We are setting up shop at the OSGeo booth Thursday 17 August at 12:00,
bring your lunch and lean more about open source, geoserver, and our
Hi,
This error:
"No top level element found in schemas"
Typically happens when app-schema cannot find the top XSD element used in the
mapping
of a feature type, in this case probably the nested (chained) feature type.
Consider this example:
(...)
datastore
Hello,
I'm trying to use app schema to expose a simple feature that have attributes
with cardinality 0...N as :
In database, I create another table with foreign key in the main table.
I tried to use feature link but an error raised "No top level element found
in schemas". It shouldn't be
Hi all,
I believe that Jody request got misunderstood, he's not asking about
missing features, he's asking
about your preferred _existing_ features (or the "wow I did not know
GeoServer could do that" ones,
which are still existing ones you weren't aware of... until you found out
:-p )
Cheers
Hi,
I experienced this error and it was the result of having an incorrect XPath
to the element (therefore making Geoserver believe the element didn't
exist). For example, if you are trying to map to an element
gsml:myTarget
which is contained in
gsml:containingElement
you have to specify the
Provide a Layer Preview utility that allows displaying multiple layers, and
using a user-defined base map.
On Sun, Aug 6, 2017 at 5:07 PM, Jody Garnett wrote:
> For me I got a see first hand out some nifty features that I had only ever
> read about before:
>
> 1)
Hi again,
I would like to add that I think this could be a bug in Geoserver's App
Schema. I frequently encounter this error when I'm working on my mapping
files (adding tags for example) and the fix is almost
always restarting Geoserver, reloading the file used in the App Schema Data
Access, and
Hi,
Is there a limit to the number of feature chained elements possible in a
single feature? I have 10 mapping files, performing feature chaining and
each file maps between 4 and 10 elements. I've noticed that I don't seem to
be able to go further. If I comment out a single it
works but if I add
Gavin,
there is no limit in app-schema, but you might be hitting a limit in the
size of the JDBC connection pool. You can increase this by using JNDI
and configuring a larger number of connections.
Very recent changes should improve app-schema connection usage:
[GEOT-5748] Improve
Thank you! That answers my question. We need to work on the database.
On Tue, Aug 8, 2017 at 3:32 PM, Ben Caradoc-Davies wrote:
> On 09/08/17 04:52, Gavin Medley wrote:
>
>> I have the data for siteName and iersDOMESNumber in Table1 and the data
>> for
>> monumentDescription
Hi Jody,
First, a "wow" moment. At UNAVCO, we are experimenting with a new way to
compose GNSS site logs. We have a Geoserver connected to our database and
we have successfully mapped most of our site log data into the foriegn
GeodesyML schema using the App Schema extension for Geoserver. There
11 matches
Mail list logo