OpenCities Map products are built on the same platform as MicroStation and therefore shares the same installation and configuration concepts.  For information on how to create a custom configuration, please refer to the articles in the following location:

Custom Configuration Guides

In previous versions, Map V8i could be repaired or modified via the Programs and Features dialog accessed from Windows Control Panel:

1. With CONNECT Edition products, you need to locate and run either of these files:

• Setup_XXXXXXx64_10.XX.XX.XX.exe which is setup file created when you make a deployment image
• Product10.xx.xx.xxen_updtx.exe which is the installation file downloaded from softwaredownloads.bentley.com

2. Run or double click the setup or installation file.

3. Select Repair or Modify

4. If choosing Repair, ensure the product(s) is selected, then click Repair.  NOTE:  This dialog may present different items that what's shown here.  This is especially true for other CONNECT Edition products.

5.  If choosing Modify, the dialog for OpenCities Map may not list specific items to modify.  However, for other CONNECT Edition products (such as MicroStation), this dialog may contain a variety of items to modify.

6. When done, click Finished.

When a deployment image has been created, all of the necessary installation files will be found in the folder specified during the creation process.  In the following example, the location C:/Bentley/DeploymentImages/OpenCitiesMap/ is used.

To install, run Setup_ProductNamex64_10.xx.xx.xxx.exe.  For this example, it would be Setup_OpenCitiesMapx64_10.03.00.023.exe as shown in the image above.  You can do this on the machine where the product will be installed by browsing to the deployment image location.

The product will be installed in the folders specified in the deployment image during the creation process.

Installing OpenCities Map requires a minimum of 12GB free space on your C:\ drive to download the package cache, otherwise known as the installation files.  This is true even if you're installing on another drive such as your D:\ drive. 

By default the location of the package cache is defined by the environment variable TEMP which is typically set to %USERPROFILE%\AppData\Local\Temp.

A quick workaround is to temporarily redirect the variable to another drive.

However, a solution that does not require editing your environment variables, is to redirect the package cache during the installation process.  

To do that, run the installer exe with the following command line argument: IsPackageCacheButtonAvailable=1

Example:  msa10020018en_updt2.exe IsPackageCacheButtonAvailable=1

Doing so will provide the installer dialog with an option button to redirect the cache location:

For more information, please refer to Redirecting the Package Cache

OpenCities Map products are built on the same platform as MicroStation and therefore shares the same installation and configuration concepts.  The following information is based on instructions found in the MicroStation CONNECT Edition ReadMe file:  Home > Installation > Deployment Guide

About a Deployment Image

The deployment image is created by a system administrator to install the application with the same installation configuration on multiple machines. The installation configuration includes the installation location, features, shortcuts, and so on. Once created, you will be able to double-click the Setup_XXXXXXx64_10.XX.XX.XX.exe file located in the deployment image folder to install the application with the defined configuration without the need of any user interaction or internet connection for component downloads.

The deployment image folder can also be moved to a shared location so that all users of the organization can directly execute the installation from there; the administrator can use this shared location in the Software Distribution System for installation of the product. Additionally, the deployment image can be shared on the network as a UNC path or pushed using SMS/SCCM.

Advantages of Using a Deployment Image

Conceptually, the deployment image can be considered as a pre-configured offline installer.Some advantages of using a deployment image include:

• Internet connection is not required for an installation from a deployment image.
• Separate pre-requisite pack or set of packages before installing product are not required.
• The installation location can be decided and set in deployment image. Once defined, the product will be installed at the same location on all the machines.
• The components to be installed are preselected at the time of creating deployment image. This results in all machines having exactly same set of installations.

Contents of a Deployment Image

The deployment image contains all the files that are packaged with the product as well as the downloadable files. The image does not analyze the system on which it is created. It simply saves all the components for installation. The deployment image also saves the installation configuration.

Before You Start

Using a non-root drive for the program installation location:

• If the installation drive set in the deployment image configuration settings is other than the root directory (usually C:\), make sure that drive exists on all machines that the application is to be installed on.
• Target installation path is defined when creating the deployment image and if the path does not exist during installation, the install will fail.

Required prerequisites for creating a deployment image:

• An internet connection is required to download all installation components.
• A minimum of 12GB free disk space on to download all the installation components that will be used to create the deployment image.  By default this is set to your C: drive.
• Write access to the location where the deployment image will be created.
• A minimum of 12GB free disk space on the drive where the deployment image will be created.

To Create a Deployment Image

1. Download the product installation executable from softwaredownloads.bentley.com

2. Using either the Command Prompt window, or the Run dialog, select the exe and append /layout as shown below. (Note - It's not necessary to use an elevated CMD.)  In this example, the command is:  ocm10030023en_updt3.exe /layout 

3. The OpenCities product installation wizard opens. 

4. Select the Configure button in the top right corner.

5. (Optional) Set the application installation location.  Then click Next.

6. (Optional) Set the location of the delivered configuration.  For example, perhaps you use d:\Bentley\Map\ rather than c:\ProgramData\Bentley\Map CONNECT Edition.

7. (Optional) Set the location of the custom (shared or network) configuration during installation. This eliminates the need to run additional procedures to deploy customised configuration files to each installation. The custom configuration location does not need to be populated with content or to even exist for the deployment image to be created successfully. The custom configuration location and content will be required for production installation to be completed.

For information on using the custom configuration folder, please refer to the following:  CONNECT Edition Custom Configuration Guides

8.Choose the deployment image setting where:

• Full UI Mode - Displays all installer windows when you install using the deployment image.
• Passive UI Mode - Installs the application in passive mode from the deployment image. In this mode, the installation wizard and the progress dialog are displayed but the installation takes place automatically. The installer takes the options selected while creating the deployment image and you cannot select any options in this mode.
• No UI Mode - Installs the application in silent mode.

9.  (Optional)  Change the location of where the deployment image will be created.

10. (Optional)  Enable the creation of a desktop shortcut icon.

11. Click Done to accept your choices.

12. Click Layout to start the process.  The usual installer dialogs will appear and all needed components will be downloaded.  When done, the deployment package will be found in the location specified in Step 9 above.

13.  When done, click Finish and review the contents of the deployment image folder specified in Step 9 above.  All required files are now available and eliminates the need for  repeated downloads of the same files.

Related Article

Installing from a deployment image

An installation executable (*.exe) that contains all of the necessary pre-requisites, required and optional components can easily exceed 1GB in size.  Issues such as:

• all users must have an internet connection to download and install software,
• having multiple users download enormous executables,  
• downloading executables that contain unwanted options or components,
• and, ensuring enough free space on all users computers

are commonplace as software installations become more complex.  In response to this, software and game developers are now delivering a small executable that downloads the installation files. This includes companies such as Microsoft, Bentley, Google (Chrome), Mozilla (Firefox) and more.  Once downloaded, the administrator can create a deployment image to distribute the needed components to install the software on each users machine.    Some advantages of using a deployment image include:

• Internet connection is not required for an installation from a deployment image.
• Separate pre-requisite pack or set of packages before installing product are not required.
• The installation location can be decided and set in deployment image. Once defined, the product will be installed at the same location on all the machines.
• The components to be installed are preselected at the time of creating deployment image. This results in all machines having exactly same set of installations.

For information on creating a deployment image, please refer to: Creating a deployment image

[[- Activate Bentley Map from Civil Engineering software products]]

[[- Add a hole to an existing polygon collection]]

[[- Add a Watermark to a View]]

[[- Attribute Masking tool]]

- Auto update Editing initial values (Sync1 MDL)

[[- Bentley Map Extended Properties - An MDL Application]]

[[- Bentley Map V8i menu guide]]

- Bing Maps

[[- Cartographic Styles Intersection]]

[[- Convert plain text to XFM and propagate text string to polygons]]

[[- Create Print Layout when Adjust Mode is selected]]

[[- Creating a custom toolbox]]

[[- Creating clickable links on Feature Properties (xslt)]]

[[- Define feature scale ranges]]

[[- Difference between Remove in the Map Manager and Delete]]

[[- Dimensions in GIS]]

[[- Drop XFM features to MicroStation elements]]

[[- Edit print model legend]]

- Edit features in reference with Make Active for Edit (V8i only)

[[- Edit features in reference with reference Activate (CONNECT Edition only)]]

- Export text string and Element ID (TextNodeToTextFile VBA)

- Extended Properties (xProps MDL)

[[- Find Slivers]]

[[- Find and Replace in Data Browser]]

[[- Generating thematic classes]]

[[- Keyin to set view scale]]

- Labeling - Rounding and/or converting numerical properties

[[- Level Symbology keyins]]

- Load business properties from text strings (text2xfm VBA)

[[- Print Preparation configuration variables]]

[[- Round off automatically generated geometry values]]

[[- Saving spatial locations]]

[[- Sharing feature properties with other Bentley desktop software]]

[[- Show XFM Properties on tool tips]]

[[- Transform DGN Graphics using Warp]]

[[- Use Color Table preference not working]]

- XFM attribute query (Feature Query VBA)

- XFMize tool and example for the developer (VBA)

~ In Progress

Bentley Map refers to the V8i product line.

OpenCities Map refers to the CONNECT Edition product line.

- In progress

This article will illustrate the process of adding a Watermark to any view in an OpenCities Map or MicroStation view.  A watermark is often a faded image or text used as a background of a view or a page. It is meant to enhance, but not be the focal point of the view. Watermarks are sometimes used in the form of a logo, discreetly placed on a slide or page to brand the presentation or document*.

The process includes creating a JPEG or other image file, modifying some MicroStation Settings, and enabling the Background view attribute. The watermark will remain in the background even as you zoom in or out, modifying the view scale.

Steps:

1. Create or locate an image file that you want to use as the watermark. The format must be supported by MicroStation. We’ll use a JPEG file for this example. 

           This example shows how to include a copyright date in the lower-left corner of the view. You can use an existing file or logo, or make a new file using an imaging processing application.

The color of the white-space should match the color of the MicroStation view’s background color, white in this case. A border is not necessary, you may create the image with all of the details to meet your needs.

The size of the image should match the pixel size defined in the MicroStation view settings. The dimensions of the file & the settings can be different, just realize that some scaling may occur when they are not the same.

2. Initialize OpenCities Map or MicroStation and select the Design File Settings option from the File menu.

3. Select the Views category in the Design File Settings. Browse for the image file you created in Step 1 and enable or check the Background option:

Select OK to apply the settings and exit the dialog box.

4. If you use a white background you should review the View Options setting to see if the “Black Background > White” option is enabled.

5. Return to the DGN file and select View Attributes dialog box (use the keyboard shortcut <ctrl>+B to open the dialog). Enable the Background option and check to see that the watermark is displayed in the lower-left corner of the view. The image remains in that position as you use the view controls to zoom in, zoom out, & change the view scale. To turn the watermark off simply toggle the Background option in the View Attributes dialog.

View 1 with copyright watermark:

communities.bentley.com/.../Watermark.pdf

* Source Lifewire.com

If the thematic Map has more than one classes with cartographic style defined then a new icon appears at the right of thematic classes tool bar. It’s called Cartographic Styles Intersections and it manages the priority of display when cartographic styles intersect. This option is not available, if only a single display scale is added or if features are not symbolized with cartographic styles.

Steps:

1)     Add a couple of display scales for any one particular class. Say 0:1500, 1500: Unlimited.

