where does the .size property come from in the code snippet for the ArcGIS API for Python User.items() method

AndresCastillo

 

 

maybe the .size property comes from the ArcGIS Rest API Users, groups, and items Item Resources, but if that were the case, shouldn't we access the "resources" key first, get the desired index, then calling the .size property rather than accessing the .size property directly?:

 

https://developers.arcgis.com/rest/users-groups-and-items/item-resources.htm

 

 

 

{
  "total": <total number of resources on the item>,
  "start": <the first record index in the response>,
  "num": <the number of resources in the response>,
  "nextStart": <the next entry index>,
  "resources": [
    {
      "resource": "<resource1>",
      "created": <resource1 created datetime>,
      "size": <resource1 size>
    },
    {
      "resource": "<resource2>",
      "created": <resource2 created datetime>,
      "size": <resource2 size>
    },
    {
      "resource": "<resource3>",
      "created": <resource3 created datetime>,
      "size": <resource3 size>
    }
  ]
}

 

 

jcarlson

It's coming from the Item class, but there do seem to be a number of properties there that are not fully documented in the API docs. Calling dir(Item) on a Feature Layer, for instance, I see:

[
  ...
  'title',
  'type',
  'snippet',
  ...
]

And other properties not listed. Interestingly, the documentation for the Item.update() method lists the various item properties that can be updated, and such properties are listed there!

I've also noticed that the contents of dir(Item) actually changes based on the item's type.

for i in gis.content.search('', max_items=-1):
    print(f'Length of dir: {len(dir(i))}    Type: {i.type}')

Length of dir: 143    Type: PDF
Length of dir: 145    Type: Feature Service
Length of dir: 144    Type: Feature Service
Length of dir: 142    Type: Form
Length of dir: 142    Type: Web Map

 

But that may be besides the point. The size property does seem to be consistently present across item types. There have been instances when the API docs just needed correcting.You could always submit a bug report at the Python API's GitHub repo.