fz0x1/HPI
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

location: make accuracy default config floats

Browse source 
previously they were ints which could possibly
break caching with cachew
This commit is contained in:
Sean Breckenridge 2023-09-30 14:23:56 -07:00 • committed by karlicoss
parent 8addd2d58a
commit f3507613f0
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
my/location/fallback/via_home.py
View file

@ -25,7 +25,7 @@ class Config(user_config):
# default ~30km accuracy # default ~30km accuracy
# this is called 'home_accuracy' since it lives on the base location.config object, # this is called 'home_accuracy' since it lives on the base location.config object,
# to differentiate it from accuracy for other providers # to differentiate it from accuracy for other providers
home_accuracy: float = 30_000 home_accuracy: float = 30_000.0
# TODO could make current Optional and somehow determine from system settings? # TODO could make current Optional and somehow determine from system settings?
@property @property

2
my/location/google_takeout_semantic.py
View file

@ -28,7 +28,7 @@ class semantic_locations_config(user_config.google_takeout_semantic):
# https://locationhistoryformat.com/reference/semantic/#/$defs/placeVisit/properties/locationConfidence # https://locationhistoryformat.com/reference/semantic/#/$defs/placeVisit/properties/locationConfidence
require_confidence: int = 40 require_confidence: int = 40
# default accuracy for semantic locations # default accuracy for semantic locations
accuracy: float = 100 accuracy: float = 100.0
config = make_config(semantic_locations_config) config = make_config(semantic_locations_config)