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

test merged cells #2

Open
phonixor opened this issue Jun 24, 2014 · 3 comments
Open

test merged cells #2

phonixor opened this issue Jun 24, 2014 · 3 comments
Labels

Comments

@phonixor
Copy link
Contributor

  • what happens currently?
  • what should happen?
@chainsawriot
Copy link
Collaborator

Tested. A merged cell can jam the parsing and produce incorrect data.

http://postimg.org/image/5tsbqyb8t/

Need to look into that or notes it in the documentation.

chainsawriot added a commit that referenced this issue Feb 7, 2016
@py-b
Copy link

py-b commented Feb 11, 2019

Hello,
Would be nice if that feature is implemented.
So, what should happen? Top-left cell takes the value of the merged cell, others remain empty?

@DataStrategist
Copy link

Something especially evil happens with merged cells + mult-row headers + skip rows, it seems to shift column headings over. Take a look at:

file_to_get <- "https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/1039305/Main_Tables_Q2_2021_22.ods"
download.file(file_to_get, destfile = "oh_no.ODS")
names(readODS::read_ods("oh_no.ODS", sheet = "S_1", skip = 3))

It seems like the third column is "Immigration and Asylum", which isn't the case. I feel there should at least be a visible warning specifying that there MIGHT be a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants