Aggregation Areas
UrMoAC can aggregate the results by variable areas. The aggregation can be applied to origins, destinations, or both.
Each of these “areas” consist of:
- a numeric ID (identifier);
- a polygon.
The following options are used in combination with this data type:
- --from-agg <SOURCES_AGGREGATION_AREAS>;
- --to-agg <DESTINATIONS_AGGREGATION_AREAS>.
Database Format
An aggregation area is represented using the following attributes in a database:
| Default Column Name | Type | Purpose |
|---|---|---|
| id | int/long | Names the area |
| geom | PostGIS-Polygon | Defines the area's shape |
Use --from-agg jdbc:postgresql:<DB_HOST>,<SCHEMA>.<TABLE>,<USER>,<PASSWORD> to load origin aggregation areas from a database. See Sources and Destinations for an explanation.
File (.csv) Format
You may load aggregation areas from .csv-files. Here, every area is stored in one line individually. The geometry must be a polygon, defined by subsequent x- and y-coordinates in meters. It is not necessary to close the polygon. The following example defines an aggregation area with ID “1000” having a box shape between -200;-200 and 200;200:
1000;-200;-200;200;-200;200;200;-200;200
Lines with a leading ‘#’ are omitted.
Please note that no projection is applied to aggregation areas stored in .csv files, thereby you should set --epsg 0.
The file type is recognized by the extension, i.e. use --from-agg <MYFILE>.csv and --to-agg <MYFILE>.csv to load origin or respectively destination aggregation areas from .csv-files.
File (.wkt) Format
You may load aggregation areas from .wkt-files. Here, every area is stored in one line individually. The geometry must be a closed polygon, stored as WKT. The following example defines an aggregation area with ID “1000” having a box shape between -200;-200 and 200;200:
1000;POLYGON((-200 -200, 200 -200, 200 200, -200 200, -200 -200))
Lines with a leading ‘#’ are omitted.
Please note that no projection is applied to aggregation areas stored in .wkt files, thereby you should set --epsg 0.
The file type is recognized by the extension, i.e. use --from-agg <MYFILE>.wkt; and --to-agg <MYFILE>.wkt to load origin or respectively destination aggregation areas from .wkt-files.
SUMO (.poi.xml)
You may load origin / destination aggregation areas from SUMO shapefiles.
Please note that currently only numerical shape IDs are accepted.
Please note that no projection is applied to locations stored in SUMO shapefiles files, thereby you should set --epsg 0.
The file type is recognized by the extension, i.e. use --from <MYFILE>.poi.xml and --to <MYFILE>.poi.xml to load origin or respectively destination aggregation areas from SUMO shapefiles.