Bug with gen_table

[Ronja-max]

When downloading the file using the gen_table command, columns are sometimes incorrectly mapped. According to Destatis, they have fixed a major bug in the flat file creation process, which could potentially lead to column mapping errors.

[yannikbuhl]

Hi Ronja-max, could you please provide the code you used when this occurred?

Normally, we do not parse the column names in any way but just extract what is delivered by the API.

[Ronja-max]

Hi, sorry for the late reply. Below is the code I used to retrieve the data table. Oddly enough, this only happens very rarely with individual tables: daten <- gen_table("12531-02-02-4", database = "regio", startyear = x, endyear = y) I just ran the code again, and this time nothing seems to have shifted. Do you have any idea why this could happen so sporadically and seemingly at random? Best regards, Ronja Berrisch Bundesinstitut für Bau-, Stadt- und Raumforschung (BBSR) Abteilung Raum- und Stadtentwicklung RS6 - Stadt-, Umwelt- und Raumbeobachtung Deichmanns Aue 31-37 53179 Bonn Federal Institute for Research on Building, Urban Affairs and Spatial Development RS6 - Urban, Environmental and Spatial Monitoring Tel.: 049 (0) 228-99401 2264 ***@***.******@***.***> www.bbsr.bund.de<http://www.bbsr.bund.de/> www.inkar.de<http://www.inkar.de/> www.raumbeobachtung.de<http://www.raumbeobachtung.de/> Von: Yannik Buhl ***@***.***> Gesendet: Freitag, 4. September 2026 18:09 An: CorrelAid/restatis ***@***.***> Cc: Berrisch, Ronja ***@***.***>; Author ***@***.***> Betreff: Re: [CorrelAid/restatis] Bug with gen_table (Issue #83) [Das Bild wurde vom Absender entfernt.]yannikbuhl left a comment (CorrelAid/restatis#83)<#83 (comment)> Hi Ronja-max, could you please provide the code you used when this occurred? Normally, we do not parse the column names in any way but just extract what is delivered by the API. - Reply to this email directly, view it on GitHub<#83?email_source=notifications&email_token=CNHSVFA7YZIIRVTLYGGGK5D5NLSKTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNJUGMZDKMRWHAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5543252680>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CNHSVFBZDOSN7VF74R2V32D5NLSKTAVCNFSNUABFKJSXA33TNF2G64TZHM2DOMZZGU3TSMBZHNEXG43VMU5TKMZSGE3DGNBTG432C5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CNHSVFAAXWXUYMKOFXOSPZ35NLSKTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNJUGMZDKMRWHAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/CNHSVFA3L2X4UYYXFHIJNXL5NLSKTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNJUGMZDKMRWHAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[yannikbuhl]

Thank you very much. We have received a similar issue via mail regarding regio database. I cannot yet say why that is the case and where the error lies. I will have to check the raw outputs of the requests, although the mail we received claims that using other clients cannot reproduce the error. We will come back to this issue soon!