Jody/GeoTools Community, I would just like to help GeoTools upgrade to JSR 385 ( https://www.jcp.org/en/jsr/detail?id=385 ) (from JSR 363). Unfortunately this upgraded API is not backwards compatible so some modifications need to be made. GeoTools upgrading to the newer API would allow projects to use JSR 385 in their projects because including libraries from both JSRs causes classpath problems. Also the new API is designed to work with Java 8 enhancements and Java 9 Modules.
I have commit the initial work to https://github.com/ddcruver/geotools/tree/update-to-jsr-385-units-2.0. Everything compiles and builds but some test failures are still present. I ran a Travis-CI build for my branch: https://travis-ci.org/github/ddcruver/geotools/builds/680853088 Let me know if you can't access the Travis build; I am new to this service. I have resolve some of the issues but some more remain. 1.) It doesn't seem to be "auto correcting" to degrees in all cases. See *org.geotools.measure.UnitsTest#testUnitsMatch2* 2.) Doesn't yet handle *NetCDF *Units completely has problems with *DU * unit. *org.geotools.coverage.io.netcdf.NetCDFUnitParserTest.SimpleTests#testDU* 3.) *ImageMosaicReaderTests#testGranuleFileViewSidecars and #testGIFSupportFiles* INFO] Running org.geotools.gce.imagemosaic.ImageMosaicReaderTest [/mnt/c/Users/daniel.cruver/Build/Libraries/geotools/modules/plugin/imagemosaic/target/test-classes/org/geotools/gce/imagemosaic/test-data/rbgFileView/global_mosaic_0.prj, /mnt/c/Users/daniel.cruver/Build/Libraries/geotools/modules/plugin/imagemosaic/target/test-classes/org/geotools/gce/imagemosaic/test-data/rbgFileView/global_mosaic_0.pgw, /mnt/c/Users/daniel.cruver/Build/Libraries/geotools/modules/plugin/imagemosaic/target/test-classes/org/geotools/gce/imagemosaic/test-data/rbgFileView/global_mosaic_0.PGW, /mnt/c/Users/daniel.cruver/Build/Libraries/geotools/modules/plugin/imagemosaic/target/test-classes/org/geotools/gce/imagemosaic/test-data/rbgFileView/global_mosaic_0.PRJ] [ERROR] Tests run: 91, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 29.848 s <<< FAILURE! - in org.geotools.gce.imagemosaic.ImageMosaicReaderTest [ERROR] testGranuleFileViewSidecars(org.geotools.gce.imagemosaic.ImageMosaicReaderTest) Time elapsed: 0.515 s <<< FAILURE! java.lang.AssertionError: Expected: iterable over [equalToIgnoringCase("global_mosaic_0.prj"), equalToIgnoringCase("global_mosaic_0.pgw")] in any order but: Not matched: "global_mosaic_0.PGW" at org.geotools.gce.imagemosaic.ImageMosaicReaderTest.testGranuleFileViewSidecars(ImageMosaicReaderTest.java:5584) [ERROR] testOverviewSupportFiles(org.geotools.gce.imagemosaic.ImageMosaicReaderTest) Time elapsed: 0.248 s <<< FAILURE! java.lang.AssertionError: expected:<2> but was:<4> at org.geotools.gce.imagemosaic.ImageMosaicReaderTest.testOverviewSupportFiles(ImageMosaicReaderTest.java:4898) [ERROR] testGIFSupportFiles(org.geotools.gce.imagemosaic.ImageMosaicReaderTest) Time elapsed: 0.026 s <<< FAILURE! java.lang.AssertionError: expected:<6> but was:<12> at org.geotools.gce.imagemosaic.ImageMosaicReaderTest.testGIFSupportFiles(ImageMosaicReaderTest.java:4854) There are more failures but my local test build keeps on failing on database connections. Thanks, Dan On Fri, Mar 13, 2020 at 5:38 PM Jody Garnett <jody.garn...@gmail.com> wrote: > I would love to see this work go ahead! Anything we can do to support you? > > As for plans this is an open community please make a proposal - and then > you are part of the planning :) > > On Fri, Mar 13, 2020 at 11:03 AM Daniel Cruver <ddcru...@gmail.com> wrote: > >> In GeoTools 20.x, the units library was updated from JSR 271 to JSR 363 >> Units (Units 1.0). Which was a great improvement because I was >> encountering classpath issues before I upgrade my projects to using a newer >> version of GeoTools. I am using JSR 385 in my project but adding GeoTools >> still causes additional ServiceProvider to be available that are >> incompatible and cause the process to close if I access them. This can be >> avoided but another problem is that including GeoTools on my projects also >> adds incompatible unit and systems to the classpath and causes confusion. >> >> JSR 363: >> systems.uom:systems-common-java8:0.7.2 >> >> JSR 385: >> systems:uom:systems-common:2.0.0 >> tech.units:indriya:2.x >> >> Basically if the packages start with "tec.uom" are from the older >> libraries but they now exist in "javax.measure" and "tech.units". >> >> I have done most of the grunt work to rename the packages but the custom >> GeoTools UnitFormats and SexagesimalConverter require more work. >> >> Good new I think some of the workarounds that had to be done in GeoTools >> related to https://github.com/unitsofmeasurement/uom-se/issues/201 are >> no longer necessary in the unitofmeasure libraries and reference >> implementation of JSR 385. >> _______________________________________________ >> GeoTools-Devel mailing list >> GeoTools-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> > -- > -- > Jody Garnett >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
