I would start by making a ticket outlining what is required, and then contact the module maintainer for netCDF for suggestions on how to proceed.
If there is significant API change that would affect others, the module maintainer may recommend writing a proposal ( https://docs.geotools.org/latest/developer/procedures/proposal.html). For new functionality that needs an API change we make major releases twice a year (making roadmap planning easier). We do this so frequently to support consultants that only get paid when the needed functionality is available for download. When we did releases once a year releases got delayed for "one more thing". Worst case roadmap change available in six months. If the new functionality is additive and does not need an API change, it can be backported to the stable branch after a month. This gives people a chance to try try out the functionality and ensure it does not compromise stability. Best case roadmap change available in 2 months. GeoTools matches release schedule with GeoServer, but our proposal process is a little more relaxed. -- Jody Garnett On Fri, Feb 2, 2024 at 4:44 AM Amirhossein Nikfal <ah.nik...@gmail.com> wrote: > The NetCDF plugin supports those NetCDF files which conform to a special > convention (COARDS). > How can Geoserver or Geotools be developed to support other NetCDF > conventions? What are the possible roadmaps for such a task? > > Best regards, > Amir > _______________________________________________ > GeoTools-Devel mailing list > GeoTools-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
