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

Simplify region shapes in projects #727

Closed
manumoreira opened this issue Apr 18, 2024 · 2 comments · Fixed by #732
Closed

Simplify region shapes in projects #727

manumoreira opened this issue Apr 18, 2024 · 2 comments · Fixed by #732

Comments

@manumoreira
Copy link

manumoreira commented Apr 18, 2024

After using Planwise in several projects it was pretty clear that the quality of the region shapes (polygons) are not aligned with the quality (level of detail) of the population and accessibility (friction) sources. In other words, we have super detailed region shapes combined with more coarse population and friction rasters.

We might consider using the mapshaper -simplify command to get a balanced quality of the 3 sources.
Here's an example of size for simplification

(defn- shrink-geojson

The main issue with having a highly detailed region shape is that it makes operating with it (eg. for filtering of providers, clipping the demand rasters) very slow while not providing any actual value.

From the slack conversation

The most complicated part would be adding a simplification step when importing the regions and choose some criteria for the precision cut.
We have a size criteria implemented here which is used for the previews. I would prefer a resolution criteria for this use case, and I'm sure it should be easily doable. Just need to stitch it together.
It may be a good time to migrate the remaining Bash scripts to Babashka. Or at least those involved here: load-regions and load-friction-raster.

@manumoreira
Copy link
Author

@ggiraldez please feel free to edit

@ggiraldez
Copy link
Member

We will want to "pair" this with adding a bit of extra border to the friction rasters (using -cblend 1 when cutting the regions in the load-friction-raster script) which should eliminate issues when there are providers near the limits of the regions and they are inside the region shape but they have no friction data.

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 a pull request may close this issue.

2 participants