Skip to content
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

Analyse nationwide planning application data from Planit #50

Open
Robinlovelace opened this issue Feb 1, 2021 · 3 comments
Open

Analyse nationwide planning application data from Planit #50

Robinlovelace opened this issue Feb 1, 2021 · 3 comments
Labels
stretch Stretch targets that go substantially beyond the minimum viable product (mvp)

Comments

@Robinlovelace
Copy link
Contributor

Split-out from the mega issue #13.

Robinlovelace added a commit that referenced this issue Feb 1, 2021
@mvl22
Copy link
Contributor

mvl22 commented Feb 1, 2021

Can you clarify what the "analysis" means in this case - what kinds of things about the data are being analysed? Can hopefully then give some input.

Is this perhaps just this one (which it sounded like Andrew is also having a look at possibly?) :

  • Analyse the existing large datasets to find out which are not actually large

@Robinlovelace
Copy link
Contributor Author

Can you clarify what the "analysis" means in this case - what kinds of things about the data are being analysed? Can hopefully then give some input.

What % of trips are made by active travel in areas with new developments compared with national averages?#

What range of JTS scores are most commonly associated with new development locations and how do they compare with national averages and ranges?

What are average distances to city centres, rail stations, bus stops?

How can answers to all these questions be visualised. In the first instance exploratory data analysis and visualisation will be enough. It would be good to feed results into app 1 and maybe app 2 also. Sound reasonable? Any other thoughts very welcome, good to have it as a separate issue leaving #13 to focus on analysis to support correct identification of large (10 or more dwellings, right?) developments.

@Robinlovelace Robinlovelace added the stretch Stretch targets that go substantially beyond the minimum viable product (mvp) label Feb 17, 2021
Robinlovelace added a commit that referenced this issue Mar 2, 2021
@Robinlovelace
Copy link
Contributor Author

Robinlovelace commented Mar 2, 2021

Place to start:

  • Visualise - map for the report
  • Exploratory data analysis what the data looks like for the report

% active travel in the area directly dev. sites.

  • Population weighted % walking, % cycling and % active associated with developments vs national

JTS variables to get for each development:

  • Average travel time in minutes to the nearest x where x is the destination type (workplace, shops, schools etc) by public transport (the priority because we don't have PT data in there)
  • Average travel time in minutes to the nearest x where x is the destination type (workplace, shops, schools etc) by cycling
  • Average travel time in minutes to the nearest x where x is the destination type (workplace, shops, schools etc) by cycling

I suggest getting those 3 variables for trips to town centre first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stretch Stretch targets that go substantially beyond the minimum viable product (mvp)
Projects
None yet
Development

No branches or pull requests

2 participants