… or at least reduce the risk of errors while creating things.
Ah, KML, otherwise known as a Google Earth (Network) Layer thing, previously Keyhole Markup Language thing and now edging towards a useful format for transporting geodata around thing as the OGC (Open Geospatial Consortium) nudge KML closer to standards and out of the Evil propriety clutches of Google.
Propriety being Evil here, not Google of course.
“Unfortunately since my laptop hard drive died last week, I donâ€™t have a development machine to build and play with this yet. But I expect to use this library in a number of projects.”
… I’ve not had a chance to play with it yet. Not so much because my laptop is broken, because it isn’t (and boy I wish it was so I could get the IT department to get me a new one), but because as anyone who knows me knows, I moan bitterly about having to type anything like
make or in this case
scons into a console. As much as I love Macs I’m no doubt still scarred from when I tried to compile PHP with some graphics libs in, anyway I digress.
Why am I happy about this, well, mainly because it’s another indicator of the progress towards KML being a standard and less Google’s thing. Which means that I don’t have to make quite so many arguments for why we should support it, being a Yahoo house and all (not that I’ve ever had to have made those arguments, but you know). Having a library means I can say “But look, we have a library”. Simple I know but never underestimate the power of a library.
Anyway, I’m rambling, basically because High Earth Orbit has it all covered in detail, so stop reading this and read that instead.