Repository navigation
Make crossing comparisons shareable and measurable - #102
Merged
Merged
Conversation
This was referenced Sep 30, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Make the San Ysidro–Otay Mesa comparison easier to share with border-crossing friends and learn whether it helps someone choose a crossing.
Change
This uses the current hosting and analytics stack. It adds no account, database, paid API, or recurring service. It does not change the free waits or Adsterra behavior.
Evidence and interpretation
The current Umami readout showed two
compare-openevents in the last seven days. That is too little to judge the new comparison.compare-feedbackis a stated opinion, not proof of an actual crossing or a paid business need. Review results after a friend pilot and the existing 30-day window.Review status
Static diff and whitespace inspection completed. Automated test suites were not run in this task; GitHub checks may run on the PR. Production remains on the existing GitHub Pages deployment pending owner review.
Related: #101