<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Thoughts on Names within InRoads - Please Add your own Thoughts</title><link>/products/road___site_design/b/road_and_site_design_blog/posts/thoughts-on-names-within-inroads-please-add-your-own-thoughts</link><description>Names, Names and More Names 
 With this post I am hoping to get some feedback as to what
others are doing with all of the named items that MicroStation and InRoads now
entails. I have been working with InRoads since its origins as TDP on the VAX.</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Thoughts on Names within InRoads - Please Add your own Thoughts</title><link>https://communities.bentley.com/products/road___site_design/b/road_and_site_design_blog/posts/thoughts-on-names-within-inroads-please-add-your-own-thoughts</link><pubDate>Wed, 03 Aug 2016 17:41:42 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a46be440-622d-480b-b165-83f5626a6f24</guid><dc:creator>caddcop</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;For all the Open Roads users, the Names of SELECTseries 2 carries forward into SELECTseries4. So the idea of point, component, style and named symbology naming convention still applies. In fact, it really needs to carry forward into Element Templates and more.&lt;/p&gt;
&lt;p&gt;I also see that in the Model Properties dialog box, you can rename models and assign a default description and logical name that will be used when a file is referenced into other files. On large projects with many users, this makes working with others files much easier. When setting up a file, you may reference in many files created by others and not return to the file for day, weeks or longer. If the descriptions and logical names automatically are filled in with useful information, that delayed return to the file will be less mysterious if it is necessary to manipulate reference files. &lt;/p&gt;
&lt;img src="https://communities.bentley.com/aggbug?PostID=144902&amp;AppID=275837&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Thoughts on Names within InRoads - Please Add your own Thoughts</title><link>https://communities.bentley.com/products/road___site_design/b/road_and_site_design_blog/posts/thoughts-on-names-within-inroads-please-add-your-own-thoughts</link><pubDate>Wed, 10 Aug 2011 14:24:47 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a46be440-622d-480b-b165-83f5626a6f24</guid><dc:creator>gjrcad</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Caddcop,&lt;/p&gt;
&lt;p&gt;I generally agree with your naming approach and degree of organization. &amp;nbsp;Naming conventions provide for user and administrative efficiency, and apparently in some cases can facilitate more functionality in the software itself. &amp;nbsp;Therefore developing naming conventions is not an option, but a necessity. &amp;nbsp;It is desirable to have these conventions simultaneously satisfy multiple criteria: &amp;nbsp;&lt;/p&gt;
&lt;p&gt;* Names are meaningful, easy to read and understand. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;* Names facilitate some sort logical grouping of similar items. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;* Convention is expandable and able to support the addition of new names. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;* Convention provides for needs but is not more complicated than necessary. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Per your discussion, I can see that this really takes shape when setting up InRoads functionality. &amp;nbsp;See my outline regarding the Developing Preferences for InRoads, in which you provided valuable input.&lt;/p&gt;
&lt;p&gt;-------------------------------------------------------------------------------------------------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;As I have explored the topic of developing Preferences, with the help of recommendations and commentary, my thoughts are directed to the need for CAD Standards, Workflow, and Best Practices. &amp;nbsp;Here is my stab at defining a process for developing InRoads Preferences:&lt;/p&gt;
&lt;p&gt;1) Define Standard Level Names and Attributes. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;2) Define Standard Text and Text Attributes. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;3) Establish Standard Symbols and/or Cell Libraries. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;4) Create Named Symbology CSV spreadsheet file (Microsoft Excel). &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	a) Define Naming Convention for Named Symbology names and descriptions. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	b) Incorporate Standard Level, Text, Symbols, Cells, and associated attributes. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	c) Apply standards to applicable Default, Plan, Profile, and Cross Section settings. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;5) Copy an existing xin file that you want to use as your starting template and open the copy in InRoads. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;6) Use Named Symbology Tools Add-in to &amp;quot;Import Named Symbology from CSV&amp;quot; into the copied xin file. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;7) Verify that the import was successful through &amp;quot;Named Symbology Manager&amp;quot;. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;8) Delete Named Symbologies from the &amp;quot;Named Symbology Manager&amp;quot;, if necessary. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;9) Copy existing Styles from other xin files by using the Copy Preferences Add-in, if needed. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;10) Create New Styles or Delete unnecessary Styles by using the &amp;quot;Style Manager&amp;quot;. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	a) Define Naming Convention for Style names and descriptions. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	b) Edit New Styles to specify settings and references to Named Symbologies for Surface, Geometry, and Survey Features.&lt;/p&gt;
&lt;p&gt;	c) Develop a spreadsheet to keep track of the Named Symbologies that are applied to each Feature Style. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;11) Define Naming Convention for Preferences. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;12) Copy existing Preferences from other xin files by using the Copy Preferences Add-in, if needed. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;13) Create New Preferences by accessing applicable Command dialog box. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	a) Apply Settings for Preference to use. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	b) Apply Named Symbologies for Preference to use, if applicable. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	c) Apply Styles for Preference to use, if applicable. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	d) Select Preferences Button, and &amp;quot;Save As&amp;quot; New Preference. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	e) Develop a spreadsheet to keep track of the Named Symbologies and/or Styles that are applied to each Command Preference. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;14) Apply additional Command settings to New Preference by using the &amp;quot;Preference Manager&amp;quot;, where appropriate. &lt;/p&gt;
&lt;p&gt;15) Delete Preferences from the &amp;quot;Preference Manager&amp;quot;, if needed. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;16) Maintain Control over the xin Preference file to prevent unauthorized modifications. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;	a) Allow Read-Only Access to other users. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;17) Establish a process to address user requests for adding new Named Symbology, Styles, or Preferences to the xin file. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;18) Repeat steps as necessary to continue building the Preference file. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Notes:&lt;/p&gt;
&lt;p&gt;* In order to create a CSV spreadsheet for your Named Symbology, use &amp;quot;Export Named Symbology to CSV&amp;quot; via the Named Symbology Tools Add-in to create a file, which you can then modify for your symbology settings.&lt;/p&gt;
&lt;p&gt;* Duplicate names of corresponding Named Symbologies, Styles, and/or Preferences, where appropriate. &amp;nbsp;I am not clear on all the benefits of duplicate naming strategies, other than you can link a Preference to a Style to facilitate dynamic display of the Preference (or something like that), if you have both a Style and Preference with the same name. &amp;nbsp;As far as linking Styles and Named Symbologies, I noticed that the civil.xin file that came with the InRoads install has duplicate names for horizontal alignment points such as POB, PC, PT, POE, etc. &amp;nbsp;I am not sure if that has any significance?&lt;/p&gt;
&lt;p&gt;* Routinely backup your Preference file prior to making modifications to facilitate an escape plan.&lt;/p&gt;
&lt;p&gt;* Document changes to Named Symbologies, Styles, and Preferences via the spreadsheets you created.&lt;/p&gt;
&lt;p&gt;* View XML Reports to assist in keeping track of Named Symbologies and Styles, and how they applied. &amp;nbsp;See FeatureStyles.xsl, MissingNamedSymbologies.xsl, and NamedSymbologiesUse.xsl listed under the XIN folder and LevelFromCode.xsl under the Survey folder when going into View XML Reports.&lt;/p&gt;
&lt;p&gt;Definitions from InRoads Help:&lt;/p&gt;
&lt;p&gt;* &amp;quot;A named symbology stores a large set of parameters that define exactly how a point, line, or piece of text will appear in plan view, in profiles, and in cross sections. &amp;nbsp;The types of parameters stored in a named symbology include: color, level, line weight, line style, text height, text justification, text font, rotation angle, and so on.&amp;quot;&lt;/p&gt;
&lt;p&gt;* &amp;quot;Part of the definition of a style is a named symbology. A style specifies a named symbology to control the appearance of the feature when it is displayed in plan view, in a profile, or in a cross section.&amp;quot;&lt;/p&gt;
&lt;p&gt;My Compiled Definitions:&lt;/p&gt;
&lt;p&gt;* Preferences define settings for a selected command. &amp;nbsp;Settings can reference command specific settings, Styles, and/or Named Symbologies.&lt;/p&gt;
&lt;p&gt;* A Preferences File (xin file) contains definitions for Named Symbology, Styles, and Preferences. &amp;nbsp;Not sure but it seems that the xin file may even contain additional information?&lt;/p&gt;
&lt;img src="https://communities.bentley.com/aggbug?PostID=144902&amp;AppID=275837&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>