Show HN: OpenTimes – Free travel times between U.S. Census geographies
21–30 of 56 posts
Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#22Does something like this exist for Europe?
Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#23Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#24Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#25I usually expect most features of a map to be zoom invariant, with the exception of level of detail. Having the colormap change is surprising, particularly that longer time buckets simply disappear as I zoom in. The two problems with this are that any time I zoom in or out I now have to double check the color key in case it's changed, and if I want to find a travel time for something far away I need to zoom in to find the destination and then back out to see the travel time. Perhaps you can let the user manually choose the colormap granularity/range, or find some way to have a colormap that works at all scales?
Second suggestion, related, is to display the travel time next to the geography ID in the bottom left corner. This would mitigate the issues with getting a good colormap, since I can then just hover over a geography to get its time anywhere that the colormap isn't sufficient.
Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#26OK the way you're publishing the data with Parquet and making it accessible through DuckDB is spectacular . Your README shows R and Python examples: https://github.com/dfsnow/opentimes?tab=readme-ov-file#using... I got it working with the `duckdb` terminal tool like this: INSTALL httpfs; LOAD httpfs; ATTACH 'https://data.opentimes.org/databases/0.0.1.duckdb' AS opentimes; SELECT origin_id, destination_id, duration_se…
Thanks! I hadn't seen anyone do it this way before with a very large, partitioned dataset, but it works shockingly well as long as you're not trying to `SELECT *` the entire table. Props to the DuckDB folks. Eventually I plan to add some thin R and Python wrapper packages around the DuckDB calls just to make it easier for researchers.
Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#27Very cool! I love the interactive map, but have a couple UX suggestions: I usually expect most features of a map to be zoom invariant, with the exception of level of detail. Having the colormap change is surprising, particularly that longer time buckets simply disappear as I zoom in. The two problems with this are that any time I zoom in or out I now have to double check the color key in case it's changed, and if I w…
I played around with a single static colormap for all scales but couldn't find one that worked well/looked good. Perhaps I'll add a slider that lets you manually select the values of the legend.
The second suggestion is a no-brainer. I'll definitely get that added.
Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#28It seems that it ignores bridges over rivers making the travel time wildly inaccurate.
It's just using OpenStreetMap tags for routing, so if a bridge is impassible by foot/bike according to OSM, then it won't be able to route there. See the Verrazano-Narrows Bridge in New York as an example.
Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#29Re: Show HN: OpenTimes – Free travel times between U.S. Census geographies
#30Very cool! I love the interactive map, but have a couple UX suggestions: I usually expect most features of a map to be zoom invariant, with the exception of level of detail. Having the colormap change is surprising, particularly that longer time buckets simply disappear as I zoom in. The two problems with this are that any time I zoom in or out I now have to double check the color key in case it's changed, and if I w…
These are great suggestions, thank you! I played around with a single static colormap for all scales but couldn't find one that worked well/looked good. Perhaps I'll add a slider that lets you manually select the values of the legend. The second suggestion is a no-brainer. I'll definitely get that added.