Node hunter seems to roughly follow the area that I see on my screen. However it will often find many nodes “off screen”. It also not clear if areas have no nodes or were not searched.
I would like to have a “box” enabled that would show the area that was searched for nodes. This could be colored differently if it found all nodes in the area vs. when it cut off nodes.
A bonus would be to let me configure the area that is searched by drawing the box. This can let me more precisely identify the area.
Yup, it uses the bounding box of what’s visible in your browser.
Hmm, yeah, the bounding box that Mapbox is giving is slightly inset from what’s fully visible … then the nodes that the database returns seems to sometimes (specific cases, not intermittently on the same requests) include some outer buffer. It must be some internal workings of && in PostGIS.
There’s no scenario of an area not being searched. When you click the Node Hunter button, it makes the request for what’s in view.
An indicator for the question of “is the request complete” seems useful … The x button appears upon requesting the data - I’ll update that to appear upon receiving the response, and include that in the next release. This will help you know that when you see the x appear, that’s the complete collection of incomplete Nodes for incomplete Streets within the view of the browser.
It sounds like you might have chosen “Don’t alert me again” when you were prompted with the message:
There is a 1,000 Node limit. You may need to zoom in to see them all.
Perhaps that is now causing you confusion when you get incomplete Node display at certain views?
Maybe add an intermediary to show node hunter is currently working then? Like, you click node hunter, a spinning symbol pops out to show it is currently running, then the x appears when it is done? The delay isn’t very long, but I think the feedback that the button is doing something would be helpful.
There’s no scenario of an area not being searched. When you click the Node Hunter button, it makes the request for what’s in view.
The problem is that once I start panning and zooming, I don’t know what was in view at the time I used node hunter. A simple box showing “node hunter searched this area” would make it clear that I have drifted out of the node hunter range.
Hmm, yeah, the bounding box that Mapbox is giving is slightly inset from what’s fully visible … then the nodes that the database returns seems to sometimes (specific cases, not intermittently on the same requests) include some outer buffer. It must be some internal workings of && in PostGIS.
I’ve seen it significantly “off” on my phone. It will often leave off a bit at the top of the screen. Then it will grab a large number of nodes out of view from the left and right of the screen. It would be great to have an idea of what region it searched.
It sounds like you might have chosen “Don’t alert me again” when you were prompted with the message:
It would be great to have an option in CityStrides to re-enable the message. (I have gone through the process of re-enabling it before, and it was not fun.)
Thanks for adding this James, I spotted it on a run tonight and it’s definitely made it more clear when Node Hunter is in that state in between being clicked and showing the nodes.
Not sure how well known this is, but if you’re looking for nodes in a given city and it happens to be near the border, if you use Node Hunter in the City map view (rather than the main Life Map) Node Hunter will only show nodes that belong to the open city. Can be quite helpful when you’re trying to fill in edges without crossing over into the next city.