Last modified: 2013-11-12 15:18:53 UTC
According to the DataModel, Locations in Wikidata should have a dimension, but they are currently lacking that. Instead they have an altitude, which should rather be represented by a statements of its own.
For thw Wikidata usecase: what if someone wants to enter the location of the top of a mountain? Two statements for this is odd - are you going to just duplicate the references?
And the qualifiers?
Denny: Could you answer comment 1 and 2, please? [This has been highest priority for six weeks, hence pinging.]
The location of a top of the mountain can be entered without an altitude. The altitude is a value of its own, to be represented with a quantity value. We need a unit for altitude, and a way to represent its upper and lower bound. Mixing it into coordinate will merely make coordinate far more complex than it already is. Two statements, one to represent the location and one to represent the altitude is not odd. It is exactly how Wikipedia is doing it: go to any mountain. You will find the location and you will find the altitude, in two different values. There is no way to represent them together. Altitude has to go.
This has been "highest" priority for 3 1/2 months now without a patch, so I'd like to question the current priority. "High" instead?
altitude is already deprecated and not supported in the api. We decided not to implement "dimension" parameter. I am marking this as fixed/resolved.
