# Upload issues with object or array properties

Ellipsis Drive does not support properties of type **object** or **array**.

This is because property values must remain filterable and queryable in the backend. Nested structures such as objects or arrays cannot be reliably used for filtering, indexing, or search operations.

***

#### Recommended approach

If you need to store complex structures, convert them into a **string representation** before uploading.

In Python, you can serialize the structure using:

import json

json.dumps(your\_object)

This stores the data as a JSON string.

When retrieving the data, you can reconstruct the original structure using:

json.loads(your\_string)

***

#### Time series data

If your object or array represents time series data, do not store it in feature properties.

Instead, use **series data via series/add**, which is designed for temporal and sequential datasets.

***

{% hint style="info" %}

### Further information

See the [Ellipsis Drive Python documentation](https://ellipsis-package.readthedocs.io/en/latest/) for implementation details and supported data structures.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ellipsis-drive.com/extra/troubleshooting/uploading-features-properties-type-object-or-array.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.