Package: caf.space
CAF.SpaceCommon Analytical Framework (CAF) Space contains geo-processing functionality useful
for transport planners. Primarily it is a tool for generating standard weighting
translations in .csv format describing how to convert between different zoning systems.
The aim is to free tools up from directly having to do their own geo-processing, andinstead have a single source of truth to get them from! For more info seehttps://cafspace.readthedocs.io/en/latest/.Tool infoThe tool has two main options for running a translation, either a purely spatial translation (where overlapping zones are split by area), or a weighted translation where overlapping zones are split by some other type of weighting data like population or employment data. For most purposes a weighted translation will be more accurate, and it is up to the user to decide the most appropriate weighting data to use. For both types of translation the tool runs from a set of parameters within a config class. If you are using the GUI then provide parameters in the first tab. If you are not using the GUI a instance of inputs.ZoningTranslationInputs is required. This can either be loaded from a yaml file, or initialised in the code.Command Line ToolThe tool can be run from command line, with the command:python -m caf.spaceThis can be run with no arguments, which will launch the GUI, but there are also 3 arguments for running in different modes.:mode: --modemust be either "GUI" (default value), "spatial", or "weighted". "Gui" launches the GUI and the other two produce spatial or weighted zone translations respectively.config_path: --configmust be provided if mode is either "spatial" or "weighted". This is a path to the config file containing parameters for that translation.out_path: --out_pathmust be provided if either "spatial" or "weighted". This is the directory you want your translation saved to. This directory must exist and will not be generated internally.Running with all three arguments would look like:python -m caf.space --mode "spatial" --config "path/to/config.yml" --out_path "path/to/output/folder"Spatial CorrespondenceFor a spatial correspondence, the only user inputs needed are shapefiles for the two zone systems you want a translation between. The parameters required for a spatial translation are as follows:zone_1:name:The name of the first zone system you are providing. This should be as simple as possible, so for an MSOA shapefile, name should simply be MSOA.shapefile:A file path to the shapefile you want a translation for.id_col:The name of the unique ID column in your chosen shapefile. This can be any column as long as it is unique for each zone in the shapefile.point_shapefile (OPTIONAL):A path to a point shapefile if you want to include true point features in a zone system.zone_2:Parameters the same as for zone_1, it doesn't matter which order these are in, a two-way translation will be created.cache_path:File path to a cache of existing translations. This defaults to a location on a network drive, and it is best to keep it there if you have access to it.sliver_tolerance:This is a float less than 1, and defaults to 0.98. If filter_slivers (explained below) is chosen, tolerance controls how big or small the slithers need to be to be rounded away. For most users this can be kept as is.rounding:True or False. Select whether or not zone totals will be rounded to 1 after the translation is performed. Recommended to keep as True.filter_slivers:True or False. Select whether very small overlaps between zones will be filtered out. This accounts for zone boundaries not aligning perfectly when they should between shapefiles, and the tolerance for this is controlled by the tolerance parameter. With this parameter set to false translations can be a bit messy.The translation will be output as a csv to your output path location, in a folder named by the names selected for each zone system. Along with the csv will be a yml file containing the parameters the translation was run with, along with the date of the run.Weighted CorrespondenceFor a weighted translation more parameters must be provided. The tool creates a weighted translation by first joining weighting data to a lower zone system - this is a zone system smaller than the two primary zone systems. Overlaps are then found between the three zone systems to create a set of weighted tiles across the extent of the zones. These tiles are then used to create the translation. There is a more detailed explanation of this process in the documentation. Below are the additional parameters required for a weighted translation rather than a spatial one.lower_zoning:lower_zoning is a subclass of the class used for zones 1 and 2, the first three parameters for this are the same as for zones 1 and 2. The additional parameters required for lower zoning are:weight_data: File path to the weighting data for the lower zone system. This should be saved as a csv, and only needs two columns (an ID column and a column of weighting data)data_col:The name of the column in the weighting data csv containing the weight data.weight_id_col:The name of the columns in the weighting data containing the zone ids. This will be used to join the weighting data to the lower zoning, so the IDs must match, but the names of the ID columns may be different.weight_data_year:Integer. The year the weighting data is for. This is a required parameter, if you don't know when your weight data is from you should consider whether to use it. If you are using it anyway, set this to 1.method:The name of the method used for weighting (e.g. pop or emp). This can be anything, but must be included as the tool checks if this parameter exists to decide whether a weighted translation can be performed.point_handling:True or False. Choose whether point and pseudo point zones will be treated specially. For an explanation of how point zones are handled see the full documentation on readthedocs.point_tolerance:Int. The area below which polygon zones will be treated as point zones in a translation. This is only needed if point_handling is selected.