commit 3d4dc2902e0b3e7b780e7d1d742ca6051ecf995d
parent ab72373489980065be50b58c0e2157279d23684d
Author: Beau <cbeauhilton@gmail.com>
Date: Mon, 27 Sep 2021 19:43:07 -0500
formatting
Diffstat:
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/posts/geocheatcode.md b/posts/geocheatcode.md
@@ -163,17 +163,22 @@ and search through the response for the part I want to extract.
Then I use a little standard Python
to parse the extracted part and save the important bits.
-PSA: don't go crazy with this.
+## With great power...
+
+Don't go crazy with this.
+
+The trick is good for
+leisurely automation
+of location retrieval
+when you have squirrelly queries.
+
If you need real-time mapping of many things,
you don't want this solution.
Use the actual APIs,
and work instead on formatting the queries properly
before sending them to Google/OSM.
-This trick is good for going leisurely,
-but automatically,
-through a pre-made list of things.
-Also, if you try to map too many things too quickly,
+Also, if you try to query too much/too quickly,
Google will shut you out after a little while.
Put a few seconds of delay between each request
and run it overnight and/or in automated batches.
