Expand from one dong to the surrounding region
Expand patients and hotspots in Graph Explorer, then trace the path from one dong to its sigungu and sido.
This step's question
Starting with Junggye 4-dong, how can we expand to related patients and higher administrative regions?
Why this matters now
An aggregate for one area shows only the result. A graph path lets you trace which patients, places, and regions contributed to that result.
Try it yourself
Open Graph Explorer from the left navigation, then select the COVID-19 Data Collection
(covid19) from the collection filter.
First, select the Patient (patient) entity and confirm that patients and their directly connected
nodes appear. Select one patient and inspect its identifier in the Node properties panel.
- Select the
hotspotnode connected to the patient byinvolved_in. - In Node properties, select Expand neighbours.
- Select the added
dongnode and use Expand neighbours again. - Continue through
sigunguandsidoin the same way.
Expected result: you can see one connected path that shows which dong contains each patient and hotspot, and which sigungu and sido contain that dong. This tells you which higher administrative unit should receive the observation.
Next, select dong under Entities and find Junggye 4-dong (중계4동). Confirm the dong
property, then select Expand neighbours. Select a hotspot connected by within and expand it once
more to add the related patients.
Other dong nodes loaded by the entity-type selection can remain on the canvas. For the following
observations, trace only the connections that start from Junggye 4-dong through within, and exclude
unconnected dong nodes from the interpretation.
Expected result: you can inspect whether several patients connect to one hotspot or one patient connects to several hotspots in Junggye 4-dong. Start follow-up checks with the places where connections converge, then inspect their original occurrence times and locations.
If no nodes or edges appear, confirm that the selected collection is covid19. If it is, return to the
previous chapter and verify that the ontology-loading pipeline finished with Success, then select
the entity again.
Read the result
The first result traces one patient's location context to a broad administrative unit. In the second, other dong may remain on the canvas, so trace only the connections that start from Junggye 4-dong. A recorded connection is not proof of causation.
First graph: find the reporting unit
The patient → hotspot → dong → sigungu → sido path connects a patient to higher administrative
regions. Use it to decide which sigungu owner should receive an observation and whether comparison with
other dong in the same area is warranted.
Second graph: inspect connection density in one area
Following the within connections from Junggye 4-dong lets you read that dong's hotspot and patient
connections without mixing in other dong that remain on the canvas. Check whether several patients
connect to one hotspot and whether one patient connects to several hotspots before interpreting
node size.
| Graph pattern | Next analytical question |
|---|---|
| Several patients connect to one hotspot | Did they actually overlap in the same time window? |
| One patient connects to several hotspots | Does the route extend into adjacent areas? |
| Connections concentrate at one place | Do facility type or opening hours reveal a shared condition? |
| Very few connections appear | Is data missing, or are routes genuinely dispersed? |
The graph is an exploration view for choosing which rows and times to inspect next, not proof of
what happened. After finding a suspicious connection, check cross_start_time and cross_end_time in
the source Hotspot Analysis Result (hotspot_result) dataset.
Next decision
The graph shows how hotspots and patients connect in Junggye 4-dong. To decide whether it should be checked before another area, compare Junggye 4-dong, Seongnam-dong, and Junggye Bon-dong by the same criteria in the next chapter.