Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@dfsnow
Copy link
Contributor

@dfsnow dfsnow commented May 13, 2025

Hi @sjsrey. I'm Dan Snow, the research assistant that created the original pre-calculated travel times listed on the access Resources page.

I've since graduated and moved on to different work, but travel times have stayed in my heart, so I created OpenTimes, a free database of travel times between all major Census geographies and years.

I'd love to replace these old pre-calculated times with ones from OpenTimes. The OpenTimes times are easier to produce, easier to access, more accurate, and have much better coverage. They'll also be free in perpetuity. They're just a fun side project for me and a way to keep tinkering with travel times.

If nothing else, we should remove the defunct interactive map from the docs on this page.

Thanks!

@jkoschinsky
Copy link

jkoschinsky commented May 13, 2025 via email

@JamesSaxon
Copy link
Contributor

This change looks fine to me, though I might drop the "research assistant" part --

a dedicated website created by Dan Snow (UChicago MPP'19)

since Dan has not been a research assistant in quite some time!

However, it looks like the CI has also completely died in the interim. If @jGaboardi can point to how to get your current CI setup going (#48), I'd appreciate it. I owe another update here for #51, but have very little time to dedicate to this right now.

@jGaboardi
Copy link
Member

@JamesSaxon

This hitch to this will be first finishing out the modernizing efforts that have languished these past year12. Also, since libpysal itself supports python>=3.10 we should probably drop support for everything less than that.

Unless I am overthinking this? Thoughts @martinfleis @knaaptime @gegen07

Footnotes

  1. https://github.com/pysal/access/issues/48

  2. https://github.com/pysal/access/issues/49

@martinfleis
Copy link
Member

@jGaboardi fair observations imho.

@jGaboardi
Copy link
Member

@JamesSaxon

Give a thumbs up here and in my free time I will start creating tickets & pushing PRs to move towards resolve the stuff above. In order for this be as efficient as possible, I'd ask that if you don't have the bandwidth to review PRs then any other PySAL core dev's approval is sufficient.

Copy link
Member

@jGaboardi jGaboardi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved pending @JamesSaxon 's re-review and input here.

@JamesSaxon
Copy link
Contributor

JamesSaxon commented May 19, 2025

Thanks @jGaboardi,

Give a thumbs up here and in my free time I will start creating tickets & pushing PRs to move towards resolve #50 (comment). In order for this be as efficient as possible, I'd ask that if you don't have the bandwidth to review PRs then any other PySAL core dev's approval is sufficient.

In general, but also especially for infra updates, I trust any pysal owner to approve PRs.

That said, I'm generally happy to do PRs and get to them promptly, I just don't have the bandwidth to get this CI going again.

Once the CI is running reliably, I'd be happy to make a few quick fixes and clean-ups.

@JamesSaxon
Copy link
Contributor

JamesSaxon commented May 19, 2025

Barring any objections, who is squash/merging here?

@dfsnow, do you want to do the honors?

Co-authored-by: James Gaboardi <[email protected]>
@martinfleis
Copy link
Member

I don't think @dfsnow has the merge rights :).

@martinfleis martinfleis merged commit acc1d5b into pysal:main May 19, 2025
0 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants