kartotherian / meddo

Kartotherian

Kartotherian is a map tile service originally built for the Wikimedia projects. Its primary components include:

• Kartotherian (readme): a map tile server tying together various open source modules from the TileLive ecosystem, thereby providing for serving tiles from a variety of sources.
• Tilerator (readme): a job scheduler used to schedule asynchronous map tile generation jobs, offering both a command-line and a GUI interface.

This is a monorepo containing (in the packages/ subdirectory) the various modules developed as part of the Kartotherian project and used in Kartotherian and Tilerator. The repo is managed using Lerna. To install the dependencies for all modules, npm install -g lerna and run the following from the project root:

lerna bootstrap --hoist --nohoist mapnik --nohoist libxmljs

The Kartotherian and Tilerator services can then be started accoring to the instructions provided in their individual READMEs.

IMPORTANT: Installing and running the Kartotherian services requires node.js 6 or 8. Node.js 10+ is not yet supported.

meddo's Issues

"pier_line" doesn't match ClearTable's "pier_line_raw"

ClearTables generate pier_line_raw table, not pier_line that's expected by meddo

Using "id" instead of "osm_id" ?

Would it make sense to use the "id" field of the vector tile, instead of "osm_id"? The "id" SHOULD be unique per layer, which I think is generally the case.

TypeError: self.project.mml.Stylesheet is not iterable

I followed the meddo's installation procedure then I would like to use meddo with kosmtik.

When I try the command: kosmtik serve data.yml, I get the following error:

/home/latitude/kosmtik/src/back/ProjectServer.js:31
for (var style of self.project.mml.Stylesheet) {
^

TypeError: self.project.mml.Stylesheet is not iterable
at Array. (/home/latitude/kosmtik/src/back/ProjectServer.js:31:44)
at Project. (/home/latitude/kosmtik/src/back/StateBase.js:27:43)
at Project. (/home/latitude/kosmtik/src/back/StateBase.js:37:13)
at DataSourceLoader.patchMML (/home/latitude/kosmtik/src/plugins/datasource-loader/index.js:51:15)
at Project. (/home/latitude/kosmtik/src/back/StateBase.js:35:74)
at done (/home/latitude/kosmtik/src/plugins/local-config/index.js:14:23)
at Project.LocalConfig.patchMML (/home/latitude/kosmtik/src/plugins/local-config/index.js:32:16)
at Project. (/home/latitude/kosmtik/src/back/StateBase.js:35:74)
at PluginsManager.handleProject (/home/latitude/kosmtik/src/back/PluginsManager.js:173:15)
at Project. (/home/latitude/kosmtik/src/back/StateBase.js:35:74)

Maybe there should be a stylesheet element in the data.yml file so I added it before Layer: but I get the same error. Am I doing something wrong?

transport vs transport_name

What is the difference between the transport and transport_name? It seems that often both identical objects are present, considerably increasing the tile size. Can we merge the two?

Add missing "maritime" field to vector tiles

Current tiles are generated without the maritime info. Is that by design?

Have consistent ordering of Layer properties in data.yml

From https://phabricator.wikimedia.org/T196202

Meddo sometimes has the properties in the order {id, geometry, description, fields, Datasource, properties} and sometimes puts properties before Datasource.

There is no technical difference to the user of the file, but it makes it easier to consistently edit and read it if they're all in the same order

Missing "buffer-size" on some layers cause web-gl rendering issues

(adding buffer-size="4" by hand into XML fixed the issue, but this should be done in yaml and with proper buffer size)

Seems that mapnik-generated tiles have bigger geometries than the allowed buffer size. I suspect this is the reason for lots of vertical & horizontal lines when drawing non-closed lines:

Shows "Geometry exceeds allowed extent, reduce your vector tile buffer size" warning in the browser console.

Similar issue with some good discussion

Clarify README's --number-processes

In README, please clarify what is the best relation between max_connections and the --number-processes. Increased by how much? How many connections does each process require? ...

If PostgreSQL max_connections is increased from the default, --number-processes can be increased.