-
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
Explore compatibility and integration with spflow #15
Comments
Hi @Robinlovelace, I am very open to the idea of integratiing {si}/{od} and {spflow}. The main goal of {spflow} is to implement efficient estimators for spatial econometric interaction models. Since you raised the issue of modeling a situation where the origin and destination characteristics are distinct, I would like to point to an article I am working on with Christine Thomas https://www.tse-fr.eu/sites/default/files/TSE/documents/doc/wp/2022/wp_tse_1312.pdf. For in-sample predictions (fitted values), {spflow} already provides several methods, but for out-of-sample predictions, there are still some hurdles to overcome. An integration with
In order for {od}'s data structures to be directly usable by {spflow}, they would have to provide the following information:
I don't know if this is something you are considering. |
Hi Lukas, quickfire follow-up: many thanks for your detailed and positive response. It sounds like {si} and {spflow} could work well together and I look forward to trying to use models generated by your package as an argument in |
Hi Robin, I also think {si} and {spflow} have great potential to complement each other. The disaggregation + jittering approach presented in your article is a great solution to the problem of representing OD flows in road networks. If you want to test the package you should know that the current version of {spflow} only allows modeling of "textbook data", where origins are equal to destinations and all potential flows are observed. |
Building on #14 how does this package link with the spflow package?
Heads-up @LukeCe, thinking that using models from functions in your package could be an input into
si_predict()
. Sound reasonable? Any input welcome, input could go both ways so any code/ideas in here, e.g. use of the od package that does the OD data processing, that could help your work let me know.The text was updated successfully, but these errors were encountered: