Open main menu
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 7 days. For the archive overview, see User talk:TilmannR/Archive.


The Great Sethahedron.svg copyright changedEdit

Tilmann: I found your message about The Great Sethahedron.svg. I changed the copyright to "public domain" as you requested. You asked, "Could you give me its vertex coordinates?" I do not have those coordinates. A brief video about TGS is posted on YouTube at The Great Sethahedron. Seth was my great grandfather and that is why the name TGS includes "Great". Scott Gregory Beach (talk) 22:10, 16 February 2019 (UTC)

A barnstar for you!Edit

  The Original Barnstar
Thanks, TilmannR for your excellent contributions to the viewstl and lang gallery templates, and Mars_elevation_2.stl – any chance you could update file:Earth_dry_elevation.stl and file:Moon_elevation.stl? cmɢʟee ⋅τaʟκ 13:44, 26 March 2019 (UTC)

Mars elevation STLsEdit

Moved from User_talk:Cmglee

Hi. I noticed that Mars elevation.stl is not quite optimal.

  1. The data is "planetocentric", so I don't believe that using a "WGS84 flattening factor" is actually correct. I'm not 100% sure though.
  2. If you look at a smoothly shaded version of the file, it becomes obvious that the positions of the peaks of your little pyramids aren't correct.
View Mars_elevation.stl  on

I uploaded Mars elevation 2.stl yesterday. It's not quite finished, but I already like it a lot. It's generated via an embarrassingly brute-force method: I use a normalized subdivided Deltoidal icositetrahedron as a base mesh, which leads to more uniform triangle sizes than using a normalized subdivided cube. Then I took nearest-neighbor-interpolated (i.e. not at all interpolated) altitude samples from megt90n000fb.img for a 207.4 MB STL. Finally I decimated the file to a tenth of its original size in Blender. Originally I intended to use an adaptive subdivision approach, but decimation (while being extremely slow and memory intensive) gives excellent results, so I don't feel motivated to do that much additional programming. My texture coordinate calculation seems to be off by one, which causes a small hole in the south pole. A "south hole", if you will. I'm thinking of doing iterated subdivision and decimation to reach an even better mesh. And I should probably use a smarter sampling method for the altitudes.

View Mars_elevation_2.stl  on

TilmannR (talk) 13:09, 24 March 2019 (UTC)

Hi @TilmannR:, Great that you managed to improve on my model; I like it a lot too. I'm no expert at STL or planetary models, and didn't know Blender can optimise STL files – that's a great resource. If I understand correctly, triangulated irregular networks are far more efficient with polygons. Are you familiar with their use in 3D modelling?
I also don't fully understand what you mean by "the positions of the peaks of your little pyramids". Can you please elaborate?
The "more interesting" side of Mars
P.S. Just a minor nitpick: would you mind turning the planet around (keeping the equator horizontal) so that Tharsis and Valles Marineris are visible in the thumbnail, as on the right? Thanks! cmɢʟee ⋅τaʟκ 13:32, 26 March 2019 (UTC)
@Cmglee: Hi. Let's continue the conversation over here. I still don't receive any pings from your talk page.
  • Yes, Blender is a surprisingly powerful tool. One of the most successful open source projects of them all.
  • As far as I can tell "triangulated irregular network" is just geography jargon for "triangle mesh". So, yeah, using an arbitrary triangle mesh is more efficient than using a regular grid, because a grid puts unnecessarily small triangles in smooth regions of the planet and it fails to put vertices at the very edge of sharp cliffs or at the very tip of sharp peaks.
  • By "little pyramids" I mean what you called "subdivide facets with local minima/maxima" in the file history. The center points of these subdivided facets end up far away from where they should be. This is particularly noticeable in the corners of the top and bottom face of the cube when smooth shading is applied, because it makes some triangles face towards the planet, which causes dark lighting artifacts.
  • I'd prefer, if there was a way to control the camera parameters of STL thumbnails, but I guess adjusting the planet's orientation is the way to go for now.
  • I'll create a new Earth and Moon once I've found a more efficient way to create these meshes. If I haven't come up with a better method by Sunday, I'll use the "Blender decimation method" again. TilmannR (talk) 21:29, 26 March 2019 (UTC)