2)     Once these scales are added, set the Symbology Type of each to Cartographic Styles and select some style from the available drop down menu.

3)     Once this is done, check the ‘Cartographic Style Intersection’ icon displayed.

4)     Selecting the Cartographic Styles Intersections tools will display the dialog as below. Each scale will show up with its set cartographic style. The styles are prioritized, based on how they are defined.

The components of the Cartographic Styles are drawn in priority order from left to right. Components to the right will be drawn on top of those to the left.

In the bottom pane, each thematic class is shown as a vertical line. A preview class is shown horizontally.

The display shows what each intersection will look like when crossing the preview class.

Adjusting the priority

Each component can be moved left or right to increase or decrease the priority of display. 

If two components are merged they are drawn at the same time.

If two classes have the same priority they are drawn in the order they appear in the map.

As the Cartographic Style components are moved left or right or are merged, the preview display is updated to show the effect on each class. Select different preview classes to verify how each class will look compared to the others.

When all priorities are correctly defined, select OK to save the cartographic definition.

The Attribute Masking tool is dynamic display tool which allows resymbolizing of selected elements based on certain properties.

The tool settings provides a wide number of display options.  For example, quickly see which elements are inferred features, or which are in an attached reference. 

The colour used to highlight the mask is set in your Workspace > Preferences > Symbology > Mask option.

For more information on the use of this tool, refer to:

https://docs.bentley.com/LiveContent/content/en/Bentley%20Map%20Help-v2/AttributeMaskingTool

Update March, 2019:  At this time, attribute Masking is not available in OpenCities Map CONNECT Edition Update 3

Note:  This article is specific to Bentley Map V8i.

Bentley Map V8i (SELECTseries 4) doesn't appear to honor the Use color table preference for references. This can be resolved by adding the following variable to your UCF:

MS_REFCOLORTABLE = 1

An alternate solution is to locate and open  ...\config\appl\msgeo.cfg. Navigate to Line 386 and comment outMS_REFCOLORTABLE = 2.  This is done by preceding the line with a #.  This ensures the variable is not read and is therefore undefined.  When undefined, Bentley Map will honour the Use Color Table preference. 

Additional Information:

MS_REFCOLORTABLE determines how the Use Color Table preference is used.

MS_REFCOLORTABLE = 1  MicroStation always uses the reference's color table. 
MS_REFCOLORTABLE is defined and set to any value other than 1 - MicroStation never uses the reference's color table. 
MS_REFCOLORTABLE is not defined -  MicroStation uses the user preference to determine whether or not to use the reference's color table.

