Talk:Q82794

From Wikidata
Jump to navigation Jump to search

Autodescription — geographic region (Q82794)

description: 2D or 3D defined space on something, mainly in terrestrial and astrophysics sciences
Useful links:
Classification of the class geographic region (Q82794)  View with Reasonator View with SQID
For help about classification, see Wikidata:Classification.
Parent classes (classes of items which contain this one item)
Subclasses (classes which contain special kinds of items of this class)
geographic region⟩ on wikidata tree visualisation (external tool)(depth=1)
Generic queries for classes
See also


not a point[edit]

"2D 3D"

We can allow to specify coordinates for 3D objects using "coordinate" properties. d1g (talk) 15:27, 29 September 2017 (UTC)[reply]

subclass[edit]

Removed subclass of (P279) of geographic location (Q2221906), because it's already subclass of (P279) of geographical feature (Q618123) that has characteristic (P1552) of geographic location (Q2221906) --Kanzat (talk) 05:48, 25 October 2021 (UTC)[reply]

Not a geometric / mathematical object[edit]

@Infovarius:

A park is not a mathematical multiset, so I removed the subclass statements. Not sure how to put the statement back, I think we should create a property like « modelled by » to link real world objects to mathematical object that represents them like « described by » or « modelled by » if we don’t have such already (can’t think of any, studied by Search is for something else but close). I’ll put a message on the ontology project to gather input. author  TomT0m / talk page 15:40, 3 June 2022 (UTC)[reply]

for a place to discuss this overall hierarchy and hopefully clarify it. JesseW (talk) 16:43, 31 July 2022 (UTC)[reply]

Geographic region and geographic location[edit]

@Swpb: On 18 November 2023, you deprecated the claim geographic region (Q82794)subclass of (P279)geographic location (Q2221906) At least by the current English descriptions, that claim seems appropriate:

I was brought here because of a constraint violation that Kentucky (Q1603) isn't an instance of geographic location (Q2221906). What should be done? Also notifying @JesseW: for your efforts in this area. Daask (talk) 13:47, 26 March 2024 (UTC)[reply]

The issue was a disjointness violation, where geographic region (Q82794) was a subclass of physical entity but geographic location (Q2221906) was a subclass of non-physical entity. I've resolved the violation in a more straightforward way. Swpb (talk) 14:28, 26 March 2024 (UTC)[reply]