# Measuring width of polygons, which is wider than long

Within my project I am trying to quantify and compare different submarine landslides with ArcGIS. Therefore, I created a polygon shapefile and mapped the spatial extent of each landslide. Now I want to calculate next to other parameters their exact width and length. For landslides which are longer than wide, the Minimum Bounding Geometry tool works really fine. However, some landslides are wider than long and this tool is totally misleading in such a case.

Does anyone know if there is a method/tool to calculate the real width and length?

• you can use the xmin,xmax,ymin,ymax values gis.stackexchange.com/questions/274188/… or use the code to find the longest edge of each polygon > community.esri.com/thread/…
– Mapperz
Mar 1, 2019 at 17:07
• Thanks for your comments! I added a screenshot and hope this makes it a bit more clear what I mean. The landslide shown on the screenshot is rather an textbook example. Here, I could switch length and width also manually (after I calculated them with: Minimum bounding geometry -> add attributes to table). This would give me also the information I need. However, most of the landslides are rather irregular shaped and less elongated, why I think this might not be the best way to go with. Mar 1, 2019 at 18:57

I would say no, as your length and width are not consistently (and somewhat arbitrarily) defined. That is, the areas you wish to measure are relative to the landslide location and orientation and are person-defined.

For example, in the image you post I would say the length is actually the width and the width is actually the length. You define it this way as the landslide originated from the SW to the NW (somewhat), so I get it, but what if the landslide originated from the east and spread to the north of the image?

You could do as the shoreline people do and have all landslide faces (the shorelines) defined as lines and then it would work but you need to define all your origins (landslide lines) as features otherwise only a human knows which is the length and which is the width of the resultant debris field.

This is actually a good problem to address with AI as humans with a priori knowledge can do it easily and explain it easily but preexisting technologies cannot do it automatically as it is almost impossible to solve via a rule-based, pixel-based, or and object-based system even with prior knowledge.

• Very well explained. If you wish to use non-standard definitions for "width" and "length", you must write your own definition and somehow communicate it to the program.
– csk
Mar 1, 2019 at 19:09
• Your above sentence is far more elegant than my four paragraphs yet manages to get the same point across. kudos. Mar 1, 2019 at 19:11

This is an untested answer but... generate a minimum bounding rectangle around each slide. Convert the rectangle to a line. Spit the line at each corner into four lines using Split Line at Vertices. Use Add Surface information (3D Analyst) to get the average elevation for each of the four lines. If the two long side average elevations are both higher and lower than the short sides average elevation you have slide that is wider than long.