Plots2: [Planning] Geographic Features Refinement

[daemon1024]

• Standardize Adding New Spreadsheet-based layers https://github.com/publiclab/leaflet-environmental-layers/issues/488
  
  
  
  • Add widget on the PL website
  
  
  • Set up script(s) to generate content for new layers https://github.com/publiclab/leaflet-environmental-layers/issues/528
  
  
  • Integrate the widget and script through API calls and GH Actions
  
  
• Increase Amount of Content on /map
  
  
  
  • Develop microservice over the current API
    
    
    
    
    
    • TBD
    
    
    
  
  
  • Benchmark and Investigate the current People API https://github.com/publiclab/plots2/issues/7556
  
  

Succeeds https://github.com/publiclab/plots2/issues/1416

Should we keep the tasks to the existing milestone i.e. https://github.com/publiclab/plots2/milestone/7 or create a separate milestone for the soc project?

This is currently broad planning points for the project. I will be detailing out, break it further, adding more relevant tasks.

[ebarry]

Let's keep this milestone, I"ll update it with this planning issue. Thanks!

[daemon1024]

https://github.com/publiclab/leaflet-environmental-layers/issues/121 I was wondering if spinning it out the component as Leaflet Plugin, would ease out our scripts and workflow.

What are your thoughts about this @jywarren ?

[daemon1024]

https://github.com/publiclab/leaflet-environmental-layers/issues/480 Bumping this issue and planning to add to tasklist.

Have we consider adding a guide/docs which doesn't require people to download/install things? Using CDNs like jsdelivr or unpkg. This would ease out for someone who is wanting to try it out without needing to externally add anything.

[jywarren]

publiclab/leaflet-environmental-layers#121 I was wondering if spinning it out the component as Leaflet Plugin, would ease out our scripts and workflow.

What are your thoughts about this @jywarren ?

I like this idea a lot! It'd be a nice output of the fellowship too!

[jywarren]

Have we consider adding a guide/docs which doesn't require people to download/install things? Using CDNs like jsdelivr or unpkg. This would ease out for someone who is wanting to try it out without needing to externally add anything.

This sounds cool -- sure!

One thing perhaps in terms of prioritization is that the current map at https://publiclab.org/map is really not as useful as we'd hope it to be. I wonder if it's worth a brainstorm of ideas for how to make the experience better. Some ideas that occur to me:

1. progressively load more content as you zoom/pan (or tune the progressive loading that does happen)
2. refine the explanations of layers that appear. Many are still unclear in that it's not very legible where the data comes from, how "reliable" it is, etc.

What other ideas might we come up with?

[ebarry]

Great ideas here! These seem like ideal goals for the Fellowship on Geographic Features. +1!

It has occurred to me that in the future we could think about:

• For people who are logged in, but who haven't added their location, we might show an "add your (blurred) location" prompt ? This or something similar might help explain why the map loads on 0,0?
• For people who are not logged in, might our website "request your location" and use that to move the map to where people are?

also for later -- cartography. The fun stuff :)

[jywarren]

For people who are logged in, but who haven't added their location, we might show an "add your (blurred) location" prompt ? This or something similar might help explain why the map loads on 0,0?

This prompt would be on the /map page itself? If so, it could mirror the logic and style of the button we show on the dashboard, which shows "Add your location" if you haven't yet. I like this!

For people who are not logged in, might our website "request your location" and use that to move the map to where people are?

I think we could, but we often request location as part of the blurred location popup itself, when we do so to save that location to ones' profile. So we would have to think about whether it's redundant to ask here, or if we can clearly and simply describe how this "request your location" prompt is not /saving/ the location, but merely /displaying/ it for you, and so, relatively, preserving your privacy? Or is that distinction not really worth trying to explain vs. just getting people to input their blurred location -- does it present too much possible confusion?

Thanks! Good ideas, happy to dig into them further as well!

[jywarren]

Also noting this issue affecting display of people! https://github.com/publiclab/leaflet-blurred-location-display/pull/123