Plan for future versions of OSMLR data and geometry tiles
In the future, as OSM / Valhalla segments change, their geometry will become out of sync with OSMLR ids, and may have implications for how OSMLR data is tied to the geometry. How will the client deal with this mismatch? (To be answered in the future.)
Related: https://github.com/opentraffic/osmlr/issues/34
At present, Analyst UI displays the GeoJSON tiles that are created with each OSMLR PBF cut (~quarterly), posted to https://osmlr-tiles.s3.amazonaws.com/listing.html
An option in the future will be to instead display the OSMLR GeoJSON tiles that are now being generated with each Valhalla associate segments run (weekly), posted to https://reporter-tiles.s3.amazonaws.com/