Include ParseInputsteam in addition to ParseFile and ParseUrl

[GoogleCodeExporter]

More of a feature request than anything.

What steps will reproduce the problem?
1. Try to use local kml files in assets folder
2. Use AssetManager to get InputStream to asset
3. Find there is no way to read and parse InputStream

What version of the product are you using?
osmbonuspack_v4.2.6

Please provide any additional information below.

I just think this would be a useful feature as getting assets from the apk is 
done through InputStreams rather than File and currently there does not appear 
to be any way to directly use these. I have a number of small KML files I would 
like to use and I see no reason to store them on the SD card.

Original issue reported on code.google.com by TravisSt...@gmail.com on 31 Jan 2014 at 10:51

[GoogleCodeExporter]

Original comment by mathieu....@gmail.com on 31 Jan 2014 at 6:06

• Changed state: Accepted

[GoogleCodeExporter]

Available in r335. 

Original comment by mathieu....@gmail.com on 31 Jan 2014 at 11:32

• Changed state: Started

[GoogleCodeExporter]

Thanks for adding this. I was wondering though, the current implementation 
requires the full file path but it is my understanding this is not possible to 
obtain as the files are in the apk.

Original comment by TravisSt...@gmail.com on 1 Feb 2014 at 9:39

[GoogleCodeExporter]

The fullFilePath is only needed for handling sub-files identified with relative 
paths. This applies to local icons, and networklinks to local files. 
Example: <Icon><href>images/my_marker.png</href></Icon>

If you don't have such a case to handle, the fullFilePath doesn't matter, put 
anything for fullFilePath, for instance "". 

If you want to handle such a case, then you have a real issue... 

Original comment by mathieu....@gmail.com on 2 Feb 2014 at 5:51

[GoogleCodeExporter]

Now integrated in v4.2.7. 

Original comment by mathieu....@gmail.com on 14 Feb 2014 at 3:33

• Changed state: Fixed

[GoogleCodeExporter]

I've been trying to use this method with some KML files but parseStream always 
returns false. I originally tested it with the PairTour.kml file and it worked 
fine, but on the files I want to use it does not. I am not really sure what 
features osmdroidbonuspack can handle so perhaps it is due to the file itself.
This is an example of the file: 
http://www.biodic.go.jp/trialSystem/EN/LinkEnt/nps/NPS_akanLinkEnt.kml

and internally it has a networklink to a kmz file. I thought this might cause a 
problem so I got the kmz file and unziped it to try it with that kml file, but 
it also fails when using that and I have not been able to determine why this is 
the case. The zipped kml file seems to basically just be a bunch of polygons.

Original comment by TravisSt...@gmail.com on 15 Feb 2014 at 12:18

Attachments:

• doc.kml
• NPS_akanLinkEnt.kml