I note from last weeks board f2f meeting that a small donation was made to GeoServer project to forward SLD interoperability with QGIS ( a source of frustration for the OSGeo community).
This donation of $1500 from OSGeo:UK for a specific task (QGIS/GeoServer SLD interoperability) which is a little unusual for a donation. The treasurer asks that we action this within a calendar year (to avoid treasurer overhead), and has added this to the OSGeo budget page.
Off the top of my head I can think of two decent approaches to improving QGIS SLD interoperability:
Set up QGIS to export an SLD export that makes use of GeoTools vendor options
Improve expression mapping from QGIS functions to GeoTools functions
Most of this work would seemly be done in GeoTools or QGIS respectively. Andrea you have more experience here, do you have any other suggestions for where improvement could be made?
Options to proceed:
Ask if any members of our community are willing to work on this - if so they could propose a small “statement of work”.
Write our own statement of work, possibly adding some of our own GeoServer budget into the mix, and invite interested parties to respond
My preference is to ask our community members (read party has obtained commit access).
Hi Jody,
GeoSolutions is keen to take on this. The evident missing bit right now it raster symbolize exchange, it
needs work on both sides, QGIS to export a SLD 1.1 raster symbolizer (completely missing right now),
and likely Geotools XSD parser (I see some support, but it’s likely missing bits here and there).
I don’t have a precise statement of work for it, we are going to put together one in the next few days
I note from last weeks board f2f meeting that a small donation was made to GeoServer project to forward SLD interoperability with QGIS ( a source of frustration for the OSGeo community).
This donation of $1500 from OSGeo:UK for a specific task (QGIS/GeoServer SLD interoperability) which is a little unusual for a donation. The treasurer asks that we action this within a calendar year (to avoid treasurer overhead), and has added this to the OSGeo budget page.
Off the top of my head I can think of two decent approaches to improving QGIS SLD interoperability:
Set up QGIS to export an SLD export that makes use of GeoTools vendor options
Improve expression mapping from QGIS functions to GeoTools functions
Most of this work would seemly be done in GeoTools or QGIS respectively. Andrea you have more experience here, do you have any other suggestions for where improvement could be made?
Options to proceed:
Ask if any members of our community are willing to work on this - if so they could propose a small “statement of work”.
Write our own statement of work, possibly adding some of our own GeoServer budget into the mix, and invite interested parties to respond
My preference is to ask our community members (read party has obtained commit access).
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.