The range generation output creates two files with names ending in _post. In anticipation of the changes to support #152 where there will also be a router-specific street file, we should change the file names to better represent the product they support:
To support this, modifications will be required in the range builder and the geocoder. Also the FME summary scripts will need to be tweaked to point to the correct inputs.
The range generation output creates two files with names ending in _post. In anticipation of the changes to support #152 where there will also be a router-specific street file, we should change the file names to better represent the product they support:
site_Hybrid_post.csv -> site_Hybrid_geocoder.csv street_load_street_segments_post.json -> street_load_street_segments_geocoder.json
To support this, modifications will be required in the range builder and the geocoder. Also the FME summary scripts will need to be tweaked to point to the correct inputs.