deck.gl based visualiser of the TFL Api + National Rails to be able to track (with minimal drift) a train along the way in London and to the nearest airports. If you pick one from any platform in https://nexttrain.london basically you can share your train journey along the rails. Build to test Cloudflare workers and their infra along with deck.gl performance that is incredible in my opinion.
This is a fun idea and interesting implementation. I know there's only so much an api can give you, but I'd love to see anything that gives more information or visuals of the surroundings.
I'd love to see a view with all/many trains. In London I was constantly wondering what the criss-cross of underground lines looked like.
Interesting but quite buggy. Example: mouse dragging seems trapped in a fairly small area.
It would appear you are missing the High Barnet branch of the Northern line.
Very nice, but the map seems to be in the wrong position vs. the trains/3d elements.
There seems to be some parallax issues between your trip layer and your 3D Tiles layer, but nice usage of deck.gl.
Having just taken the Elisabeth Line to LHR T5 and sitting here, this was fun. Thanks.
Edit: Is there a Repo to look at and learn from this?
This is really cool!
Quick suggestion: When not tracking a train, the mouse wheel should zoom into / out from where the cursor is pointing, rather than the center of the window.
This is incredibly cool. I had it open on my desktop for most of the day.
A bit buggy in term of tiles jonctions
model rough but amazing. i cant do this
I'm curious what the 3D model source is - the Gherkin is kinda weird.
The train paths are drawn on a 2D layer above the buildings, not at z-index that matches the proper 3-D position. So the paths appear to weave around and over the tops of buildings.
This is frustratingly close to amazing. Obviously you went through all the trouble of pulling all the data from all the trains and displaying them in 3d, but then lock our view on to just one train or one station while all that interesting information zips around in the periphery. The view port needs to be more free form...less on rails.