some notes about tiles
This commit is contained in:
parent
a8f100b528
commit
41e34b3654
41
README
41
README
@ -45,15 +45,8 @@ of the screen
|
||||
random notes follow ...
|
||||
|
||||
|
||||
|
||||
https://git.syndicate-lang.org/tonyg/squeak-phone/raw/commit/474960ddc665ed445a1f5afb0164fe39057720f9/devices/pine64-pinephone/modem-docs/80545ST10798A_LM940_QMI_Command_Reference_Guide_r3.pdf
|
||||
|
||||
|
||||
|
||||
1) [done] connect Satellite to qmi-nmea
|
||||
|
||||
https://codeberg.org/tpikonen/satellite/src/branch/main/satellite/nmeasource.py#L106
|
||||
|
||||
2) [nope] do we need modemmanager? might be required if we want lte data,
|
||||
but that's up to the "site admin" - we don't need it for biscuit itself
|
||||
|
||||
@ -88,14 +81,6 @@ elapsed time: what should it actually show? moving time, I guess
|
||||
|
||||
should we rename bearing as course in nmea?
|
||||
|
||||
rotating the map is going to be complicated because the widget we're
|
||||
using doesn't support it (bitmapped map tiles)
|
||||
|
||||
|
||||
|
||||
perhaps we need a server-side component for route planning
|
||||
|
||||
|
||||
7) think about how to use nfc tags or something for profiles so that
|
||||
it can recognise when it's attached to bicycle or motorbike
|
||||
|
||||
@ -127,10 +112,30 @@ the benefit of the caching. If we're going to do that, should it also
|
||||
do transformation e.g. from lat/long to x/y co-ordinates? We don't
|
||||
need this bit yet though
|
||||
|
||||
3) alternatively we could use mapbox vector tiles, but tbh I'm
|
||||
struggling to see now that helps. we don't have to transform from
|
||||
lat/long but instead we have to parse a protobuf, how is that simpler?
|
||||
|
||||
https://git.syndicate-lang.org/tonyg/squeak-phone/raw/commit/474960ddc665ed445a1f5afb0164fe39057720f9/devices/pine64-pinephone/modem-docs/80545ST10798A_LM940_QMI_Command_Reference_Guide_r3.pdf
|
||||
|
||||
----
|
||||
|
||||
... sod, forgot to push latest changes from noetbook
|
||||
|
||||
we need to extend to multiple tiles'-worth of map
|
||||
|
||||
* get tile for curent lat/long and request overpass data for enough
|
||||
surrounding tiles to fill the screen
|
||||
|
||||
* I think a way is served with all its nodes whether or not they're in
|
||||
the bbox, so we can just store the ids of ways we've seen and skip
|
||||
them if the come up again
|
||||
|
||||
* render all the polylines into the widget (some day also the labels etc)
|
||||
|
||||
* to get it centred on the cyclist, take the tile fractional part *
|
||||
256, and translate the canvas up and left by that amount
|
||||
|
||||
|
||||
|
||||
and offset
|
||||
by
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user