osmdata icon indicating copy to clipboard operation
osmdata copied to clipboard

R package for downloading OpenStreetMap data

Results 29 osmdata issues
Sort by recently updated
recently updated
newest added

@Mashin6 raised valid concerns in #252, supported by @stragu, that the current design in counter-intuitive: **OR** ``` r add_osm_features (features = c (...)) ``` **AND** ``` r add_osm_feature() |> add_osm_feature()...

enhancement
help wanted

As suggested in #178 trimming by area polygon using Overpass is fast and useful way of data filtering. _Note: OP now treats all [closed ways as areas](http://dev.overpass-api.de/blog/way_based_areas.html) thus allowing filtering...

Because I finally had call to trim a huge data set (New York City within the official boundary polygon => around 700,000 vertices submitted to `sp::point.in.polygon` or `sf::st_within`). The latter...

future stuff

First of all, awesome job with parsing OSM data and making use of overpass user friendly! Although most of the use cases are just a simple filter queries, I think...

enhancement

PR for issue #247 (this is my first PR ever, tell me if there's anything missing !)

I had performance issues with osmdata_sc used directly on OSM data (by providing a local .osm file), with medium to large files (30 Mo to 300 Mo, extracted with osmextract...

Coz things have moved on a lot since [these comments](https://github.com/hrbrmstr/overpass/issues/13#event-1623082590). It should be pretty straightforward to `Rcpp::RcppParallel`-ize the main loops over nodes, ways, relations in `src/osmdata_sf/sp`.

future stuff

Instead of repeatedly bombing the `overpass` API, it'd be pretty easy to implement a local caching system that would record the call and store the pre-processed data returned from the...

enhancement

Thanks to @Robinlovelace, and extending from [this discussion](https://github.com/cyipt/cyipt/issues/22), the rules provided [here](https://github.com/keepright/keepright/tree/master/checks) could easily be translated into `osmdata` terms and used to analyse local data in same way. An `osmdata_check()`...

future stuff

I think there is are advantages of having this in **osmdata** instead of other pkgs such as dodgr. I've thought about this before, but am finally opening opening this issue...