Morning, Here is a list of some of the nodes that would require a manual correction: 2796279335: '+31 499 475415;toets 1 voor spoed' 2818035695: '+31 6 165 567 969’ 2818064864: '+31 65397447’ 2824141858: '+31 13 522 09 72 "emergency”' 2824141869: '+31 13 522 09 72 "emergency”' 2824142102: '+31 13 528 6060 "Algemene spoedljn OisterwijkKliniek"’ 2853116449: '+31 0162 – 242 006 of +31 06 – 421 27 994.’ 2853564877: '+31 01620 456 790’ 6176636305 2862917377 2724284582 34206650: '09002357275 13ct/m’
One question regarding to have phone number description in the phone tag though, are we allowed to have description in the phone tag other than the actual phone number? I couldn’t find any conventions about it. Vast majority of bad phone tag values are either not following the proper syntax of separation of multiple values in one tag <https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator>, invalid phone tag value such as invalid number or having the contact:website value as the phone number. Example of nodes that would need format correction (there are thousands of nodes that would require format correction): 1653511382: '+31 (222) 319 309' ==> '+31 222 319 309' 821734360: '+31 297 324548;+31 172 508360' ==> '+31 297 324 548; +31 172 508 360’ 520290181: '0204276833' ==> '+31 20 427 6833’ I am still working on the script, it’s expected that I will be done with it later today or tomorrow. I’ll let you know when I’ve created a repo for it. Regards, Marc > On Jun 7, 2022, at 09:15, Maarten Deen <md...@xs4all.nl> wrote: > > Do you have a link to your script and maybe some examples of phone numbers > that need correcting? > > Regards, > Maarten >> Op 06-06-2022 21:11 schreef Marc Zhou Toneu via Talk-nl >> <talk-nl@openstreetmap.org>: >> >> >> To whom it may concern, >> >> I’ve recently written a pythons script that would automatically format the >> phone numbers in NL should it be wrongly formatted, and I would like to hear >> your opinion about it. >> >> So far I am proposing to do the following: >> Formatting phone numbers according to the ITU-T E.123 format pattern >> Phone numbers that were not parsable would be left untouched >> Phone numbers that do not need formatting would be left untouched >> >> There were some edge cases that I’ve seen so far such as: >> Having URL links or opening times as phone numbers >> Having ‘/‘ for indicating multi value tag >> Phone numbers but with description as part of it, such as ‘10ct/m’ or >> ‘emergency’ >> >> Phone numbers that would require manual inspection/correction such as the >> following will be send to map roulette: >> Phone numbers belonging to other countries >> Phone number values that is just completely wrong >> >> Please let me know if you have any concern or objections about it, and I’ll >> gladly take your feedback into account. >> >> Kind regards, >> Marc >> _______________________________________________ >> Talk-nl mailing list >> Talk-nl@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk-nl > _______________________________________________ > Talk-nl mailing list > Talk-nl@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-nl
_______________________________________________ Talk-nl mailing list Talk-nl@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-nl
