Add 256x256 tile size and (perhaps) custom tile naming convention

[yaapu]

Hi, very nice tool, I love it!

I'm (slowly) adding 256x256 tile size support for high res radios, would you consider adding that resolution as well, it's a POC right now, it works but since tiles so big do not fit vertically in a 800x480 (256x2 > 480) the tile centering algos need to be adjusted, I'd rather not scale the tiles vertically but that might be the best solution, I could resize tiles on the fly but it would cost some CPU that "could" CPU kill the script on older radios

[MartinovEm]

Hi @yaapu,
really glad you like the tool, and thanks a lot for the detailed feedback and POC work.

Both ideas seem possible on our side:

1. 256x256 tile export support
2. optional custom naming/folder convention

Before implementing, I want to make sure we do it safely, especially for users with older radios.

Main risks we see for end users/radios:

1. RAM usage on radio: 256x256 tiles are much heavier than 100x100.
2. Performance/CPU on radio: runtime resize/recenter logic may increase CPU load and can risk script slowdowns or watchdog/script-kill behavior on older radios.
3. Storage size and SD I/O: bigger tiles increase file size and load times.
4. Viewport fit issues: on 800x480, 2x256 = 512 vertically, so centering/alignment logic can produce clipping/misalignment if not handled carefully.
5. Backward compatibility: changing naming/layout can break existing setups unless we keep strict compatibility presets.
6. Old radio risk: users on older hardware are most exposed to RAM/CPU regressions if they enable high-res options.

To implement this correctly, could you clarify a few points:

1. Which Yaapu target should be affected first: Yaapu ETHOS, Yaapu EdgeTX, or both?
2. For 256x256 support, do you want:
   • export-only support (generator outputs 256 tiles, widget handles them), or
   • any additional generator-side adjustments beyond tile size?
3. About “custom naming convention”: what exactly should be customizable?
   • map folder names?
   • zoom/x/y folder structure?
   • tile filename pattern (for example s_x.png vs another pattern)?
4. Could you share one concrete expected path example for a single tile (including Z/X/Y), for each affected target?
5. Should this be:
   • a fixed new preset, or
   • user-selectable naming profiles?
6. Do you want 100x100 to remain the default for compatibility, with 256x256 as opt-in/experimental?

Once you confirm these, we can implement a safe first version with compatibility guards and clear warnings for older radios.

[yaapu]

@MartinovEm perhaps best solution is limit the feature to recent powerful radios and limit the older ones to 100x100.
I never had issues with 100x100 but I understand that hybrid maps might get hard to read with aggressive resizing.
so to recap:

• 256x256 no post processing since it's targeted at high end radios
• no prefix in the tile name to make it clear it has not neen post-processed (no real advantage actually, we might keep the same naming convention, no big deal)
• as for path my POC uses
  100x100 <provider>/<provider specific tile path>
  256x256 <provider>/_256x256/<provider specific tile path>
  But we can find a better solution, main point IMO is keep the tiles separated by provider first and then by resolution

[MartinovEm]

Hi @yaapu, thanks, this is very clear and helpful.

Here is my proposal:

1. I’ll implement this in a separate experimental branch (test-256x256).
2. 256x256 will be available only for Yaapu targets.
3. 100x100 will stay the default for compatibility.
4. 256x256 export will be no post-processing.
5. I’ll keep provider-first + resolution-separated paths for 256x256 (for example: provider/_256x256/...).
6. I’ll keep the current tile filename convention unless you request specific naming changes.

Could you also share which radios you consider “high-end” (a few concrete model examples)?
I want to include those examples directly in the 256x256 warning message so users can choose the right mode.

[MartinovEm]

@yaapu Also, can you take a look at that issue please and tell me the final tile format, so I could change it (if needed) for both of Yaapu target in Map generator.
Thanks!

#4 (comment)