This dataset gives the second level of administrative divisions within the Sectors. These administrative divisions serves the purpose of land parcel referencing. The dataset gives these divisions boundaries, ID numbers, names, etc..
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.
having any query feel free to contact us.
Done
Send Feedback
KML
| Field | Value | |||||||
|---|---|---|---|---|---|---|---|---|
| Data Provenance | All applications that require administrative boundaries. | |||||||
| Dataset Source | ESRI SDE Geodatabase | |||||||
| Format | KML | |||||||
| Created | 08 Jul 2019 | |||||||
| Last updated | 23 Apr 2024 | |||||||
| Frequency of Update on Source | Daily | |||||||
|
Frequency of Update to SDP
|
Monthly
|
|||||||
|
Expected Volume/Ingestion Cycle(Daily if Real-time)
|
NA
|
|||||||
| Language | Arabic~English~Arabic~English~English~Arabic~English~English~English~English~English~English~English~English~English | |||||||
| State | active | |||||||
| Rights | Intelectual | |||||||
| License | notspecified | |||||||
| Show more | ||||||||
| Name | Description | Primary Key | Size | Datatype | Foreign Key | Range of Values | Language | Classification |
|---|---|---|---|---|---|---|---|---|
| c_prefix_a | Community Name Arabic | No | 15 | TEXT | Arabic | OPEN | ||
| c_prefix_e | Community Name English | No | 15 | TEXT | English | OPEN | ||
| cname_a | Community Name Arabic | No | 100 | TEXT | Arabic | OPEN | ||
| cname_e | Community Name English | No | 100 | TEXT | English | OPEN | ||
| comm_num | Community Number | Yes | 4 | NUMBER | English | OPEN | ||
| community_a | Prefix Arabic text used for the display | No | 200 | TEXT | Arabic | OPEN | ||
| community_e | Prefix English text used for the display | No | 200 | TEXT | English | OPEN | ||
| dgis_id | GIS internal ID text field | Yes | 7 | NUMBER | English | OPEN | ||
| label_a | Community Name Arabic with number used for labeling | No | 100 | TEXT | English | OPEN | ||
| label_e | Community Name English with number used for labeling | No | 100 | TEXT | English | OPEN | ||
| ndgis_id | Internal ID used by Arc GIS software | No | 4 | NUMBER | English | OPEN | ||
| objectid | GIS internal ID Numeric field | No | 4 | NUMBER | English | OPEN | ||
| shape | Shape of the data | No | 100 | GEOMETRY | English | OPEN | ||
| shape.area | Area of the data that is calculated automatiaclly by ARC GIS software | No | 8 | DOUBLE | English | OPEN | ||
| shape.len | Length of the data that is calculated automatiaclly by ARC GIS software | No | 8 | DOUBLE | English | OPEN | ||
| Show more Show less | ||||||||
Dubai Pulse Data API
Access resource data via a web API with powerful query support.
The Data API can be accessed via the following actions of the CKAN action API.
-
Query
https://www.dubaipulse.gov.ae/dataset/86178b92-7d7a-4d2f-b13e-b16aedf53721/resource/d22b4dd2-dded-4666-bc0b-97bd11e8e0a5/download/community.kml
-
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.
-
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