-
Notifications
You must be signed in to change notification settings - Fork 0
spec: add network-transport-static specification #3573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Empty file.
Empty file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| # network-transport-static: Static Transport Network Diagram | ||
|
|
||
| ## Description | ||
|
|
||
| A directed network visualization for transportation systems where stations are displayed as labeled nodes and train/bus routes as directed edges. Edges display departure times, arrival times, and route identifiers. Designed for visualizing timetables, route maps, and connection patterns in rail, bus, or flight networks. This static version focuses on clear, readable presentation without interactive repositioning. | ||
|
|
||
| ## Applications | ||
|
|
||
| - Visualizing regional train networks with departure and arrival times at each station | ||
| - Displaying bus route maps showing service frequency and travel times between stops | ||
| - Analyzing flight connections between airports with layover and connection information | ||
| - Planning public transit coverage by mapping routes and identifying service gaps | ||
|
|
||
| ## Data | ||
|
|
||
| - `stations` (list of dicts) - nodes with `id`, `label`, `x`, `y` coordinates for positioning | ||
| - `routes` (list of dicts) - directed edges with `source_id`, `target_id`, `route_id`, `departure_time`, `arrival_time` | ||
| - Size: 8-20 stations with 15-60 routes for optimal readability | ||
| - Example: A regional rail network with 12 stations and 35 daily train services showing hourly departures | ||
|
|
||
| ## Notes | ||
|
|
||
| - Station nodes should display labels clearly; size nodes to accommodate station names | ||
| - Edges must show direction with arrows indicating travel direction | ||
| - Edge labels should display route identifier and times (e.g., "RE 42 | 08:15 → 09:30") | ||
| - When multiple routes connect the same station pair, use curved or offset edges to distinguish them | ||
| - Node positioning based on provided x/y coordinates; no force-directed layout needed | ||
| - Consider color-coding routes by type (regional, express, local) or frequency | ||
| - Tooltips (where supported) should show full route details on hover |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,11 @@ | ||||||
| spec_id: network-transport-static | ||||||
| title: Static Transport Network Diagram | ||||||
| created: 2026-01-10T00:00:00Z | ||||||
| updated: 2026-01-10T00:00:00Z | ||||||
| issue: 3463 | ||||||
| suggested: null | ||||||
| tags: | ||||||
| plot_type: [network, graph, directed] | ||||||
| domain: [transportation, logistics, infrastructure] | ||||||
| features: [labels, directed-edges, multi-edge] | ||||||
| data_type: [categorical, temporal] | ||||||
|
||||||
| data_type: [categorical, temporal] | |
| data_type: [categorical, temporal, network, relational] |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The YAML file is missing comments and structure that are present in other specification files. According to the project's pattern (see network-basic and network-directed), the file should include:
The tags structure should also follow the established pattern with list items on separate lines using hyphens, not inline brackets.