Skip to content

Commit 0b3f5f8

Browse files
author
pcoma55
committed
added more direct links to troubleshooting doc
1 parent 8524ce3 commit 0b3f5f8

File tree

1 file changed

+38
-37
lines changed

1 file changed

+38
-37
lines changed

‎articles/planetary-computer/error-codes-ingestion.md

Lines changed: 38 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -16,48 +16,49 @@ This article lists the error codes that can occur when ingesting geospatial data
1616

1717
Ingestion errors can occur during various stages of the data ingestion process, including authentication, validation, transformation, and storage operations. The following table provides detailed information about each error code, its meaning, and steps to resolve the issue.
1818

19-
| Code | Error message | Details |
19+
| Code | Explanation | Troubleshooting |
2020
| --- | --- | --- |
21-
| `AssetTransformationError` | Asset transformation failed | The system failed to transform the asset during ingestion. Verify that your asset files are in a [supported format](./supported-data-types.md) and aren't corrupted. Check that the asset URLs are accessible from your ingestion source. |
22-
| `CogTransformationError` | Error occurred during COG transformation | The Cloud Optimized GeoTIFF (COG) transformation process failed. Ensure your source files are valid GeoTIFF files with proper georeferencing information. Try validating your files with GDAL tools before ingestion. |
23-
| `CogTransformationTimeout` | COG transformation timed out | The transformation process exceeded the time limit. This error typically occurs with very large files. Consider splitting large files into smaller tiles or ensure your files are already in COG format to skip transformation. |
24-
| `CanceledOperation` | Operation was canceled | The ingestion operation was manually canceled or terminated. No action required unless this error was unexpected, in which case check system logs for automatic cancellation reasons. |
25-
| `CollectionDoesNotExist` | The specified collection doesn't exist | The STAC collection ID referenced in your ingestion request doesn't exist in the GeoCatalog. [Create the collection](./create-stac-collection.md) before attempting to ingest items into it. |
26-
| `EmptyAsset` | Asset content is empty | The asset file referenced in the STAC item has no content or is 0 bytes. Verify that the asset files exist at the specified URLs and contain valid data. |
27-
| `ErrorsInBatchOperation` | Multiple errors occurred in batch operation | One or more items in a bulk ingestion operation failed. Check the operation details for specific item failures. Consider ingesting failed items individually to isolate issues. |
28-
| `GenericHttpIngestionError` | HTTP error during ingestion | A general HTTP error occurred while accessing ingestion resources. Check network connectivity and verify that all asset URLs are accessible. Review HTTP status codes in logs for specific issues. |
29-
| `GenericIngestionError` | General ingestion error occurred | An unspecified error occurred during ingestion. Check the detailed error message and system logs for more information. Contact support if the issue persists. |
30-
| `ImportFileValidationFailed` | Import file validation failed | The STAC catalog or collection file failed validation. Ensure your STAC JSON files conform to the [STAC specification](./stac-overview.md) and include all required fields. |
31-
| `IngestionAuthenticationFailed` | Authentication to ingestion source failed | The GeoCatalog couldn't authenticate to the ingestion source. Verify your [ingestion source credentials](./ingestion-source.md) are valid. For SAS tokens, ensure the token isn't past its expiration date. |
32-
| `IngestionResourceConnectionFailed` | Connection to ingestion source failed | Unable to establish connection to the storage container. Check that the storage account is accessible and that network policies allow connections from GeoCatalog. |
33-
| `IngestionResourceForbidden` | Access to ingestion source is forbidden | The GeoCatalog lacks permissions to access the resource. Ensure your [managed identity has the Storage Blob Data Reader role](./set-up-ingestion-credentials-managed-identity.md) or that your SAS token has `read` permissions. |
34-
| `IngestionResourceTimeout` | Ingestion source access timed out | The request to access the ingestion source exceeded the time limit. This error can indicate network issues or an unresponsive storage service. Retry the operation or check Azure service health. |
35-
| `IngestionResourceUriNotFound` | Resource URI wasn't found | The specified asset or catalog URI doesn't exist. Verify all URLs in your STAC items point to existing files. Check for typos in file paths and ensure files haven't been moved or deleted. |
36-
| `InternalError` | Internal service error occurred | An unexpected error occurred within the GeoCatalog service. Retry the operation. If the error persists, contact support with the operation ID and timestamp. |
37-
| `InternalIntermitentError` | Intermittent internal error occurred | A temporary internal error occurred. Wait a few minutes and retry the operation. These errors typically resolve automatically. |
38-
| `InvalidAssetHref` | Asset href URL is invalid | The asset URL in the STAC item is malformed or invalid. Ensure all asset hrefs are properly formatted URLs pointing to accessible resources. Use absolute URLs, not relative paths. |
39-
| `InvalidGeoparquet` | GeoParquet file is invalid | The GeoParquet file doesn't meet the required format specifications. Validate your GeoParquet files using appropriate tools and ensure they contain valid geometry columns. |
40-
| `InvalidInputData` | Input data for ingestion is invalid | The STAC item or collection data contains invalid fields or values. Review the [STAC item creation guide](./create-stac-item.md) and validate your JSON against the STAC schema. |
41-
| `InvalidStacCatalog` | STAC catalog format is invalid | The STAC catalog structure doesn't conform to specifications. Ensure your catalog follows the [STAC catalog specification](https://github.com/radiantearth/stac-spec/blob/master/catalog-spec/catalog-spec.md) with proper links and child references. |
42-
| `ItemAlreadyExistsInCollection` | Item with this ID already exists | A STAC item with the same ID already exists in the collection. Use unique IDs for each item or delete the existing item before attempting to ingest again. |
43-
| `ItemSizeExceeded` | Item size exceeds limit | The STAC item JSON is too large. Reduce the number of assets or properties in the item. Consider splitting large items into multiple smaller items. |
44-
| `ItemTransformationError` | Item transformation error occurred | Failed to process or transform the STAC item. Verify that all required STAC fields are present and that datetime values are properly formatted. |
45-
| `ManagedIdentityInfoNotFound` | Managed identity information not found | The specified managed identity doesn't exist or isn't associated with the GeoCatalog. [Configure a managed identity](./set-up-ingestion-credentials-managed-identity.md) for your GeoCatalog. |
46-
| `NoRecordsToDelete` | No records found to delete | The delete operation didn't find any matching records. Verify the STAC item IDs or search criteria used for deletion. |
47-
| `NoRecordsToPatch` | No records found to patch | The patch operation didn't find any matching records. Ensure the STAC items you're trying to update exist in the collection. |
48-
| `NoRecordsToUpdate` | No records found to update | The update operation didn't find any matching records. Verify that the items exist before attempting updates. |
49-
| `OperationIsCanceled` | Operation was canceled | The ingestion operation was canceled before completion. Check if this was intentional or if system limits triggered automatic cancellation. |
50-
| `OperationNotExistsInCollection` | Operation not found in collection | The referenced operation ID doesn't exist for this collection. Verify you're using the correct operation ID and collection. |
51-
| `PatchValidation` | Patch validation failed | The patch operation contains invalid data or operations. Ensure your patch follows [JSON Patch](https://jsonpatch.com/) specifications and targets valid fields. |
52-
| `PostItemCollectionSizeExceeded` | Item collection POST size exceeded | The batch of items being posted is too large. Reduce the number of items in a single request or use the [bulk ingestion API](./bulk-ingestion-api.md) for large datasets. |
53-
| `PublicAccessRestricted` | The data you're trying to ingest restricted public access | The storage resource doesn't allow public access. Configure proper [ingestion sources](./ingestion-source.md) with appropriate authentication instead of using public URLs. |
54-
| `StacValidationFailed` | STAC item validation failed | The STAC item doesn't meet validation requirements. Use STAC validation tools to check your items and ensure all required fields are present with valid values. |
55-
| `TotalAssetsExceeded` | Maximum number of assets exceeded | The STAC item contains too many assets. Reduce the number of assets per item or split into multiple items. Check service limits for maximum assets per item. |
21+
| `AssetTransformationError` | The system failed to transform the asset during ingestion. | • Verify asset files are in a [supported format](./supported-data-types.md)<br>• Check that asset files aren't corrupted<br>• Ensure asset URLs are accessible from your ingestion source |
22+
| `CogTransformationError` | The Cloud Optimized GeoTIFF (COG) transformation process failed. | • Ensure source files are valid GeoTIFF files with proper georeferencing information<br>• Validate your files with GDAL tools before ingestion |
23+
| `CogTransformationTimeout` | The COG transformation process exceeded the time limit, typically with very large files. | • Split large files into smaller tiles<br>• Convert files to COG format before ingestion to skip transformation |
24+
| `CanceledOperation` | The ingestion operation was manually canceled or terminated. | • No action required for intentional cancellations<br>• Check system logs for automatic cancellation reasons |
25+
| `CollectionDoesNotExist` | The STAC collection ID referenced in your ingestion request doesn't exist. | • [Create the collection](./create-stac-collection.md) before attempting to ingest items into it |
26+
| `EmptyAsset` | The asset file referenced in the STAC item has no content or is 0 bytes. | • Verify asset files exist at the specified URLs<br>• Ensure asset files contain valid data |
27+
| `ErrorsInBatchOperation` | One or more items in a bulk ingestion operation failed. | • Check operation details for specific item failures<br>• Try ingesting failed items individually to isolate issues |
28+
| `GenericHttpIngestionError` | A general HTTP error occurred while accessing ingestion resources. | • Check network connectivity<br>• Verify all asset URLs are accessible<br>• Review HTTP status codes in logs for specific issues |
29+
| `GenericIngestionError` | An unspecified error occurred during ingestion. | • Check detailed error messages and system logs<br>• Contact support if the issue persists |
30+
| `ImportFileValidationFailed` | The STAC catalog or collection file failed validation. | [Troubleshooting STAC validation errors](./troubleshooting-ingestion.md#cause-2-stac-metadata-validation-failed) |
31+
| `IngestionAuthenticationFailed` | The GeoCatalog couldn't authenticate to the ingestion source. | [Troubleshooting access permission issues](./troubleshooting-ingestion.md#cause-1-geocatalog-cant-access-source-data) |
32+
| `IngestionResourceConnectionFailed` | Unable to establish connection to the storage container. | [Troubleshooting access permission issues](./troubleshooting-ingestion.md#cause-1-geocatalog-cant-access-source-data) |
33+
| `IngestionResourceForbidden` | The GeoCatalog lacks permissions to access the resource. | [Troubleshooting access permission issues](./troubleshooting-ingestion.md#cause-1-geocatalog-cant-access-source-data) |
34+
| `IngestionResourceTimeout` | The request to access the ingestion source exceeded the time limit. | • Retry the operation<br>• Check Azure service health for outages<br>• Verify network connectivity between GeoCatalog and storage |
35+
| `IngestionResourceUriNotFound` | The specified asset or catalog URI doesn't exist. | [Troubleshooting access permission issues](./troubleshooting-ingestion.md#cause-1-geocatalog-cant-access-source-data) |
36+
| `InternalError` | An unexpected error occurred within the GeoCatalog service. | • Retry the operation<br>• If the error persists, contact support with the operation ID and timestamp |
37+
| `InternalIntermitentError` | A temporary internal error occurred. | • Wait a few minutes and retry the operation<br>• These errors typically resolve automatically |
38+
| `InvalidAssetHref` | The asset URL in the STAC item is malformed or invalid. | • Ensure all asset hrefs are properly formatted URLs<br>• Use absolute URLs, not relative paths<br>• Verify all URLs point to accessible resources |
39+
| `InvalidGeoparquet` | The GeoParquet file doesn't meet the required format specifications. | • Validate GeoParquet files using appropriate tools<br>• Ensure files contain valid geometry columns |
40+
| `InvalidInputData` | The STAC item or collection data contains invalid fields or values. | [Troubleshooting STAC validation errors](./troubleshooting-ingestion.md#cause-2-stac-metadata-validation-failed) |
41+
| `InvalidStacCatalog` | The STAC catalog structure doesn't conform to specifications. | [Troubleshooting STAC validation errors](./troubleshooting-ingestion.md#cause-2-stac-metadata-validation-failed) |
42+
| `ItemAlreadyExistsInCollection` | A STAC item with the same ID already exists in the collection. | • Use unique IDs for each item<br>• Delete the existing item before attempting to ingest again |
43+
| `ItemSizeExceeded` | The STAC item JSON exceeds the maximum allowed size. | • Reduce the number of assets or properties in the item<br>• Split large items into multiple smaller items |
44+
| `ItemTransformationError` | Failed to process or transform the STAC item. | [Troubleshooting STAC validation errors](./troubleshooting-ingestion.md#cause-2-stac-metadata-validation-failed) |
45+
| `ManagedIdentityInfoNotFound` | The specified managed identity doesn't exist or isn't associated with the GeoCatalog. | [Troubleshooting access permission issues](./troubleshooting-ingestion.md#cause-1-geocatalog-cant-access-source-data) |
46+
| `NoRecordsToDelete` | The delete operation didn't find any matching records. | • Verify the STAC item IDs or search criteria used for deletion<br>• Confirm items exist in the specified collection |
47+
| `NoRecordsToPatch` | The patch operation didn't find any matching records. | • Ensure the STAC items you're trying to update exist in the collection<br>• Verify item IDs are correct |
48+
| `NoRecordsToUpdate` | The update operation didn't find any matching records. | • Verify that the items exist before attempting updates<br>• Check item IDs and collection IDs for accuracy |
49+
| `OperationIsCanceled` | The ingestion operation was canceled before completion. | • Check if cancellation was intentional<br>• Review system logs for automatic cancellation triggers |
50+
| `OperationNotExistsInCollection` | The referenced operation ID doesn't exist for this collection. | • Verify you're using the correct operation ID and collection |
51+
| `PatchValidation` | The patch operation contains invalid data or operations. | • Ensure your patch follows [JSON Patch](https://jsonpatch.com/) specifications<br>• Verify patch operations target valid fields |
52+
| `PostItemCollectionSizeExceeded` | The batch of items being posted exceeds the size limit. | • Reduce the number of items in a single request<br>• Use the [bulk ingestion API](./bulk-ingestion-api.md) for large datasets |
53+
| `PublicAccessRestricted` | The storage resource doesn't allow public access. | [Troubleshooting access permission issues](./troubleshooting-ingestion.md#cause-1-geocatalog-cant-access-source-data) |
54+
| `StacValidationFailed` | The STAC item doesn't meet validation requirements. | [Troubleshooting STAC validation errors](./troubleshooting-ingestion.md#cause-2-stac-metadata-validation-failed) |
55+
| `TotalAssetsExceeded` | The STAC item contains too many assets. | • Reduce the number of assets per item<br>• Split into multiple items<br>• Check service limits for maximum assets per item |
5656

5757
## Related content
5858

5959
- [Ingest data into Microsoft Planetary Computer Pro](./ingestion-overview.md)
6060
- [Configure an ingestion source using managed identity](./set-up-ingestion-credentials-managed-identity.md)
6161
- [Configure an ingestion source using SAS tokens](./set-up-ingestion-credentials-sas-tokens.md)
6262
- [Create a STAC Item](./create-stac-item.md)
63-
- [Bulk Ingestion API](./bulk-ingestion-api.md)
63+
- [Bulk Ingestion API](./bulk-ingestion-api.md)
64+
- [Troubleshooting data ingestion in Microsoft Planetary Computer Pro](./troubleshooting-ingestion.md)

0 commit comments

Comments
 (0)