Change Neighbor list to use advert location rather than query by query #59

New Issue

2026-10-05T01:55:34+02:00

adam commented

2026-10-05 01:55:34 +02:00

The Lat/Long query the neighbors query uses are done separately. I don't know why but sometimes one of the two (lat/long) fail.

Can we instead just use the advert location which should already be stored in the db to render the neighbors map instead and not have multiple queries?

The Lat/Long query the neighbors query uses are done separately. I don't know why but sometimes one of the two (lat/long) fail. Can we instead just use the advert location which should already be stored in the db to render the neighbors map instead and not have multiple queries? <img width="855" height="858" alt="Image" src="https://github.com/user-attachments/assets/ec598186-2e7e-43f5-b488-d56bb96a9364" />

adam closed this issue

2026-10-05 01:55:34 +02:00

adam commented

2026-10-05 01:55:34 +02:00

Hm, I had already implemented this; if we have the complete lat long available from an earlier query we will use it but otherwise we will fall back to using the known node location. Are you not seeing that behavior on latest?

Hm, I had already implemented this; if we have the complete lat long available from an earlier query we will use it but otherwise we will fall back to using the known node location. Are you not seeing that behavior on latest?

adam commented

2026-10-05 01:55:35 +02:00

I hadn't realized. I wrote this out this morning before I did a pull. It does appear current is fetching neighbor data without pulling node info now if the contact has a location.

I hadn't realized. I wrote this out this morning before I did a pull. It does appear current is fetching neighbor data without pulling node info now if the contact has a location.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#59