Inspired by a post about car park identifiers, I started wondering if we could avoid two adjacent car parks having identifiers which could easily be mistaken for each other:
What are the best arrangements of all the decimal numbers of a certain length are there that have the property that for each number, a single replacement or adjacent transposition does not occur in the list within X numbers.
(for example: 142 should not be near 172 (single replacement) nor 124 (adjacent transposition))
(I'm pretty happy with alternatives that have other criteria for typo-resistance)
Prior art
Gray code has the nice property that every number shares all-but-one (binary) digits; this feels like the opposite property of what I want.