![]() ![]() The first table shows a one-to-many join. The following tables include possible outcomes of performing a join with various inputs. Then use the new feature class as input to other geoprocessing tools. Because many geoprocessing tools do not support data with duplicate Object IDs and processing such data can produce unexpected results, it is recommended that you first copy the joined layer to a new feature class using the Export Features tool. When a one-to-many join is produced by the join, the result of the join can be viewed in the attribute table, where a warning message will indicate if the table has duplicate Object IDs. If the input is a feature class or dataset path, this tool will automatically create and return a new layer with the result of the tool applied. Field aliases are persisted from the layer to the output, except when the output is a shapefile. ![]() When saving the results to a new feature class or table, the Qualified Field Names environment can be used to control whether the joined output field names will be qualified with the name of the table the field came from. To make a permanent join, either use the Join Field tool or use the joined layer as input to one of the following tools: Copy Features, Copy Rows, Export Features, or Export Table. The join will always reside in the layer, not with the data. If a data path is used, the layer will be created with the join. The Input Table parameter value can be a feature layer, a table view, or a raster layer with an attribute table. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |