Quantcast
Channel: OpenRoads | OpenSite Forum - Recent Threads
Viewing all articles
Browse latest Browse all 15087

[OR IR] Feature Definitions and Native Styles - Are All Native Style Display Modes Recognized in Open Roads?

$
0
0

I've watched all the Feature Definition Videos and they missed a big part of the puzzle. In a Feature Definition, there are Native Style settings for:

  • Survey
  • Plan
  • Profile
  • Intersected Profile
  • Projected Profile
  • Cross Section
  • 3D

In InRoads Native Styles, there are Features and Named Symbologies. Features take care of whether a features is a Surface Feature, a Geometry (Point, Line, Arc and/or Spiral) Feature and a Survey Feature, but also control symbologies along with a number of specific settings for the type of feature.

Within the symbologies, are the options for different settings for Lines, Text and Points. And for these, is a Default mode, a 3D/Plan mode, a Profile Mode and a Cross Section mode. These work in conjunction with the features settings sand what workflow they are used. If a Default mode symbology is defined, it can be used for 3D/Plan, Profile or Cross Section if any of those modes are not defined. But if one of those modes is defined and the workflow calls for it, the symbology defined under that mode is used. So for the native product, we can have unique symbology for how a feature is displayed in 3D/Plan, Profile or Cross Section.

So, for Open Roads, when using a Native Style what is not made clear is this:

  • If a Feature Definition uses Native Styles everywhere it can and the native styles use unique symbology for both lines and points for 3D plan, Profile and Cross Section, does the 3D/Plan Line or Point symbology get used fpr Survey, Plan and 3D in the feature Definition?
  • And, in that same Feature Definition and Native Style, does the Profile and Projected Profile use the Native Style Profile symbologies (line and/or point, as called for?
  • And again, in that same Feature Definition and Native Style, does the Cross Section use the Native Style Cross Section symbologies (line and/or point, as called for?

I understand that the Plan and 3D in Open Roads are two different things (2D or 3D model) while in InRoads, 3D/Plan shared symologies, so the best practice approach is to not use Native Style for one or the other, unless having identical symbologies is acceptable.


Viewing all articles
Browse latest Browse all 15087

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>