ArcGIS REST Services Directory Login
JSON

Layer: b5_2021 (ID: 0)

Name: b5_2021

Display Field: Project_Name

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 14 0;"><SPAN>The Project information was sourced from National Treasury, Provincial Budget,2021 Estimate Provincial Revenue and Expenditure.</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN>B5 schedule coordinates were used to geolocate the project. Further desktop verification was done by using the below methodology:</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>Project datasets were sourced from various formats. Primarily from PSDF plans for different Local municipalities or districts in the Eastern Cape.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>These datasets were digitised, cleaned and imported into geo-database format.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>From here the data was assessed in terms of accuracy of the spatial information supplied in the original project datasets. </SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>Individual departmental datasets were cleaned in order to make the data schemas compatible.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>This allowed the data to be merged into one geo-database table.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>The spatial accuracy of the supplied information was assessed. The records with missing spatial coordinates were then assessed and a process of locating the correct spatial reference was undertaken.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>This process involved sourcing other spatial datasets such as human settlements, schools, health and existing projects etc.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>A join to whichever dataset was most logical was performed in order to populate the spatial fields.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>The resultant spatial locations of these projects cannot be guaranteed, therefore a field called "</SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>VERIFIED</SPAN></SPAN><SPAN><SPAN>" was created in order to indicate where possible, the data had been supplied in the original project datasets, or had been sourced and linked from other datasets. </SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 14 0;"><SPAN>Field : Verified</SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Verified</SPAN></SPAN><SPAN><SPAN>: Either coordinates were supplied in the original project datasets or it was sourced from other datasets where matches could be found. As example - where schools had no coordinates in the original project datasets, EMIS schools datasets were linked and consulted in order to match the school names so the coordinates could be transferred.</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Unverified</SPAN></SPAN><SPAN><SPAN>: No coordinates supplied with the original project datasets.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>

Service Item Id: b0693f2a2ddc43939251adb84868441b

Copyright Text: Fish.A & Tucker.A.2021. B5 Projects for Eastern Cape Province. East London.South Africa

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata