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.

Sign up for GitHub

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

Jump to bottom

table: issue with exporting excel files with duplicate column names #447

Closed
lanselin opened this issue Jun 21, 2016 · 1 comment
Closed

table: issue with exporting excel files with duplicate column names #447

lanselin opened this issue Jun 21, 2016 · 1 comment
Assignees
@lixun910
Labels
bug fixed: verify! Milestone-Release1.8
Milestone
1.8

Comments

@lanselin
Copy link
Collaborator

there seems to be a problem in the edge case where an excel file contains duplicate column names. the file loads properly into GeoDa and the duplicate headers are only shown once. however, when trying to "save as" some other format (e.g., dbf or csv), there is an error pertaining to empty field names. when the duplicate names are removed from the original excel file, everything works fine. so, somehow the handling of the duplicate header is not robust.

screen shot 2016-06-21 at 1 56 05 pm
@lixun910 lixun910 added this to the 1.8 milestone Jun 21, 2016
@lixun910 lixun910 self-assigned this Jun 21, 2016
lixun910 referenced this issue in lixun910/geoda Jun 23, 2016
@lixun910
#447 fix exporting with dup field names
1d44e0f 
Update the internal logic&datastructure of field names to allow detect
dup field names when save/saveas
This was referenced Jul 8, 2016
Merged
Merged
@jkoschinsky
Copy link
Collaborator

Verified in GeoDa 1.8.9.1 (OSX Yosemite, 10.10.5).
works now: when saving as xls to dbf with duplicate field name, unique field name is added (e.g. _1), which then saves correctly:

screen shot 2016-07-08 at 10 33 28 pm

This was referenced Jul 14, 2016
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lixun910 lixun910

Labels
bug fixed: verify! Milestone-Release1.8
Projects
None yet
Milestone
1.8
Development

No branches or pull requests
3 participants
@lixun910 @lanselin @jkoschinsky