GeoTools / GeoServer Meeting 2014-06-10
Attending
---------
Ben Caradoc-Davies
Andrea Aime
Jody Garnett
Jukka Rahkonen
Sampo Savolainen
Justin Deoliveira
Agenda
------
* wfs-ng
* next release
* outstanding pull requests
* guava
* WFS SWG:
- CITE tests for WFS 2.0
- OWS-10 Service Integration (GetAssociation)
* GeoNode problems with GeoServer?
Action items from last meeting
------------------------------
- (JD) Template for the proposals
- (AA) Link proposals wiki from the web site
- (AA) Hit the button on pull request #591
- (JG) Blogpost on GeoServer code sprint (save the date!)
wfs-ng
------
Will wfs-ng work for everyone?
Not quite, gt-wfs had some fun axis order hacks that are required to "Correct" a few misguided WFS servers out there in the wild.
So we will need to keep both around for a while
Q: Why was this not picked up for wfs-ng?
A: It is getting done ... but was missed during the initial port.
wfs-ng not a drop-in replacement ... yet! Niels will race to try and get this done in available time.
How to handle migration:
- gt-wfs as "core"
- gt-wfs-ng as "extension"
What is "drop in replacement"?
- same parameter names
- parameter names to "Adjust/Correct" axis order
- anything else?
Q: What happens to stored queries work? Pull request from Sampo does it against wfs-ng, core changes that need wfs-ng to be core
Q: State of sync between Niels' work and Sampo's work? Sampo took a branch yesterday, Niels has made two pull requests since then.
Options forward:
* bring all in at one time, synch Niels and Sampo work
* otherwise... missed it
Niels seems to be almost done (but no confirmation).
One more data point, feature freeze is in 1 month 8 days, so whatever we do, needs to be done "quickly"
Q: How about Rini's pull request about wfs-ng app schema:
https://github.com/geotools/geotools/pull/406
A: Not the focus for this round
a) Justin will test in the next couple of days
b) Swarm merge from gt-wfs to gt-wfs-ng in geoserver
c) Jody is sitting this one out .. but has tested in uDig
d) Look Rini's patch, if upgrade smooth merge this one too
e) Sampo's work merge
Release Schedule
----------------
Jody work on release this month
Outstanding pull requests
-------------------------
Limited discussion to pull requests of interest to those in this meeting
1) [GEOS-6524] Allow python wps processes to fill the input and output Parameter metadata section
Review needed? Justin +1 Merged.
2) [GEOS-6522] Add support for raw inputs and outputs to GeoServer WPS
Note: This is GeoServer specific, see mailing list discussion ...
Q: Do need access to Request?
A: Nope ...
Q: Direct response output?
A: No GeoServer encodes the draw data in Base64 or something
Q: Anything else missing?
A: Indicate which outputs are being grabbed up front (ie output number 2 of 3)
4) Fix handling of NPE in AdvancedDispatchFilter
Whitespace changes ... at the end of lines
5) Migrate GeoServerPersister to GeoServerResourceLoader (GSIP-106)
Q: Any idea what is going on?
A: Feedback with Andrea (making this safe for multiple GeoServers to write a file) ... we expect Kevin is down to build issues.
A bunch from GeoTools, Andrea is going to nominate a colluge who now writes test cases
Guava
-----
Upgrade to v 17 already done.
Newest versions, if you use annotations there are separate jars now, gwc already upgraded.
Andrea delegates the choice of upgrade of Guava on the stable series to people that know Guava better than him
OGC WFS/FES SWG
---------------
WFS Standards Working Group - report from Ben
- OGC TC meeting in Geneva on Wednesday (16:00 Geneva time)
- Presentations by Peter Vretanos in WFS session:
- CITE tests for WFS 2.0
- OWS-10 Service Integration (GetAssociation) to discover relationships between services
Get a bit of linked data action going into the OGC Standards. Not full REST, but allows some of that functionality.
GeoNode problems with GeoServer
-------------------------------
Problems doing WFS-T Transactions - they were going to drop into the meeting? But they not here ...
Basically the schema cache gets cleared each time a layer is added. So how to stop this?
Patch submitted that only recalculates the changed layer, rather than all of them.
Q: Does the patch have at test case?
A: Even if it does we will need to look at the performance implications for the normal "Smaller" GeoServer uses case.
Justin will see if he can have a look. So take this to email ...
FOSS4G Code Sprint
------------------
Ideas:
- Wicket?
- or ... wait for it ... upgrade CITE tests! Yay!
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre