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

v2.0.0 #492

Merged
merged 136 commits into from
Mar 29, 2018
Merged

v2.0.0 #492

merged 136 commits into from
Mar 29, 2018

Conversation

schloerke
Copy link
Contributor

@schloerke schloerke commented Feb 12, 2018

Resolves #476 (which merges #453, #458, #462, #405, #396, #393).

Remaining PR's to possibly include:

    • CLA Signed
    • Needs more work. Will wait for next release

Remaining Issues to address:

Tasks left before merging

  • update pkg version
    • 1.2.0
    • 2.0.0
      • with the upgrade to 1.3.1, there will most likely be breaks in the js code that people submit. We should make it a 'major' version update.
  • Should we update to leaflet.js 1.3.1 ?
    • no. release to public. then upgrade to 1.3.1 (or latest) in next release
    • Yes! leaflet.extras and leaflet.esri need updating. Since we are doing work for both packages, then we should update leaflet version as well.
  • Packages ready for rstudio/leaflet 2.0.0
    • leaflet.extras
      • needs leaflet 1.3.1 updates
    • leaflet.esri
      • needs leaflet 1.3.1 updates
    • mapview
    • mapedit
    • sf
  • Internal lints
    • with the update of leaflet version, maybe this could be included in the release
  • issue addLegend should support data argument #491 - addLegend should support data arg
  • leaflet.extras has no zIndex = NULL
  • update NEWS with information
    • ... ongoing process
  • raster auto method, and color
  • add auto method for raster data
  • add raster examples
    • numeric
    • character
    • factor
    • weird
  • Fix known broken examples (added below)
  • run revdepcheck::revdep_check() on final version

Known broken examples:

topoData <- readLines("https://d3js.org/us-10m.v1.json") %>% paste(collapse = "\n")
leaflet() %>% setView(lng = -98.583, lat = 39.833, zoom = 3) %>%
  addTiles() %>%
  addTopoJSON(topoData, weight = 1, color = "#444444", fill = FALSE)
# map shows up with no topo viz

timelyportfolio and others added 30 commits December 30, 2016 12:01
@schloerke schloerke changed the title v1.2.0 v2.0.0 Mar 26, 2018
@schloerke
Copy link
Contributor Author

Known broken example:

topoData <- readLines("https://d3js.org/us-10m.v1.json") %>% paste(collapse = "\n")

leaflet() %>% 
  setView(lng = -98.583, lat = 39.833, zoom = 3) %>%
  addTiles() %>%
  addTopoJSON(topoData, weight = 1, color = "#444444", fill = FALSE)

is fixed by changing the data source:

topoData <- readLines("http://bl.ocks.org/mbostock/raw/4090846/us.json") %>% paste(collapse = "\n")

leaflet() %>% 
  setView(lng = -98.583, lat = 39.833, zoom = 3) %>%
  addTiles() %>%
  addTopoJSON(topoData, weight = 1, color = "#444444", fill = FALSE)

I believe Bostock is projecting the data. This raw data from an old block is not geo projected. The raw data is leaflet ready, where as the original data is ready for D3.

…io#388)

GitHub patch would not copy, so i added verbatim and documented package
* copy over gh-pages into docs folder

* use usa_sf instead of usa_composite

> rmapshaper::ms_simplify(usa_composite())
Error in ogrInfo(dsn = dsn, layer = layer, encoding = encoding, use_iconv = use_iconv,  :
  Cannot open data source

No errors when using `usa_sf()`

* compile docs

* Add note to where data came from (rstudio#498)

Will be true once branch is merged into master

* Add docs for input$MAPID_center from @michael-chong for (rstudio#450)

had to copy verbatim as the website moved from gh-pages to docs folder
@schloerke schloerke merged commit 339341d into rstudio:master Mar 29, 2018
@timelyportfolio
Copy link
Contributor

timelyportfolio commented Mar 29, 2018

@schloerke thanks for incredibly hard work on this. I will start testing with mapedit.

@jrisi256
Copy link

jrisi256 commented Apr 2, 2018

@jcheng5 Hi! I submitted issue #496 (related to #152, #163, #170, and #303), and I didn't quite understand your response to @timelyportfolio by saying "The restyle operation seems like something you should be able to do to anything, not just GeoJSON?" Could you explain further if there are any plans to implement setStyle or restyle? Or if not, could you point out a way/gesture towards how to implement it using some Javascript? Thanks for your time and for helping make such a great package.

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 this pull request may close these issues.

9 participants