Cadastral Mapping requires clean linework so that accurate area measurements can be obtained.  Early implementations of the Topology Creation and Topology Cleanup tools were written for MicroStation GeoGraphics and carried forward through the Bentley Map 2004, XM, and V8i (SELECTseries) products. 

While spatial data creation has improved over time, the data requirements (boundaries made from lines, with centroids) have not changed for these commands.  If you have areas, polygons, or other closed shapes made from MicroStation elements, you will have to use MicroStation tools to break them down into their component parts for these commands to work properly. This can be done with the Drop Element tool, or in extreme cases by redigitizing.   

The Find Slivers command can be found in the Tolology Cleanup toolbox and is used to flag or merge slivers into adjacent areas.

Slivers are very thin or small areas that are inadvertently created during digitizing or from the result of overlaying two topology layers. Removing slivers after digitizing consists of the following tasks:

• Use the Topology Cleanup tools to clean the linework
• Place centroids
• Validate the topology (repeat until the topology is completely validated)
• Remove slivers
• Create new topology layer

Consider combining Layer A+B with Layer C:

Which results in:

The Find Slivers tool can locate the erroneous sliver that was created when the layers were combined.

For details on the tool settings, please refer to:

Find Slivers Tool

To add a hole or island to an existing polygon collection feature, use the Place command with Add to Existing Collection enabled.

Then just read the prompts.

Notice that the Geometry_Area and Geometry_Perimeter will update to reflect the changes to the geometry.

communities.bentley.com/.../Add-hole-to-existing-polygon.mp4

The articles in this section relate to managing your Bentley Map projects.  Emphasis includes general articles for Workspace management and the overall operating environment, as-well as the XML Feature Modeling (XFM) engine.

[[- Bentley Geospatial Desktop Platform Extranet]]

[[- CONNECT Edition Configuration Migration tool]]

- Connecting OpenCities Map 64-bit to Microsoft Access (mdb) 32-bit

[[- Decimal Precision in GML Storage]]

[[- Dynamic Feature Scoring]]

- Feature names, groups and aliases

[[- Hide Command Manager upon startup]]

[[- How Bentley Map usage is reported in SELECTserver]]

[[- Installing two versions of Bentley Map]]

[[- Introduction to Dynamic Feature Scoring]]

[[- Locating default cartographic styles]]

[[- Migrate from Intergraph’s MGE system to Bentley Map]]

[[- Mobile Mapping Tool, software for AT&T Communications Networks]]

[[- Print Preparation configuration variables]]

[[- Remove display of geometric properties]]

[[- Reregister features when upgrading]]

[[- Silent Installation]]

[[- Using Map Finishing in a Map workspace]]

[[- XFMize tool and example for the developer]]

Download and review this Bentley Map V8i menu guide to familiarize yourself with the menus and toolbars that Bentley Map provides.

 communities.bentley.com/.../4263.Bentley-Map-V8i-_2800_SELECTsereis-4_2900_-menu-items.pdf

When you "Activate Map" from one of the Civil Engineering applications, a new "Geospatial" menu item will appear in the Tools menu.  Other menu items appear as-shown in the PDF file.

~ In progress

When using Print Preparation, you can define and select from a list of Scales in the "Add Rectangular Viewport" command, separate from the Plot Scales defined by a Geospatial Administrator Schema or DGNLIB file.

The scales presented in the list and those available at placement time are defined by a Workspace variable pointing to an XML file containing the appropriate scales. If this variable is not defined or the file is not found then the software provides certain built-in scales. The scale value will be calculated by NumDgnUnits / NumPaperUnits. If the unit in PaperUnitName and DgnUnitName is different, the values will be converted to the same unit first.

MS_GEOXFM_BORDER_SCALE_DOMAINLIST_FILE XML file describing the scales for the project.

The file is of the format below.

<?xml version="1.0" encoding="UTF-8" standalone="yes"
?>

<Scales name="BorderScales">

<scale DisplayName="1"=400'" name="1in=400'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="400.0" />

<scale DisplayName="1"=200'" name="2in=200'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="200.0" />

<scale DisplayName="1"=100'" name="3in=100'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="100.0" />

<scale DisplayName="1"=50'" name="4in=50'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="50.0" />

<scale DisplayName="1"=25'" name="5in=25'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="25.0" />

<scale DisplayName="1"=20'" name="6in=20'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="20.0" />

<scale DisplayName="1"=8'" name="7in=8'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="10.0" />

<scale DisplayName="1"=4'" name="8in=4'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="5.0" />

<scale DisplayName="1"=2'" name="9in=2'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="2.5" />

<scale DisplayName="1"=1'" name="10in=1'" PaperUnitName="Inches"
NumPaperUnits="1.0" DgnUnitName="Feet" NumDgnUnits="1.25" />

</Scales>

This information is available in the Bentley Map Help documentation.