The geographic data model defines a general model for geographic information. This model can be used to define and apply different users or special application models. By defining and improving a variety of different behaviors on a general geographic model. We have a solid foundation for a variety of users.
Like the Coverage model, geodatabase supports model models with topological relationships, which extends the Coverage model by other object-oriented elements, which have other object-oriented elements, other-oriented elements, with relationships between the transformation networks, topologies and feature classes. Esri's ArcGIS desktop applications (ArcMap, Arccatalog and Arctoolbox) work as geodatabases, like Coverages and Shapefiles.
Tools for establishing and editing geodatabases are mainly in ArcCatalog and ArcMap. ArcCatalog is constructed from various different establishment and changing geodatabase models, ArcMap, is analyzed and edited for geodatabase content.
For how to establish and edit geodatabases, please see Editing in ArcGIS
Object-oriented data model
Geographically hard model supports an object-oriented vector data model. In this model, the entity is represented by an object having attributes, behaviors, and relationships. Support for a variety of different geographic object types has been built into the system.
These object types include:
L ???????? Simple object
L ???????? Geographic elements (with location objects)
l ???????? network element (object with other elements geometric integrated relationship) Arcinfo and Arceditor ONLY
l ???????? Topological relations elements.
l ???????? Task elements. LIMITED in Arcview
l ??????? Other more special elements.
• This model is that you can build relationships between objects and define rules for the reference and topology integration between maintenance objects.
Design a geodatabase
Successful use ArcInfo and ArcSDE to complete a multi-user GIS system, start with a good data model design and database tuning. Data in the database stores, using its application, and client and server hardware configurations are key factors for successful multi-user system. Designing geodatabases is a key process, it needs to be planned and constantly corrected until it reaches your needs and platform needs. When you start your geodatabase design, please refer to Before You Create Your Geodatabase to get more advice.
The key to a geodatabase that performs high efficiency is to tun to store the database management system of the stored geographic data. You don't need to tune your personal database, but it is critical to ArcSDE. For information on database tuning for ArcSDE and geodatabases: Configuration and Tuning Guide For
PDF file.
Designing geodatabases is a key process, it needs to be planned and constantly corrected until it reaches your needs and platform needs. One, you have a design, you can build geodatabases and its architecture by loading existing Shapefiles and Coverage data. Using ArcCatalog to establish new data items, use UML and CASE tools, or these three combinations.
ArcCatalog has many tools that create and modify geodatabases, and ArcMap has tools for analyzing and editing geodatabases.
Method for establishing geodatabase
Oh, you designed a geodatabase, you can use any of these three methods to create a new geodatabase. The way you choose depends on the following factor: what is your geodatabase, whether you store custom objects to geodatabases or if you will build a new database from newly created, you usually use this three mid-term The combination. The first step is the actual geodatabase, one but the design is complete, you can use the best to build the database.
Establish a new geodatabase
In some cases, you may have no ready-made geographic data, perhaps the data is only part of your database design. In this case, you can use the tools provided by ArcCatalog to create the architecture of the data set, the table, the geometry network, and other items in the database. ArcCatalog provides a complete toolset for design and management entries. Migrate existing data to geodatabase
In most cases, you have already wanted to store data in various formats in Geodatabase --- Shapefiles, CaveRages, Info Tables and DBASE tables. You may have stored in other multi-user GIS data formats such as ArcScorm, Map Data Museum, and ArcSDE.
With ArcCatalog, you can convert the data format by importing them into the Language database. A series of dialogs will guide your conversion process. One but you are familiar with this process, more advanced batch data conversions can be more efficient. Please see how to convert data better understand this.
When data conversion, the space and non-spaced parts of each entity will be converted. For example, geometry entities and properties are stored in the geodatabase when converting ShapeFiles to feature classes. Properties can be left or changed. Shapefiles with the same spatial reference can be imported into the same elements set. All or part of the Coverage feature class can be imported into the geodatabase. Topological rules can be created to control the relationship between the elements and features of the elements stored in the geodatabase.
Establish geodatabases with CASE tools
Case, computer aided software engineering, including tools and techniques for automating software development and database design processes. You can use the CASE tool from the UML chart to create a new custom object and generate a database template.
See another article about Case tools.
You can use object-oriented design tools to establish models that represent your custom objects. Based on these models, the CASE Tool Code Generates Wizard to help you create a COM object model, which completes custom object behavior and database architecture in its production and management.
The steps to establish a custom object are as follows:
1. ??????????? Use the UML design object model of Visio2000 or Rational Rose.
2. ???????????? Put the model to XML
3. ???????????? Generate a stub code and complete the behavior.
(1-3 Reference Modeling Our World and the 'Creating Custom Behavior with the UML' PDF File In The Arcsdk Documentation.).
4. ??????????? to establish a geodatabase frame for a custom object. (Refer to Generating Schema from the Repository), rendering separately.
Deep refine geodatabase (slightly ...)
Load data into the database architecture
After building a database architecture as above, you want to add data to it. This is a different process with importing external data. You can do this, build a new object by editing the database in ArcMap, or from external data, such as: Shapefiles, Covers, Cad Feature Classes, Info Tables, DBASE TABLES ARCSTORM, or Map Librarian import objects.
The establishment and maintenance of data can include the management of version and topological information. Arccatalog and Arctoolbox have help you: Simple Data Loader and Object Loader. .
