Where would you make this request?
The AllTrails style is based on MapBox Outdoors v11, Possibly built in MapBox Studio itself, the json style has no references to Maputnik.
I use that json style in OruxMaps with some minor modifications made by me. (change from imperial to metric units and 3d enablement).
Komoot’s json style is built around the Vector Sources API from Thunderforest thunderforest.outdoors-v2
I also use it in OruxMaps with some minor modifications such as darker building colors to make them easier to recognize and enabling MapTiler 3D.
Which part of the AllTrails json code do you need to study?
Only the lines referring to NO ACCESS? Or the full json style?
I can also give you the URL for the Komoot style so you can analyze it.
You need a json style editor to be able to view it correctly or if you have enough experience with json styles you can simply use a basic text or code editor to view the style syntax.
Just a little tip = Each json style must go with its compatible json style editor. MapBox Studio only accepts its own products and sources, that is, you cannot bring a json style with MapTiler, ProtoMaps, MapLibre sources, etc. to MapBox Studio unless you do a complete re-edit of the styles changing the sources and the id resources . Maputnik It is more versatile and accepts everything except Gaia GPS styles that use sources that point to their own resources (g://…), the MapTiler editor has also improved a lot and is easy to use.
The code for the OsmAnd app itself is maintained in this repository:
But some resources like the rendering styles are in a seperate repository. Checking the default.render.xml and seeing what adjustments could be useful there would probably be the best approach
I didn’t know komoot had publically accessible code/Styles.
Would love to take a look at it once things calm down again. =)
Edit: while we are at it. Maybe we can document open resources/repositories for the apps in the wiki while we are at it, to make it easier for people to find them.
Ahh, ok, I thought you meant AllTrails.
With MapBox it is easy to access map styles with the json style retrieval API. Komoot has its own online style, whether it is private or public I couldn’t say but it is there.
Previously, a problem with the “(No Access)” or “(Private)” text was that it didn’t appear at zoom levels at which you might logically plan a route, but that’s no longer an issue since they’re now clearly shown in a different colour (red):
It depends on what you mean by that - it might mean “as a toolkit to create their own maps” (which is what it looks like AllTrails are doing above) or it might mean “just using an off the shelf MapBox style”, or it might be somewhere in between.
Here is a UK Ordnance Survey example that looks pretty close to Mapbox Outdoors, but is missing all of the vital access information that the AllTrails map has. That’s not a fault of the toolkit that MapBox provided, and might be an entirely appropriate style in some places in the world; the map that the OS present is their design choice and really doesn’t work in England and Wales.
At a stretch, you could argue that the OSMF are “using MapBox” by creating vector tiles in a Mapbox-compatible format .
Alltrails told me they can’t customize the highway=road style because Mapbox doesn’t allow it (I even submitted a bug about this). However, Strava and Komoot hide those by default, so I’m guessing this is more about overriding the default Mapbox styles rather than the tooling itself?
If I read that documentation correctly**, I think that it is saying that that schema amalgamates highway=road info a layer with some other data, and doesn’t make it easy to tell them apart (likely for reasons around keeping the tiles fast and small that make perfect sense).
That might explain the response that you got. I’m not familiar with Mapbox’s offerings these days, but would be surprised if they didn’t offer to help customers create their own schemas - though the cost of hosting that may not make financial sense to a company that “just wants to get an app out there” (although OSM Americana has written quite a bit about how to do that sort of thing on the cheap).
There is a grouping by categories to optimize both data and rendering. But if it is possible to hide or style highway=road differently, Several different map style providers do this, including AllTrails.
The solution is to bring your own vector data into MapBox Studio.
You need to bring your own Tileset to MapBox, download all the highway=road on the planet in geojson, upload them to MapBox Studio, open the style you want to edit and attach the Tileset, give it the visual style and behavior you want. It would work as a kind of patch over the MapBox data. The new Tileset should act the same as the category it is going to overlay on, I’m talking about the same behavior at different zoom levels. It’s just an idea, but you can give it a style whose geometry fits the center of the street category, it will only affect the highway=road and thus it will be represented differently than the other highway=*
this could become expensive, (depending how much data it is and at which quality you need it)
(or they have made some fundamental changes to their pricing since I last looked into it)
The main thing is to know how much all the highways=road on the planet weigh. MapBox offers a fairly large limit on views and data uploads for free accounts, I believe it’s 300 mb per month for Tileset.
The resulting geojson can be optimized since only the geometries are needed, any other data is unnecessary.
Previously I showed how the OsmAnd Walking profile (available by default) shows a path with access=no. As I mentioned, this requires switching on the “show access restrictions” option, which is off by default.
As it happens, today I’ve been looking at the downloadable “OsmAnd-Rendering” Hiking rendering. As you can see, this shows the closed way in red. Unlike the default Walking profile, you don’t need to change any defaults for this.
.
(depending how much data it is and at which quality you need it)