Data requests

[octycs]

This is a proposed tracking issue for specific data requests. Please comment if you have ideas of how to improve.

Coordinates

Based on calendar events in a reference week from the 16-20 Jan 2023, the following (subset of) rooms have events happening in them but no coordinate known:

Stammgelände

• 0305.02.520 (5 events)
• 0206.02.202 (4 events)
• 0204.04.403 (4 events)
• 0502.03.250 (2 events)
• 0509.02.998 (2 events)
• 0104.02.407B (2 events)
• 0305.04.523 (2 events)
• 0401.03.311 (1 events)

RiWa 1 (HfP, Governance)

(Has neither maps nor coordinates at the moment)

• 2911.01.103 (25 events)
• 2911.02.204 (25 events)
• 2911.02.200 (24 events)
• 2911.01.100 (21 events)
• 2910.EG.003 (19 events)
• 2911.02.203 (19 events)
• 2910.EG.004 (18 events)
• 2910.02.206 (14 events)
• 2910.01.103 (12 events)
• 2910.EG.001 (9 events)
• 2910.01.158 (7 events)
• 2910.02.262 (6 events)
• 2910.04.414 (6 events)
• 2910.01.162 (5 events)
• 2910.03.351 (4 events)
• 2910.01.160 (2 events)
• 2910.04.456 (1 events)
• 2911.03.308 (1 events)

Weihenstephan

• 4214.EG.030 (21 events)
• 4277.EG.128 (18 events)
• 4214.EG.010 (17 events)
• 4102.01.040 (17 events)
• 4214.EG.020 (16 events)
• 4277.EG.129 (16 events)
• 4217.EG.041 (16 events)
• 4124.U1.104 (15 events)
• 4317.03.305 (14 events)
• 4101.01.129 (14 events)
• 4219.U1.001 (14 events)
• 4102.EG.034 (14 events)
• 4277.EG.109 (14 events)
• 4308.EG.112 (13 events)
• 4102.01.038 (13 events)
• 4214.U1.034 (12 events)
• 4308.EG.114 (12 events)
• 4277.EG.130 (12 events)
• 4224.02.298 (12 events)
• 4113.01.105 (12 events)
• 4277.EG.073B (11 events)
• 4215.U1.058 (11 events)
• 4214.EG.040 (9 events)
• 4277.EG.108 (9 events)
• 4215.U1.026 (9 events)
• 4153.EG.001 (9 events)
• 4213.EG.302 (8 events)
• 4219.01.020 (8 events)
• 4219.U1.003 (8 events)
• 4224.02.234 (8 events)
• 4214.EG.041 (7 events)
• 4102.01.043 (6 events)
• 4277.EG.083 (6 events)
• 4215.EG.040 (6 events)
• 4215.EG.041 (6 events)
• 4234.EG.526 (6 events)
• 4213.EG.310 (5 events)
• 4109.EG.050 (5 events)
• 4108.EG.106 (5 events)
• 4277.EG.073A (5 events)
• 4220.EG.112 (5 events)
• 4220.02.101 (5 events)
• 4215.EG.039 (5 events)
• 4215.U1.026A (5 events)
• 4217.01.114 (5 events)

(<4 truncated)

Garching (Chemie)

• 5406.01.641A (23 events)
• 5403.04.330A (21 events)
• 5406.01.641K (16 events)
• 5403.04.330F (16 events)
• 5402.EG.240J (10 events)
• 5406.02.622K (7 events)
• 5407.01.760E (5 events)
• 5406.01.650E (4 events)
• 5407.02.710E (2 events)
• 5406.03.630F (2 events)
• 5406.01.650A (2 events)
• 5403.05.340A (2 events)
• 5406.04.630F (1 events)
• 5406.EG.630G (1 events)

Garching (MW)

