Yes Sir.
I might ultimately have to contact ESRI directly, I am exploring every rabbit hole to no end. what I am looking into right now has me scratching my head a little.
If you look at the Desktop Help for Multiple Ring Buffer (it is a Python Example), however it shows multiple distances being passed into the Distances property.
However
if you look here (Path might be different for you)
C:\Program Files (x86)\ArcGIS\Desktop10.2\ArcToolbox\Scripts
<MultiRingBuffer.py>
Look at this it seems that each distance is ran separately then merged into a single FC at the end.
# Loop through each distance creating a new layer and then buffering the input.
# Set the step progressor if there are > 1 rings
if len(distList) > 1:
gp.SetProgressor("step", "", 0, len(distList))
stepProg = True
else:
gp.SetProgressor("default")
stepProg = False
bufferedList = []
# Buffer the input for each buffer distance. If the fieldName is different than
# the default, add a new field and calculate the proper value
for dist in distList:
if stepProg:
gp.SetProgressorPosition()
gp.SetProgressorLabel(msgBuffRings + str(dist) + "...")
bufDistance = "%s %s" % (dist, unit)
bufOutput = gp.Buffer_analysis(input, gp.CreateUniqueName("buffer", scratchWks),
bufDistance, sideType, "", dissolveOption).getOutput(0)
if fieldName.lower() != "buff_dist":
gp.AddField_management(bufOutput, fieldName, "double")
gp.CalculateField_management(bufOutput, fieldName, dist, "PYTHON")
bufferedList.append(bufOutput)
gp.ResetProgressor()
gp.SetProgressor("default")
gp.SetProgressorLabel(msgMergeRings)
This is the current rabbit hole I am chasing.