GeoTools / GeoServer Meeting 2014-05-27
Attending
---------
Ben Caradoc-Davies
Andrea Aime
Jody Garnett
Jukka Rahkonen
Agenda
------
- pull request overview
- foss4g presentations
- Nodata handling in GeoTools coverages
- Validation ideas for WPS inputs?
Action items
------------
- (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!)
Actions from last meeting
-------------------------
- AA: switch the proposals to the wiki
https://github.com/geoserver/geoserver.github.io/wiki/Proposals
Quite a bit of work, pandoc + aaime for the win!
Only page to have trouble? Jody's fault: https://github.com/geoserver/geoserver.github.io/wiki/GSIP-106---ResourceStore-API
Everything else came across fine.
Tips for the new wiki:
1) Links
[title](page)
2) Voting sections
Add in bullet points
3) Cannot do nested lists so don't even try
4) Markdown has syntax to do tables
| col1 | col2 | col3 |
|------|+----+|-----+|
| |centered|right aligned|
Todo:
- Template for the proposals
- Link proposals wiki from the web site
Pull request overview
---------------------
- Discussion on Kevin's pull request. Discussion around ResourcePool using a visitor to turn file references into absolute file references. Andrea prefers the use of resource locator (which allows the parser to look up images correctly).
- ImageIO-ext 1.1.10 upgrade. Need to backport a fix to stable branch, to enable work.
- Transparency GIF, contribution agremeent sent, need a test case.
- #590 DDS Plugin - waiting on contribution agreement
- Jarrod / Ericson: code editor wicket editor, upgrade code mirror (shuts out Internet Explorer 6 and 7). Waiting on browser based fallback to plain text area.
- #581 Path Mapper extension, waiting to be merged. GSIP is good etc.
- KVP parse patch, need to run cite tests, so in limbo
Foss4g Presentations
--------------------
1) We got a combined State of GeoServer and State of GeoTools.
- Feature / Product talk is the GeoServer one
- RnD / Development: GeoTools, ImageIO-Ext, Marlin-Renderer, etc...
A longer time slot, rapid pace, try and keep up.
2) GeoServer Feature Frenzy: Jody / Andrea
- like state of geoserver, but all the good stuff for the last 10 years.
3) Advanced Security: Andrea / Simone
4) Mapping in GeoServer with SLD and CSS: Andrea / Simone
Anyone else with GT/GS presentations/workshops accepted? Please let us know.
5) WPS Shootout: Jody was looking into participation
Workshops:
- GeoServer Style workshop: Jody/Mike
- GeoTools DataStore workshops: Jody/Eva
- Web mapping with OGC services and GeoServer: an introduction (short, Andrea)
- GeoServer: from journeyman to master
- Intro to GeoServer: Benjamin Trigona-Harany
- GeoWebCache in Production: Benjamin Trigona-Harany
- SpatioTemporal data handling with GeoServer: an introduction with examples for MetOc and Remote Sensing data for WMS and WCS (Simone)
- Enterprise class deplyoment for GeoServer and GeoWebCache: optimizing performances and robustness
- Introduction to high availability clusters with GeoServer and GeoWebCache (Andrea)
- From data to maps and services with MapStore, GeoServer GeoNetwork and CKAN (Simone)
Nodata handling in GeoTools coverages
-------------------------------------
Nothing to see here move along.
Need to improve our Data Processing in terms of raster no-data aware. This is because JAI likes to process everything, so we probably need to trick out the whole chain to check for no-data.
This results in a complete rewrite of all the JAI Operations (mostly interpolation) so that they don't die. So nearest-neighbor 1 pixel in 1 pixel out. Everything else check the sample as you go and adjust average based on the number of real pixels involed:
TLDR: Migrate Raster Processing chain to https://github.com/geosolutions-it/jai-ext
Q: License? Not picked yet, probably LGPL since that is what it says in pom.xml
That may cause Jody some problems for LocationTech, and I suppose ImageIO-Ext as well.
Validation in WPS?
------------------
Q: When is WPS 2.0 going to come out?
How to check if inputs are valid? Well the "right answer" is to check against the schema. Schematron is often used for extra credit validation checks.
How to we go from the annotations out to enforce restrictions on the inputs.
Well in that case the Param thing offers Filters?
Answer after discussion:
1) Parameter metadata map for Filter
2) Annotation taking a String to be parsed as ECQL
3) Input names can be referenced via PropertyName allowing cross input validation
This is a reply of a conversation with Victor
Discussion
----------
Jody had a joint workshop with uDig and Oracle Raster last week at Location Intelligence. Had a few fun ideas for possible future contributions.
Jukka has bravely signed up for stack exchange:
- Sccored 400 points of reputation in two weeks, but does not feel rewarded. He enjoys beer not points
- After 50 points of reputation you can start adding comments, which is esential for asking for test data, java version, etc...
- Many of these questions are hard. AA: Can you direct them to mailing list? JR: To links of old mailing list discussions.
- Many questions are simple, hand out documentation links as they have not read the docs.
- A few following old tutorials that no longer work.
- Many are actually open layers questions
- AA: stackexchange good for multi-topic problems
- Tag for multiple topics
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre