You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building blocks, users should be able to add an arbitrary set of boundaries to include in a block definition (i.e., user supplied data on admin divisions or urban boundaries, or geohashes).
The use case for this is that some users may want to cut and delineate block geometries for their specific application based on different criteria (maybe they need to link to special administrative boundaries or want to focus their analysis on urban areas using some morphological definition). As as result, it may make sense to expose an option that allows users choose what kinds of additional divisions they'd like to incorporate in the block geometry. These arbitrary definitions can also help with chunking the data.
This goes beyond a blob of linestrings from OSM that a user would define however they want (but the default option would be natural features + highways minus footpaths + railroads).
So we may want a class of methods for adding custom boundaries to block definition:
known admin boundaries (user supplied GeoDataFrame) i.e., OSM with "admin_level=4"
The text was updated successfully, but these errors were encountered:
nmarchio
changed the title
Option to include periurban boundary in blocks definition
Option to include urban and periurban boundary in blocks definition
Mar 9, 2023
When building blocks, users should be able to add an arbitrary set of boundaries to include in a block definition (i.e., user supplied data on admin divisions or urban boundaries, or geohashes).
The use case for this is that some users may want to cut and delineate block geometries for their specific application based on different criteria (maybe they need to link to special administrative boundaries or want to focus their analysis on urban areas using some morphological definition). As as result, it may make sense to expose an option that allows users choose what kinds of additional divisions they'd like to incorporate in the block geometry. These arbitrary definitions can also help with chunking the data.
This goes beyond a blob of linestrings from OSM that a user would define however they want (but the default option would be natural features + highways minus footpaths + railroads).
So we may want a class of methods for adding custom boundaries to block definition:
"admin_level=4"
representative_pt = gadm_blocks.geometry.representative_point().to_list()
blocks['block_geohash'] = list(map(lambda x: pygeohash.encode(x.x,x.y, precision=10), representative_pt))
Block script: https://github.com/mansueto-institute/kblock/blob/main/kblock/batch_1b_generate_blocks.py
Unsupervised methodological ideas for urban network:
Use network analysis:
https://docs.momepy.org/en/stable/user_guide/graph/coins.html#Using-OpenStreetMap-data
https://docs.momepy.org/en/stable/user_guide/graph/centrality.html#Global-closeness
Data to define buffers around urban boundaries (see images):
The text was updated successfully, but these errors were encountered: