openstreetmap-carto

There's often discussions in the default OSM map renderer project[1] about what the goal of the project should be. A lot of people have niche interests that they want implemented in the map, but that just looks busy to everybody else. [1] https://github.com/gravitystorm/openstreetmap-carto

I'm not sure if you read his recent comment (from March) where he explains the reason for blocking the PR. The reason so far is that there is no consensus on whether highway=busway should replace the additional tags one can add to indicate that a highway street is limited for buses only. > However, so far we are pretty far away from highway=busway replacing highway=\* + access=no + bus=yes as the consensus tagging for any and all bus only roads world wide. Hence my suggestion in #4226 (comment) still applies - solving #214, and in context of that think about rendering highway=busway in a way that reflects a distinct meaning (which would likely be in analogy to highway=pedestrian). A possible design approach to this is shown in https://imagico.de/blog/en/rethinking-road-access-restrictions-rendering/ So, no, it's not stagnated because t

I wouldn't compare osm-website and osm-carto at all. The commit logs are very different. openstreetmap-website: https://github.com/openstreetmap/openstreetmap-website/commi... . Numerous commits most days. openstreetmap-carto: https://github.com/gravitystorm/openstreetmap-carto/commits . So far in 2024; one small regression fixed, one niche bit of tagging added to an existing style, some largely pointless code style tidying. That's it.

Note that the author of this piece is also directly responsible for blocking the acceptance of many new features in Carto, including community-developed and broadly accepted features like highway=busway: https://github.com/gravitystorm/openstreetmap-carto/issues/4... Carto is of course just one style for OpenStreetMap, but it is also the default style shown on openstreetmap.org, with direct support from the operational team (server resources etc.). If a high-profile feature is not rendered by Carto, gaps show up all over the world where people use Carto-based screenshots, etc., and of course on openstreetmap.org. The stagnation of Carto, and thus openstreetmap.org, the website, is one of the major pain points for many mappers and developers in the OSM community, including myself. (It also highlighted the failure of the OpenStreetMap Found

The current default layer [1] has a short 'turnaround' time, meaning that changed tiles are quickly rendered, giving very short feedback time. The Tracestrack Topo is provided by a third party, without explicitly stated re-rendering turnaround times. [1]: https://github.com/gravitystorm/openstreetmap-carto

I have had a lot of "fun" with this feature in the past. It has earned a permanent place in my setup script: ALTER SYSTEM SET jit=off; Basically a performance blackhole for more complex queries. Most OSM related projects disable it straight away as it only creates headaches. https://github.com/osm-search/Nominatim/pull/2559 https://github.com/gravitystorm/openstreetmap-carto/blob/mas...

What's the advantage compared to using https://www.openstreetmap.org/ and Organic Maps, or self-hosting them? (the website is https://github.com/openstreetmap/openstreetmap-website and the tile server is https://github.com/gravitystorm/openstreetmap-carto/)

OpenStreetMap has all the curbs, sidewalks and crosswalks, too. They are not rendered in OSM Carto [1], but show up in the data, when you click on the edit link, or load the region in JOSM [2]. Here's a screenshot of the region in JOSM https://share.getcloudapp.com/X6uEexZo, and here in iD [3]: https://share.getcloudapp.com/7KuQPyLg The benches are even mapped with their 'viewing direction' and color :) [1]: The standard style on osm.org: https://github.com/gravitystorm/openstreetmap-carto [2]: The powerful editor for OSM data: https://josm.openstreetmap.de [3]: The editor behind the 'Edit' button on osm.org: https://github.com/openstreetmap/iD

The OSM style is here: https://github.com/gravitystorm/openstreetmap-carto There is an issue about converting it to vector: https://github.com/gravitystorm/openstreetmap-carto/issues/3... Doesn't seem like there's any current vector versions of that style, but you could make one yourself using Maputnik or similar; you'd probably want to start with OpenMapTiles and maybe even one of the pre-existing styles for OMT like OSM bright.

I'm not sure what you mean by "in a script form". In any case, the "authoritative" source of the template served by time.openstreetmap.org is this GitHub: https://github.com/gravitystorm/openstreetmap-carto

For a web mapping interface: * https://www.openstreetmap.org/ * https://wego.here.com/ * https://mapy.cz For maps on your phone: * Apple maps * https://maps.me/ * https://osmand.net/ * https://www.generalmagic.com/magic-earth/ * https://galileo-app.com/ For maps on your website, you'll probably have to combine a couple of services: * https://www.mapbox.com/ * https://opencagedata.com/ * http://www.thunderforest.com/ If you're willing to self-host: * https://github.com/komoot/photon * https://github.com/gravitystorm/openstreetmap-carto/blob/mas...

OSM's default road colouring is actually about to change: https://github.com/gravitystorm/openstreetmap-carto/pull/173...

Prior to the last half of August the OSM.org style had not been touched in several years. If you're seeing problems you should file a bug on the style's Github page: https://github.com/gravitystorm/openstreetmap-carto