Hello all, or rather hello developers!
In don’t know if this is the right way to contact you. So if there is a better way, please give me a hint J
My Question is:
While using GeoServer to publish our data via services, we experienced some bugs or rather lacks of features, e. g. the interpretation of some definitions in SLDs that were exported from QGIS.
The response/solution of the community to those issues has been to fund further development of those parts.
As some of those features are important for us, we are evaluating the option to take on this suggestion. In that sense, and because I did not find anything on the GeoServer Community sites, I wanted to ask how we could manage this, which options there would be and which would be the one preferred by you.
How would it work if we would hire a contractor and contribute these features to GeoServer?
And for the specific feature of the GeoServer being able to fully interpret all definitions in SLDs exported from QGIS, would you be able to guess the amount of work this would take? In that way, we maybe could estimate the costs of hiring a developer for this feature.
Thank you in advance!
With kind regards
Erik Böhm
Erik Böhm (MDZ2207)
Open Data Coordination
Tel: +49 40 3190-3429
Bernhard-Nocht-Straße 78 | 20359 Hamburg
erik.boehm@anonymised.com
The Federal Maritime and Hydrographic Agency is a higher federal agency under the Federal Ministry for Digital and Transport
To start with you would need to clearly list exactly which features of the SLD generated by QGIS that are not understood by GeoServer.
Ian
···
Ian Turton
Have you tried also the geocat bridge qgis plugin?
Alexandre
···
Ian Turton
See notes inline below:
As some of those features are important for us, we are evaluating the option to take on this suggestion. In that sense, and because I did not find anything on the GeoServer Community sites, I wanted to ask how we could manage this, which options there would be and which would be the one preferred by you.
How would it work if we would hire a contractor and contribute these features to GeoServer?
The GeoServer commercial support page offers a list of companies that can take on this kind of task.
And for the specific feature of the GeoServer being able to fully interpret all definitions in SLDs exported from QGIS, would you be able to guess the amount of work this would take? In that way, we maybe could estimate the costs of hiring a developer for this feature.
As others, I’d urge you to come out with a specific list of features that are missing. In GeoSolutions we did an analysis in the past and come up with a variety of issues
- Bits that could be exported to SLD, but are not (e.g., attribute dependent values and expressions)
- Bits that are exported, but using invalid SLD syntax
- Bits that cannot be exported, because there is no equivalent SLD syntax
The list is large, making an estimate is not very likely. Rather than “I want to export everything possible”,
approach the commercial support providers with a firm list of features you need instead.
Cheers
Andrea