Owain
Joined 9 April 2013
 Archives | |
|---|---|
|
|
County Bot
editHey. I just wanted to say thank you for running and maintaining the County Bot. It is really useful to have such a consistent property across geographical items, which makes it really easy to write queries for places in Wales. Jason.nlw (talk) 14:28, 3 August 2021 (UTC)
- Hi, is there any possibility that the scope of the bot could be expanded to populate country (P17) and/or located in the administrative territorial entity (P131) too? I understand the complexity of programming these based on the coordinates, but it would be really useful! — Martin (MSGJ · talk) 12:28, 10 November 2021 (UTC)
- I imagine so. The way it is currently written relies on country (P17) and located in the administrative territorial entity (P131) being set correctly in the first place so it can do the point-in-polygon work using the co-ordinates. The page generator creates batches of pages based on regions ('Q22', 'Q25', 'Q26', 'Q23306', 'Q47967', 'Q47983', 'Q47994', 'Q48006', 'Q48015', 'Q48026', 'Q48038', 'Q48063') otherwise there are too many pages and the generator times out. Ideally there would be one generator for any UK place with co-ordinates set and then it could add located in the administrative territorial entity (P131) at the same time. If the page generator capacity is ever improved then it should be possible! Owain (talk) 12:35, 10 November 2021 (UTC)
- Hi Owain!
- The CountyBot is also writing the historic county into items for places in the ROI, which seems to cause some constraint conflict. Might be an indicator that this kind of datapoint isn't very helpful for ROI locations. Braveheart (talk) 13:05, 24 January 2022 (UTC)
- It shouldn't do unless they have incorrect located in the administrative territorial entity (P131) attributes, because as previously explained, the page generator works based on the UK regions listed above. There shouldn't be any constraint conflict because country (P17) can be any one of: United Kingdom, Ireland, United Kingdom of Great Britain and Ireland, Great Britain, Kingdom of England or Kingdom of Scotland. Owain (talk) 14:11, 24 January 2022 (UTC)
- I imagine so. The way it is currently written relies on country (P17) and located in the administrative territorial entity (P131) being set correctly in the first place so it can do the point-in-polygon work using the co-ordinates. The page generator creates batches of pages based on regions ('Q22', 'Q25', 'Q26', 'Q23306', 'Q47967', 'Q47983', 'Q47994', 'Q48006', 'Q48015', 'Q48026', 'Q48038', 'Q48063') otherwise there are too many pages and the generator times out. Ideally there would be one generator for any UK place with co-ordinates set and then it could add located in the administrative territorial entity (P131) at the same time. If the page generator capacity is ever improved then it should be possible! Owain (talk) 12:35, 10 November 2021 (UTC)
Constraint
editHi Owain, I've started to see some constraint violations on your bot's edits like "Entities using the historic county property should be instances of geographic location or battle (or of a subclass of them), but xxx currently isn't." Please see River God Tyne (Q117812066) for an example — Martin (MSGJ · talk) 12:38, 25 April 2023 (UTC)
- Yes, I've spotted these too. Apparently this constraint doesn't apply to located in the administrative territorial entity (P131), which means that the constraint is probably unnecessary. Owain (talk) 12:43, 25 April 2023 (UTC)