Skip to main content
Solved

CITYgml:'CityGML Reader: The number of UV Texture coordinates did not match the coordinates of the geometry

  • May 7, 2013
  • 1 reply
  • 22 views

Hello everybody, I'm a noncertiefied FME-Greenhorn.

 

 

I will try to transfer CITYgml- Data into Microstation V8 and both, the internal MS- FME- Port and FME as Standalone, will give the Errorcode: 'CityGML Reader: The number of UV Texture coordinates did not match the coordinates of the geometry. Received '0' texture coordinates but the geometry has '4' points.'. There is some Geometry, which apperas in Microstation as single Lines (no shapes!) - but the Textures are not transfered (or not displayed because of the Elementtype?).

 

The same Error will apear by transfer to dxf, kml, LANDxml or SetchUp- Format - without the Geometrydata as Result. So maybe the Reader will not accept the Data?

 

On the other hand, i'm easily able to watch the Data inside Terrainview of Terratec!

 

 

Any Ideas?

 

Best Regards

 

tom

 

Best answer by fmelizard

Hi,

 

 

Some more information can be useful, are you using FME 2013?

 

How are you setting the citygml reader (schema, ADE)?

 

Have checked the include texture option on?

 

 

Itay
View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • Best Answer
  • May 7, 2013
Hi,

 

 

Some more information can be useful, are you using FME 2013?

 

How are you setting the citygml reader (schema, ADE)?

 

Have checked the include texture option on?

 

 

Itay

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings