OSG CityGML plugin produces corrupt texture coordinates/texture mappings.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open the citygml file using osgviewer.

What is the expected output? What do you see instead?
The expected output can be seen on the left side of the attached image. This 
output is produced by using LandXplorer Citygml Viewer from 
ftp://ftp.fpk.tu-berlin.de/pub/Kolbe/LDX_CityGML_Viewer_2009a_TS.zip. Using 
osgViewer, the image on the right side is produced instead.

What version of the product are you using? On what operating system?
I'm using SVN Trunk Revision 114 of libcitygml and SVN Trunk Revision 12295 of 
OSG, on Windows 7 x64 (libcitygml and OSG are compiled as x64).

Please provide any additional information below.
I'm not sure if this is really a libcitygml issue, but the problem could only 
be observed when using citygml. There's no difference whether I load the file 
in my own code or use osgViewer.

I cannot provide the complete file because it is intellectual property of our 
project partner, but I attached the citygml-snippet corresponding to the 
problematic polygon (large building wall).

Regards

Original issue reported on code.google.com by lethal.g...@googlemail.com on 19 Apr 2011 at 6:52

Attachments:

• LandXplorer-vs-osgviewer.PNG
• Snippet.xml

[GoogleCodeExporter]

Hi!

Thanks for reporting this bug.
Could you provide the texture image, so we can reproduce the problem.
Even a degraded one should be enough.

Thank you,

Manuel

Original comment by garnier....@gmail.com on 16 Jun 2011 at 2:49

[GoogleCodeExporter]

Hi,

Sure, I can provide the texture file. Unfortunately, I won't be able to do so 
before next week. 

Regards, Niko

Original comment by lethal.g...@googlemail.com on 27 Jun 2011 at 4:39

[GoogleCodeExporter]

Hi again,

I've prepared a complete example .citygml file. Sorry for not providing this 
from the start, but I had to ask for permission to do so first. I stripped all 
geometry except the faulty building wall polygon. Note that I kept all the 
texture definitions though, because removing them surprisingly also removes the 
problem.. (maybe a hint?). The texture is also included. Just unzip and open 
the .citygml file using osgviewer. 

I also checked if the problem is really related to libcitygml, and it seems so. 
The coordinates returned by citygml::Polygon::getTexCoords() are different than 
the values in the xml file.

Regards,

Niko

Original comment by lethal.g...@googlemail.com on 4 Jul 2011 at 3:29

Attachments:

• BugReport.zip

[GoogleCodeExporter]

Hi,

Excellent! We'll look into it as soon as we can.
Thanks for the hint about the function that may cause a problem :)

Cheers,

Manuel

Original comment by garnier....@gmail.com on 5 Jul 2011 at 1:24

[GoogleCodeExporter]

Sorry for the delay. I think I have just fixed the issue in revision 116.
Please update and tell me if it's better now.

Best regards,
Joachim

Original comment by jpouder...@gmail.com on 20 Jul 2011 at 3:04

• Changed state: Started

[GoogleCodeExporter]

Hi Joachim,

i tested it with several tiles that where formerly affected by this issue. 
Looks very good. I did not find buildings with obviously wrong texture mappings.

Thanks a lot,
Jan

Original comment by jan.kli...@gmail.com on 21 Jul 2011 at 7:23

[GoogleCodeExporter]

Original comment by jpouder...@gmail.com on 21 Jul 2011 at 7:25

• Changed state: Verified