Is your feature request related to a problem? Please describe. The Site Maps are pretty small. Especially for older folks/ people with disabilitys this represents a significant hurdle. As the text on the image has a fixed size.

Describe the solution you'd like For accassability it may be nice to offer an option for users to zoom into the image/pop it out like for headline images.

i.e. I would prefer a solution like this:

Describe alternatives you've considered In the long term, we are reducing our reliance on these maps anyway as they offer imo worse UX than the map, but sometimes having the extra context of a site-map may be nice.

Additional context Not a active issue for the person, who suggesed this but something he found a nice to add.

Describe the bug The geolocatecontroll does not respect our colorscheme.

To Reproduce Steps to reproduce the behavior:

1. Tap the geolocatecontroll
2. See ugly cyan

Expected behavior I would expect the locate me button to have TUM-relevant styling.

Screenshots

Additional context Not a high-priority bug

• [x] integrated our alternative map style
• [x] changed to a custom (only for this project) style.json
• [x] integrated into the build system

Discussion

The current implementation has slightly worse performance, due to using https://github.com/mapbox/mapbox-gl-leaflet under the hood. This is because:

Slower performances: When using mapbox-gl-leaflet, mapbox-gl-js is set as not interactive. Leaflet receives the touch/mouse events and updates the mapbox-gl-js map behind the scenes. Because mapbox-gl-js doesn't redraw as fast as Leaflet, the map can seem slower.

Alternatives I have considered:

• using a custom rasterisation service. This is costwise not an option for us, as I dont want to pay as much as for example MapTiler charges for serverside rasterisation
• using a tilejson compatible api. Not an option, because the one I found only has guides for vue-3 (we currently use vue-2) and the libarys I found which support vue-2 have other drawbacks. There may be one which I have not found, but currently this is not the case

resolves #8

Screenshots

before:

after:

This PR implements a coodinate Picker. resolves #107

Todo:

• [x] add translations
• [x] figgure out a way of creating a draggable custom marker (I have tried the simple ways, something is not working; I have to spend some quality time debuging this)
• [x] add a better styling than this:

since you are more into design: what UI would you (@octycs ) prefer?

This PR adds the best images from mediaTUM to NavigaTUM.

There are still some issues, that have to be resolved, before this can be merged:

• [x] I'd like your feedback on the values, I chose for THUMBNAIL_SIZE and HEADER_MAX_SIZE
• [x] There seem to remain some issues with the image-matching

-- 50 Add image information
Warning: No source information for image '0509.EG.980_0.webp', it will not be used
Warning: No source information for image '0509.EG.980_1.webp', it will not be used
Warning: No source information for image '0509.EG.980_2.webp', it will not be used
Warning: No source information for image '2319.EG.001_0.webp', it will not be used
Warning: No source information for image '5401.01.101K_0.webp', it will not be used
Warning: No source information for image '9001.EG.012_0.webp', it will not be used
Warning: No source information for image '5532.Z1.003_0.webp', it will not be used
Warning: There are images for 'tb-stammgelaende', but it was not found in the provided data, ignoring
Warning: There are images for 'tb-chemie', but it was not found in the provided data, ignoring
Warning: There are images for 'ottobrunn', but it was not found in the provided data, ignoring

• [x] I have not implemented a way of controll how a thumbnail is cropped. See 5304_0.webp (the mensa) for an example, why this is nessesary. My strategy of using the center square of the image works pretty much on every other image, but here it fails.

Resolves: https://github.com/TUM-Dev/NavigaTUM/issues/143

Is the roomfinder-map sufficient or should the map-cross also be implemented to the modal? I already tried to implement the cross but it is a bit difficult with the position because I think you have to make a function like the loadRoomfinderMap-function for the roomfinder modal.

This PR replaces our documentation via openapi docs. This PR also fixes some errors in the server that came to light while documenting it.

Todo:

• [x] fix error, that keeps tripping up the server
• [x] validate, that the shema I have written down is actually correct
  • [x] search
  • [x] get
  • [x] get_token
  • [x] feedback
  • [x] healthcheck
• [x] proofread the docs

@octycs I have one problem with the server. This is why I am publishing this PR now, instead of later when I would be more shure, that the openapi.yaml I have written is 100% correct. You can reproduce the issue by

0. run the server in a different tab
1. installing schemathesis
2. st run --endpoint /api/search/.+ ./openapi.yaml --base-url http://localhost:8080

I am not getting anywhere debugging this (the error seems to pop out of nothingness). Could you look into this

Describe the bug Z10 (and potentially other entries) have an error in the Roomfinder Maps data.

To Reproduce Steps to reproduce the behavior:

1. Go to https://nav.tum.sexy/building/0510
2. Get an empty page because of the error: TypeError: view_data.maps.roomfinder.available[state.map.roomfinder.selected_index] is undefined

Expected behavior Should not crash

Additional context This is a crash in the frontend (which shouldn't happen), but probably related to an error in the data.

Updates the requirements on actix-web to permit the latest version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

This PR adds the possibility to add custom maps that appear in the Roomfinder map lists and includes some maps for the StudiTUM Garching along with coordinates.

ToDos:

• [x] Unify and document data format changes (especially ids are now mixed between str and int)

Hallo, ich möchte diese Koordinate zum Roomfinder hinzufügen:

"5506.01.628": { lat: 48.26626184691719, lon: 11.66844799348732 }  

mein letzter request 301 wurde zwar gelöscht, aber der Ort auf dem Plan hat sich nicht verändert.

Is your feature request related to a problem? Please describe. The API from russqlite not great to work with and likely error prawn. I think it is time to switch to a real ORM.

Describe the solution you'd like I would like to exchange all usages of russqlite with the respective usecases from diesel

Describe alternatives you've considered Sticking with russqlite. While being an option, manually constructing queries and extracting from them increases the likelyhood of errors.

Additional context This is becoming an issue in #324, as there more SQL is needed.

Describe the bug When you resize the window the cross of the roomfinder map is not at the right place anymore.

To Reproduce Steps to reproduce the behavior:

1. Go to any room
2. Click on roomfinder
3. Make your browser-window smaller
4. The cross is at a wrong place

Expected behavior The cross should stay at the right place when resizing the window.

Screenshots

Fullscreen

Smaller Window

Desktop:

• OS: Windows 11
• Browser: Mozilla Firefox
• Version 107.0 (64-bit)

Is your feature request related to a problem? Please describe. Currently, our approach to the search page was this I think we could improve this UX

Describe the solution you'd like Meilisearch has introduced a pagination feature. This would be a good fit for our search results page.

Describe alternatives you've considered Leave as is: The current approach works quite well. If talking about room-searches it is usually not that important to offer all the rooms, but only the first 30'ish ⇒ offering all via pagination is not a huge priority

Closes https://github.com/TUM-Dev/NavigaTUM/issues/289

I added the modal for the calendar when clicking on the calendar icon. I used an iframe to display the TUMOnline website but the URL is not found. I don't know what's the problem because it is the same URL which is used to open the website.

This PR provides the setup script for automatically setting up our future HA cluster (currently our deployment is really not in this ballpark. This would be a big improvement.) It is currently very WIP.

Current Roadblock: ZIT is sitting on their hands for “important reasons”. We cannot switch to a quicker provider for

• “We cannot help a central service, as our Profs would not allow this”~ Rechnerbetriebsgruppe or
• “Our Vereinszweck sadly does not allow this”~ StuStaNet or
• “We won't offer this”~ Compref

This will mostly just go through a Docs-review.