Earlier quoted context omitted.
I think more of the issue might be the eink screens. As far as I can tell, there just aren't 5+ inch eink screens for cheap.
yes they are: https://www.waveshare.com/product/displays/e-paper.htm?___SI... A 4.37inch E-Paper in 3 colors is $24, problem is need you to program yourself (they have code sample in python, for raspberry pi), and you need a raspberry pi, case, cables, etc. Also, these cheap epaper displays are, of course, of lower quality (slower, lower resolution) than an kindle display.
Never Missing the Train Again
131–140 of 147 posts
Re: Never Missing the Train Again
#132Earlier quoted context omitted.
If you live in a city that already has a OneBusAway server How do you find a list of places it's deployed. I tried Googling "onebusaway cities" which got me this page https://onebusaway.org/onebusaway-deployments/ but that doesn't list cities like Adelaide that you mention.
See the footnote in GP's comment.
[1] New York, Seattle, Washington, D.C., San Diego, Alexandria, Victoria, Adelaide, Buenos Aires, etc.
I was trying to figure out what "etc." meant.
Re: Never Missing the Train Again
#133Maybe I'm not understanding the use case. I don't want to "take the train". I want to get from A to B. If the train is broken, the workers are on strike, the route is blocked between 1pm and 4pm, or it's outside of operating hours then I want an alternative. So for me, I actually want what Google Maps gives me (or tries to give me). I do not just want to know about trains. Maybe I want to get from the Ferry Building…
> So for me, I actually want what Google Maps gives me (or tries to give me). One thing I find is that Google Maps really, really assumes that walking is very very bad and no-one wants to do it. So for instance, if I'm going to a particular place I will get a 39 bus and then walk 15 minutes. If I ask Google how to get there, I'll get a route with two transfers; if the stars align it'll take about as long as one-bus p…
Indeed, they assume all kinds of things - with no option to customize. For example, they assume that a 1 or 2 minute transfer will happen. Which you might want to override, but can't. You have your reasons to want to route through Caltrain instead of BART... and you can't. This is a characteristic of the brand really: Google people know what's good for you. I mean, them.
Re: Never Missing the Train Again
#134This may not be strictly required by your use-case at this scale - 27MB of data is not a lot, after all. And the filter ordering performance is probably trivial given its all in memory (I'd be curious to see a benchmark!) However, a) efficiency is always good, especially on a Pi, and b) if you make the code more efficient it makes it easier to scale later if you want to.
Also, regarding the BOM problem you had, wouldn't it be nice if all APIs had a "developer feedback" mode built into it? That is, you can send feedback to the ppl who own the API endpoint by...posting to the endpoint. In this case you could send "Please remove the BOM. k thanks."
Re: Never Missing the Train Again
#135Re: Never Missing the Train Again
#136I'm kind of surprised that no one in here seems to have mentioned https://oeffi.schildbach.de/index.html so far. It does exactly what seems to be wanted here.
Re: Never Missing the Train Again
#137Earlier quoted context omitted.
Ehh... Cough, tough, bough, lough, slough, and rough called, they wanted to know when English phonology became logical and consistent, and why no one informed them about it?
Rough and cough have different sounds so... buses is the winner? Not seeing the connection.
The fact you think "busses" is a preferable spelling to "buses" because it might help you pronounce "buses" differently to "fuses" is only relevant to you yourself. I would have thought this was tautological, myself.
In summary, we could avoid all these fusses with a bit of effort to adhere to accepted usage.
Re: Never Missing the Train Again
#138Earlier quoted context omitted.
In this case, we really, really don’t want to continue using “busses” as a plural noun. Merriam-Webster is the authority. We’d rather fight our holy war over labor and center.
I sympathizzze he-ugely with what you're saying, as "busses" looks very strange to me, I admit.
Re: Never Missing the Train Again
#139BART and MUNI both support the General Transit Feed Specification.[1] There's a standard way to obtain this data. [1] https://gtfs.org/documentation/overview/#gtfs-realtime
Do you know how reliable is the realtime info? I find that Google maps very often says “bus coming in 4 min” as im watching the bus drive away. Or “delayed by 5 min” and it’s early by 2, etc.
In my experience in NYC, the subway data is extremely accurate in terms of the minimum time until the next train. The subway virtually never arrives "early".
Buses seem to have a problem where their location transmission sometimes fails for a few minutes. The system always assumes the bus is still stuck at its last reported location rather than moving. That's why you get a bus arriving when the feed says it's 4 minutes away.
A good rule of thumb is that if you see the minutes away change, e.g. from 7 to 6 minutes, it's accurate. If it's not changing (e.g. just sits at 7), it might be because it's genuinely stuck in traffic, or because it's stopped transmitting. (Which explains the "delayed by" situation you describe.)
Re: Never Missing the Train Again
#140Maybe I'm not understanding the use case. I don't want to "take the train". I want to get from A to B. If the train is broken, the workers are on strike, the route is blocked between 1pm and 4pm, or it's outside of operating hours then I want an alternative. So for me, I actually want what Google Maps gives me (or tries to give me). I do not just want to know about trains. Maybe I want to get from the Ferry Building…
If the train is broken or the workers are on strike, that will be reflected in the unexpected absence of live trains listed.
I pull up Google Maps and plug in my destination when I'm running around the city. I don't pull it up when I'm leaving my home to go somewhere I've been 500 times before.