My plan to iteratively subdivide and decimate in order get a better mesh didn't quite work out. The rough parts of the planet require a huge amount of geometry in order to be represented accurately, which leaves only very sparse geometry for the smooth parts and that just doesn't look very good. TilmannR (talk) 03:52, 27 March 2019 (UTC)
Got your ping (wonder why you don't get mine...) Anyway, thanks for trying. If Blender automatically does the equivalent of TIN, perhaps it's simpler just to use Blender for that. By the way, I've since found a better DEM for Earth: the ETOPO1 dataset cmɢʟee ⋅τaʟκ 13:53, 27 March 2019 (UTC)
Thank you so much for uploading File:Earth_dry_elevation_2.stl and File:Moon_elevation_2.stl and rotating File:Mars_elevation_2.stl. They are much more detailed than mine and are simply stunning! Earth is an example where Blender's optimising may be suboptimal though: it loses the faint coastlines visible in mine, such as north of Australia, that makes it easier to identify countries. If only it's possible to tell Blender to weight the coastlines...
And sorry I'm nitpicking again, but would you mind rotating the globe as you did for Mars to show a more interesting thumbnail? I'll leave what to show to you (though I'm partial to showing both the Himalayas and Marianas Trench myself). Thanks in advance!
Lastly, I read that STL unofficially supports a colour for each polygon, but haven't found any viewers that support this. This is something which put me off making more STL models, as they all end up some bland grey. If colour and preferably other material properties like specularity, opacity and reflectivity were supported, I'd be tempted to add more to. Cheers, cmɢʟee ⋅τaʟκ 22:38, 27 March 2019 (UTC)

WAM logo in SlovakEdit

Hi TilmannR, I saw that you created WAM logo in Malay and I wanted to ask how did you change the handwriting. I want to make Slovak version of logo with "ÁZIJSKÝ MESIAC" instead of "ASIAN MONTH" and I wrote to 林立云 who wrote the original one if he would be able to make Slovak name but he didn't reply. If it would be possible for you, would you be please able to make the Slovak version?

As I said, "ASIAN MONTH" should be changed to "ÁZIJSKÝ MESIAC" and the "WIKIPEDIA" to "WIKIPÉDIE". The order should be reversed, therefore "ÁZIJSKÝ MESIAC" should be first and "WIKIPÉDIE" below.

If you cannot do it, it is okay, I can still wait if he replies but I wanted to speed things up a bit so I can prepare this year's edition of WAM.

Thanks, --Luky001 (talk) 16:00, 4 June 2019 (UTC)

@Luky001: I copied most of the letters from the original image. The "L" and the "U" in "BULAN" are just slightly modified versions of the "T" and the "M" in "MONTH". If I remember correctly, I made the "B" out of two copies of the "O". I don't have any experience in creating calligraphy from scratch, so I recommend waiting for 林立云 to reply.
Or you could make a request at the Illustration workshop. TilmannR (talk) 18:32, 4 June 2019 (UTC)
@Luky001: I am extremely busy these months. I will reply your email and write for you in two weeks. 林立云
@Li-Yun Lin: So?--Luky001 (talk) 06:20, 1 July 2019 (UTC)

@TilmannR: Hi, I have the handwritings from Li-Yun Lin, could you please send me an email (via Email this user) so I can send them to you? I don't want to upload them to Commons since those files shouldn't be here permanently and they are not my work. --Luky001 (talk) 11:17, 19 July 2019 (UTC)

SVG Translation Campaign 2019 in India: Feedback surveyEdit


Many thanks for participating in the SVG Translation Campaign 2019 in India. It had been quite a successful campaign—194 users from 19 Indic languages took part in the campaign for 38 days, and have created more than 2,500 SVG files, all of them having labels in native Indian languages. You may read the complete report of the campaign at

We would like to thank you again for translating SVG files as a part of this campaign, your contributions have given thousands of people the knowledge that they need the most. Now we would like to have your feedback about the overall campaign, how effective were the training sessions, the resources provided, the support etc.

Please fill the feedback survey at

Your responses are extremely valuable to us, and will be of immense help to understand further training needs or plan future activities in this area. Let us know if you have any questions.

Please note that 4 August 2019 is the last date to complete the survey. KCVelaga (talk · mail) 05:40, 23 July 2019 (UTC)

Return to the user page of "TilmannR".