Config options can be set by using @config config_option config_value;
in the MapCSS file or as parameters to pgmapcss, by using -c
or --config
, e.g. pgmapcss --config option1=value1 option2=value2 option3
(option3 will be set to 'true').
The following config options are supported:
Config option | Description | Possible values |
---|---|---|
josm_classes | when 'true', a set foo; statement will also set the class foo (synonymous to set .foo; ) |
'true' or 'false' (default) |
angular_system | choose which angular system will be used for trigonometric functions | 'degrees' (default), 'radians' |
db.srs | Spatial Reference System used in the database. Autodetected. | Usual values: 4326 (WGS-84), 900913 resp. 3857 (Spherical Mercator for Web Maps) |
db.search_path | Set a PostgreSQL search_path (works only with mode standalone) | |
unit.srs | Spatial Reference System to use for distances. If other values than 900913 are used, unexpected behaviour might happen. | 900913 |
srs | Default Spatial Reference System to use on the frontend side | 900913 when using with renderer (mode 'database-function'), 4326 otherwise |
db.hstore-only | osm2pgsql only: Do not use the separate tag columns, only use the hstore 'tags' column. Might be faster on large databases in combination with a multicolumn index on way and tags: e.g. create index planet_osm_point_way_tags on planet_osm_point using gist(way, tags). Requires --hstore-all on osm2pgsql when importing the database. | true/false |
db.overpass-url | overpass only: Use this alternative Overpass API url. default: http://overpass-api.de/api | |
offline | When compiling standalone mode, do not make any requests to the database. | true/false |
debug.profiler | during execution, show some statistics about query/processing time and count of objects. | true/false |
debug.context | show bounding box and scale denominator of requests. | true/false |
debug.counter | Count of rendered map features in comparison to map features loaded from the database. If 'verbose', print each map feature which was not rendered. | true/false/verbose |
debug.rusage | show resource usage at end of processing. | true/false |
debug.explain_queries | Print queries, their plans and count of executions to stderr (standalone mode only). | true/false |
debug.overpass_queries | overpass only: Print a debug message for each query posted to the Overpass API | true/false |
Advances options:
Config option | Description | Possible values |
---|---|---|
db.columns.node | osm2pgsql only: Specify comma-separated list of database tag columns for planet_osm_point. Usually autodetected. Needed when using offline mode. | |
db.columns.way | osm2pgsql only: Specify comma-separated list of database tag columns for planet_osm_line and planet_osm_polygon. Usually autodetected. Needed when using offline mode. | |
db.columns | osm2pgsql only: Use the specified list for db.columns.node and db.columns.way | |
db.has-hstore | osm2pgsql only: Additional tags can be read from the 'tags' column (of type hstore). Usually autodetected. Needed when using offline mode. | |
db.multipolygons | osmosis only: Specify whether the multipolygons table is present and should be used. Usually autodected. Needed when using offline mode (default: false) | true/false |
db.hstore_key_index | osm2pgsql/osmosis: Assume that there's a btree index on the specified keys (,-separated) and therefore add a tag-exists condition into the SQL query. E.g.: db.hstore_key_index=sport,amenity . | |
db.overpass-timeout | overpass only: specify timeout in seconds for queries to the Overpass API (make sure that the Overpass server accepts timeouts that long, e.g. by adding a "Timeout" parameter to Apache2). As a render job usually needs several queries, the total rendering time might be a multiple of this value. | 180 |
db.overpass-memory | overpass only: Sets the 'maxsize' parameter for an overpass query, which indicates the maximum allowed memory for the query in bytes RAM on the server. | 536870912 (512 MB) |
db.overpass-profiler | overpass only: prints all queries, their duration (incl. parsing json) and the count of returned features. | true/false |
db.overpass-blocksize | overpass only: When reading from Overpass API read in blocks of specified size. Reduces memory impact. | 67108864 (64 MB) |