Wikipedia:Featured picture candidates/MH370 Burst Timing Offset

MH370 Burst Timing Offset

Voting period is over. Please don't add any new votes. Voting period ends on 29 Jun 2015 at 22:31:05 (UTC)

Original – This graphic is used to illustrate one of the two main measurements used in the analysis of satellite communications made with Malaysia Airlines Flight 370, which disappeared in March 2014 in baffling circumstances. The subject of the article in which this graphic is used (analysis of the communications) is a very technical subject, while the missing aircraft is a very famous subject. Without going into a lot of detail (read the article), the BTO measurement was analyzed to determine the distance between the satellite and the aircraft. The result of the BTO analysis are rings on Earth (adjusted to account for a flying altitude of about 10,000m) where the aircraft was located when the communications were made. The graphic illustrates what the BTO measurement represents. The analysis is key to determining where the aircraft flew and, thus, defining the search areas for the aircraft.

Reason

The image helps make a technical article more accessible (WP:TECHNICAL) and the main subject (Malaysia Airlines Flight 370, which covers six articles) more understandable, despite the fact that the graphic is not used in the other articles. Therefore, I believe this graphic has a very high encyclopedic value. It is not an artistically outstanding work, but it is simple, has good composition, and does not contain chartjunk (eg. no overly-detailed graphics, or unnecessary words like "Not to scale").

Rendering issue has been fixed! NOTE: Mediawiki does not render the image preview correctly! In other words, when you view the file page of Wikipedia or Commons, the PNG image preview does not look right and so the PNG version is used in the article. However, if you click the image preview and view the actual SVG file, it renders correctly (the same as the PNG image displays)!!! I started to write this nomination for the PNG file, but then decided to nominate the SVG version because I realized the file was ok and that is what is being nominated. If the Mediawiki rendering is a problem, then I am not opposed to the PNG file being the candidate (if it is possible to discuss two different versions of the file in one nomination).

• SVG version (nominee show at right, but not rendered correctly by Mediawiki)
• PNG version (used in article, but inferior file type for this type of graphic)

Articles in which this image appears

Analysis of Malaysia Airlines Flight 370 satellite communications,

FP category for this image

Wikipedia:Featured pictures/Diagrams, drawings, and maps/Diagrams

Creator

AHeneen

• Support as nominator – AHeneen (talk) 22:31, 19 June 2015 (UTC)
• Comment The problem with the SVG is that you are using non-free fonts that Mediawiki does not support. Use the Commons:SVG Check tool to check out your graphic, open your SVG in a text editor, and make the corrections suggested by the tool. After fixing and adjusting your line lengths, your problem with overlap should be gone. Stigmatella aurantiaca (talk) 23:13, 19 June 2015 (UTC)
• Comment Aside from Stigmatella's point, there's the fact that the version promoted as FP must also be the one used in the article. Otherwise said FP will have no encyclopedic value (what value can it have if it's already been replaced?) — Chris Woodrich (talk) 23:49, 19 June 2015 (UTC)
• Note: Rendering issue has been fixed and the version in the article has been changed to the SVG version. AHeneen (talk) 05:00, 20 June 2015 (UTC)

• Here is a an old list of approved SVG fonts for Wikimedia and a current unformatted list of available fonts. Arial is not a font available for SVG rendering. If you absolutely must use a font that is installed on your computer but not on the server, you can convert the text to a path. That bloats the file size and makes it harder to modify the text, but you're assured that, except for browser issues, the downloaded SVG will render properly on different computers. Stigmatella aurantiaca (talk) 15:30, 20 June 2015 (UTC)

Arial is converted to Liberation Sans on Commons (commons:Help:SVG#Fallback fonts), so use of Arial is not a problem (and certainly does not need to be converted to vector). The two fonts are practically identical. AHeneen (talk) 22:50, 22 June 2015 (UTC)

Non-vectorised fonts in SVGs are notoriously problematic. When I look at the SVG version in IE or Chrome, I see a serif font with messy alignment. 109.152.146.250 (talk) 23:51, 23 June 2015 (UTC)

I see the same thing that you do. I customarily convert text to paths in my own SVGs, to heck with file bloat. Stigmatella aurantiaca (talk) 00:05, 24 June 2015 (UTC)

Why would the text not be aligned? All the text elements are center-aligned, so any font issues wouldn't impact the alignment of the text. Arial is a sans-serif font and no other font is specified in the file, so there's no reason why the text would be in serif font. Furthermore, Arial is one of the most common fonts used and is supported my nearly all OSs and browsers. The issue with Mediawiki support only affects the rendering of the PNG preview, not the svg file itself. Nonetheless, I have changed the file from "font-family:Arial" to "font-family: Liberation Sans, Arial, sans-serif" per the instructions at commons:Help:SVG#Fallback fonts. AHeneen (talk) 01:56, 25 June 2015 (UTC)

Check that "Time slot for reply" is centred. I still see a serif font in both IE and Chrome, even though I have Arial installed. Whether it's browser issues or something else, fonts in SVGs always seem to be a pain in the a**e. You can never be confident that another user will see the same as you. 86.152.161.192 (talk) 20:48, 25 June 2015 (UTC)

That was the only one that wasn't center-aligned. Fixed. There's no reason why you should see a serif font. As mentioned above, all the text elements have been changed to "font-family: Liberation Sans, Arial, sans-serif". AHeneen (talk) 04:58, 26 June 2015 (UTC)

Not Promoted --Armbrust ^{The Homunculus} 02:42, 30 June 2015 (UTC)