-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#Enhancement Trace road in between the points #5
Comments
Hi @MueJosh, my first thought is that we don't have data to indicate the route which was actually taken between two waypoints, thus we would only be guessing if we chose, for example, the shortest route. This wouldn't necessarily represent the traveller's actual movements. It may be more helpful to number the waypoints in some way, or possibly give the user the ability to traverse them sequentially (i.e. an animation that moves the map view from one waypoint to the next)... You can already do this when sorting the waypoints by date, then clicking them in order. Keeping the data local (basically serverless) is an important feature of the app, for privacy, and also for the ability to freely publish the app without paying for costly cloud servers to do the processing. I wonder if this processing may be able to run locally in the browser instead of offloading to a Pi or other linux machine. The user's computer in many cases would have equivalent or better processing power than a Pi, and we even have browser support for Python nowadays. (although it may not be very performant.) I suppose the other hang-up is the user needing to download a large chunk of road network data in order to process the waypoint connections, but again this could likely be accomplished in the browser without a need to upload to a server. Your thoughts appreciated! |
Hey @ryangriggs , We are definitely just guessing, but for points that are relatively close to each other, there is a high probability that the shortest route is the correct one. Ive got osrm running (docker on windows) and it definitely works great! For points that are hundreds kilometers away (e.g. airplane) it's definitely wrong. But it looks great (lol) Understandable! Now everything works, I've changed html.index to sent a request for connecting points to localhost.5000 (container with osrm running). It takes around 1second to calculate 600 routes (thousands of kilometers!) and map them as polylines on the map (still inside the browser). I've added a function so it export the routes as a single track via kml and GPX. I've just realised that they are also doing this: geofabrik routing service The map of europe (45gb) and each country: geofabrik Europe A server is not needed but a powerful PC... and time. I'll upload the code as soon as i have time for it (and it still needs some touchups here and there), though probably no one will use it that way. |
Hi @ryangriggs It's been a few weeks (actually months) since ive last worked on my own little Program. Ive managed to get rounting to work (local via OSRM in a docker container and with external routing from https://router.project-osrm.org or other services) and it pretty much a fully working (except some smaller bugs) html application now. I have NO Time for this (my) project but dont want to dump it completely and waste the spendend time. It traces all the points and exports them as an geojson track (I think kml and GPX had some issues). It's optimised for Desktop usage- on my iPad it looks kinda odd- I still attach some Screenshots. As already mentioned, it's not perfectly working but the core functionality is doing what's it's supposed to do. Sidenote: I still don't have the new Format for the timeline (or whatever it's called now), so I can't help with that. If you're are not interested I would "dump" it in my own repository and probably won't maintain it. |
Hi, it sounds like you have created a very interesting side project based
on the Timeline Mapper. If you would like to dump the project into a
sub-folder of the Timeline Mapper project, I'm certainly fine with that. Or
if you would prefer to publish it under your own Github account please feel
free. I'm happy to link to it from the main Timeline Mapper page also.
My main concern atm with the Timeline Mapper is to build support for the
new Google export format, so the app can continue to be used moving forward.
Thanks and best regards!
…-------------------------
Ryan Griggs
Hilltop Computing
www.hilltop.net
859-328-3223
Toll Free: 1 (888) 5-HILLTOP (888-544-5586)
On Sun, Sep 22, 2024 at 1:06 PM MueJosh ***@***.***> wrote:
Your thoughts appreciated!
Hi @ryangriggs <https://github.com/ryangriggs>
It's been a few weeks (actually months) since ive last worked on my own
little Program.
Ive managed to get rounting to work (local via OSRM in a docker container
and with external routing from https://router.project-osrm.org or other
services) and it pretty much a fully working (except some smaller bugs)
html application now.
I have NO Time for this (my) project but dont want to dump it completely
and waste the spendend time.
If you are interested I can give you the code.
It works with the exported CSV from your GoogleTimelineMapper.
It traces all the points and exports them as an geojson track (I think kml
and GPX had some issues).
It's optimised for Desktop usage- on my iPad it looks kinda odd- I still
attach some Screenshots.
As already mentioned, it's not perfectly working but the core
functionality is doing what's it's supposed to do.
Sidenote: I still don't have the new Format for the timeline (or whatever
it's called now), so I can't help with that.
If you're are not interested I would "dump" it in my own repository and
probably won't maintain it.
BE6FEE1A-8BF0-43D3-9060-2969B6864DDD.jpeg (view on web)
<https://github.com/user-attachments/assets/8a18aa4c-c7e8-43e2-b386-564710ea1a5e>
16A24016-1F40-4903-94A7-5C40E7141B03.jpeg (view on web)
<https://github.com/user-attachments/assets/a35da5fc-fd9f-436a-bd89-c6d2091248f5>
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMVKGLE5J25VFUXDZ63AX3ZX32HXAVCNFSM6AAAAABIZKVPCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHA3TMOBUGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
As soon as my other (feels like hundreds) Projects are finished Id love to help with the new Export Format. |
I have something like this in mind, but the problem for that is - it can’t be done locally…
To trace tracks/roads/whatever between points there needs to be a API for routing. One great option would be OSRM, it works on a raspberry pi or inside a docker container or whatever server that’s not running windows.
Before I even attempt something like this, the program needs a function to add tracks (e.g. from “connect sequentially”) and export them in the kml and/or gpx file.
That was my initial idea (visualisation of routes without tracks and just some waypoints) and that’s why I’m pushing my features here ;) // My mothers phone didn’t track all routes (see first issue I’ve written here)
I know- The idea of this repo is to run it locally, I prefer this too(!) but my idea above can’t be done in a different way, or maybe it does? (Any ideas to do this locally are appreciated!)
while wringing my code (/editing code from THIS repo) and researching functions etc., I found some sites that do just that (paid or with datalogging or both at the same time..) but considering how good this code is working I can’t stop now.
Even when this feature won’t come here I’ll try to get it running on a Pi (though I won’t open the Pi / OSRM api to the world because of safety and my ISP wouldn’t approve any more traffic)
The text was updated successfully, but these errors were encountered: