dafz_chiller_plant_optimization-open-api

Published by
DAFZA
Number of Data Files / Resources 1
Updated: 19 Sep 2021
Open Data
Optimisation of Chiller Plant
Show more
Request Permission

I acknowledge that I have read and agree to the terms and conditions

Cancel
Send Request
Your request has been successfully submitted
You will receive a confirmation within 14days time period. If you are
having any query feel free to contact us.
Done
Send Feedback
dafz_chiller_plant_optimization-open-api
Updated: 19 Sep 2021
API
Get Access
Field Value
Data Provenance
Dataset Source BMS (Building Management System)
Format API
Created 11 Dec 2019
Last updated 19 Sep 2021
Frequency of Update on Source Monthly
Frequency of Update to SDP
Monthly
Expected Volume/Ingestion Cycle(Daily if Real-time)
500 mb
Language English~English~English~English~English~English~English~English~English~English~English~English~English~English~English
State active
Rights
License notspecified
Show more
Name Description Primary Key Size Datatype Foreign Key Range of Values Language Classification
cooling_tower_kw_per_ton Cooling Tower Efficiency Kilowatt per Ton No 10 numeric Denormalized 0.00 to 9999999999 English Open
building_secondary_pump_kw_per_ton Building Secondary Pump Efficiency Kilowatt per Ton No 10 numeric Denormalized 0.00 to 9999999999 English Open
plant_trh Building Cooling Consumption in Refrigeration Ton Hours No 10 numeric Denormalized 0.00 to 9999999999 English Open
total_plant_kwh Total Plant Electrical Consumption Kilowatt Per Hours. No 10 numeric Denormalized 0.00 to 9999999999 English Open
total_plant_kw_per_ton Total Plant Efficiency Kilowatt per Ton No 10 numeric Denormalized 0.00 to 9999999999 English Open
year Measuring period-Year Yes 7 numeric Denormalized English Open
month Measuring period-Month Yes 7 nvarchar Denormalized English Open
chillers_kwh Chillers Electrical Consumption Kilowatt Per Hours. No 10 numeric Denormalized 0.00 to 9999999999 English Open
primary_pump_kwh Primary Pump Electrical Consumption Kilowatt Per Hours. No 10 numeric Denormalized 0.00 to 9999999999 English Open
condensor_pump_kwh Condensor Pump Electrical Consumption Kilowatt Per Hours. No 10 numeric Denormalized 0.00 to 9999999999 English Open
cooling_tower_kwh Cooling Tower Electrical Consumption Kilowatt Per Hours. No 10 numeric Denormalized 0.00 to 9999999999 English Open
building_secondary_pump_kwh Building Secondary Pumps Electrical Consumption Kilowatt Per Hours. No 10 numeric Denormalized 0.00 to 9999999999 English Open
chillers_kw_per_ton Chillers Efficiency Kilowatt per Ton No 10 numeric Denormalized 0.00 to 9999999999 English Open
primary_pump_kw_per_ton Primary Pump Efficiency Kilowatt per Ton No 10 numeric Denormalized 0.00 to 9999999999 English Open
condensor_pump_kw_per_ton Condensor Pump Efficiency Kilowatt per Ton No 10 numeric Denormalized 0.00 to 9999999999 English Open
Show more Show less

Dubai Pulse Data API

Access resource data via a web API with powerful query support.

Endpoints
Expand
Collapse
The Data API can be accessed via the following actions of the CKAN action API.
  • Query
    https://api.dubaipulse.gov.ae/open/dafza/dafz_chiller_plant_optimization-open-api
How to Use?
Expand
Collapse
  • End Users will receive "API Key" and "API Secret" in two separate emails on the first time Grant of a Dataset, first Purchase of a Commercial Dataset, or Purchase of an API Package. This API Key and API Secret combination should be used to generate API token and the token will need to be included in the http headers of every API call made.

    Authentication Service to generate API token: https://api.dubaipulse.gov.ae/oauth/client_credential/accesstoken?grant_type=client_credentials with body 'client_id={API Key}&client_secret={API Secret}

    Read the value of "access_token" from the response of the above service and use it in the header of every API call. The obtained API token is valid for certain duration (for example 30 minutes) after which a fresh token needs to be obtained.

    Header Name : Authorization
    Value : Bearer {access_token}

  • Query Parameters
    API calls can be made for full dataset result (subject to maximum results limit) or to a subset of results. Different filters can be applied on the results. Developers can use the attributes to apply a combination of filters with and/or conditions.
  • Limiting the Response Size
    Developers can limit the number of records returned by an API call passing the "Limit" parameter in the call. The value of the "Limit" must be less than the allowed maximum limit.
  • Limiting the Attributes
    Developers can limit the API response to specific set of attributes by passing the attribute names in the API call. The example below explains how the attributes can be specified in the API call. This feature can be used in conjunction with query parameters.
Examples
Expand
Collapse
  • Curl Command Sample:
    curl -X GET --header "Authorization: qMtn6xQapeouAlirfHXD7DWJFabV" "https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api"
  • Query Samples:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 AND zone_id=2 https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 OR zone_id=2
  • Record Limit Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?limit=10
  • Record Offset Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?order_by=primary_key_attribute&offset=10
  • Record Order By Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?order_by=location_id
  • Attribute Limiting Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 OR zone_id=2 &column=zone_id,line_name,location_id