Developing a entry point/index for OSM Analytics projects

[brendangatens]

Goal of the idea
Create a site that serves as an entry point to OSM analytics tools from various organizations.

Initial proposal
List of tools

Initial proposed direction

Considering the intial list of tools has grown, could we give primary treatment (called Core analytics tools below) to the most relevant tools, and give secondary treatment to all other tools?

There has been some discussion on categorizing or tagging tools based on purpose, action, and organization. We discussed having more granular filters on a Tools page.

We're also looking at ways to highlight the organizations and individuals who are contributing to these tools, while finding ways to better call out information on how people (developers) can become contributors, and point out / link to contribution details for individual tools.

Homepage

Menu

Tools page

[awright]

@brendangatens I think we should/could do an "above the fold" grouping of Core Projects and then Additional Work following, as second priority. This is exactly how you have it organized here and I wouldn't second guess it?

For this initial MVP, I would put the tools marked as HIGH priority in the OSMA Ecosystem spreadsheet as are the core projects.

RE: tagging -- next week @cgiovando and I will put together a series of themes. The way I was imaging it, all projects -- core or not -- would have a tag(s). I was thinking of a lot of blog formats, including the Medium screenshot below.

I would like to see a little less real estate to these themes below the core projects (perhaps shorten the height here) and add a section about supporting the work. There are 2 key pieces to that support/involvement-- 1) "join the community" as a developer and/or users and 2) contribute money.

The first could have a link to the slack channel and a general GitHub and contact email the latter a (perhaps) an email address to keep in touch. I see this as really critical to the ongoing development of these projects. They are sustained by us, but also the community in more ways than one.

In the initial Language Document I wrote this to support the work. I would recommend we work on this language but it's general point is still valid:

Roadmap
All are non-commercial and open software project, and as such there is no formal list of feature requirements required for development. Features and development the Suite team have discussed include…. Etc.
Support the Work
The future direction of OSMA is shaped by the constant flow of code contributions and funding directed towards the implementation of new features.

Like OpenStreetMap which it rests upon, OSMA is constantly evolving. It is a community effort built with the commitment of various OpenStreetMap contributors and organizations, the latter including the Humanitarian OpenStreetMap Team which serves as a coordinating actor in this work. A full list of supporting organizations can be found below. OSMA was not done alone.

If you are interested in supporting the ongoing development of the OSMA Suite of tools including development of the roadmap, please reach out to us directly. .

Note: this was inspired by other OS projects, including PostGIS.

MEDIUM BLOG TAGGING below

Hope this is helpful.

[willemarcel]

Proposal of data store architecture:

• A YAML file to store the analytic tools
• Another YAML to the OSM tools

The YAML would look like this:

projects:
    - name: OpenCities
      url: http://opencities.org
      github: http://github.com/opencities/opencities
      image: images/cities.jpg
      description: |
        Open data today to build resilient and sustainable societies tomorrow. 
      categories:
        - mobility
        - environment
      owners:
        - HOT
        - Someone else
    - name: OSM Analytics for Health
      url: http://osma.hotosm.org
      github: https://github.com/hotosm/osma-health
      description: |
        Extension of OSM Analytics for health campaigns.
      categories:
        - health
      owners:
        - HOT
        - Someone else

Software stack proposal:

• React
• Assembly (CSS Framework)