nrw.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Wir sind eine freundliche Mastodon Instanz aus Nordrhein-Westfalen. Ob NRW'ler oder NRW-Sympathifanten, jeder ist hier willkommen.

Serverstatistik:

2,9 Tsd.
aktive Profile

#gpx

2 Beiträge2 Beteiligte0 Beiträge heute

#Biketooter :When planning a #bike #route with #FOSS and #OSM based #routing engines, such as #Brouter / #Bikerouter ,the result analysis frequently shows some #surface percentage as "unknown". I guess that's because the #information is missing in the #OpenstreetMap #database .However, when I upload the same track as #GPX into a #commercial #biking application, such as #Komoot or #Cyclers ,the "unknown" has disappeared, while they are also based on OSM. How come?

WTF moment of the day: You cannot, by any means, export custom POI lists from Google Maps.

I mean, I anyway wanted to get away from Google Maps, but hey come-on, you can export starred places and your reviews, but not the fuckin lists?!

I had to workaround and add all 150 castles my wife and me visited to starred places to get them exported...

Then converting the geojson to gpx and import to OsmAnd. Done. All locations in OsmAnd and always the possibility to export/import, do what the fuck you want with the data you created yourself. FREEDOM!

Auf Nimmerwiedersehen Google Maps, gtfooml (get the fuck out of my life).

More progress on my GPS , GPX comparison tracker!

Still not what I want, but I am getting close!

To do:

☑️I want to move the data labels to a table
☑️Calculate the difference between them
☑️color the faster day
☑️change the day to a colored dot matching the track
☑️sort them the fastest on top
☑️….

So close and yet so far! 😅

#run#gpx#runnersofmastodon

I have lots of favorites (starred places) in #OSMand and I want to view them on a map on a bigger screen, not just on the phone. When I export them, I get a favorites.gpx file.

As far as I understand, these are waypoints on a track?

I opened the file in the nextcloud map, and it displays the points, but without any text.

The entries look like this:

<wpt lat="51.5320587" lon="-0.1773316">
<time>2025-01-18T22:23:30Z</time>
<name>Abbey Road Crossing</name>
<extensions>
<osmand:amenity_subtype>attraction</osmand:amenity_subtype>
<osmand:address>Abbey Road (South Hampstead), Camden Town</osmand:address>
<osmand:amenity_origin>Amenity:Abbey Road Crossing: tourism:attraction</osmand:amenity_origin>

I tried converting the file to (geo)json, but so far the file has come out empty. I realize I don't really know what I'm looking for. It doesn't have to be nextcloud compatible at all, that was just the first thing I had on hand.

I would like to see the points and their names on a map on a bigger screen.

Any suggestions please?

#android#app#osm

Mon premier #50pasouf avec mon nouveau #vélo à ma taille. Depuis ~Orly pour un tour de la forêt de Sénart. Du bleu, un peu de vent, des fleurs, des arbres, la nature, les pitizoizo, la Seine, du single au bord de l'eau, du gras, les pieds dans la gadoue à en boucher les cales, et une côte de dingo pour remonter de la Seine sur le plateau à Juvisy 😱. Mais c'était trop bien ! 🤩☺️ Si vous voulez le #gpx... @emeline

Playing with some #GPX data for an upcoming #TrailRunning race. Two different tools come up with wildly different total elevation gain/loss numbers: Garmin says 2,600 feet and GPS Visualizer says 5,200. Just for fun, I asked Strava and they said 3,000. Evidently nobody can agree.

I think Garmin is closer to reality here, although GPS Visualizer talks a big game about the myriad elevation data sources they enlist. You can see in the attached image that the Garmin elevation profile is much smoother than the more jittery GPS Visualizer profile. I think all that jittering is the source of most of the additional 2,600 feet, although GPS Visualizer does think that some peaks are >100 feet higher than Garmin does.

If you find yourself wanting precise elevation data, who do you typically turn to?

Made some progress on my script to compare gps / gpx tracks.

It now loops over my workouts and gives me the f-score (frechet distance) in a neat dataframe so I can then compare the stats on similar workouts.

I still need to decide on a proper f-score threshold, but for what I have seen so far it looks like less than 0,002

More to come!

Mein Workflow, wenn ich eine Strecke plane oder auf dem #Garmin haben möchte:

- #GPX erstellen (bevorzugt mit bikerouter.de, weil es gibt nichts besseres!)

- GPX Datei auf Garmin kopieren (#Cloud Sync von Garmin oder File-Sync am Desktop)

Fertig.

Wüsste gar nicht, wobei ich mit #Komoot einen Vorteil gehabt hätte, wenn ich die Plattform genutzt hätte, die mit dem Verkauf von #OSM-Karten Geld macht(e).