
	Applies To

	Product(s):	MicroStation GeoGraphics
	Version(s):	V8.1
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A
	Original Author:	Bentley Technical Support Group

What databases are supported with MicroStation GeoGraphics 8.1?

The following databases may be used:

Oracle9i Database Release 2 (9.2.0.1) Enterprise Edition or Standard Edition Oracle9i
Database Release 1 (9.0.1) Enterprise Edition or Standard Edition
Oracle8i Database Release 3 (8.1.7) Enterprise Edition
Microsoft Access (via ODBC, OLEDB)
Microsoft SQL Server (via ODBC, OLEDB)
Oracle 8i, Oracle 9i (via ODBC, OLEDB)

*Oracle 10g (via ODBC, Oracle Direct Connection) using MicroStation and GeoGraphics 08.05.xx.xx releases

No Oracle Spatial functionality is available via an ODBC connection to Oracle.

For further information on connecting to a database via OLEDB, refer to TechNote 8255.

I've searched Web Downloads for GeoCoordinator and GeoSELECTools for V8. Are they available?

Yes. The functionality contained in both products is available in MicroStation GeoGraphics v8.1. The Coordinate System Tools may be found under the Tools > Coordinate System and Settings > Coordinate system. The Import/Export ESRI (shp, e00) and MapInfo (mif) functions are available under the File > Import or File > Export menu. Uncompressed ESRI coverage (e00) files may be imported only.

When I start MicroStation GeoGraphics v8.1, I seem to be missing some GeoGraphics tools from the Main toolbar. Where are they?

Navigate to Tools > GeoGraphics to display the GeoGraphics tools as additional GeoGraphics toolbars are listed here.

Is it possible to associate or link documents to graphic elements in the design file?

With ProjectWise Links functionality contained within MicroStation GeoGraphics, documents residing in a ProjectWise vault may be linked to an element in the design file. It is recommended that the ProjectWise client components be installed prior to the MicroStation GeoGraphics installation, to ensure proper configuration of GeoGraphics. The ProjectWise client components consist of the ProjectWise Explorer and the ProjectWise Generic QuickView. If the ProjectWise components are installed after the GeoGraphics installation, the variables PW_COMMONBINDIR and PW_EXPLORERBINDIR in the msgeo.ucf user configuration file must be edited to contain the correct paths. The ProjectWise Application Server must also be operational.

MicroStation GeoGraphics has returned an Oracle error message. How can I determine what the error message really means?

MicroStation GeoGraphics returns these messages (which are generated by the Oracle Server) to users so that they can diagnose, and accordingly troubleshoot their database. Spatial errors will usually be in the range of ORA-12700 to ORA-19399. For more information on errors that fall within these values, please check the following link: http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96525/e12700.htm#ERRMG110 A full list of Oracle errors message and descriptions can be found at: http://otn.oracle.com/pls/db92/db92.error_search?remark=homepage&prefill=ORA-

Note: In order to access this information Oracle requires that you have a login which may be obtained free of charge at this location: http://profile.oracle.com/jsp/reg/RegisterUser.jsp?act=5&src=1180585&language=en

Are there any sample applications I can use that demonstrate the functionality of Bentley's SDODGN API?

The SPATIALVIEWER application is now delivered with MicroStation GeoGraphics in the ..\Bentley\Program\GeoGraphics\jmdl\examples\sdodgn\viewer directory. This example application provides a graphical interface for posting and querying spatial geometries utilizing Bentley's SDOAPI technology. Documentation on the SDODGN Package may be found in the MicroStation GeoGraphics program group, under the Documentation folder.

How do I run the SPATIALVIEWER application?

MicroStation GeoGraphics comes configured to run the SPATIALVIEWER application. Open a MicroStation keyin window and type the following, exactly as it appears:

java com.bentley.sdodgn.spatialviewer.SpatialViewer

I have just upgraded to MicroStation GeoGraphics v8.1, and can log into my project, but when I access the project setup dialog the following error message is displayed: exception in thread (main) java.lang no such method error: Oracle.sdo.api.sref.srmanager:method set connection (loracle/jdbc/oracle connection;) v not found. Why?

Check to ensure that the Oracle Spatial Java Class Library version 1.0.1 SDOAPI has been installed by the user. The previously released Oracle Spatial Java Class Library version 1.0.0 is not compatible with the 8.1 and higher release. The SDOAPI zip file must be downloaded from the Oracle web site. Refer to the MicroStation GeoGraphics Readme file, requirements section for more information.

When I open my project with the Oracle Spatial connection, the project open seems slow. What can I do to improve the performance?

If you have a large number of maps registered in the GeoGraphics project, you should create indexes on the two tables that contain the information about the maps. Use the following syntax to create them:

create unique index maps_ndx on maps(mslink);
create unique index ugmap_ndx on ugmap(mapid);

Are there any considerations when upgrading to a newer version of Oracle?

Yes. When you install MicroStation GeoGraphics, you are asked to select the desired Oracle installation to be used. The path to the Oracle client files is stored in the configuration variable MS_ORACLE_HOME. If it becomes necessary after GeoGraphics has been installed, to change the version of Oracle, you must modify MS_ORACLE_HOME in the ..\Bentley\Program\MicroStation\config\appl\sdodgn.cfg file.

If I am having trouble with a spatial layer are there any Oracle tools for diagnosing the problem?

Oracle provides two very similar tools to use for validating spatial geometry's - a function SDO_GEOM.VALIDATE_GEOMETRY and a procedure SDO_GEOM.VALIDATE_LAYER. Running the Oracle function or procedure is one of the first troubleshooting steps you'll want to take if you experience undesired results with your data. This function/procedure determines whether all the geometries in a layer follow the defined rules for geometry objects. After running the function/procedure, any Oracle error number along with a unique identifier for the row are reported to the results table.

For complete instructions on SDO_GEOM.VALIDATE_GEOMETRY and SDO_GEOM.VALIDATE_LAYER please refer to the Oracle Spatial Users Guide.

Where can I find out more about Oracle's Spatial database capabilities? Is there any documentation or training material available on Oracle Spatial?

Oracle maintains a Spatial web site as part of its Technology Network. This site includes the Oracle Spatial User's Guide and Oracle Spatial Training Class material - as well as the Oracle Spatial Java Class Library (SDOAPI) that is required in order to operate MicroStation GeoGraphics.

Can I view existing spatial layers from other sources with MicroStation GeoGraphics?

MicroStation GeoGraphics will automatically see any existing spatial layers that reside in the current schema regardless of whether these layers are registered as part of a MicroStation GeoGraphics spatial project or not. Non registered layers will be available for query purposes only. Additionally, since element attribute information may be in a format unrecognized by MicroStation GeoGraphics, these layers will initially query back in pure Oracle Spatial format: point, line and polygons without style. In order to query these layers back with the desired element attributes, they will either need to be feature coded and incorporated into the project or this information can be provided via XML.

Can I view layers I created in MicroStation GeoGraphics from other spatially enabled applications?

Yes. The geometry data that is stored by MicroStation GeoGraphics is 100% Oracle Spatial and OGIS compliant. Please keep in mind however that other software may have different methods of accessing and storing element attribution information. Accordingly, layers that query back in MicroStation GeoGraphics with unique line styles, colors, and as various MicroStation element types will likely query back as pure Oracle Spatial: points, lines and polygons without style. MicroStation GeoGraphics provides storage of attribute information in XML format in an effort to make sharing of element attribute information as easy as currently possible. Advanced users can utilize this XML data to successfully reconstitute elements with correct style when using software other than MicroStation GeoGraphics.

How can I keep my data in one Oracle schema, and have many users access it?

The Sharing menu item from the MicroStation GeoGraphics Project Setup dialog will create synonyms and grant privileges required for a user to access a project that resides in another Oracle schema. The database user that owns the schema must share the project. Users attempting to access a shared project must create the variable MS_GEOPROJADMIN and set this to equal to the name of the shared schema.(we suggest you set this variable in your UCF file). Additionally, any objects owned by the user accessing the project that have the same name as an object in the shared project will take precedence over the shared object.

Should I access my spatial layers via the Map Manager or from the new Spatial query tools?

It is possible to use either the Map Manager method of retrieving spatial data for display in MicroStation GeoGraphics, or to handle spatial data as layers unto themselves. The Map Manager functionality provides integration with the traditional MicroStation GeoGraphics workflow and may be ideal for users looking to incorporate a few spatial layers into an existing dgn based project. The Spatial Query options allows for quick retrieval of an entire spatial layer or specific layer data based on spatial or attribute criteria. In general, Spatial Query provides a more powerful interface to Oracle Spatial's capabilities.

How does MicroStation GeoGraphics round trip elements from Oracle Spatial and keep MicroStation specific element attribute information?

MicroStation GeoGraphics by default relies on feature definitions to faithfully reproduce elements. However, in anticipation of future standards for storing style, we also store this information in XML format for all geometries. In MicroStation GeoGraphics, a query option "Use XML Style" is provided if you wish to override display based on feature code definitions and use XML definitions. Advanced users can utilize the XML data stored by MicroStation GeoGraphics to return elements with attributes intact when using software other than MicroStation GeoGraphics.

How can I make sure that I have all the current client and server patches from Oracle? How can I get these Oracle client and server patches?

All Oracle software and Oracle patches must be obtained through Oracle. Current software versions can be downloaded from the Oracle TechNet web site.

Oracle patches are obtained through the MetaLink web site. Note: You must have an active support service contract with Oracle in order to access this site. Please do not contact Bentley Technical Support for these patches.

How can I speed up spatial querying and posting?

A: The first step you should always take is to make sure that your network is optimized for Oracle Server, and that Oracle itself has been properly tuned for performance. A discussion of those topics is far beyond the bounds of this document however. Pertaining to MicroStation GeoGraphics performance, a good checklist of items to look into when hoping to speed up query and post time is:

When Querying:

Make sure you are querying indexed data, and that your choice of Spatial index is correct for your data.
Use the Estimate Index tool from MicroStation GeoGraphics Spatial Configuration dialog to make sure your index is created with the proper tiling levels. This tool provides an easy graphical method of accessing Oracle's procedure for index tiling suggestions.
Oracle strongly recommends that you regularly Analyze your Spatial schema.
Use the provided MicroStation GeoGraphics tools to query only the data you wish to view. For example, query back only a specific feature rather than an entire layer with just one feature turned on for display. Making use of Spatial Query's Where Clause capability is another way to ensure precise queries.
Validate your layers to ensure you are querying valid data.
Querying from a large number of layers will require more processing, and increase query times.

When Posting:

When posting data, if Spatial indexes exist they must be updated along with the table they apply to. Substantial performance gains will be seen if you drop your indexes before posting, as the overhead of updating the indexes is eliminated. Be sure to recreate your indexes after posting.
Be sure that you are posting supported element types. MicroStation GeoGraphics will pass over any unsupported elements, but will have to process this data just as it will for the successfully posted items.
Oracle strongly recommends that you regularly Analyze your Spatial schema.
Use the provided MicroStation GeoGraphics tools to post only the data you wish to view. For example if you've only made a few changes to your data, post these changes by fence or selection set rather than ALL.
Posting to a large number of layers will require more processing, and increase posting times.

What is spatial indexing and which indexing option should I be using?

A spatial index provides a mechanism to limit searches and speed up spatial queries, as well as allowing users to query on a specific geographic area. Its function is really quite similar to that of any other index in Oracle, only the data being indexed is of a spatial nature. Oracle allows you to select either R-Tree indexing or quadtree indexing (Fixed or Hybrid). R-Tree indexing is the default for Release 8.1.7 and 9i, but the decision of which indexing method is most appropriate for a layer is dependent on your data. The Oracle Spatial Users Guide goes into great depth describing indexing concepts and advising on when to use a given index type.

In Spatial Configuration, when I attempt to drag a feature into a layer table I receive the message "One invalid element skipped." How do I resolve this so that I can add this feature?

To resolve this error, go into Feature Setup and highlight the feature you wish to assign to your table/layer. Take note of the field in the Feature Setup dialog entitled "Table." This key-in field is used to associate a user attribute table with a feature. If you are using the single table model (geometry and attribute data in the same table), this entry must contain the name of the table that you want to assign the feature to. Entering the name of the attribute table here will remedy the 'invalid element' message and allow you to add the feature to the geometry and attribute table from Spatial Configuration.

Is MicroStation GeoGraphics designed to be used with Oracle Spatial projects exclusively?

No. You may use traditional (non spatial) projects that store elements in design files and attribute information in any of the supported MicroStation GeoGraphics databases.

I am looking for the MicroStation GeoGraphics locks dialog. It is no longer located under the Settings Menu?

Look for the Locks settings under the Workspace > Preferences. Change the Category to GeoGraphics and the lock settings are there. Additional settings for using the Oracle Spatial capabilities can be found in the Spatial Category.

What effect does the "Use Immediate Database Updates" setting have on my Oracle Spatial project?

If this is toggled on, any changes made to design file elements will automatically be updated in the database. There is no need to use the Spatial Post dialog to update the information into the database as elements drawn in the design file are immediately added to the spatial database layer. In addition, as features are attached to elements in the design file, they are added to the database. Use this setting with caution, as an element that is deleted from the design file will be immediately deleted from the Oracle database.

How can I autoload a project in MicroStation GeoGraphics?

There are seven MicroStation GeoGraphics configuration variables that must be defined to do this:

Variable	Function
MS_GEOPROJDIR	Sets the project directory to be opened by default
MS_GEOPROJNAME	Sets the name of the project directory
MS_GEODBCONNECT	Sets the database connection
MS_GEODBTYPE	Sets the database server in the Project Open dialog (can substitute with the wd <database name> command line switch instead, if desired)
MS_GEOINITCMD	Designates the first command to execute when MicroStation GeoGraphics is loaded
MS_GEODBLOAD	Loads the database
MS_GEODBLOGIN	Sets your database connect string login

Most of these variables must first be created before they are defined with a value. Open MicroStation GeoGraphics, and go to the Workspace > Configuration dialog box. Choose "All (By Level)" under Category, and then look for the above variables in the View/modify all configuration variables portion of the dialog. If any are not present, then you must create them by hitting the "New" button, and defining the variable name (for example, MS_GEODBCONNECT) and value (for example, 1). Here is an example of how these variables could be set to automatically load the delivered MYTOWN sample dataset:

MS_GEOPROJDIR = c:/Program Files/Bentley/Program/GeoGraphics/prj/
MS_GEOPROJNAME = mytown
MS_GEODBCONNECT = 1
MS_GEODBTYPE = odbc
MS_GEOINITCMD = project open
MS_GEODBLOAD = 1
MS_GEODBLOGIN = mytown

Note: If you are connecting to an Oracle database that requires a forward slash between username and password (for example, scott/tiger@myserver), MS_GEODBLOGIN must be defined in the MSGEO.UCF file located in the \Bentley\workspace\users\ directory. The Oracle connect string in this variable must be defined as follows:

MS_GEODBLOGIN = scott\/tiger@myserver

Note: The "\/" between scott and tiger; this is a backslash ( \ ) followed by a forward slash ( / ). MicroStation GeoGraphics will interpret this as a forward slash, which is needed for the Oracle connect string. The "\/" may only be done in the MSGEO.UCF file while opened in a text editor (such as Windows Notepad). If you don't need to use a Work Map or the Map Manager, define these variables:

MS_GEONOWORKMAP = 1
MS_GEONOMAPS = 1

By using these variables, you can automate user login so these steps don't have to be manually executed. Remember that by doing this you may compromise database security by logging in automatically.

What is TML and what can I do with it?

TML stands for Topology Macro Language. Script files, with a .tml extension are created in any text editor and executed from the MicroStation keyin window. With TML, you are able to create dynamic topology layers, which react to changes in the source data. Refer to the Topology Macro Language Command Syntax section in the GeoGraphics readme for documentation on TML. Examples of tml scripts are delivered in the \bentley\program\geographics\prj\mytown\tml directory.

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

MicroStation GeoGraphics V8.1 General [FAQ]