Page MenuHomePhabricator

[Story] allow to select globe in the UI
Open, HighPublic


It is currently only possible to select the globe for a coordinate via the API. It should be possible in the UI as well.



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:13 AM
bzimport set Reference to bz54097.
bzimport added a subscriber: Unknown Object (MLST).
  • Bug 51373 has been marked as a duplicate of this bug. ***

paperoastro wrote:

A suggestion for adding a "celestial sphere" globe for celestial coordinate system. Celestial coordinates usually used are equatorial coordinate system ( and needs "right ascension" (longitude expressed in hours, where 1h = 15 degrees), "declination" (latitude) and an epoch.

With setting this globe, the mask will ask "right ascension" and "declination" instead of latitude and longitude and will not ask altitude; "right ascension" (longitude) will be expressed in hours instead degrees. The epoch will be a qualifier.

Lydia_Pintscher removed a subscriber: Unknown Object (MLST).
Lydia_Pintscher removed a subscriber: Unknown Object (MLST).
aude renamed this task from allow to select globe in the UI to [Story] allow to select globe in the UI.Sep 11 2015, 8:19 AM
aude set Security to None.

T127950 has been created for celestial coordinate support (which needs more than just changing the globe).

Is this likely to be fixed any time soon? I've noticed some people have been adding coordinates for non-Earth objects despite not being able to change the globe. I've been reluctant to do that, but looking at the age of this ticket, I'm thinking it might be more productive to add them without changing the globe and convince someone to run a bot to fix them (using the statements).

Oh, and here's a query for items where the coordinate globe doesn't match the P376 statement.

I think we need to have a look into this, since query like this:

SELECT ?item ?place WHERE {
  ?item wdt:P31 wd:Q55818 .
  ?item wdt:P625 ?place .

Produces very weird results since half of the places have right globe and other half doesn't.

I also think having a bot fix at least those with P376 contradicting the coordinate is a good idea.

I've added a bot request here:

I think someone might have already fixed some of them (the number seems a lot lower than I remember), but I'm not sure who.

Oh, cool :) Would it be possible to run it daily?

There's a few that haven't been fixed, it seems their globes aren't in the supported list?

Since it uses pywikibot, it is limited by what pywikibot's set of globes, which currently seems to have some missing. I'll submit a patch to update it.

@Lydia_Pintscher Looking through this after our discussion today, @bzimport's comment above about the needs for astronomy looks good. RA, dec and epoch, e.g. see the values in the infobox at . Support for other astronomical coordinate systems (such as Galactic coordinates) would also be good, but that can be done later (and possibly by auto-converting them) - for now, just supporting equatorial coordinates would be incredibly useful for the work I'm doing with astronomical infoboxes.

7 years and this is still an annoying issue.

Mike_Peel raised the priority of this task from Medium to High.Oct 12 2020, 7:10 PM

Raising this to high priority, this is really important to properly support coordinate systems for other planets without mistakenly implying that they are on Earth.