-
Notifications
You must be signed in to change notification settings - Fork 93
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
South Korea single_member_constituencies update #369
South Korea single_member_constituencies update #369
Conversation
South Korea single_member_constituencies update
The valid from for new constituencies should be set to the date of the election for which they will be used: April 10th |
I would have expected 254 valid constituency after 2024-05-30. Can you please explain why the number is 260 ? Also, can you order the list of ids in alphabetical order ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added few comments to resolve.
- I was thinking that some of these new district are renamed not newly created. Can you double check ?
- valid from for new constituencies set to April 10th - order changed, sort by ID
Hello, |
I would expect 254 single seat constituencies. In the change, only 253 will be valid starting 2024-04-10. Can you double check the numbers and provide the sources if needed ? |
added missing item
@azuser Sorry for the inconvenience, missing item recovered, now should be 254 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes look good to me
Noting that these were also obsoleted (not listed above) Buk District and Gangseo District First (Busan) About dates: I think we have always had them either one day apart or the same day (probably more correct and easier on users to have one day apart). I don't think it's correct for there to be overlap, as that confuses two different perspectives. If the question is "what is the validity, with respect to the division to be represented by the winner of an election?" then the date is 2024-04-10. If the question is "what is the validity, with respect to the division represented by the active officeholder?" then the date is 2024-05-29. To date, we have only concerned ourselves with the election date. That said, in pretty much every election, the officeholder remains in office for some time after the election date (notably, because many elections are not 100% decided on the election date). If we want to answer both questions, we should have different fields. However, I don't know if any users of OCDIDs really care to know the date when responsibilities are transferred. This is also the sort of date that sometimes moves if the election is hard to decide – and whereas I think we try to have the correct election dates (which also sometimes move), I don't think anyone is really monitoring whether this other date moves. I would assume any current user of OCDIDs is just using the logic of: is today between validFrom and validThrough? Then the division is relevant. But this simple logic will fail with the dates in this PR. Users would now have to ask, is today after validFrom, and – if the division sets a validThrough in the future – is today also before the earliest future validFrom among other divisions, minus one day? (This logic is too bizarre.) |
Changed from FOURTH to Fourth
Fixed. (changed to Fourth)
These are sourced from the official list. The same one in Korean we have supplied and translated.
We can adjust the zone dates for To and From to equal the election date if that's easiest. |
added missing change to country-kr.csv
You didn't answer. Please provide a URL.
I'm confused. Let's take a specific example: ocd-division/country:kr/ed:ansan_city_district_1,Ansan City First,,2024-04-10 This is one of the new districts. There is no reason for the ID to contain "district_". The name you provide above and in the PR ("Ansan City First") doesn't contain "District". The name is what comes from the official sources. The only change would be to remove "district_" in this case (and the other similar cases). This simple transformation does not take 2 weeks.
This change only requires "Nam District First Busan" -> "Nam District First (Busan)". This is one of the new districts. In every other case, a name that appears after First, Second, etc. is parenthesized. There is no reason to have this one exception.
What we have done in other countries is set validThrough to the day before the election, and validFrom to the same day as the election.
As I already explained, this is true in pretty much every country. The problem is that you are trying to use the same fields to answer two different questions.
I don't know what CDF guidelines are - you should provide links when referring to sources. As I explained, the fields are used to answer a specific question. Let's say a voter uses a geolocation service (that is part of a voter information service) to determine which district they fall within that is valid as of election day (2024-04-10). In the current PR, where districts have changed, like Ansan, voters will get two answers: the old district (validThrough 2024-05-29) and the new district (2024-04-10). This is clearly undesirable. The voter information service should be responding with a single district: the district to which the new representatives are being elected. If you ask a different question, like "which valid district am I currently within, and who is the current officeholder?" – then, of course, you will need different dates. But if that's what you want, then add new fields for those dates. Don't use fields that are designed to answer a different question – that will not work. |
review changes: - validThrough date changed from 29/05/2024 to 9/4/2024 - removed _district for some districts (if no district in the name) - changed Busan to (Busan) - added 2 new districts: Yeongju City, Yeongyang County and Bonghwa County Uiseong County, Cheongsong County, Yeongdeok County, Uljin County
Hello,
|
Thank you. Last thing is: Can you provide a URL or document for the source of these names? There are 21 districts expiring on 2024-04-09 and 22 districts starting on 2024-04-10. It seems a bit strange that there is such a small change in the number of districts, so I'd like to compare against a source. |
Hello, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and the new/surviving districts add up to 254 like in the source.
South Korea single_member_constituencies update
Hello,
South Korea confirmed its new electoral districts for the April 10, 2024 elections
We have added the new districts with new OCD-IDs
Until the winning candidates take office on 5/30/2024, we will need to have both old and new districts in place.
This is because existing officeholders will still be assigned to the "old" OCD-IDs until new officeholders take office in the new districts.
List of new zones (validFrom set to 05/30/2024):
Nam District First Busan
Buk District First
Buk District Second
Gangseo District
Dong District and Gunwi County First
Dong District and Gunwi County Second
Seo District Third
Pyeongtaek City Third
Dongducheon City, Yangju City and Yeoncheon County First
Dongducheon City, Yangju City and Yeoncheon County Second
Ansan City First
Ansan City Second
Ansan City Third
Hanam City First
Hanam City Second
Hwaseong City FOURTH
Gunsan City, Gimje City and Buan County First
Gunsan City, Gimje City and Buan County Second
Namwon City, Jangsu County, Imsil County and Sunchang County
Wanju County, Jinan County and Muju County
List of zones which will be obsolete (validThrough set to 05/29/2024):
Ansan City Danwon District First
Ansan City Danwon District Second
Ansan City Sangnok District First
Ansan City Sangnok District Second
Bucheon City Fourth
Dongducheon City and Yeoncheon County
Gimje City and Buan County
Gunsan City
Hanam City
Namwon City, Imsil County and Sunchang County
Nowon III
Wanju County, Jinan County, Muju County and Jangsu County
Yangju City
country-kr.csv file was updated by compile script.