...
- Both your point data and polygon data must be in PostgreSQL. They can be loaded using a Workflow Spatial Data Transformation Task, or a Data Share Connection, in Studio.
- Both datasets must contain a geometry column called wkb wkb_geometry. If the point dataset does not, then it must contain some form of spatial identifier such as Eastings and Northings or a Postcode.
- If the point data has Eastings and Northings then the function at_wkf_geo_createpointsfromxy can be used in a Workflow Stored Procedure Task (from v6.0.0 this is called wkf_geo_createpointsfromxy under the -Workflow- Function filter).
- If the point data has a Postcode, then it will be necessary to join the data to a postcode dataset containing geometries, for example Code-Point Open from the Ordnance Survey (http://www.ordnancesurvey.co.uk/oswebsite/products/code-point-open/index.html). The Workflow function at_wkf_executecmd can (from v6.0.0 this is called wkf_executecmd under the -Workflow- Function filter) can be used with a select query to join these two datasets together on a common column e.g.
...
If there is no existing count column one can be added using a Studio Workflow Stored Procedure Task. This should run the at_wkf_executecmd function (or from v6.0.0 the wkf_executecmd), creating a new table, and adding an additional column called count, that contains the value 1 (as an integer) for each row in the existing table:
...