Add manual stop creation and override alerts with alternate stop codes (#74)

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: arielcostas <94913521+arielcostas@users.noreply.github.com>
Co-authored-by: Ariel Costas Guerrero <ariel@costas.dev>

1 files changed, 31 insertions, 0 deletions

diff --git a/data/vigo/overrides/example-new-stops.yaml b/data/vigo/overrides/example-new-stops.yaml
new file mode 100644
index 0000000..6937471
--- /dev/null
+++ b/data/vigo/overrides/example-new-stops.yaml
@@ -0,0 +1,31 @@
+# Example: Adding a new stop using the 'new' parameter
+# New stops are added directly in override files with new: true
+
+# Example 1: New stop with basic information (commented out to avoid affecting production)
+# 99001:
+#   new: true
+#   name: "New Development Stop"
+#   location:
+#     latitude: 42.229188
+#     longitude: -8.722469
+#   lines:
+#     - "5"
+#     - "12"
+#   amenities:
+#     - shelter
+
+# Example 2: New stop with alert information
+# 99002:
+#   new: true
+#   name: "Temporary Event Stop"
+#   location:
+#     latitude: 42.230000
+#     longitude: -8.723000
+#   lines:
+#     - "EVENT"
+#   title: "Special Event Stop"
+#   message: "This stop is active during special events only."
+
+# Note: The 'new: true' parameter tells the system to create a new stop.
+# This parameter is automatically removed after the stop is added to the dataset.
+# Choose stop IDs in the 90000+ range to avoid conflicts with existing stops.