-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Try the glossary for more information. For example here is some help on the downhillcost:
https://github.com/poutnikl/Brouter-profiles/wiki/Glossary#d
:)
> in a new location and I do not move much
I though about it some time ago - and main problem here is that StreetComplete would need to sit in background and keep downloading/processing data what is quite battery and CPU heavy.
Right now I see no good way to implement this. But maybe it should just query data in a very narrow area, like 20m?
Also, from looking at https://github.com/streetcomplete/StreetComplete/issues/48 one of arguments against it is that you will get some quests ANYWHERE.
Have you disabled many quests? Or maybe you are in rural area with lower number of objects? In cities you tend to have endless supply of objects to tag and quests to answer.
Do you have some code already working for the WASM part?
BRouter works by relying on segments (relevant extracts from the OSM data, in a custom format) of 5x5 latitude/longitude degrees. See https://github.com/abrensch/brouter/blob/f3895791766dfcd7cd0... for their creation (full doc https://github.com/abrensch/brouter/blob/1765ec45230e337319c...).
From my knowledge of the BRouter codebase and past contributions, it should not be a big deal to move from 5x5 to something more web tractable (as 1x1 latitude/longitude).