From 63a22d8618d2c5377d9fd2d26d26045fb6547866 Mon Sep 17 00:00:00 2001 From: John Wiseman Date: Sat, 14 Dec 2019 17:16:44 -0800 Subject: [PATCH] Fixed units. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 9e0632b..865da03 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ The bot will consider an aircraft to be "circling" if: degrees in one direction. 2. The centroid of the last 3 minutes worth of positions must be more - than 2.5 miles away from all known airports. + than 2.5 km away from all known airports. 3. The centroid must be located within the county of Los Angeles. (This is just because I don't yet have airport data outside Los @@ -34,9 +34,9 @@ The bot will consider an aircraft to be "circling" if: 4. The aircraft must, at the moment of decision, be at an altitude of 300 feet or more. -5. If an aircraft was previously circling, it must be considered - not-circling for at least 30 minutes before it is again eligible to - be considered circling. +5. Once an aircraft is considered to be circling, it will be tweeted + about. It won't be eligible to be considered circling/tweeted about + again until it stops circling and 30 minutes pass. There are a lot of weird flight paths that can meet criterion #1, and I kind of like it that way. For example, see