tag:blogger.com,1999:blog-21167013.post-39752297316597859952008-04-15T04:36:00.000-07:002008-04-15T04:36:00.000-07:00I really agree with you thoughts about KML and standardizing, however I kind of like the idea of having a library that does all the hard lifting for me.<BR/><BR/>Like yourself, I have implemented KML readers in the past. I transitioned to using LibKML recently, and I must say the library is ... for the lack of better words, not pretty.<BR/><BR/>It looks like they had some intern slap it together for them. It's hard to follow and the amount of hierarchies you have to go through is quite ridiculous.<BR/><BR/>The compelling argument I keep telling myself, is that updates to the reader will come automatic. Deep down, I know this is just me trying to validate using the library. The reality is that new features won't break old ones, so using the library won't give you them for free.<BR/><BR/>As of right now, I haven't seen a good reason to use the library really. It doesn't handle LOD calculations or region calculations for you. It simply parses the file and gives you interfaces for the data. I am hoping once I hit styles, using the library will pay off. I implemented the style map in the past, but hopefully this library will do all the aggregation for me.lxnycehttp://vizure.comnoreply@blogger.com