When you attempt to add features outside the domain, you will get the following error: "The coordinates or measures are out of bounds." It is important that you do not make your resolution values so small that you will not be able to add features for your entire study area. As your resolution values get smaller, the extent of your domain also gets smaller. Because you have 2.14 billion integers, there is an outer edge for the domain. The relationship between the resolution and the x,y domain is directly proportional. You only need to be concerned about this shift if you are manually calculating your resolution and domain. The decimal-based coordinate values are also shifted during the conversion. The geodatabase actually does a little more to convert decimal values to integers. The following table shows examples of the minimum separation between coordinates, the coordinate system units, and the equivalent resolution values.Įxamples of the minimum separation between coordinates, the coordinate system units, and the equivalent resolution values The geodatabase converts them on the fly, allowing you to work with decimal numbers only, even if you are using the lowest-level ArcObjects API. Resolution values are used to convert decimal values to the integers stored in the geodatabase. Resolution values represent the minimum allowed separation between two coordinate values. Or you could decide to store centimeters, in which case you would have 2.14 billion centimeters to work with (about one-half the circumference of the earth). If you need to store meter precision, you have 2.14 billion meters to work with (approximately 53 times the circumference of the earth). It may seem that you are limited to storing 1-foot or 1-meter precision with an integer, but that is not the case you decide what your 4-byte integer units represent. You cannot create low-precision stand-alone feature classes or feature datasets within any new geodatabase you create with ArcGIS version 9.2 or higher, or within any geodatabase you have upgraded to version 9.2 or higher.Ī low-precision geodatabase stores coordinates as positive 4-byte integers that have a maximum value of 2,147,483,647. Because of this, you can create a new low-precision feature class within an existing low-precision feature dataset.
#Arcgis 10.3 environment output coordinate system upgrade
If you have upgraded a pre-9.2 geodatabase, existing feature datasets are still low precision until you upgrade the spatial references. If you create a new feature class or feature dataset with this geodatabase or import data into it, the new data will have a low-precision spatial reference. In ArcGIS 9.2 and higher, you can continue to create low-precision datasets by using a pre-9.2 geodatabase that has not been through the upgrade process. If you need to deliver data to clients who have not upgraded or you are satisfied with your existing situation, you might decide to continue using low-precision spatial references for now. However, data with low-precision spatial references continues to work in ArcGIS as it always has. To take advantage of these benefits, converting data to high precision is recommended in most cases. Compared to low precision, high-precision storage allows you to store coordinates closer together while expanding the x,y,z,m domains (the area you can store) of the dataset. The ability to store coordinates in high-precision spatial references was a new aspect introduced at ArcGIS 9.2. For information on the differences, see Migrating to high precision. Before reading this topic, you should understand the differences between low- and high-precision spatial references. To use the conversion methods, the load() method must be called first if isLoaded() is false.ĬoordinateFormatter.load().This topic only applies to creating new datasets with low-precision spatial references in ArcGIS version 9.2 or higher. The methods that convert points to formatted strings expect the point's spatialReference.The methods that convert formatted strings to points expect the spatial reference parameter to be a geographic coordinate system.
The browser must support WebAssembly for this module to work.(Added at v3.24)This module converts between points and formatted coordinate notation strings such as:
0 kommentar(er)
