use 1/0 for value of boolean data type instead of true/false

[GoogleCodeExporter]

The KML generated from the library seems to always uses true/false 
instead of 1/0 for boolean data types. This validates correctly and 
displays correctly in Google Earth, but I find that it does not 
display correctly within Google Maps. Attached are two kml files which show 
a polygon, with the  only difference between them being this data type 
change 

- polygon_truefalse.kml 
- polygon_onezero.kml 

Google maps correctly shows one/zero case as a filled polygon, where 
the true/false case shows no polygon at all 

The KML reference never mentions using true/false, it always uses 1/0. 
Thus, I would recommend for maximum compatibility that 1/0 is always used. 

Original issue reported on code.google.com by joel.car...@gmail.com on 18 Nov 2009 at 12:26

Attachments:

• polygon_onezero.kml
• polygon_truefalse.kml

[GoogleCodeExporter]

Original comment by bachmann...@gmail.com on 23 Nov 2009 at 7:31

• Changed state: Started

[GoogleCodeExporter]

Original comment by bachmann...@gmail.com on 23 Nov 2009 at 7:33

[GoogleCodeExporter]

Original comment by bachmann...@gmail.com on 30 Nov 2009 at 10:19

• Changed state: Done