[Task 2C.3] Map Component pi3d Rendering (Backend for #652)

[helgeerbe]

While the frontend UI for the Map Component (Ticket #652) is complete, the backend needs to generate or fetch static map tiles and render them via pi3d on the physical display when location data is present. Map rendering involves external API calls (e.g., OpenStreetMap), tile caching, and complex pi3d texture mapping, which is significantly more complex than standard text overlays.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[helgeerbe]

Closing this as not desired / superseded by the current architecture decision.

#654 proposes generating/fetching static map tiles and rendering a graphical map via pi3d on the physical display. That is not the intended behavior for next-gen Picframe.

Decision:

• The physical frame displays media files only.
• Temporary on-frame metadata is limited to text/clock overlays.
• The graphical map is UI-only and belongs in the web Remote view.
• Backend responsibility is to expose media location metadata/coordinates to the UI, not to render map tiles on the frame.

The current code already follows this direction: the Leaflet map lives in the frontend MapComponent, while RenderCommand / pi3d rendering remain focused on media and overlays. No static-map tile cache or pi3d map renderer should be implemented unless a new explicit product requirement reverses this decision.