Error handling summary

Updated Jul 16, 2026

API consumers should handle the following error types surfaced by the library:

  • WeightError: returned by InterestProfile::try_set_weight when weights are out of range or non-finite.[^14]
  • SolveError: produced by solvers when requests violate invariants or when a backend is not yet implemented.[^15]
  • TravelTimeError: emitted by travel-time providers for invalid input such as empty POI slices.[^16]
  • SqlitePoiStoreError: covers storage and validation failures encountered when opening SQLite-backed stores.[^17]