Closed GoogleCodeExporter closed 8 years ago
There is a very very strange issue with the online KML content from Google Maps
used in the sample
(http://mapsengine.google.com/map/kml?mid=z6IJfj90QEd4.kUUY9FoHFRdE):
The standard Java DOM parsing raises an exception:
kmlDoc = docBuilder.parse(uri);
The KML content seems perfectly valid. Transfering the file on an other Web
server, then it works.
I don't understand...
You can try the YOURS sample
(http://www.yournavigation.org/api/1.0/gosmore.php?format=kml&flat=52.215676&flo
n=5.963946&tlat=52.2573&tlon=6.1799), it should work fine.
Original comment by mathieu....@gmail.com
on 6 Nov 2013 at 11:39
"Technical Error to Get KML Content" is shown using this KML :/
Original comment by alexis.v...@gmail.com
on 6 Nov 2013 at 2:11
"/" ?...
Original comment by mathieu....@gmail.com
on 6 Nov 2013 at 9:48
The ":/" is just here to see I am annoyed
Original comment by alexis.v...@gmail.com
on 7 Nov 2013 at 7:56
Oh... OK.
So, "Technical Error to Get KML Content" is shown using which KML exactly?
Original comment by mathieu....@gmail.com
on 7 Nov 2013 at 9:09
It is shown using the example or using the KML you gave me the 6th
Original comment by alexis.v...@gmail.com
on 15 Nov 2013 at 8:30
I completely rewrote the KML parser, moving from a DOM to a SAX implementation.
This is in v4.2 release.
It now works for my GoogleMaps test url
(http://mapsengine.google.com/map/kml?mid=z6IJfj90QEd4.kUUY9FoHFRdE).
If you want to try again...
Original comment by mathieu....@gmail.com
on 24 Nov 2013 at 11:43
Now, this app crashes and stops using the default sample or the last one...
Original comment by alexis.v...@gmail.com
on 25 Nov 2013 at 1:53
If you can get a logcat stracktrace, this would be helpful to analyze.
Download the latest version of the app (4.2.2 now), before trying again.
Original comment by mathieu....@gmail.com
on 17 Dec 2013 at 11:32
We are at v4.2.5 now, after a lot of changes and improvements around KML
handling.
I consider this issue is obsolete.
If it happens again with v4.2.5, please raise a new issue, providing the url
used, and the logcat stacktrace.
Original comment by mathieu....@gmail.com
on 22 Jan 2014 at 11:23
Original issue reported on code.google.com by
alexis.v...@gmail.com
on 5 Nov 2013 at 5:21