pombreda / libkml

Automatically exported from code.google.com/p/libkml
Other
0 stars 0 forks source link

Region latlonaltbox not parsed #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Load the attached kml file.
2. The network links region pointer returns false for has_latlonaltbox()

What is the expected output? What do you see instead?
Without this information, there is no way of knowing what the bounding box
for that kml region is. Is it supposed to discard the region information if
you set the minLodPixels to zero and the maxLodPixels to -1. I would expect
for it to show me the region information anyways, since it's still a part
of the xml file.

What version of the product are you using? On what operating system?
libkml-0.2.2, Windows XP, VS2005

Original issue reported on code.google.com by lxn...@gmail.com on 2 Jun 2008 at 3:40

Attachments:

GoogleCodeExporter commented 9 years ago
I can't reproduce your problem. Build and run the attached file (which parses 
your
attached KML file and prints the children of the Region's LatLonAltBox) and 
compare
your output to this:

petrichor:build$ ortho4-4-test ~/Desktop/ortho4-4.kml 
north: 90
south: -90
east: 180
west: -180
minAltitude: 0
maxAltitude: 0

By the way, your KML is malformed. A Region has one LatLonAltBox. You also have
flyToView (illegal) and LatLonBox (also illegal).

Original comment by kml.mash...@gmail.com on 18 Jun 2008 at 7:10

GoogleCodeExporter commented 9 years ago
Be easier if I attached the file...

Original comment by kml.mash...@gmail.com on 18 Jun 2008 at 7:11

Attachments:

GoogleCodeExporter commented 9 years ago
Closing. Please reopen if any issues remain with 0.3 (just now uploaded to the 
downloads area).

Original comment by kml.mash...@gmail.com on 28 Jun 2008 at 6:17