---
title: "Example Queries"
slug: "example-data-lake-queries"
updated: 2026-10-27T23:12:37Z
published: 2026-10-27T23:12:37Z
canonical: "ims-handbook.cenosco.com/example-data-lake-queries"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://ims-handbook.cenosco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Example Data Lake Queries

The Data Lake service is accessed using the OData standard. Because some of the fields in the Data Lake contain JSON data, the standard OData specification is unable to filter those items. To work around this limitation, the *Path* variable was introduced to allow filtering of JSON data.

## Data Lake Contents

The metadata of the available data sources in the Data Lake can be accessed at the following location [https://ims-datalake.shell.com/odata/$metadata](https://ims-datalake.shell.com/odata/$metadata). A small section of the metadata is reproduced below.

```json
<EntityType Name="DataLakeHierarchy">
    <Property Name="Id" Type="Edm.Int64" Nullable="false"/>
    <Property Name="Plant" Type="Edm.String"/>
    <Property Name="Unit" Type="Edm.String"/>
    <Property Name="Floc" Type="Edm.String"/>
    <Property Name="FlocDescription" Type="Edm.String"/>
    <Property Name="Active" Type="Edm.Boolean"/>
<EntityType Name="DataLakeSystems">
    <Property Name="Id" Type="Edm.Int64" Nullable="false"/>
    <Property Name="Site" Type="Edm.String"/>
    <Property Name="Plant" Type="Edm.String"/>
    <Property Name="Unit" Type="Edm.String"/>
    <Property Name="SapflocId" Type="Edm.String"/>
    <Property Name="CorrosionLoops" Type="Collection(DataLakeService.Models.JsonEntities.SystemCorrosionLoops)"/>
    <Property Name="Rcmsystem" Type="Collection(DataLakeService.Models.JsonEntities.SystemRCMSystem)"/>
```

The metadata describes the structure of the data as well as the Name and Type of parameters that can be queried using OData.

You can access items contained within the DataLakeHierarchy EntityType, use the following base URL for the query:

- [](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)[](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)https://ims-datalake.shell.com/odata/datalakehierarchy?filter=[](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)[](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)

For items located within the DataLakeSystems EntityType, use the following base URL:

- [](https://ims-datalake.shell.com/odata/datalakesystems?$filter=)[](https://ims-datalake.shell.com/odata/datalakesystems?$filter=)https://ims-datalake.shell.com/odata/datalakesystems?$filter=[](https://ims-datalake.shell.com/odata/datalakesystems?$filter=)[](https://ims-datalake.shell.com/odata/datalakesystems?$filter=)

Items with Type Collection(...), contain JSON data and cannot be accessed using *filter.* Use *path* in place of *filter*, depending on the EntityType as shown in the two base URLs below:

- [](https://ims-datalake.shell.com/odata/datalakehierarchy?path=)[](https://ims-datalake.shell.com/odata/datalakehierarchy?path=)https://ims-datalake.shell.com/odata/datalakehierarchy?path=
- [](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)[](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)https://ims-datalake.shell.com/odata/datalakesystems?path=[](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)[](https://ims-datalake.shell.com/odata/datalakehierarchy?filter=)

Property Type describes the Entity Data Model (Edm) that describes the data type contained in the field. The main types of properties used are as follows:

- **Boolean:** true or false.
- **Byte:** unsigned 8-bit integer.
- **DateTimeOffset:** represents date and time.
- **Double:** floating point number with 15-digit precision.
- **Int32:** signed 32-bit integer.
- **Int64:** signed 64-bit integer.
- **String:** character data.

## OData Basic Operators

OData queries can be executed using some basic equality operators:

- **eq:** tests whether a field is equal to a value.
- **ne:** tests whether a field is NOT equal to a value.

Or using range operators:

- **gt:** test whether a field is greater than a value.
- **lt:** test whether a field is less than a value.
- **ge:** test whether a field is greater than or equal to a value.
- **le:** test whether a field is less than or equal to a value.

Take NoteFurther documentation on the OData protocol and how to construct queries can be found [here](https://www.odata.org/documentation/).

## Example URLs for OData Queries

Examples of OData filtering:

- https://ims-datalake.shell.com/odata/datalakehierarchy?filter=EquipmentNumber eq '100000754050'
- https://ims-datalake.shell.com/odata/datalakehierarchy?$filter=Floc eq 'S901-51RV154'&path=Schedule.ScheduleId eq 'CAIR00001415'

Examples of JSON filtering:

- https://ims-datalake.shell.com/odata/datalakehierarchy?path=EquipmentSpecs.Qualifier eq 'OUTSIDE DIAMETER #1' and EquipmentSpecs.ProcessMode eq 1
- https://ims-datalake.shell.com/odata/datalakehierarchy?path=EquipmentSpecs.Category eq 'GENERAL' and EquipmentSpecs.Spec eq 'START DATE'
- https://ims-datalake.shell.com/odata/datalakehierarchy?path=EquipmentSpecs.Value eq '150' and EquipmentSpecs.UoM eq 'MM'
- https://ims-datalake.shell.com/odata/datalakehierarchy?path=RCMData.Tag eq '054QR006-TX'
- https://ims-datalake.shell.com/odata/datalakehierarchy?path=Schedule.ScheduleId eq 'INSP00000216'
- https://ims-datalake.shell.com/odata/datalakesystems?path=RCMSystem.SequenceString eq 'Failure 1 A'
- https://ims-datalake.shell.com/odata/datalakesystems?path=RCMSystem.RCMSystem eq 'PU6- AIR AND NITROGEN SYSTEMS'

Example combining OData and JSON filtering:

- https://ims-datalake.shell.com/odata/datalakesystems?$filter=Plant eq 'S901-SRU'&path=CorrosionLoops.Active eq true