File talk:Comparison satellite navigation orbits.svg
Better labels on the axes
[edit]As of 2012-06-10, all of the four axes have no labels for the data value at Geosynchronous orbit.
While this doesn't matter too much, at least for the technically inclined, on three of the axes, it matters greatly for the "Orbital Speed" access.
Why? Well the "Radius of orbit" and "Height above sea level" are linear scales, where the data value corresponds linearly with distance on the graph. And while the "Orbital period" axis is non-linear, every space geek knows that the orbital period of a Geosynchoronous orbit is 24 hours. So it is not too difficult to figure out the (approximate) value at GEO for those three axes.
But the "Orbital speed" access is non-linear, and the vast majority of Wikipedia (and Wiki-media) readers are not going to be very facile in interpolating data values to unlabeled cross-hatches on a non-linear axis scale.
Net, this is a wonderful graphic; I'm really pleased someone took the time to develop it. But it would be much better with data values given at GEO on all four axes. (And even if you disagree with labeling all four axes at GEO, I hope someone will produce a version of this graphic with the "Orbital speed" axis labeled at GEO.)
Cheers, N2e (talk) 22:34, 10 June 2012 (UTC)
- Thanks for the excellent observation, @N2e: . Fixed as requested! cmglee (talk) 22:27, 16 April 2016 (UTC)
Cropped too much
[edit]I think a little bit of white space padding would improve the overall balance of the diagram. The Geostationary Earth Orbit label at the top, and the line pointing to the circle, is too close to the edge that it doesn't stand out. The line overlaps with the edge of the image. --Makkachin (talk) 01:10, 15 December 2015 (UTC)
- Good point, @Makkachin: . Fixed as requested, though I couldn't add too much to avoid the annotation being too misaligned. cmglee (talk) 22:29, 16 April 2016 (UTC)
PNG rendering error
[edit]"Inner Van Allen Belt" has extra spaces, presumably to keep the letters away from the Y axis. Two of these spaces are rendered as question marks in the PNGs.--88.74.213.82 10:51, 23 October 2016 (UTC)
Done ... and also added animation! cmɢʟee⎆τaʟκ 14:15, 23 October 2016 (UTC)
Request for machine-readable text labels
[edit]This is a very educational file. If someone with knowledge in SVG-editing could change the texts within to machine-readable text labels it would be great, since that would make it a lot easier to translate this file using the SVG Translate tool on Toolforge. :-)
Scouten (talk) 11:21, 13 November 2019 (UTC)
- Thanks, @Scouten: The text labels are already internationalised using switch and systemLanguage (English and Spanish are supported as of today), as can be seen by opening the file in a text editor. The tool should be updated to support them, if it doesn't yet. I'll write to the tool developers and refer to your request. Cheers, cmɢʟee ⋅τaʟκ 00:07, 17 November 2019 (UTC)
- P.S. Reported on commons_talk:SVG_Translate_tool#Problem_with_comparison_satellite_navigation_orbits.svg
- cmɢʟee ⋅τaʟκ 00:15, 17. Nov. 2019
- @Scouten and Cmglee: SVG translate tool only supports simple svgs. All bug-reports can be read here: https://phabricator.wikimedia.org/tag/svg_translate_tool/. The File uses several tspans without coordinates, which seems not to be supported, see phab:T230357. (Did not check if it is related.) — Johannes Kalliauer - Talk | Contributions 22:53, 10 December 2019 (UTC)
- Thanks, @Scouten and JoKalliauer: that seems a rather severe limitation. It's common to have tspans without coordinates, as tspans are used to modify text appearance e.g. bold (font-weight) or italics (font-style), in addition to positioning. Is there a reason for the tool to not support all tspans? Cheers, cmɢʟee ⋅τaʟκ 01:23, 23 December 2019 (UTC)
Featured Media and Featured Picture issues
[edit]First, many thanks to everyone who approved its candidacy and gave feedback (whether support or opposition) and @It Is Me Here: for bringing it to my attention. To address issues on Commons:Featured_media_candidates/File:Comparison_satellite_navigation_orbits.svg,
Re @El Grafo:
1) The mouse-over functionality is behaving very strangely for me. Default status for labels is highlighted (saturated). Default for the orbits is also highlighted, but as soon as my mouse pointer moves inside the image boundaries, they all turn to be desaturated. When I hover over a label (e.g. "Galileo"), all other labels turn to be not highlighted, and all orbits turn to be highlighted instead. Hovering over an orbit highlights that orbit only, but does nothing to the labels (all remain highlighted) and removes both of the Van Allen Belts completely (though their labels remain). The Graveyard Orbit label is always highlighted/saturated. For reference: I'm using Firefox on Ubuntu 18.04
Fixed It was intended for a teacher or instructor to be able to highlight different features on mouseover. In the internationalisation process, the behaviour broke, and I've hopefully fixed it as intended. To avoid flicker when the mouse crosses a shape, I've made only text labels trigger the effect.
2) The whole thing is visually busy. It is really difficult to find the actual content between all those giant labels. I'd tone down the visual weight of the axes a bit, and make the orbits stand out more. If you adjust the axis labels to something like Orbital period (hours) you can get rid of the repeated use of hours, km/h and mph (personal opinion: get rid of the miles and mph completely). Adding some white space around the current image could make the whole thing feel less busy and give you some space for proper label placement.
Comment Agreed that I tried to pack in perhaps too much info. I don't find the labels "giant": they're sized to make major ones legible in (large) thumbnails. It would be inconsistent to have "(hours)" for only Orbital period as other properties have Imperial and metric values. I'd much prefer to stick to metric, but sadly a large fraction of readers come from a country in which miles and mph still predominate. Agree on whitespace but didn't want to change it until after the FP period.
3) I don't really like the color scheme – maybe because it reminds me of the terrible 1990's MS Excel default colors for charts. ... --El Grafo (talk) 14:41, 20 July 2020 (UTC)
Comment I've to differ on that: I find the saturated colours fairly attractive and much easier to tell apart. I'd rather not have the blue background gradient, but needed a way to show the extent of the outer Van Allen belt.
Re @Xorx: I really like the idea and implementation of this active and animated diagramm. But as the previous voter I see annoying flaws in the mouse over function. There seems to be a "gap" inside the white ring above the "inner van allen belt". I would love to change my vote to "pro" when mouse over behaviour is improved because I really love this kind of diagram. So don't hesitate and improve it :-) -- Dr. Schorsch (talk) 11:58, 3 August 2020 (UTC)
Comment As in (1). I don't fully understand what you mean about the "gap", but hopefully the change has fixed it.
Thanks,
cmɢʟee ⋅τaʟκ 01:36, 19 August 2020 (UTC)