SNAP 8.0.6/8.0.7 update released

Hello,

we released a small updated for SNAP and you can trigger the installation by selecting from the help menu ‘Check for Updates’.
This update contains two improvements

  • When data data is written the cache is cleared earlier. This should improve the memory consumption a bit. [SNAP-1462]
  • The label for the sea between Korea and Japan is now correctly shown as “Sea of Japan/East Sea” [SNAP-1476]
    image
6 Likes

We had to release another update. Now version 8.0.7 fixes the label of the ‘Sea of Japan/East Sea’ in all places (word view, WW analysis view and product library) where the world view is used.

1 Like

Dear @marpet, it does not contain this fix here? https://senbox.atlassian.net/browse/SITBX-882

Also getting an error on startup (using Mac OS Catalina )

java.util.ServiceConfigurationError: javax.xml.stream.XMLInputFactory: Provider com.ctc.wstx.stax.WstxInputFactory not found
at java.util.ServiceLoader.fail(ServiceLoader.java:239)
at java.util.ServiceLoader.access$300(ServiceLoader.java:185)
at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:372)
at java.util.ServiceLoader$LazyIterator.access$700(ServiceLoader.java:323)
at java.util.ServiceLoader$LazyIterator$2.run(ServiceLoader.java:407)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:409)
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
at javax.xml.stream.FactoryFinder$1.run(FactoryFinder.java:353)
at java.security.AccessController.doPrivileged(Native Method)
at javax.xml.stream.FactoryFinder.findServiceProvider(FactoryFinder.java:341)
Caused: java.lang.RuntimeException: Provider for class javax.xml.stream.XMLInputFactory cannot be created
at javax.xml.stream.FactoryFinder.findServiceProvider(FactoryFinder.java:367)
Caused: javax.xml.stream.FactoryConfigurationError: Provider for class javax.xml.stream.XMLInputFactory cannot be created
at javax.xml.stream.FactoryFinder.findServiceProvider(FactoryFinder.java:370)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:313)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:227)
at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:154)
at gov.nasa.worldwind.util.WWXML.openEventReaderStream(WWXML.java:353)
at gov.nasa.worldwind.util.WWXML.openEventReader(WWXML.java:502)
at gov.nasa.worldwind.util.WWXML.openEventReader(WWXML.java:464)
at gov.nasa.worldwind.ogc.OGCCapabilities.createReader(OGCCapabilities.java:89)
at gov.nasa.worldwind.ogc.OGCCapabilities.(OGCCapabilities.java:70)
at gov.nasa.worldwind.ogc.wms.WMSCapabilities.(WMSCapabilities.java:71)
at gov.nasa.worldwind.util.SessionCacheRetrievalPostProcessor.handleWMSCapabilitiesContent(SessionCacheRetrievalPostProcessor.java:248)
at gov.nasa.worldwind.util.SessionCacheRetrievalPostProcessor.handleContent(SessionCacheRetrievalPostProcessor.java:238)
at gov.nasa.worldwind.util.SessionCacheRetrievalPostProcessor.onRetrievalSuceeded(SessionCacheRetrievalPostProcessor.java:193)
at gov.nasa.worldwind.util.SessionCacheRetrievalPostProcessor.run(SessionCacheRetrievalPostProcessor.java:177)
at gov.nasa.worldwind.retrieve.URLRetriever.end(URLRetriever.java:352)
at gov.nasa.worldwind.retrieve.URLRetriever.call(URLRetriever.java:280)
at gov.nasa.worldwind.retrieve.URLRetriever.call(URLRetriever.java:27)
at gov.nasa.worldwind.util.SessionCacheUtils.retrieveSessionData(SessionCacheUtils.java:80)
at gov.nasa.worldwind.util.SessionCacheUtils.getOrRetrieveSessionCapabilities(SessionCacheUtils.java:170)
at gov.nasa.worldwind.layers.BasicTiledImageLayer.retrieveResources(BasicTiledImageLayer.java:723)
at gov.nasa.worldwind.layers.BasicTiledImageLayer$2.run(BasicTiledImageLayer.java:811)
[catch] at java.lang.Thread.run(Thread.java:748)

The S1TBX issue is not solved with this update, because only the SNAP core was update but not the S1 Toolbox.

The error you see is tracked in this ticket
[SITBX-847] Error “WstxInputFactory not found” caused by s1tbx-cloud module - JIRA (atlassian.net)
As far as I know this is only solved in for the next major release. And is not included in an update.
.

Hi @marpet,
I’m also running into the same issue @AVollrath mentioned.
Any idea when the next S1TBX update is due?

No. I have no idea. Sorry.
@lveci do you plan an update?