Safe FME and GeoServer
OpenGeo and Safe Software have been talking about working together to make life easier for users of FME and GeoServer. We’ve both been hearing more about organizations using FME to solve their data conversion challenges and then making the results available to the world using the OpenGeo Stack.
While many people are making things work with the software now, we figure that a few improvements towards tighter integration could be a big win. Our end goal is to enable FME Server and GeoServer to work together seamlessly. This allows each piece to solve the area they excel at - GeoServer in OGC standards and web output formats, FME at complex data conversions and translations. With a few key improvements the combined solution should solve the ‘Community Schema’ problem that Ron Lake recently brought up better than any software in world. In time the GeoServer community will definitely build the capability to handle the full community schema transformation natively, but integrating with FME should provide a transitional path, and FME will always be ahead in terms of the most advanced translations.
If you are a user of both FME and GeoServer we’d love to hear from you with input on how we could work together to make your life easier (or you can just give us encouragement ;). We are still in the early stages, hoping to put together a rough prototype relatively soon, but beta testers in the future will be appreciated. And of course additional funding will enable us to prioritize the work and get it done faster. If you are interested in helping out please get in touch at the OpenGeo contact form.
Vulnerability
- GeoServer 2.26.1 Release
- GeoServer 2.25.4 Release
- GeoServer 2.26.0 Release
- CVE-2024-36401 Remote Code Execution (RCE) vulnerability in evaluating property name expressions
- GeoServer 2.25.2 Release
- GeoServer 2.24.4 Release
- GeoServer 2.23.6 Release
- GeoServer 2.25.1 Release
- GeoServer 2.25.0 Release
- GeoServer 2.23.5 Release