Coordinate Table To Ellipse (Defense)

Summary

Creates ellipse features from coordinates stored in a table and input data values.

Usage

  • Ellipses are stored as polygons.

  • Major axis, minor axis, and orientation values are stored as fields in a table.

  • Ellipses are constructed using a major and minor axis. When discussing the major and minor axes of an ellipse, lengths can be given in both full or half values. The Coordinate Table To Ellipse tool assumes values supplied for the major and minor axes are full values. If the Major Field parameter contains 1000.0 units, the ellipse will have a major axis length of 1000.0 from one side of the ellipse, though the center, to the other side of the ellipse.

  • The Azimuth Field parameter is measured zero units north (up) in a clockwise direction, for example, 90 degrees is east, 180 degrees is south, and 270 degrees is west.

  • The output ellipse feature class will contain individual ellipses for each row in the input table.

Syntax

CoordinateTableToEllipse(in_table, out_feature_class, x_or_lon_field, major_field, minor_field, in_coordinate_format, {distance_units}, {y_or_lat_field}, {azimuth_field}, {azimuth_units}, {coordinate_system})
ParameterExplanationData Type
in_table

The table containing the source coordinates.

Table View
out_feature_class

The feature class containing the output ellipse polygon features.

Feature Class
x_or_lon_field

The field in the input table containing the x or longitude coordinates.

Field
major_field

The field in the input table containing the major axis values.

Field
minor_field

The field in the input table containing the minor axis values.

Field
in_coordinate_format

Specifies the format of the input table coordinates.

  • DD_1Coordinates will be formatted in a decimal degrees coordinate pair stored in a single field with coordinates separated by a space, comma, or slash.
  • DD_2Coordinates will be formatted in a decimal degrees coordinate pair stored in two table fields. This is the default.
  • DDM_1Coordinates will be formatted in a degrees and decimal minutes coordinate pair stored in a single table field with coordinates separated by a space, comma, or slash.
  • DDM_2Coordinates will be formatted in a degrees and decimal minutes coordinate pair stored in two table fields.
  • DMS_1Coordinates will be formatted in a degrees, minutes, and seconds coordinate pair stored in a single table field with coordinates separated by a space, comma, or slash.
  • DMS_2Coordinates will be formatted in a degrees, minutes, and seconds coordinate pair stored in two table fields.
  • GARSCoordinates will be formatted in Global Area Reference System.
  • GEOREF Coordinates will be formatted in World Geographic Reference System.
  • UTM_BANDSCoordinates will be formatted in Universal Transverse Mercator coordinate bands.
  • UTM_ZONESCoordinates will be formatted in Universal Transverse Mercator coordinate zones.
  • USNGCoordinates will be formatted in United States National Grid.
  • MGRSCoordinates will be formatted in Military Grid Reference System.
String
distance_units
(Optional)

Specifies the unit of measurement for the major and minor axes.

  • METERSThe unit will be meters. This is the default.
  • KILOMETERSThe unit will be kilometers.
  • MILESThe unit will be miles.
  • NAUTICAL_MILESThe unit will be nautical miles.
  • FEETThe unit will be feet.
  • US_SURVEY_FEETThe unit will be U.S. survey feet.
String
y_or_lat_field
(Optional)

The field in the input table containing the latitude coordinates.

The y_or_lat_field parameter is used when the in_coordinate_format parameter is set to DD_2, DDM_2, or DMS_2.

Field
azimuth_field
(Optional)

The field in the input table containing the ellipse azimuth values.

Field
azimuth_units
(Optional)

Specifies the unit of measurement for the azimuth field.

  • DEGREESThe angle will be degrees. This is the default.
  • MILSThe angle will be mils.
  • RADSThe angle will be radians.
  • GRADSThe angle will be gradians.
String
coordinate_system
(Optional)

The spatial reference of the output feature class. The default is GCS_WGS_1984.

Spatial Reference

Code sample

CoordinateTableToEllipse example 1 (Python window)

The following Python window script demonstrates how to use the CoordinateTableToEllipse function.

import arcpy
arcpy.env.workspace = r"C:/Data.gdb"
arcpy.CoordinateTableToEllipse_defense(r"C:/CSV/TableToEllipse.csv",
                                       "Out_Ellipses",
                                       "x",
                                       "Major",
                                       "Minor",
                                       "DD_2",
                                       "KILOMETERS",
                                       "y",
                                       "Orient",
                                       "DEGREES")
CoordinateTableToEllipse example 2 (stand-alone script)

Create ellipses from tabular data and merge them into a single feature.

# Description: Create ellipses from tabular data and create a single feature 
#              representing area coverage of ellipses.

# Import system modules
import arcpy

# Set environment setting
sarcpy.env.workspace = r"C:/Data.gdb"
arcpy.env.overwriteOutput = True

# Create ellipses
input_table = r"C:/CSV/TableToEllipse.csv"
result_ellipse = "Output_Ellipse"
arcpy.CoordinateTableToEllipse_defense(input_table,
                                       result_ellipse, 
                                       "x",
                                       "Major",
                                       "Minor",
                                       "DD_2",
                                       "KILOMETERS",
                                       "y",
                                       "Orient",
                                       "DEGREES")

# Union resulting ellipses
result_union = "Output_Union"
arcpy.Union_analysis(result_ellipse, result_union)

# Dissolve polygons into one feature
result_dissolve = "Output_Dissolve"
arcpy.Dissolve_management(result_union, result_dissolve)

Environments

This tool does not use any geoprocessing environments.

Licensing information

  • Basic: Yes
  • Standard: Yes
  • Advanced: Yes

Related topics