Kyle, Yes, I just removed the spaces after the commas in the <coordinates> tag and was then able to open one of the kml files in G.E. I suspect that there are m(b)illions? of kmz files in cyberspace that won't meet the 2.2 standard because of this. I am not sure of the most effective solution. In addition to documentation, perhaps we need a conversion tool for legacy 2.1 kml superoverlays. Perhaps getting the 2.2 KML standard to lighten-up a tad would be complicated.
Thanks Again, Roland On Fri, Nov 18, 2011 at 11:14 AM, Kyle Shannon <[email protected]>wrote: > Possible issue with output (from > http://earth.google.com/support/bin/answer.py?answer=40901):**** > > ** ** > > *To conform more closely with the OGC KML 2.2 standard, we've made the > parsing of the <coordinates> tag more strict in version 6.1. Spaces must > only be used to separate the (longitude,latitude,altitude) triplets which > specify the coordinates of a single point. It is invalid to add spaces > between individual coordinates. We understand that previous versions of the > client were more lenient, so if your KML files contain spaces beween > coordinates in coordinate triplets, an easy workaround is to remove all > whitespace located immediately before or after commas inside a > <coordinates> tag.* > > * * > > I checked one file, and there were spaces after the commas:**** > > ** ** > > <kml xmlns="http://earth.google.com/kml/2.1"; xmlns:gx=" > http://www.google.com/kml/ext/2.2";>**** > > <Document>**** > > <name>1/1/1.kml</name>**** > > <Style>**** > > <ListStyle id="hideChildren">**** > > <listItemType>checkHideChildren</listItemType>**** > > </ListStyle>**** > > </Style>**** > > <Region>**** > > <Lod>**** > > <minLodPixels>128</minLodPixels>**** > > <maxLodPixels>2048</maxLodPixels>**** > > </Lod>**** > > <LatLonAltBox>**** > > <north>41.900791</north>**** > > <south>41.890160</south>**** > > <east>12.505676</east>**** > > <west>12.492253</west>**** > > </LatLonAltBox>**** > > </Region>**** > > <GroundOverlay>**** > > <drawOrder>1</drawOrder>**** > > <Icon>**** > > <href>1.jpg</href>**** > > </Icon>**** > > <gx:LatLonQuad>**** > > <coordinates>**** > > 12.492253, 41.890160, 0**** > > 12.506078, 41.890461, 0**** > > 12.505676, 41.900791, 0**** > > 12.491848, 41.900490, 0**** > > </coordinates>**** > > </gx:LatLonQuad>**** > > </GroundOverlay>**** > > ...**** > > ** ** > > Seems like a quick fix. Someone should probably file a ticket for > documentation, I can do that if need be.**** > > ** ** > > kss**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Roland Duhaime > *Sent:* Friday, November 18, 2011 7:14 AM > *To:* [email protected] > *Subject:* Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001**** > > ** ** > > Roger,**** > > ** ** > > The PNG gdalinfo details are:**** > > ** ** > > Driver: PNG/Portable Network Graphics**** > > Files: 7.png**** > > Size is 218, 218**** > > Coordinate System is `'**** > > Image Structure Metadata:**** > > INTERLEAVE=PIXEL**** > > Corner Coordinates:**** > > Upper Left ( 0.0, 0.0)**** > > Lower Left ( 0.0, 218.0)**** > > Upper Right ( 218.0, 0.0)**** > > Lower Right ( 218.0, 218.0)**** > > Center ( 109.0, 109.0)**** > > Band 1 Block=218x1 Type=Byte, ColorInterp=Red**** > > Mask Flags: PER_DATASET ALPHA**** > > Band 2 Block=218x1 Type=Byte, ColorInterp=Green**** > > Mask Flags: PER_DATASET ALPHA**** > > Band 3 Block=218x1 Type=Byte, ColorInterp=Blue**** > > Mask Flags: PER_DATASET ALPHA**** > > Band 4 Block=218x1 Type=Byte, ColorInterp=Alpha**** > > ** ** > > Thanks,**** > > Roland**** > > ** ** > > ** ** > > On Thu, Nov 17, 2011 at 5:21 PM, Roger André <[email protected]> wrote:**** > > What is the output of gdalinfo on one of the PNG's in the superoverlay?*** > * > > ** ** > > ** ** > > On Thu, Nov 17, 2011 at 1:36 PM, Roland Duhaime <[email protected]> > wrote:**** > > ** ** > > Has anyone else experienced the latest version of Google Earth > (6.1.0.5001) or the G.E. API not loading PNG formatted KMLSUPEROVERLAYs > created using gdal_translate? The same KMZ files worked in the past.**** > > ** ** > > Thanks,**** > > Roland**** > > ** ** > > ** ** > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev**** > > ** ** > > ** ** > > This email message is for the sole use of the intended recipient(s) and > may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and delete the > original message. >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
