The extent poly* features done previously, is one of the standard containers. The convex hull is the most widely used and the easiest to implement, not because of the simplicity but because of the availability of standard algorithms. Many packages use modules from the ... qhull … package.
Normally containers only make sense if you are using projected coordinates or can perform geodesic densification.
Pretty well sums it up.
Specify the input featureclass (polygon, polyline or multipoint),
The full call to the tool, or the equivalent bits that I need.
A spatial or attribute join would be another alternative if you need attributes as well.
If you have a preference let me know.
The results are derived quickly and there is an optimization if the number of points making up the shape exceed about 50. This was a qualitative estimate of the cross-over point between implementing a python solution versus a C compiled solution from qhull.
I have code that checks the validity of the file paths. If you input or output paths contain spaces or other flotsam, then the tool will not produce any results. Why? Too many questions where file paths are the problem. I won't 'enable' the current practice
You can copy the contents of the folder on my GitHub pages. No fancy install, just create a folder, through the stuff in, load the toolbox and give it a try.