You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: spyhunter99 [Submitted to the original trac issue database at 12.41pm, Tuesday, 8th August 2017]
Running osmosis 0.45 against the same dataset (tried with both pbf and bz2) . On JRE/JDK is performs well and reads the files with no problems. On Android, (v6). it looks like it reads the bounds of the document, then the first node, and then suddenly stops without warning, exception or output.
I've attempted stepping through the debugger but I've been unable to find the source of the issue. The callback for process(Entity...) just stop firing. I think what's happening is that android is seeing some api call and is changing it to NOOP at some point but I'm not sure what's going on.
Reporter: spyhunter99
[Submitted to the original trac issue database at 12.41pm, Tuesday, 8th August 2017]
Running osmosis 0.45 against the same dataset (tried with both pbf and bz2) . On JRE/JDK is performs well and reads the files with no problems. On Android, (v6). it looks like it reads the bounds of the document, then the first node, and then suddenly stops without warning, exception or output.
I've attempted stepping through the debugger but I've been unable to find the source of the issue. The callback for process(Entity...) just stop firing. I think what's happening is that android is seeing some api call and is changing it to NOOP at some point but I'm not sure what's going on.
Sample code below. Please source is here https://github.com/spyhunter99/osmreader
boolean pbf = false;
CompressionMethod compression = CompressionMethod.None;
The text was updated successfully, but these errors were encountered: