Bentley Communities
Site
Search
User
Site
Search
User
Welcome
Products
Support
About
More
Cancel
Product Communities
Geospatial
Bentley Map | OpenCities Map
More
Cancel
Bentley Map | OpenCities Map
Bentley Map | OpenCities Map Wiki
- Limitations of Esri File Geodatabase support
Sign in
-
Bentley Map | OpenCities Map Wiki
-
OpenCities Map
Working from home with OpenCities Map
+
Release Information
+
Installation Information
+
Getting Started
+
Administration
+
General Topics
+
Geospatial Administrator
-
Interoperability
- Add properties to MicroStation elements without a Map project
- Add properties to SHP files using Map
- Apply symbology when importing Esri Shapefiles
- Assign attributes when importing Shapefiles
- Connect to ESRI File Geodatabase
- Convert numerical properties upon import from SHP
- Create a join between Microsoft Excel and Esri Shapefile data
- Create join to SHP file to update properties
- Export arcs and stroking tolerance
- Export textures to CityGML
- Export thematic symbology to MicroStation
- Export to Esri Shapefile format
- Export to Google Earth, polygon issues
- Export to Shapefile makes two Shapefiles
- Exporting a DGN to shapefile with properties
- File Geodatabase and Custom Coordinate Systems
- File Geodatabase reports unknown spatial reference
- Import coordinate and property information from an XLS or CSV file
- Import INSPIRE GML using FME (Video)
- Import multiple folders of Shapefiles by using GDI key-ins
- Import Oracle data using VRT
- Import requirements for geospatial file formats
- Import text strings from point SHP properties
- Importing 3D shapefiles with elevation
- Interoperability key-ins
- Key-in to execute import for an IMPX file
- Limitations of Esri File Geodatabase support
- MXD files
- Protecting Bentley Map design file data in a MicroStation session
- Queries are not undoable
- Selecting specific feature properties when importing Shapefiles
- VRT file parameters to import Points, Lines, and Polygons
- VRT files to import ODBC and CSV data sources
+
Spatial Databases
+
Spatial Analysis
+
3D Geospatial
+
Geographic Coordinate Systems
+
Troubleshooting
+
Freeware - Utilities - Applications - Programs
+
Advanced Map Finishing
+
Bentley Cadastre
Bentley Descartes
+
Other Geospatial Products
+
Bentley Map Mobile
+
Bentley Map Mobile Publisher
Questions about this article, topic, or product? Click here.
- Limitations of Esri File Geodatabase support
The limitations of Esri File Geodatabase support is as follows
Subtypes are registered as a single feature with a domain containing the subtype values. Property based symbology rules can be used to differentiate the subtypes.
Feature data sets are registered as separate features.
Domains are supported only as coded value domains.
Relationships that can be modeled as sub features are supported. However, support is read-only. Features involved in relationships cannot be created, updated, deleted, or exported.
Annotation sub features are not supported in the Esri file geodatabase due to limitations of the API.
File Geodatabase
Interoperability
Share
History
More
Cancel
Created by
Anupama Joshi
When:
Wed, Aug 10 2016 1:52 AM
Last revision by
Inga Morozoff
When:
Wed, Oct 24 2018 2:14 PM
Revisions:
6
Comments:
0
Recommended
Related