ORD 2020 R3

Just saw it online ;)

Btw a few extra features not listed in What's New:

• Added Aquaplaning Analysis warning message when user defined maximum flow depth is exceeded
• Added option to ignore steep slopes in Aquaplaning analysis above a user defined value
• Revised Reports variable to allow reports in multiple folder locations and ProjectWise integration
• Thr Template Library editor now prompts you to check the ITL back in to Projectwise when closing the editor to free up the ITL for others to access in team projects

It all looks great. Too bad I may not be able to use it. There's been another schema change.

Can you use the new Downgrade export option?

Maybe...Our workspace resources are developed by our DOT, and I don't know how comfortable I will be trying to bring any of that forward if it needs it. Do you know how much data gets lost in the downgrade?

Probably better to use the other schema thread to get a Bentley response - but on testing everything is still there for me. Im pretty sure its just data on the backend that users dont see.

Like Mary said, there s a schema/civil data format change. I assume the DGN format itself doesn't change, but the civil data itself does? Is there a file somewhere that documents these changes, so users can be aware as the upgrade to ORD and/or receive files? 

Like Mary said, there s a schema/civil data format change. I assume the DGN format itself doesn't change, but the civil data itself does? Is there a file somewhere that documents these changes, so users can be aware as the upgrade to ORD and/or receive files? 

jcallicott said:

I assume the DGN format itself doesn't change, but the civil data itself does?

Yes, it's right. DGN V8 format is still the same ... even when it's probably true in fact. I am quite sure the format itself has evolved between V8i and CE, but they are internal changes not breaking compatibility.

What changed is "civil schema(s)", which is a mechanism how OpenRoads Designer work with data stored in DGN file. Every civil feature is internally represented by geometry and addition data, and this structure is defined by particular EC schema.

When new version of EC schema is implemented, it breaks backward compatibility, because older ORD version does not contain this updated version and even when it will, it will likely not understand the changes.

jcallicott said:

Is there a file somewhere that documents these changes, so users can be aware as the upgrade to ORD and/or receive files? 

I am not daily ORD user, but I am not aware of any such documentation. Even in What's new section there is no information that backward compatibility breaking changes were introduced, which I think is a huge fail.

ORD itself (at least current ORD 2020 R3) offers schema upgrade when older DGN is opened and there is Technology Preview of "schema downgrade" tool.

With regards,

  Jan