In: Civil Engineering
ArcGIS is a geographic information system (GIS) for working with maps and geographic information. It is used for creating and using maps, compiling geographic data, analyzing mapped information, sharing and discovering geographic information, using maps and geographic information in a range of applications, and managing geographic information in a database.
The system provides an infrastructure for making maps and geographic information available throughout an organization and across a community.
ArcGIS includes the following:
There are also server-based ArcGIS products, as well as ArcGIS products for PDAs. Extensions can be purchased separately to increase the functionality of ArcGIS.
The conforming properties are:
The properties that has the property and that does not have the property are :
NUMBERS:
These can store numbers in one of four numeric data types:
In choosing the data type, first consider the need for whole numbers versus fractional numbers. If you just need to store whole numbers, such as 12 or 12,345,678, specify a short or long integer. If you need to store fractional numbers that have decimal places, such as 0.23 or 1234.5678, specify a float or a double.
Second, when choosing between a short or long integer or between a float or double, choose the data type that takes up the least storage space. This not only minimizes the amount of storage required but also improves performance. If you need to store integers between -32,768 and 32,767 only, specify the short integer data type, because it takes up only 2 bytes, whereas the long integer data type takes up 4.If you need to store fractional numbers between -3.4E38 and 1.2E38 only, specify the float data type, because it takes up 4 bytes, whereas the double data type takes up 8.
Specifying the precision and scale allows you to restrict the range of values and number formats a field can accept, giving you greater control. For example, if you specify a float with a precision of 4 and a scale of 2, the field will accept 12.34. If you try to enter 12.345 into the field, an error message would display, as this exceeds the maximum number of digits and decimal places allowed. On the other hand, if you specify a float with a precision of 5 and a scale of 3, the field would let you enter 12.345.
Computers can only store a limited number of digits, depending on the storage space being allocated. Fields of data type double in databases and geodatabases can precisely store numbers that contain up to 15 digits only, because this is the longest number that can fit into 8 bytes of storage space. Numbers that have more digits than this are rounded and stored in a format similar to scientific notation, making them approximate numbers only. For example, if you enter the 20-digit number 12,345,678,901,234,567,890, it is rounded and stored as the 15-digit number 1.23456789012346E+19. The coded value at the end, E+19, defines the placement of the decimal point.
Floats in file and personal geodatabases can precisely store numbers that contain up to 6 digits only. For example, you could not store the number 123,456.7 precisely in a float field, because this number contains more than six digits. You can enter the number into a float field in a file or personal geodatabase, but it will be rounded to 123,457, a number containing the permissible 6 digits. If you need to store this number precisely, you could store it in a double field. Float fields in enterprise, workgroup, and desktop geodatabases and databases do not let you enter more digits than the precision for the field, so no rounding takes place.
TEXT:
A text field represents a series of alphanumeric symbols. This can include street names, attribute properties, or other textual descriptions. An alternative to repeating textual attributes in a geodatabase is to establish a coded value. A textual description would be coded with a numeric value. For example, you might code road types with numeric values by assigning a 1 to paved improved roads, a 2 to gravel roads, and so on. This has the advantage of using less storage space in the geodatabase; however, the coded values must be understood by the data user. If you define your coded values in a coded value domain in the geodatabase and associate the domain with the integer field storing your codes, the geodatabase displays the textual description.
The characters used for text vary by language. To allow text to more easily convert between languages, ArcGIS uses Unicode to encode characters.
DATES:
The date data type can store dates, times, or dates and times. The default format in which the information is presented is mm/dd/yyyy hh:mm:ss and a specification of AM or PM. When you enter date fields in the table through ArcGIS, they are converted to this format.
BLOBs:
A BLOB is data stored as a long sequence of binary numbers. ArcGIS stores annotation and dimensions as BLOBs, and items such as images, multimedia, or bits of code can be stored in this type of field. You need to use a custom loader or viewer or a third-party application to load items into a BLOB field or view the contents of a BLOB field.
Object identifiers:
The ObjectID field is maintained by ArcGIS and guarantees a unique identifier for each row in the table. Key functions in ArcGIS, such as panning, identifying features, and displaying selection sets, depend on the presence of this field and requires that the values are unique.
Since most basic ArcGIS Desktop functionality requires the ObjectID to be unique, ensure you do not duplicate ObjectID values when working directly with the database outside of ArcGIS. For example, when creating views with a one-to-many relationship, there is the possibility that ObjectIDs will be duplicated. This will cause inconsistent behavior in ArcGIS Desktopfunctionality.
When you add a database table to ArcMap, an object identifier is needed. If ArcGIS cannot find a not null, integer field to use as an object identifier, you will be prompted to choose a field. See Choose a unique identifier field for a query layer for more information.
Global identifiers:
Global ID and GUID data types store registry style strings consisting of 36 characters enclosed in curly brackets. These strings uniquely identify a feature or table row within a geodatabase and across geodatabases. This is how features are tracked in one-way and two-way geodatabase replication. Developers can use them in relationships or in any application requiring globally unique identifiers. In a relationship, if a Global ID field is the origin key, a GUID field must be the destination key. You can add global IDs to a dataset in a geodatabase by right-clicking it in the Catalog tree and clicking Add Global IDs. The geodatabase maintains these values automatically. You can create GUID fields as well, but you must maintain the field's values.
Databases with a native GUID data type, such as personal geodatabases and Microsoft SQL Server, store global ID and GUID values as 16 bytes. Databases without a native GUID data type store them as 38 bytes.
Fields of type raster:
Unlike a hyperlink that simply links a feature's field to an image, a field of type raster can actually store the raster data within or alongside the geodatabase. To learn more, see Adding raster datasets as attributes in a feature class.
Geometry:
In ArcGIS, the geometry data type indicates the type of geometry—point, line, polygon, multipoint, or multipatch—the table stores. The field stored as geometry type is called SHAPE when created through ArcGIS.
Geometry is the data type used by ArcGIS. For example, if you choose Polygon Features for a new feature class, as shown below, ArcGIS adds a SHAPE field and sets the ArcGIS data type to Geometry.
In the Field Properties section of the New Feature Class dialog box, you see the Geometry Type listed as Polygon.
If you create a feature class with a different feature type—line, point, multipoint, multipatch, dimension, or annotation—the geometry type for the SHAPE field would change accordingly—to line, point, multipoint, multipatch, or polygon for dimension and annotation.
When you create a geometry field in a feature class in a database or enterprise, workgroup, or desktop geodatabase, there is an additional data type to consider: the database data type. How the value of the SHAPE field is stored in the database depends on the geometry storage type used by the DBMS. When you create a feature class in a database, you define the spatial type of the field in the Field Properties section of the New Feature Class dialog box. When you create a feature class in a geodatabase, the geometry storage type used is determined by the GEOMETRY_STORAGE parameter setting of the configuration keyword you specify.
ArcGIS for Desktop, which is licensed under three functionality levels:
ArcGIS for Desktop Basic (formerly known as ArcView), which allows one to view spatial data, create layered maps, and perform basic spatial analysis;
ArcGIS for Desktop Standard (formerly known as ArcEditor), which in addition to the functionality of ArcView, includes more advanced tools for manipulation of shapefiles and geodatabases;
ArcGIS for Desktop Advanced (formerly known as ArcInfo), which includes capabilities for data manipulation, editing, and analysis.