Wikidata:Property proposal/axis

From Wikidata
Jump to navigation Jump to search

x-offset[edit]

Return to Wikidata:Property proposal/Generic

   Under discussion
Descriptionoffset on the x-axis or primary axis, abscissa
Representsx-axis (Q25599399)
Data typeQuantity
Allowed unitsif applicable
Example 1SWSW block (Q65965927) → 0 block (Q66319570)
Example 2NWNW block (Q65965923) → 0 block (Q66319570)
Example 3SESE block (Q65965939) → 3 block (Q66319570)

y-offset[edit]

Return to Wikidata:Property proposal/Generic

   Under discussion
Descriptionoffset on the y-axis or secondary axis, ordinate
Representsy-axis (Q26262125)
Data typeQuantity
Allowed unitsif applicable
Example 1SWSW block (Q65965927) → 0 block (Q66319570)
Example 2NWNW block (Q65965923) → 3 block (Q66319570)
Example 3SESE block (Q65965939) → 0 block (Q66319570)

Motivation[edit]

Maybe we have this somehow, but I don't think so. Feel free to add a property for z-axis. Above samples from w:Section_(United_States_land_surveying)#Subdivision_of_a_section (Add your motivation for this property here.) --- Jura 01:40, 29 July 2019 (UTC)

Discussion[edit]

Pictogram voting comment.svg Comment Could this be somehow done with our geo coordinates datatype? I realize this is for a relative coordinate vs absolute, but as presented here this seems to assume "x axis" = distance eastward, "y axis" = distance northward (I think?) which would otherwise be rather arbitrary. Is "x axis", "y axis" actually the terminology used in the original source for this proposal? ArthurPSmith (talk) 17:42, 29 July 2019 (UTC)
Yeah, that was my first thought too, but the datatype has degree as unit hardcoded. For PLSS terminology, see w:Public_Land_Survey_System#Commonly_used_terms; for the axes, w:Cartesian coordinate system. --- Jura 14:32, 30 July 2019 (UTC)
PLSS apparently uses "range" for east-west coordinate, and "township" for north-south, according to your source? Those terms seem confusing though. Anyway, "x" and "y" are definitely not defined. If we do have wikidata properties for this, we definitely need a clearer name. Maybe just "eastward distance" and "northward" distance", if that's how these should be defined? ArthurPSmith (talk) 17:19, 30 July 2019 (UTC)
By the way, we already have elevation above sea level (P2044) as a property for z-axis, although perhaps a relative measure is needed there too - "relative altitude"? ArthurPSmith (talk) 17:21, 30 July 2019 (UTC)
Reading the article last week, I concluded that a township is a much larger unit than a block or a section. I don't think the terminology needs to be identical. --- Jura 11:29, 5 August 2019 (UTC)
  • Pictogram voting comment.svg Comment @ديفيد عادل وهبة خليل 2, Nomen ad hoc: I updated the sample. I think it's sufficient to define it in terms of blocks. Compare Subdivision_of_a_section. What do you think. --- Jura 11:29, 5 August 2019 (UTC)
    OK. Thank you. Nomen ad hoc (talk) 13:19, 5 August 2019 (UTC).
  • But "block" is an area, not a distance. This whole thing doesn't make sense to me - would these properties only apply to the 16 stated items? Or where else would it be used? If it's less than 100 or so items that could use this, I Symbol oppose vote.svg Oppose special properties just for this purpose. ArthurPSmith (talk) 19:06, 5 August 2019 (UTC)
  • Pictogram voting comment.svg Comment Prefer x-offset and y-offset as labels. There *might* be other contexts where this could be useful. Jheald (talk) 20:17, 5 August 2019 (UTC)
  • Pictogram voting comment.svg Comment thanks for your feedback. I updated the sample and label accordingly. Don't hesitate to improve it further. --- Jura 14:49, 9 August 2019 (UTC)