jonamat
commented
8 months ago Woah you've done a ton of work! Love your superoverlay project! I'm so glad that someone is interested in this project, I still use it when I go for a walk, but I thought I was the only one confortable with this way of finding new trails, so I never got around to fixing bugs or adding features. Thanks for the hints! Let me share my thoughts line by line:
- Elegant, I like it!
- I didn't know about those files, I will definitely use them too!
- Yes I initially developed the tool for myself, and I didn't spend much time making it fit for others
- Great idea! I need to figure out how users can set those parameters. I remember trying to make an interactive KML to send commands to the server, but no luck. maybe a settings page served from a specific url?
- I was thinking the same, but I liked the stateless approach. At that time I didnt want to implement all the stack to manage a db for the cached trails (potentially turned into a Wikiloc replica :p).
- I'm not super skilled with KMLs, I'll take a deeper look at what you've done! 7c. That's really clever, I'll think about it
And about your in-progrss works:
- Quick thought: have you ever considered authenticating through google oauth? it wont ask you for the captcha and should give you a session token, but not sure if it's possible
- I also struggled with the limitations of the KML format. the only way I found to get around it is to re-process the cookies on the server, keeping the most recent data, adding the newer ones to the payload, and removing the oldest. I'd love it if Earth Pro could handle some client-side operations, it would be a game-changer for us
Let's keep in touch, I'll go back on this as soon as I can!
nono303
Hi @jonamat, Many many Thx for this project! 🤩
I tested and used it few days with success but when I wanted to make some modifications - since I have never developed in Go - I rewrote it in a dirty PHP script with a class scrapper.
It completes my list of topo & overlay (see https://github.com/nono303/kmlsuperoverlay) for Google Earth.
Therefore, I’ll not be able to directly make a PR but here are some modifications / improvements and ideas that I have or will apply
Here is the result of an update example, to illustrate these changes
What i've done
wikiloc-earth-layer.kmlstub on/request rather than redirecting to your website)nbpageparameter (1: 24, 2: 48...)Documenttrack into aFolderwith activity type icon in left menu a. Compact display in the left menu ofFolderPlacemark-Point&Placemark-LineStringelements with<Snippet>:warning:
maxline=0attribute must be present forNetworkLink, although this is not necessary in static kmla. Changing displayed name by the technical criteria (elevation – difficulty – elevation + – distance) ... Wikiloc name are often dirty ^^
b. Description rewrite Compacted in a single html table
c. Color of the layout style depending on the difficulty (compliant with SAC notation based on the principle that 'skill' corresponds to T1 to T5 ratings) … but Wikiloc skill are often dirty too!
What's in progress
login.doendpoint is protected by a captcha.I have not (yet) found a way to do it automatically (the https://github.com/ivecanski/scrape_my_wikiloc_stats require solving the captcha via selenium...)
a. Therefore, I use the wikiloc
SESSIONcookie retrieved from my authenticated browser to use the filters.Its lifespan being short, I will dig into the point to try to find automation (note that builtin Google Earth browser doesn't allow script to resolve captcha: it's impossible to login on wikiloc and share cookie :() b. In the meantime, I plan to create a small html page where I define my criteria and this dynamically generates a
wikiloc-earth-layer.kmlstub with the parameters passed to/initwhich are then used by/update.<cookie>transmitting the list of ids in GET: we can quickly reach the limit of 2048 characters. To bypass this:a. Passing the cookie in POST but I didn't find anything https://developers.google.com/kml/documentation/kmlreference?csw=1&hl=fr#cookie
b. Passing a session identifier (server) into a kml cookie and saving the ids displayed on the server side corresponding to the kml cookie session
So, I would be glad to keep this topic open and share with you what can be improved or added on this wonderful tool - independently of the backend language :)