Roshini Seelamsetty : Fix Global Volunteer Network map Not Populating (Total Org Summary Dashboard)#5305
Open
roshini1212 wants to merge 3 commits into
Conversation
added 2 commits
May 23, 2026 21:43
…de) in Role Distribution Chart
…tion mapping issues
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…eer-Network-map-Not-Populating-(Total-Org-Summary-Dashboard)
|
DeepighaJ
approved these changes
May 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





Description
Related PRS (if any):
N/A
Main changes explained:
location._id.lat/lng
location.lat/lng
location.latitude/longitude
How to test:
npm start
Dashboard → Total Org Summary
“Global Volunteer Network: Uniting Communities Worldwide” map renders correctly
Screenshots or videos of changes:
Before:
Screen.Recording.2026-05-25.at.16.53.58.mov
After:
Screen.Recording.2026-05-25.at.16.54.51.mov
Note:
This was a frontend rendering and data normalization issue. Backend location data was already being returned successfully, but the frontend component did not safely handle inconsistent coordinate schemas or undefined location values.