• 5507.01.701 (16 events)
• 5502.03.237 (14 events)
• 5504.03.414 (13 events)
• 5506.01.638 (13 events)
• 5506.EG.690H (10 events)
• 5501.02.142 (10 events)
• 5507.03.707 (8 events)
• 5504.01.401 (7 events)
• 5501.02.104 (6 events)
• 5505.02.537 (6 events)
• 5504.02.412 (4 events)
• 5504.01.442 (4 events)
• 5504.02.452 (4 events)
• 5503.03.340 (4 events)
• 5505.U1.550 (4 events)
• 5503.01.301 (3 events)
• 5501.EG.199A (3 events)
• 5501.U1.150 (3 events)
• 5505.03.502 (3 events)
• 5515.EG.005 (3 events)
• 5504.03.408 (2 events)
• 5504.01.404M (2 events)
• 5510.U1.050 (2 events)
• 5506.03.643 (2 events)
• 5502.01.264 (2 events)
• 5501.01.126 (2 events)
• 5501.02.101 (2 events)
• 5505.03.533 (2 events)
• 5504.U1.450 (1 events)
• 5504.02.407 (1 events)
• 5506.02.636 (1 events)
• 5506.02.613B (1 events)
• 5506.EG.699A (1 events)
• 5502.01.237 (1 events)
• 5505.02.501 (1 events)
• 5505.01.501 (1 events)

Garching (Rest)

• 5901.EG.051 (22 events)
• 5140.01.201 (18 events)
• 5140.01.202 (18 events)
• 5415.EG.006A (17 events)
• 5901.01.032 (13 events)
• 5901.02.021 (12 events)
• 5901.03.013 (10 events)
• 5901.01.013 (10 events)
• 5112.EG.101S (10 events)
• 5701.EG.026 (9 events)
• 5414.EG.002 (9 events)
• 5410.02.002 (9 events)
• 5415.EG.006B (9 events)
• 5901.03.022 (7 events)
• 5701.01.211 (6 events)
• 5111.01.116 (6 events)
• 5901.02.049 (5 events)
• 5204.01.005 (5 events)
• 5901.01.035 (4 events)
• 5433.EG.004 (4 events)
• 5115.02.003 (4 events)
• 5901.02.013 (3 events)
• 5212.02.202 (3 events)
• 5530.01.102 (3 events)
• 5530.01.101 (3 events)
• 5530.EG.003 (3 events)
• 5433.02.001 (3 events)
• 5701.01.222 (2 events)
• 5901.02.052 (2 events)
• 5612.02.020 (2 events)
• 5415.EG.003 (2 events)
• 5532.03.302 (2 events)
• 5532.U1.020 (2 events)
• 5901.03.049 (1 events)
• 5901.03.052 (1 events)
• 5901.01.016 (1 events)
• 5608.03.022 (1 events)
• 5410.03.046 (1 events)
• 5410.01.105 (1 events)
• 5112.03.402S (1 events)

[CommanderStorm]

I did some analytics on 2022. This is a more complete view:

General Event Statistics

Events in Rooms we have coordinates for: 62581
Events in Rooms we don't have coordinates for: 292719
=> 21.37% of Events are in Rooms for which we don't have coordinates

Code for this analytic

SELECT COUNT(*)
from calendar c
WHERE extract(year from DATE(c.dtstart)) = 2022 AND
      extract(year from DATE(c.dtend)) = 2022 AND
      NOT EXISTS(
          SELECT * FROM unacurate_coordinates u
          WHERE u.key = c.key
      )

All Rooms

This is the List of rooms with events in 2022, for which we dont have exact coordinates

Code for this analytic

SELECT c.key,Count(*) --,DATE(MIN(c.dtstart)),DATE(MAX(c.dtend))
from calendar c, unacurate_coordinates u
WHERE extract(year from DATE(c.dtstart)) = 2022 AND
      extract(year from DATE(c.dtend)) = 2022 AND
      u.key= c.key
group by c.key
order by Count(*) desc

High-Traffic Rooms

I assume that not all rooms are equally important.
There are 249 work days in a year => lets look at these rooms.

HT Rooms with coordinates: 249
HT Rooms without coordinates: 83
=> we are missing 25% of HT rooms

Code for this analytic

SELECT c.key,Count(*)
from calendar c
WHERE extract(year from DATE(c.dtstart)) = 2022 AND
      extract(year from DATE(c.dtend)) = 2022 AND
      EXISTS(
          SELECT * FROM unacurate_coordinates u
          WHERE u.key = c.key
      )
GROUP BY c.key
HAVING COUNT(*) > 249

[octycs]

I was curious why 5612.02.020 has so many events; apparently IRIS adds any usage into the calendar. Anyway it is probably easy to add this coordinate (given 5612.02.018 and 5612.02.019 or you might be close occasionally).

[CommanderStorm]

Closing as I don't think without #670 this issue makes a how lot of sense. (plus I don't think it has had any effect ^^)