Reality Capture Quotas
The Reality Capture service observes quotas to ensure that all clients get sufficient service and that runaway applications don’t consume excessive resources. APS Rate Limits and Quotas describes quotas in general.
Quotas
Reality Capture quotas limit resource consumption when using the Reality Capture service.
Scope
Quotas are enforced individually for each application (specified by client ID) that uses the Reality Capture service, and are measured at endpoint calls.
Endpoint
These quotas limit resource consumption through service endpoints.
Method |
Endpoint |
Limit Description |
Limit |
Units |
Notification |
---|---|---|---|---|---|
POST | file | The maximum uncompressed image file size after the submitted JPEG file is decompressed. The uncompressed file is a bitmap of 32 bytes per pixel, so a 512-megabyte uncompressed file is approximately 134 megapixels in size. | 512 | MB | None. The image is reduced in resolution to bring the file size within quota limits. The HTTP 200 success response shows the new file size as described below. |
POST | file | The maximum number of geo-tagged images that may be added to an aerial photoscene. | 2000 | Geo-tagged images | No immediate response. Notification comes later through the HTTP 200 response to a POST photoscene call that specifies the overloaded photoscene. Read about details below. |
POST | file | The maximum number of object images that may be added to an object photoscene. | 300 | Object images | No immediate response. Notification comes later through the HTTP 200 response to a POST photoscene call that specifies the overloaded photoscene. Read about details below. |
Quota Violation Notification
Quota violation notification differs depending on the quota that’s violated.
Image File Size Quota Violation
If an application uses POST file to submit a JPEG file that is too large after decompression to a bitmap image, the Reality Capture service downsizes the image to fit quota limitations and stores the image in a reduced-size JPEG file. The service does not report an error, but returns an HTTP 200 success response that contains the new size of the JPEG file as shown below.
To see if the JPEG file has been downsized, you must compare the reported size of the file to the original size of the file. If, for example, the original size of the submitted JPEG file “_MG_9026.jpg” was 487,221 bytes, then comparing values shows that the original image was too large and was reduced to a JPEG file of 364,436 bytes.
{
"photosceneid": "AtAuFsedTdqWdhF9VzHepp5oM9PITiuizI4xdMbz",
"Files": {
"file": [{
"filename": "_MG_9026.jpg",
"filesize": "364436",
"msg": "No error"
}]
}
}
Photoscene Maximum Images Quota Violation
If an application uses POST file to add more images to a photoscene than quotas allow, the Reality Capture service does not report an error. When the application uses POST photoscene to specify the overloaded photoscene, the endpoint returns an HTTP 200 response that contains an error code listing, 55, in the body. For example, POST photoscene returns HTTP 200 with the following body when the specified photoscene has exceeded the image quota:
{
"Error": {
"code": "55",
"msg": "Too many images have been provided to this project"
}
}
Changing Limits
APS Rate Limits and Quotas describes how to request quota changes for APS APIs.