Open jcfilben opened 1 year ago
Child Issues of #42409
Work with @gregfuruiye and @ecircenis to discuss their use cases
Notes from Aruba (via Fred):
In networking
A need for maps, the way people manage their networks is by locations
"Locations" are down to GPS coordinates (e.g. coordinates within a building and even across floors in the building --> not just lat, lng, but also a z coordinate)
The “proportional status” concept needs work — I would think that we should still be able to distill the proportion into a single status indicator and not have to make the user do analysis within the map.
Reset view control
Positioning of controls (e.g. layered atop the map or live outside?) — my thinking has been that any data collection views should be able to be substituted for one another. I can represent a data collection as a table, list, grid, or map and have similar controls for each — even let the user choose their preferred method (Fred mentioned the flexibility for users being able to choose their preferred method).
Connecting nodes (e.g. directionality of networks between sites) was a use case I hadn’t yet considered.
Site type seemed to be more important than number of devices — that’s a bit different than what I have seen from Private Cloud Enterprise or Compute Ops Manager.
Where to show site/location detail? How much lifting does the map do vs. serving as a hub that routes to spokes?
Map can serve as a filter itself (e.g. as I zoom in/out, the locations in my current view are what is shown in my data collection)
A bit unclear as to what degree they were heading from the 3D aspect. I got mixed messages between desire vs. feasibility.
Resources from Winnie / Storage:
Matt, Do you have the visualizations from early CoM that we did?
Greg Furuiye Designer HPE Experience Studio Hewlett Packard Enterprise
From: Matthew Glissmann @.> Date: Wednesday, April 26, 2023 at 2:33 PM To: grommet/hpe-design-system @.> Cc: Furuiye, Greg @.>, Mention @.> Subject: Re: [grommet/hpe-design-system] Map visualization guidance (Issue #3143)
Resources from Winnie / Storage:
— Reply to this email directly, view it on GitHubhttps://github.com/grommet/hpe-design-system/issues/3143#issuecomment-1524010228, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEIPRKZVP4VAZXP3C3ABBDDXDGBALANCNFSM6AAAAAAUW54UOI. You are receiving this because you were mentioned.Message ID: @.***>
@gregfuruiye where can we find the CoM visualizations you mentioned?
Can we include GLC's Figma file here too please. @halocline @SOjaHPE
Can we include GLC's Figma file here too please. @halocline @SOjaHPE
Tracking issue for:
Background
Brought up by Greg in office hours 2/9/23:
There is a need to show the physical location of devices on a map. We don't have a way of doing this in Grommet and should provide a recommendation for a tool that should be used as well as how it should be styled.
Edgar also mentioned a need for this. For his use case he needed to be able to show a detailed map down to street addresses. Both Greg and Edgar mentioned having this ready to show at discover.
When you zoom out locations in close proximity should be grouped.
Some tools mentioned: Open Maps, Google Maps API
Sam Goff mentioned he has done a lot of work with google maps api and would be willing to collaborate. Chris Carlozzi mentioned that there are security issues with using Google Maps.
Screenshot shared by Greg of what they currently have implemented:
Main Jira ticket to track this: View Device / Asset View by Location on GLCP-42409