Map view mapping to different silos

[EnriqueCorado]

As a user I want to load my map based on the silo that I am in. Not always load the map ping static to the bay area as it currently stands

Description: center the map on SP and public view depending on the user's silo

Load map view based on silo e.g. bay area silo load bay area on map view (like it currently stands)

• marin silo, load marin map area on map view
• linkforcare load kansas map view

dev: please advice if you think another approach may be easier Possible solution:

SELECT percentile_cont(0.5) WITHIN GROUP (ORDER BY GR.latitude), percentile_cont(0.5) WITHIN GROUP (ORDER BY GR.longitude) FROM geocoding_result GR, location_geocoding_results LGR, location L, organization O, silo_organizations SO WHERE SO.silo_id = 'fa9b0a3c-c73a-41d6-818a-de26244b85da' and O.id = SO.organization_id and L.organization_id = O.id and LGR.location_id = L.id and LGR.geocoding_results_id = GR.id

another approach John - check out my percentile approach. If we try this we can kinda ignore specific silos entirely. I also dont know if google maps API has something similar of 'fitting' the view to the pins

• if you use the percentile approach it occurred to me that my SQL wouldn't include records created by ServiceProviders - so youll need to include those in addition to silo_organizations records

Question dev: if the above solution is the best solution do we load the map with center at x,y and radius of 20mi to encompass many CBO pings? or a greater number of miles?

Scope (includes UI mockups, user flow, and out of scope):

• how Kansas silo should look like

Acceptance criteria (includes edge cases):

• Now that we have different silos, there needs to be an efficient way to center the map from different silos appropriately in order to ensure and avoid user confusion as to where the map loads

Dependencies (links to other related tasks): *#1351 it was previously tasked to center map on san Francisco. However, this was before we had different active silos

Any required analytics for task: *

Dev Signoffs

• [x] Unit test added for the core business features at the minimum
• [x] Code review passed
• [x] CI passed successfully
• [x] CodeQL scan for vulnerabilities in code has passed
• [x] Docker images have been built and deployed to the dev server

QA Signoffs

• [x] Passes Acceptance Criteria
• [x] All bug reports fixed/merged/tested
• [x] Regression test cases cycle updated if needed

Product Signoff

• [x] Approved for release

[jkondrat]

@EnriqueCorado should we center the map on public view only, or would we do that depending on the user's silo too?

[EnriqueCorado]

@jkondrat

• do it for SP and public view depending on the users silo

[johnhbenetech]

@jkondrat check out my percentile approach. If we try this we can kinda ignore specific silos entirely.

I also dont know if google maps API has something similar of 'fitting' the view to the pins

[johnhbenetech]

also @jkondrat if you use the percentile approach it occurred to me that my SQL wouldn't include records created by ServiceProviders - so youll need to include those in addition to silo_organizations records

[jkondrat]

@johnhbenetech is it okay to initially get X closest records to this percentile point? I think we then could fit the map to these pins instead of centering it at that exact point.

[johnhbenetech]

@jkondrat yes thats fine

[abaranowska1]

@jkondrat During testing, I encountered an issue that after the second click "map view" button the user saw a different map, we were moved to the SanFrancisco view.

[abaranowska1]

Tested with success Now in different silos, the map is center appropriately in order to ensure and avoid user confusion as to where the map loads.