mirror of
https://github.com/nspcc-dev/locode-db.git
synced 2026-03-01 04:28:42 +00:00
Wrong number format in origin files #3
Labels
No labels
I2
I3
I4
S2
S3
S4
U2
U4
blocked
bug
bug
bug
enhancement
enhancement
feature
go
go
good first issue
help wanted
help wanted
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/locode-db#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ZhangTao1596 on GitHub (May 21, 2021).
Originally assigned to: @End-rey on GitHub.
As we know, we expect specific integer and decimal parts in latitude or langitude numbers.
As I port neofs c# and do unit tests, I find there are wrong formats in origin downloaded files.
2020-2 UNLOCODE CodeListPart1.csv, wrong longitude format10247:,"CA","BHH","Blockhouse","Blockhouse","NS","--3-----","RL","1707",,"4427N 064250W",2020-2 UNLOCODE CodeListPart1.csv, wrong latitude format11243:,"CA","JSS","Jerseyville","Jerseyville","ON","--3-----","RL","1707",,"43120N 08006W",2020-2 UNLOCODE CodeListPart3.csv, no lontitude symbol E or W7030:,"SA","SAL","Salw�","Salwa","04","--3-----","RL","1707",,"2444N 05045",2020-2 SubdivisionCodes.csv, Line:218,219, unexpected wrapMaybe we should correct these files and store them in this repo.
@alexvanin commented on GitHub (May 21, 2021):
Unfortunately, these files will always have some inconsistency inside. Maintaining several large database files with fixes is hard and there may be some license issues. Instead we can maintain a short list of "overrided" UN/LOCODE records. These records can be applied to the database after parsing.
If this option is okay, then we will add support of overrided values into locode generator in CLI as in example above.
For now I see that these records with invalid coordinates are simply ignored in v0.1.0 database
I think it is okay for now. But before N3 release (maybe for RC3) we will recompile it with newer database files and list of overrided values and publish it as v0.2.0
Thougths? @cthulhu-rider @realloc
@alexvanin commented on GitHub (Jun 9, 2021):
NeoFS CLI LOCODE generator has
--inflag to provide database files. We can provide any number of such files. In case of record collisions, data from latter file is being used. Therefore we can use--inflag with override.csv file as the last argument to achieve our goal.I propose to create separate PR that adds
override.csvfile in this repository. There we can discuss content ofoverride.csvfile.