Repository navigation
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
|
@copilot this is covering up too many events. can we use the previous approach but reduce the radius so that separate buildings are not grouped together. it would be nice if grouping was recalculated on zoom |
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Updated in |
|
@copilot actually, I think clustering by venue was the correct approach. I think the geocoding script is not using the full address and venue name. In addition to the city. I think it's only using the city. So I would like you to fix the geocoding script and go back to grouping by venue |
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Updated in |
Summary
Some venue records contain only city-level coordinates, so separate markers can still overlap until their coordinates are corrected.
Validation
node --test 19hz/map.test.js 19hz/scripts/venues.test.jsnode --check 19hz/map.js