-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Resolve address number output issue and refactor road_formats for clarity #2138
base: master
Are you sure you want to change the base?
Conversation
As this is a bug of the previous variant, shouldn't there be a test which checks for the previously broken behavior as well? |
Hello,
Please review these changes. Since I'm using ChatGPT for communication, there may be some nuances lost in translation. Thank you. |
If addresses are supposed to never contain |
Good morning from Korea. Thank you for clarifying the task.
Please let me know if anything else is needed! |
What does this change
This change addresses the issue in the previous implementation (#2133), where
#
was mistakenly printed instead of the actual address numbers. Additionally, theroad_formats
structure has been simplified by incorporating{{building_number}}
directly for more concise formatting.What was wrong
The original code had a formatting error where
#
was printed instead of the intended numeric address numbers. This caused unexpected outputs in the feature responsible for generating ROK (🇰🇷) road addresses (도로명 주소), leading to inaccuracies.How this fixes it
The building_number method now correctly handles the generation of building numbers. It produces a standard building number or, with a certain probability, generates variations such as underground entrances using
building_number_underground()
orincludes sub-building numbers via building_number_segregated()
. This probability was determined arbitrarily, as there are no official government statistics available for this data.Checklist
make lint