No, the above link is not valid for “Min karta”. “Terrängkartan” (and some others) are open data, but in general the aerial imagery in “Min karta” is not open data and you cannot use it for Openstreetmap editing.

Have a look at the bottom of this page: https://www.lantmateriet.se/tips-minkarta for more info.

SRTM data is probably far too coarse in resolution and has too low accuracy. The trail can have lots of small “ups and downs” that are too small to be in any DEM dataset, but still contribute to the trail being hard.

Thanks for the links, I will check them out!

I hope you will be able to report your progress on the OSM diary, it will be an interesting read. Best of luck!

This is important, and rather difficult. I try to add the mtb:scale tag when adding/editing trails, but I find it hard to be consistent. For instance, a path may be rather easy (technically) for the most part, but has a small section that is difficult. Sometimes I then divide the path into sections with different values for “mtb:scale” but I do not want to divide the path into too many sections. It is also hard to remember this when I edit the map after a bike ride; it is easier to remember the overall feel of a whole path.

Would it be possible to use, say, data from Strava (or similar) to calculate the difficulty? Or directly from uploaded gps tracks? Of course one needs to know if each individual trace is from biking or hiking and so on. And it is quite dependent on who is hiking/riding as well.

Regarding visualization, I know that the OsmAnd mobile app can show mtb:scale on the map. I use it quite a lot and agree that it would be useful for other map applications as well.

Excellent, I’ve been looking for a guide like this, thanks!

How difficult is it to change the styling and/or what features that are included in the resulting img-file? For instance, Since I am often using my Garmin in the forest, I do not want the forests to be shown at att, since that is kind of the default state, so removing forests or change the style for them would be very useful…

Very impressive mapping; good work!

Nice post; it’s nice to read about this kind of mapping-adventures.

While I’m comfortable using the mouse for my edits, I think this is really clever. Good work!

I am not sure have the different apps (Strava, Komoot, etc) calculate routes and which OSM-attributes they use. I usually add mtb:scale to the paths I ride, but it is quite difficult to be consistent when deciding on the mtb:scale attribute.

Have you looked at the OSM wiki for the description of smoothness and mtb:scale?

osm.wiki/Key:smoothness osm.wiki/Key:mtb:scale

Anyway, best of luck!

You can set up an Openstreetmap account and then do the edit yourself in a web browser.

Good luck

The reason that the map download took longer than other apps may be that OsmAnd contains more map details and hence the download is larger.

Regarding addresses, OsmAnd only contains Openstreetmap data (plus elevation contours) and so if the adresses are not in Openstreetmap, they will not be found in OsmAnd. So let’s all work towards more complete adresses in Openstreetmap.

Seems to work nicely, good work!

Nice to hear there are other fatbikers out there!

Do you mean that the trails are temporary and only exist during winter?

I did some similar tests around 2013, comparing a smartphone and the Garmin eTrex30. Then I could clearly see that the smartphone did fairly well out in the open, but as soon as I entered a forest it lost accuracy much more than the eTrex did.

Do you have any idea wether your new Garmin outdoor GPS might be better than my old eTrex (from 2012)?

Interesting read. I’m looking forward to the next part.

Looks very nice!

Fantastic work, well done!

Nice work!

Men kan MapWithAI hitta något annat än vägar? Jag provade lite snabbt i JOSM och fick bara några vägar, som visserligen hade hyfsad geometri men ingen vidare taggning. Hur funkar MapWithAI med okorrigerad satellitdata? Ofta ligger ju Bing/Mapbox/Maxar fel, dessutom olika fel på olika platser och på olika zoomnivåer…

För vägar skulle jag absolut använda NVDB! Geometrin är bra (kan vara halvdan på riktigt små grusvägar) och alla info man behöver finns med. Sen får man ju göra manuellt arbete med att jämka samman det man vill importera från NVDB med befintliga vägar i OSM, men så är det ju alltid när man vill importera saker.

För att kartera större områden där det saknas data i Sverige (trol glesbygd främst) tror jag på: 1. NVDB för vägar 2. LM Marktäckesdata för skogar och större ytor 3. Namn på saker/platser från Ekonomiska kartan / Terrängkartan 4. LM terrängkartan för tex “berg i dagen”, våtmarker mm. Dessa behöver justeras manuellt från satellitbilder. Även en del traktorvägar kan tas från Terrängkartan även om jag inte tror att dom är särskilt aktuella i vissa fall. 5. Byggnader manuellt ritade från satellitbilder. Alternativt med AI-stöd. 6. Finlir från satellitbilder, ev- Mapillary bilder osv.

I am quite sure that Strava Heatmap used to be available as a layer in JOSM. But then Strava changed the free heatmap to be low-res only, making it less useful. It’s a shame that Strava, that use OSM data themselves, do not want to contribute to the OSM project. Higher OSM data quality would benefit them also.

I’d recommend using a GIS-software for this, since you want an EPS file. Use QGIS since it is free software, then download shapefiles from (for instance) Geofabrik.de . Load the shapefiles in QGIS, set up the styles you wish to have, then export a map to PDF or similar.