Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Backend] Render the campus and EC floors 1–2 from the map seeds, as the base for the Map mockup

Closed
  • Is something wrong?
#162 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
java, json, spring-boot
Domain
backend, data-visualization

Research direction

Start with the map seed JSON files under app/backend/microservices/map-service/src/main/resources/db/seed/map/ and inspect SpaceRendering in map-service or the existing plan-tracing scripts for a way to render their real plan shapes. Generate campus.svg/.png and ec-p1.svg/.png and ec-p2.svg/.png in docs/entrega/segunda-entrega/mapa-base/, commit the rendering script, and include a one-line regeneration note. Done means all three SVG and PNG pairs are generated from the current seeds, with no personal data.

Written by the indexing model from the issue text.

Description

area/backend

Part of the first delivery (parent issue above, due 2026-10-23). Alejandro will draw the Map mockup, and it has to come from the real plan shapes in the map-service seeds, never drawn by eye.

What to produce

SVG and PNG renders straight from app/backend/microservices/map-service/src/main/resources/db/seed/map/*.json:

  • the campus;
  • the Edificio Central (EC), floors 1 and 2.

They go in docs/entrega/segunda-entrega/mapa-base/, as campus.svg/.png, ec-p1.svg/.png and ec-p2.svg/.png. If one already exists, reuse its script; SpaceRendering in map-service or the plan-tracing scripts may already do most of it. Commit the script with a one-line note on how to regenerate them, and no personal data.

Phase 5 does not block this. It is a render of what the seeds hold today.

Done when

  • The three renders are in mapa-base/, generated by a committed script.
  • Merged into develop by 2026-10-21.
Dominant language
Java
Stars
1
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
85

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from K-Forge/KApp

All issues in K-Forge/KApp

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.