fixup! Import A/B Street map data for ATIP route info. See acteng/ati…

…p#154

README.md

@@ -33,13 +33,14 @@ ATIP's route snapper tool loads a binary file per authority area.
 
 To regenerate them:
 
-1.  Install [pueue](https://github.com/Nukesor/pueue)
-2.  Set up the submodules in this repo: `git submodule init && git submodule update`
-3.  Complete the section above to split OSM files
-4.  Make sure the pueue daemon is started, and tasks cleared out. (`pueued -d; pueue status; pueue clean`
-5.  Run `./build_route_snappers.sh`
-6.  Wait for all pueue commands to succeed (`pueue status`)
-7.  Manually upload to S3, following instructions in that script
+1.  Make sure you have about 25GB of disk free
+2.  Install [pueue](https://github.com/Nukesor/pueue)
+3.  Set up the submodules in this repo: `git submodule init && git submodule update`
+4.  Complete the section above to split OSM files
+5.  Make sure the pueue daemon is started, and tasks cleared out. (`pueued -d; pueue status; pueue clean`)
+6.  Run `./build_route_snappers.sh`
+7.  Wait for all pueue commands to succeed (`pueue status`)
+8.  Manually upload to S3, following instructions in that script
 
 ## Route info
 

build_route_info.sh

@@ -22,5 +22,6 @@ done
 # Put in S3
 # prod: aws s3 sync --dry abstreet/data/system/zz/oneshot/maps/ s3://atip.uk/route-info/
 # dev: aws s3 sync --dry abstreet/data/system/zz/oneshot/maps/ s3://atip.uk/route-info-dev/
+# If the same files are going in dev and prod, this saves bandwidth: aws s3 sync --dry s3://atip.uk/route-info/ s3://atip.uk/route-info-dev/
 
 # Have to invalidate the CDN manually! Use the S3 console