Meeting on May the 8th 2024 at 09 am (rotating chair: Helsinki)

[VuokkoH]

Rotating chair: @VuokkoH from Helsinki, Finland
Attendees: @carlhiggs @dapugacheva @ryn-trnr @duelran
FYI: @gboeing @rychennn @shiqin-liu ; others?

GHSCI software/ spatial meeting May 8th (rotating chair: Helsinki)

First rotating timezone meeting (?): Let's continuing these rotating time zone meetings (and keep discussing how it works!)

Points about spatial team practices /mentoring

• Quick discussion on common practices
• - proposed approach/guidelines for resolving validation issues
• Contributing quidelines: do they need updating?
• Reminder: Preferably let's raise (and encourage others to raise) issues on github rathern than sending emails [to Carl :D]
• Applies also how we approach mentoring: rather than individual emails, would be good to refer to the Frequently asked questions (and update those when needed): (do they need updating + is this the right place for the FAQ?)

Sofware improvements:

• Carl demonstrated some improvements, great work!
  • getting example region; generating reports in different languages, simpler way to open jupyter lab..
  • GUI: seeing the region(s) on the map, summary view, indicator map (quick summary of different indicators)
• Open issues: 37 issues, maybe 20 already addressed :)
• Todo in the future:
  • making configuration easier
  • priority to implement new indicators into the process (Ryan's work)

Languages/Translations: 28 languages + English in the pipeline

• Some technical wrapping issues with character-based languages (such as Japanese)
• May 15th deadline for adding /revising launguages for the next release
• Finnish coming up soon, Russian potentially later

Green space validation

• OSM tags in different cities: see notes here (Ryan had tested the natural:wood tag in Helsinki; eventually no huge impact on accessibility % result, but important to have a valid green space extent for the credibility of the results)
• Next up: testing Mexico city
• SOlution: not to modify the original list of tags, but:
  1. allow exceptions (custom tag list) for spesific regions
  2. allow configuration of custom data (now possible for destinations, could expand this to polygon input)
  3. optional workflow to include google API key

-Youth mappers: continuing the conversations in July

• Jonathan will contact the Youth Mappers
• Vuokko keen to participate; combining the top-down (ornaizational) and bottom-up approach to engaging mappers
• Should find funding to support the work (to reach 1000 cities)

Other news:

• Relevant ongoing projects to be aware of:
  • https://github.com/goat-community/goat
  • https://www.helsinki.fi/en/researchgroups/digital-geography-lab/projects/greentravel
• Urban transitions workshop in November (!)

Next meetings:

• Wed(?) 5th of June (updated invite and agenda sent by Carl)
• Tuesday 2nd of July

[eugenrb]

Hello,

Thanks @VuokkoH for the notes! I tried to stay up and attend but I was not able to join.
@ryn-trnr let me know if you need/want to check-in with me re: green space validation testing for Mexico City.

[dapugacheva]

One more thing to bring up for the discussion:

@rychennn and I have been collecting data to run the full analysis for the Los Angeles Metro area (with the LA urban area boundaries we used for the green public spaces validation) on the enhancement branch. There are several issues with our machines' capacity to run the analysis for the entire area, and we are examining different options for how to execute the final analysis. As we are anticipating a new release mentioned in #400 by @carlhiggs, would it be a better idea to run this analysis for the LA Metro area after the new release? We welcome your thoughts.

[carlhiggs]

Hi @dapugacheva , if you're experiencing issues feel free to share in an issue and we can work through it. The enhancements branch will be the version merged into main, so should be no difference (and if there are issues that we can document/address, will be good in case helps others). I've taken sick leave today, but should be in a position to engage with things (including the translation aspects we discussed in the meeting) next week. Hope that's okay, Carl