Hi,
I tried to load a file KMZ, but received an error in
System.Xml.Linq.XDocument.Load(String uri, LoadOptions options)
OK, means there is no support for this format.
I unpacked from the archive file KML and got this error
System.NullReferenceException: Object reference not set to an instance of an object.
at 1BM=.ixk=.vBk=()
at 1BM=.ixk=.rxk=()
at ThinkGeo.MapSuite.Core.KmlFeatureSource.OpenCore()
at ThinkGeo.MapSuite.Core.FeatureSource.Open()
at ThinkGeo.MapSuite.Core.FeatureLayer.OpenCore()
at ThinkGeo.MapSuite.Core.Layer.Open()
…
In other GIS System perfectly open file
Here is the link to the file
dropbox.com/s/7apzsbjjgrkkexy/WialonExportKml.kmz?dl=0
KML Layer.Open -> NRE
I manualy replace in file text <kml><kml xmlns="opengis.net/kml/2.2">and KmlFeatureCore.Open() no longer throws an exception.
tag "kml" replace with "kml xmlns="opengis.net/kml/2.2"
But still does not work, for the reason that you do not have initialization code in KmlFeatureSource
<featuresourcecolumn>private Collection<featuresourcecolumn> columns;
in my code
kmlLayer.Open();
var columns = kmlLayer.FeatureSource.GetColumns().Select(col => col.ColumnName).ToList();
// source is null
var all = kmlLayer.FeatureSource.GetAllFeatures(ReturningColumnsType.AllColumns);
// NRE
kmlLayer.Close();
// and tried in this way, I get an error "Read and write not equal!"
Collection<mapshape> allShapes = KmlFeatureLayer.GetAllMapShapes(filename);
<mapshape>
</mapshape></featuresourcecolumn></featuresourcecolumn></kml></kml>
I some time ago tried your library, and then everything was working with KML files. Maybe it was the version 7
Hi hovevecum,
It proved that it’s a bug and we have fixed it.Please get the latest version(8.0.274.0) or later and have a try.
If the issue still persist, please feel free to let us know.
Thanks,
Kevin
I tried the version 8.0.275.0, the problem still remains.
The file can not be loaded.
The file is "KML Samples - Google Developers"
Hi hovovecum,
We can reproduce this issue but seems it is pretty complex
than we thought, we are still working on this, any process we will update here
to let you know.
Thanks,
Kevin
Hi Hovovecum,
We’ve resolved this issue in the latest development version(8.0.281.0), please get it or a higher version and have a try.
If the issue still persist, please feel free to let us know.
Thanks,
Kevin