Road Metadata Inconsistencies Between Imported and Created Elements in Forma

[vc6XFSA]

Hello! We are now concerned about importing roads from Forma into our plugin and have encountered one curious inconsistency in the data of imported, amortized but edited in Forma roads and created in forma native roads. I would be grateful if you could tell me if this is a bug or done on purpose. And if so, how we could bring all the data to the same format. 🙂

I will describe the problem in more detail

Three roads are shown in the picture, they look the same to the user. But in their properties they are different.

1. Roads imported from services like OpenStreetMap and placed in the Forma environment do not include any coordinate data in their metadata.

2. When one of these imported roads is manually edited, it acquires 2D coordinate data, even though visually it already appears to exist in 3D space.  

3. On the other hand, roads created directly in Forma immediately include full XYZ coordinates. 

For our workflows, this difference creates extra effort, as we have to normalize all road objects to the same structure during geometry import. It would be very helpful if this was streamlined directly in Forma. Thanks for any advice or ideas on what can be done about it 🤗

[syed_ammar_abbas_naqvi]

Hello!

Thank you for your detailed description of the issue with importing roads from Forma into your plugin. I understand how these inconsistencies can create extra effort in your workflows.

Yes, the roads from OSM and natively drawn roads are inconsistent, and unfortunately, that is how it is for now. I have notified the team that added the new natively drawn roads, It might be updated in the future, but I can't say when.

The Z coordinate values being there is indeed a bug; those are bogus values that should be ignored. All the roads are supposed to be 2D. The bug should be fixed soon. 

In the meantime, for roads from the basic system, you have to read the footprint representation, and for the parametric system, read the horizontalAlignment representation. What you are talking about now is __INTERNAL__ representations that should be ignored.

Thanks for your patience and for bringing this to our attention! 

Best,

Ammar