Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map - Tracking issue #3143

Open
8 of 13 tasks
jcfilben opened this issue Feb 9, 2023 · 8 comments
Open
8 of 13 tasks

Map - Tracking issue #3143

jcfilben opened this issue Feb 9, 2023 · 8 comments
Labels
BigThing:Map Owner:Development Used in issues that are being worked on/should be worked on by a developer. Platform Commitments Used in issues that are asks from Green Lake Platform.

Comments

@jcfilben
Copy link
Collaborator

jcfilben commented Feb 9, 2023

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:
Screen Shot 2023-02-09 at 12 14 02 PM

Main Jira ticket to track this: View Device / Asset View by Location on GLCP-42409

@ericsoderberghp ericsoderberghp added the Platform Commitments Used in issues that are asks from Green Lake Platform. label Mar 14, 2023
@SOjaHPE
Copy link
Collaborator

SOjaHPE commented Apr 10, 2023

Child Issues of #42409

  • Design System develop a map component for use by this and other future features GLCP-42657
  • Split the Epic into just adding location to the table, not the map GLCP-42711

Work with @gregfuruiye and @ecircenis to discuss their use cases

@halocline
Copy link
Collaborator

halocline commented Apr 17, 2023

Notes from Aruba (via Fred):

  • In networking

  • A need for maps, the way people manage their networks is by locations

    • Managing, universities, Home Depots - all stores
    • Locations could be multiple stores, on different floors in buildings
    • Admins, what to know, particular - visualize status of the system
      • How a particular site is doing. Aggregated view of your networks
      • Simple use case, not complicated
      • Able to search in the maps, particular location
      • Zoom in / out
      • Street / Satellite view / 3D views
        • 3D - access points with GPS coordinates
        • Anchor points in buildings, precisely locate assets in buildings
      • Want a clean, simple view of the map.. only important information
      • Need to see if a site is orange or red, can have readability issues for status to communicate w/ user w/o distractions for users
      • Satellite view is useful when users need it
      • Not necessary yet, to show the inside of the building
        • Floor view of the building, it is a 2D view - floor plan is flat
      • Color blindness, accessibility concerns
      • Different types of entities - branch, campus, main, data center - type of site you’re managing, all stores of big box retailer are considered branches.
      • A site will never be all red, all green, all yellow. Raise by exception
  • "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.

Image

Image

@halocline
Copy link
Collaborator

Resources from Winnie / Storage:

  • Figma file
  • Staging (might be slightly out of date, but the latest one we know of. There are some visual issues that haven’t been addressed yet.) link

@gregfuruiye
Copy link
Collaborator

gregfuruiye commented Apr 26, 2023 via email

@vavalos5
Copy link
Contributor

@gregfuruiye where can we find the CoM visualizations you mentioned?

@gregfuruiye
Copy link
Collaborator

@vavalos5 , all of the CoM map explorations are in the Positano Figma file. There are some here and here.

@vavalos5
Copy link
Contributor

Can we include GLC's Figma file here too please. @halocline @SOjaHPE

@halocline
Copy link
Collaborator

@halocline halocline changed the title Map visualization guidance Map - Track issue Jul 8, 2024
@halocline halocline changed the title Map - Track issue Map - Tracking issue Jul 8, 2024
@halocline halocline added Owner:Development Used in issues that are being worked on/should be worked on by a developer. BigThing:Map and removed 0 - office hours labels Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BigThing:Map Owner:Development Used in issues that are being worked on/should be worked on by a developer. Platform Commitments Used in issues that are asks from Green Lake Platform.
Projects
None yet
Development

No branches or pull requests

6 participants