Talk:Q27096213
Autodescription — geographic entity (Q27096213)
- Useful links:
- View it! – Images depicting the item on Commons
- Report on constraint conformation of “geographic entity” claims and statements. Constraints report for items data
- Parent classes (classes of items which contain this one item)
- Subclasses (classes which contain special kinds of items of this class)
- ⟨
geographic entity⟩ on wikidata tree visualisation (external tool)(depth=1) - Generic queries for classes
Union and disjoint queries
- Instances of geographic entity (Q27096213)
that are instances of none of the classes natural geographic entity (Q27096220) and artificial geographic entity (Q27096235) [1]
- See also
- This documentation is generated using
{{Item documentation}}.
Useless because of geographic location (Q2221906)
[edit]Same problem as with geographic region (Q82794) and geographical feature (Q618123)
Real discussion here: Talk:Q618123#subclass d1g (talk) 16:35, 29 September 2017 (UTC)
This vs geographic location (Q2221906)
[edit]@Infovarius: over the past week I've been removing links to this item because I think it should be merged with geographic location (Q2221906); as far as I can tell they represent the same thing: a thing in a place. But I saw you just changed it to be subclass of (P279)entity (Q35120). I am curious how you intend this thing to be used then? ―Jochem van Hees (talk) 10:14, 28 March 2022 (UTC)
- @Jochem van Hees: I didn't notice you in the discussion and now you are changing things... I believe that things which are not located in one place (regions, lines, and movable objects like cyclons) are not locations, they are just, well, geographical things (in our term, entities). Location, in brief, is a set of coordinates, or by metonymy, thing which is uniquely defined by this set. So these are different classes. --Infovarius (talk) 14:07, 29 March 2022 (UTC)
- Oh. That's not how this entity was used though; cyclone (Q79602) was never a subclass of geographic entity. It was used in properties like place of birth (P19) as a value-type constraint, but that's to indicate one location; it doesn't make sense to set it to a movable object. ―Jochem van Hees (talk) 15:16, 29 March 2022 (UTC)
- May be. But why not to do in such logical manner? I would make low pressure area (Q209190) subclass of merged item instead of weather (Q11663). --Infovarius (talk) 10:19, 31 March 2022 (UTC)
- Oh. That's not how this entity was used though; cyclone (Q79602) was never a subclass of geographic entity. It was used in properties like place of birth (P19) as a value-type constraint, but that's to indicate one location; it doesn't make sense to set it to a movable object. ―Jochem van Hees (talk) 15:16, 29 March 2022 (UTC)
@Infovarius: I see you're now repurposing this item, but I think it's better to just create a new item instead for the new thing. A lot of things now link here when it still had its original meaning of being a geographic location (Q2221906). (I know I'm replying quite late, I've been away this weekend.) ―Jochem van Hees (talk) 15:48, 5 April 2022 (UTC)
- I believe that I fixed all links from items. --Infovarius (talk) 12:54, 6 April 2022 (UTC)
for a place to discuss this overall hierarchy and hopefully clarify it. JesseW (talk) 16:44, 31 July 2022 (UTC)