We currently have console warnings in the script for things like missing lat/lng, missing stname, etc.
If a record has no lat/lng, it does not belong in the geocoder, and should be excluded from the output.
The end state we shoot for is a 1 to 1 match for records in the normalized pad CSV and records in the elasticsearch database. This will be helpful in troubleshooting the imports.
@chriswhong commented on Wed Jan 24 2018
We currently have console warnings in the script for things like missing lat/lng, missing stname, etc.
If a record has no lat/lng, it does not belong in the geocoder, and should be excluded from the output.
The end state we shoot for is a 1 to 1 match for records in the normalized pad CSV and records in the elasticsearch database. This will be helpful in troubleshooting the imports.