Google Earth Pro: KML/KMZ organization per project · measure/paths for spacing checks · historical imagery (before/after!) · Street View desk-review workflow (SPM Plan Review Checklist pass 1) · export map figures at consistent scale. QGIS/ArcGIS: load FDOT open data + county parcels/centerlines · buffer/select for study areas (crash polygons, school proximity — your MDCPS-buffer workflow generalizes) · GeoJSON/shapefile hygiene · ArcGIS REST query patterns you already run (FeatureServer → JSON → pandas) belong in code-script notes. Products to standardize: study area map · crash location map · parking inventory map · comp-site location exhibits — one style, reused. Sources: MOC - Data Sources rows for FDOT GIS, county portals, OSM/Overpass (with the OSM caveat: community data — verify before it drives a conclusion).