Open Robinlovelace opened 3 years ago
Ping @mvl22 any ideas on this welcome after conversation today.
Yes, I agree that a general-purpose 'mechanics' package like osmextract
is probably best not concerned with domain-specific functionality, which is best in a separate package, since that is a higher-level concern.
PS I would flag my usual caution that a function like oe_get_cycleways
should be extremely clear as to what it does or doesn't cover. People constantly ask us "how do we get the cycle network from OSM", to which the answer is "please define cycle network". Just getting highway=cycleway
is inadequate.
PS I would flag my usual caution that a function like
oe_get_cycleways
should be extremely clear as to what it does or doesn't cover. People constantly ask us "how do we get the cycle network from OSM", to which the answer is "please define cycle network".
Agreed.
The documentation of extending this package, and possibly an osmcycleinfra
package could help people answer that question : )
See here for definition of cycleway @mvl22 https://ohsome.org/apps/osm-history-explorer/#/cycleways_w/2020-06-01T00:00:00Z/2/45.4908851942306/9.264549335457264
Well, that is one view, yes.
Hi @Robinlovelace and @mvl22 and thank you for starting this discussion. I'd like to work on this problem in the next days and I was wondering if there are official guidelines on how to subset OSM data for walking/cycling/driving mode of transport. Suggestions are welcome!
Hi @agila5 see below for a good 'starter for 10' on tags for different modes (walk/bike/drive). Source: https://github.com/gboeing/osmnx/blob/c17ad723223fead5b1cd6d15e60ba91ba5a19154/osmnx/downloader.py
As far as I can tell this is hardcoded specifically for the OSMnx project and it may be good to be more flexible.
I know @mpadge has implemented this functionality for osmdata
. Any tips/tricks/ideas Mark?
Cheers!
The package is very useful in some areas so I think we should encourage domain-specific functions to be written, e.g.
oe_get_cycleways()
to get cycleways with the appropriate query. However, such functions are best suited to packages that build onosmextract
which I think should be kept to generic functionality to avoid mission creep.Proposed solution: vignette (or content in a paper/article/blog) documenting how to write functions that extend
osmextract
, e.g. based on a hypothetical package calledosmcycleinfra
.