bchapuis commented on issue #943: URL: https://github.com/apache/incubator-baremaps/issues/943#issuecomment-3504978406
The examples stored in /examples are really introductory and they provide minimal configurations (no simplification, simple style, etc.). They are aimed at understanding the tool. The basemap stored in /basemap is the full featured example. You shouldn't need more libraries than baremaps and a working postgis installation. Normally if you follow the commands in this [README](https://github.com/apache/incubator-baremaps/blob/main/basemap/README.md) file, you should see a map that includes all the objects (oceans, buildings, highways, natural, etc.). Here are the most important ones that need to be executed: ```bash baremaps workflow execute --file create.js baremaps workflow execute --file import.js baremaps workflow execute --file refresh.js baremaps map dev --log-level DEBUG \ --tileset 'tileset.js' \ --style 'style.js' ``` The javascript format was aimed at avoiding the bloat, modularizing, and commenting. I recognize that it is not necessarily easy to understand and a kind of moving target that we refactor from time to time. I think it helps to see it as a javascript function that returns json objects that follows the [MapLibre Style Spec](https://maplibre.org/maplibre-style-spec/) or the [TileJSON Spec](https://github.com/mapbox/tilejson-spec/tree/master/3.0.0) (with extra SQL queries). Regarding the UK data differences you noticed: if after importing with the provided commands you still notice significant differences, it would be great if you could report them with screenshots in new issues and tag them with `basemap` (as in #932). The vector style is a port of OpenStreetMap Carto and a work in progress. Tracking these issues help a lot at improving the map and at documenting decisions. For instance, dashed lines do not always render as well in vector maps as in raster map due to scaling issues. Therefore, we often decide to use a line instead. Regarding the inclusion of additional data, to get started, I would store the additional data in additional tables in the same database. Then, I would add a new layer in the tileset.js and in the style.js. Depending on the zoom level you use, you may need to simplify the data and modify the import.js and refresh.js files Regarding the import error you mentioned: could you share the exact error message? This might help explain why your data appeared modified after restarting. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
