Hi Andrea,
Thanks for your help. I also found the log in GeoWebCache and did a comparison
with non populated tile cache :-).
I thought I would double check by asking the list to cover all the bases - in
case it's used elsewhere.
Thanks again.
Cheers
Rini
Hi list,
We notice a warning about Native JAI not being installed in the log files. I
did a simple WMS GetMap performance comparison with and without native JAI, and
they seem to be pretty much the same. Does anyone know if/how native JAI affect
performance?
WARN [layer.MetaTile] - *
Hi Ben, Valentina,
This is a bug indeed. I tried creating secondary namespace for xlink and it
doesn't work.
Thanks for reporting. I'll try to fix this before I start my year long leave in
6 weeks time.
https://jira.codehaus.org/browse/GEOT-4894
Cheers
Rini
-Original Message-
From:
It sounds like joining is turned on, i.e. only 2 queries run, but the filter
involves nested attributes from another table.
This kind of filter currently isn't incorporated into the SQL query yet, thus
the inefficient iterating through the features.
This is a gap we're looking to fix. The
Hi Ryan,
I suspect it has something to do with your style.
Is it referring to some properties that don't exist in the complex feature type?
This might help:
http://docs.geoserver.org/latest/en/user/data/app-schema/wms-support.html
Some examples in the unit tests here:
That's a good idea, but that would make it more complicated to implement.
Will consider it when I have the time to do this.
Cheers
Rini
From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea
Aime
Sent: Tuesday, 15 October 2013 2:01 PM
To: Angreani, Rini (CESRE,
Perhaps we could improve the joining setting by applying it per feature type,
instead of per GeoServer instance.
I raised this task, but I can't commit on working on it anytime soon.
https://jira.codehaus.org/browse/GEOT-4596
-Original Message-
From: Caradoc-Davies, Ben (CESRE,
Hi,
That's not possible with the current joining implementation, as it uses INNER
JOIN between the linked tables - not possible across different databases.
It has to use the old implementation (without joining), which is painfully slow
for large datasets.
It's probably OK for demonstration
Hi,
Ben is quite right. The id ordering is used to handle multivalued properties.
If idExpression is missing, it will order by primary key.
If you don't want it to select v_super_class.sub_id, then perhaps you can
set idExpression to map to another column.
Hi John,
Judging by the SQL error, your problem seems to be different from the bug I
fixed.
I'll have a look at your workspaces (from Ben) and see if I could spot a
configuration issue.
Cheers
Rini
From: John Callahan [mailto:john.calla...@udel.edu]
Sent: Monday, 2 September 2013 2:24 PM
To:
Hi John,
This looks like a bug when idExpression is not specified:
https://jira.codehaus.org/browse/GEOT-4554.
While I'm fixing the bug, you can use a workaround by specifying idExpression
to your database id column.
Hi Marcus,
I missed the import but you're right, it's there. My theory is that the
imported location
(http://schemas.geosciml.org/cgiutilities/3.2/cgiUtilities.xsd) didn't exist at
the time (as mentioned in my last reply), but it must've been added recently
because the link now works. If you
Hi Miguel,
This sounds like a bug introduced in 2.2 release.
If you're using 2.2.x, please use 2.3 instead and see if it fixes the problem.
Cheers
Rini
From: Miguel R. Luaces [mailto:lua...@lbd.org.es]
Sent: Wednesday, 3 April 2013 2:14 PM
To: Caradoc-Davies, Ben (CESRE, Kensington)
Cc:
Hi Julián,
Like Ben said ValueReference is not yet supported with app-schema (although
this may change soon if IGN work gets committed).
This would explain why your filter results return the wrong results with
property files.
GetFeature: asking for an AdminUnitName that is situatedwithin the
Hi,
Due to increasing demands, I made app-schema joining turned on by default.
This means joining will take effect even if app-schema.joining parameter is not
specified in app-schema.properties.
If you want to override it, you can set it to false.
The default joining value will be ignored for
Hi Marcus,
Actually I found out how to fix it without joining. The issue with xlink:href
happens because there are multiple rows that are unordered (the xlink:href-ed
rows weren't grouped with the rows with the same gml:id).
This means you need to index your data by the gml:id. I forgot about
Hi Marcus,
Sorry for the late reply. That one seems like a bug too, but probably related
to the xlink:href bug since it makes the output corrupted with invalid
xlink:hrefs.
Before I go on to investigate, can you tell me if you're using joining?
Cheers
Rini
-Original Message-
From:
Hi Marcus,
I could recreate the invalid xlink:href problems without joining.
With joining, I couldn't recreate the problem. It would be faster with joining
too.
I guess it's about time I make joining the default behaviour.
Also, I think the problem with your filters should be solved with
Hi Marcus,
It would be good to see the configuration mapping files to investigate the
empty gsmlgu:GeologicUnit/.
It's strange that there's a child inside an xlink:href. Also, I'm not able to
access your links.
Re: the 2nd issue (ValueReference filter). This is WFS 2.0 filter syntax and
not
Hi Marcus,
The xlink:href with wfs:member seems like a bug. I will include the fix for
next month's plan.
https://jira.codehaus.org/browse/GEOT-4406
Re: filtering. ValueReference is not implemented in app-schema. WFS 1.1.0 uses
PropertyName, which is supported.
WFS 2.0 specific syntax are
I actually thought about it. We should do it now that more people (should) use
joining.
-Original Message-
From: Caradoc-Davies, Ben (CESRE, Kensington)
Sent: Wednesday, 6 February 2013 3:56 PM
To: Andrea Aime; Angreani, Rini (CESRE, Kensington)
Cc: Gavin;
Hi Lukas,
It seems to me your feature chaining doesn't work because your element names
are different.
You are expecting heart:Time element when the chained type is a
heart:AvailableTime element.
You could either:
1) Change the HeartStarter definition so AvailableTimes contains AvailableTime
Hi,
We have never tried it before and there is no such test case, but I don't see
why it won't work.
If there is no binding for the type, during encoding it will fall back to
ComplexSupportXSAnyTypeBinding where id is handled.
Cheers
Rini
-Original Message-
From: Caradoc-Davies, Ben
Hi Alessandro,
I had a look at the code that throws the exception and it seems like a bug.
I have raised a JIRA issue for this: https://jira.codehaus.org/browse/GEOT-4196.
As a workaround, you have to duplicate the non-feature type mapping and give it
a different mappingName.
Thanks for
Yes, this issue is still open in our internal JIRA. I have reopened the JIRA
issue on Codehaus and updated it with the possible solution (to introduce a
configurable tag).
Cheers
Rini
From: alessandro marrone [mailto:alessand...@hotmail.it]
Sent: Friday, 20 April 2012 5:05 PM
To: Angreani, Rini
If you only map the client property and no values for the element, it will be
skipped if minOccurs = 0 for the element.
This was a requirement to skip empty tags with no values (except when
xlink:href is also specified).
However, since Alessandro mentioned that he mapped almost everything, this
Well I haven't worked on the patch (and test) yet. But, I created JIRA issue
for next iteration: http://jira.codehaus.org/browse/GEOT-4006.
The workaround should work for now.
Cheers
Rini
From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea
Aime
Sent: Wednesday, 11
Actually, no the workaround doesn't work. Sorry.. was a bit hasty.
From: Angreani, Rini (CESRE, Kensington)
Sent: Wednesday, 11 January 2012 5:08 PM
To: 'Andrea Aime'
Cc: geoserver-users@lists.sourceforge.net
Subject: RE: [Geoserver-users] [ExternalEmail] Re: app-schema WMS
Well I haven't worked
28 matches
Mail list logo
