kml file reader problem

4 posts, 0 answers
  1. Kevin
    Kevin avatar
    3 posts
    Member since:
    Jul 2011

    Posted 01 Mar 2012 Link to this post

       There are some problem in the KmlReader.Read(STR)
    1. It is very slow for long kml string-mostly we can not control the size of kml file.
    2. Read method is a static method. It does not support multithread to process KML file in the same time.
    3. When I use the Shape file to populate the map, it is still slow.

    Question: Any other ways to make the performance better, when I read the KML file?
    or how to implement the multithread to read KML by KmlReader.Read(STR) .

  2. Andrey
    Andrey avatar
    1681 posts

    Posted 06 Mar 2012 Link to this post

    Hello Kevin,

    Unfortunately you can't improve the performance for reading the KML file. Currently the KmlReader does not support multithreading for processing the KML file.
    We have created a PITS issue to implement this feature in future releases of map control. You can track implementation of it using the following link:

    Kind regards,
    Andrey Murzov
    the Telerik team
    Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>
  3. Farkas
    Farkas avatar
    3 posts
    Member since:
    Jul 2010

    Posted 17 Jul 2013 Link to this post


    I have a kml file, and I can't read with Telerik Silverlight KML Reader. I attached the kml look, and the exception. (Unable to cast object of type 'System.Xml.Linq.XProcessingInstruction' to type 'System.Xml.Linq.XElement'.)
    I appreciate any help.

  4. Andrey
    Andrey avatar
    1681 posts

    Posted 18 Jul 2013 Link to this post

    Hi Farkas,

    Unfortunately we can't reproduce the problem without your kml-file. Could you, please, open a support ticket and attach it for detail analysis?

    Andrey Murzov
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
Back to Top