Wikidata:Property proposal/BG localisation unit ID

BG localisation unit ID

Originally proposed at Wikidata:Property proposal/Authority control

   Withdrawn

Description	ID in the official Bulgarian database of localisation units (alias: BG street number)
Data type	External identifier
Domain	Places in Bulgaria
Allowed values	\d{5}
Example 1	Hubavka (Q123951168) (Sofia street) --> 68134-18798
Example 2	Tsarigradsko shose (Q7849422) (Sofia street) --> 68134-60112 (Sofia), 14831-60112 (German), 99139-60112 (Gorubliane), 44063-60112 (Lozen)
Example 3	Tsarigradsko Shose (Q58220744) (Plovdiv street) --> 56784-10015 (same name as example 2)
Example 4	Heracles (Q124053954) (Varna street) --> 10135-18798 (same suffix as example 1)
Example 5	Sveshtnik (Q124054005) (Gotse Delchev street) --> 17395-60112 (same suffix as example 3)
See also	Unique Street Reference Number (P8447)

Motivation

The Bulgarian Ministry of Regional Development and Public Works (Q12286838) regularly publishes a complete National database of localisation units of Bulgaria (Q124040693) listing all the localisations units in the country. It consists mostly of street names.

The identifier is a non unique 5 digit code, so it should always be coupled with the BG EKATTE place ID (P3990) of the parent territorial entity in order to ensure uniqueness. In the source data the two are paired. We are contemplating building a 10 digit code by systematically concatenating the two and will appreciate discussing this option here.

Having this identifier in Wikidata will reinforce a data round tripping effort between the Bulgarian OpenStreetMap (Q936) and Wikipedia communities and ensure better correspondence of street level geographical data in Bulgaria (Q219)

See also this thread on the Bulgarian OSM forum --Nikola Tulechki (talk) 09:28, 29 December 2023 (UTC)

Tobias1984 (talk) 18:29, 20 September 2016 (UTC) Nk (talk) 08:44, 27 September 2016 (UTC) Vladimir Alexiev (talk) 14:11, 5 December 2017 (UTC) Datawiki30 (talk) 12:26, 10 November 2018 (UTC) StanProg (talk) 13:29, 22 November 2018 (UTC) Nikola Tulechki (talk) 13:09, 3 January 2023 (UTC) Rumyana.tsoneva (talk) 20:06, 5 March 2023 (UTC) Dimitar999 (talk) 15:50, 8 March 2023 (UTC)

Notified participants of WikiProject Bulgaria

Discussion

•  Support --Boyan Bechev 07:11, 02 January 2024 (UTC)
•  Support --Nikola Tulechki (talk) 13:32, 30 December 2023 (UTC)
•  Support Useful. Concatenating "EKATTE-localizationID" is a good idea, but then a street extending through several settlements will get multiple IDs (see above). I edited the proposal a bit, and added some info to National database of localisation units of Bulgaria (Q124040693). Can you give a few examples from OSM? None of the 3 examples has OSM, and https://www.openstreetmap.org/way/255785589 on OSM doesn't have "localization ID"? -- Vladimir Alexiev (talk) 07:16, 31 December 2023 (UTC)
•  Support Dimitar999 (talk) 11:37, 31 December 2023 (UTC)
•  Support --Pl71 (talk) 20:13, 1 January 2024 (UTC)
•  Support --Dbalinov (talk) 11:37, 4 January 2024 (UTC)
•  Comment - I didnt do my research, but apparently there is already generic property street key (P1945) which can be used for our case. It requires catalog code (P528) as a qualifier and we could even add BG EKATTE place ID (P3990) also as a qualifier and thus have uniqueness with without building complex identifiers. --Nikola Tulechki (talk) 08:37, 2 January 2024 (UTC)
• @Nikola Tulechki: Do you think you should withdraw this proposal then? If not there are some things that need fixing (the regular expression for one). ArthurPSmith (talk) 20:25, 7 January 2024 (UTC)

  Yes, after some deliberation, we decided that we will use street key (P1945) coupled with located in the administrative territorial entity (P131) pointing to the city. Please remove the proposal. Thanks --Nikola Tulechki (talk) 12:53, 9 January 2024 (UTC)