ImBenji/Roadbound-BRR
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add bus detail functionality and update organization selection UI

Browse Source
This commit is contained in:
ImBenji
2026-03-29 19:12:49 +01:00
parent 55cd970173
commit 3dfea45afb
10 changed files with 425 additions and 97 deletions
Download Patch File Download Diff File Expand all files Collapse all files
supabase/functions/operations-stop-alias-enhance/index.ts
+9 -10
View File
@@ -14,24 +14,23 @@ type OpenAiAlias = {
estimated?: string;
};
const prompt = `You are interpreting abbreviated station names from a rail replacement service display.
const prompt = `You are interpreting abbreviated stop names from a bus schedule display.
Each entry follows this structure:
* A 4-letter station code (derived from the real station name, often by removing vowels or compressing syllables)
* A 2-letter stop code (ignore this; it is ambiguous and not needed)
* A short stop code (typically 4 letters, derived from the stop name by removing vowels or compressing syllables)
* A 2-letter zone or bay code (ignore this; it is not needed)
* An optional "T" indicating terminus (ignore for naming purposes)
Your task is to infer the full station names from the 4-letter codes.
Your task is to infer the full stop names from the short codes.
Guidelines:
* Treat the 4-letter code as a compressed version of a real station name (e.g. consonant-heavy, missing vowels, or merged syllables)
* Use pattern recognition rather than strict decoding
* Prefer real-world plausibility over perfect letter matching
* Assume all stations are on the same rail corridor or geographically connected route
* Use the sequence of stops to inform your guesses (adjacent stations should make sense geographically)
* If a code is slightly irregular, prioritise what fits the route best over what matches the letters exactly
* Treat the code as a compressed version of a stop or locality name
* Use pattern recognition rather than strict letter matching
* Do not assume any specific country, region or city — infer purely from the codes and their sequence
* Use the sequence of stops to inform your guesses (adjacent stops should make sense as a connected route)
* If a code is ambiguous, prefer the interpretation that best fits the surrounding stops
Output:
Return JSON with shape {"aliases":[{"original":"<code>","estimated":"<name>"}]}.