Meeting on 2024-03-06 at 09:00 PST

[ruoyuch]

Rotating Chair: Geoff Boeing from Los Angeles

Attendees: @gboeing @shiqin-liu @dapugacheva @ruoyuch

USC Team Updates:

• Seattle test completed, previous crash attributed to insufficient docker memory.
• Working on improving docker accessibility by removing the authentication process.
• The next focus is on the green space indicator, addressing issues with the local boundary of LA intersecting with the global human settlement layer.
• Facing merge conflicts on GitHub and resolved.

UMN Team Updates:

• Engaged in green space validation work, highlighting the need to refine the definition of green space.
• Example: In Minneapolis, there is a long parkway with some vegetation, trees, and green pavement in the middle, which is not very accessible as green space by pedestrians, things we might want to pay attention to when defining the green space.

Updates from Emails:

• Geoff went through the email threads sent by @carlhiggs and @VuokkoH
• Carl provided software development updates and aims for a deadline by the end of April.
• Vuokko raised the missing data issue and recommended loading another non-OSM dataset to complement the OSM source green space data.

Future works:

• Aim for the end of April to fold up software improvement works
• Work on the green space validation tasks

[shiqin-liu]

Thanks for notes! Just to clarify a bit, the case I have seen in the greenspace validation in Minneapolis is a long parkway with some vegetation, trees and green pavement in the middle, which is not very accessible as green space by pedestrains, things we we might want to pay attention to when defining the green space; I will add this to the spreadsheet discussion

[ruoyuch]

Thanks for the clarification. I edited the corresponding texts in the notes. Thanks.

[carlhiggs]

Thanks @rychennn for the notes, and all for carrying on the meeting!

Regarding the Docker memory issue, this has come up a few times with people running larger study regions. We should add advice about this to an entry in the FAQ, drawing on the solutions covered in the Github issue related to this (#366). I just created an issue to remind us to do this for the upcoming update (#405).

Regarding improving docker accessibility by removing the authentication process, is this more to do with launching Jupyter Lab with more user friendly guidance (ie. as per @dapugacheva proposed update #399 ), or is this a seperate issue with Docker? If its a different thing, I'd love to know more about it.

Re: the Minneapolis public green space identification (which @ryn-trnr will be interested in), if modification and/or customisation of open street map tags for identifying what is public or open space is required lets discuss this. I believe @VuokkoH had suggestions related to this for the Finnish context, and I suggested in an e-mail we could look to either modifying the overall tags used to identify open space (if we felt that would be universally applicable) or adding optional customisation of this within region configuration files. If this is something that would be useful, let's discuss further.

[ryn-trnr]

Thank you for the Minneapolis feedback @shiqin-liu

@carlhiggs I agree, having a discussion about either modifying OSM tags for universal application or introducing optional customisation within region config files would help move things forward. This is something @VuokkoH has also raised as important.

[dapugacheva]

@carlhiggs Yes, 'Working on improving docker accessibility by removing the authentication process' point was about #399 proposal.