Should we change Australia to Oceania?
This will be more welcoming for Fiji, New Zealand, Papua New Guinea etc.

Also our regional SotM is going by this name.

In the build script we should validate that

• event date should be parsable by new Date()

Each resource has a "type" property..

{
    "type": "Feature",
    "properties": {
        "id": "OSM-US-Slack",
        "type": "slack",
        "country_code": "US",
        "name": "OpenStreetMap US Slack",
        "description": "Sign up at {url}",
        "url": "https://osmus-slack.herokuapp.com/"
    },
    "geometry": { 
        ...
    }

I left this a free-text property. But we might want to have a list of acceptable types.

Community Resource Name

What is it?

URL link to the resource

Points of contact

Bounding polygon

Description (optional)

Languages spoken (optional)

Country codes (optional)

Add an emoji flag (optional)

OpenStreetMap Chile Lista de Correos

mailinglist

https://lists.openstreetmap.org/listinfo/talk-cl

Julio Costa, [email protected]

chile

Suscríbete a nuestra lista de correos: https://lists.openstreetmap.org/listinfo/talk-cl

es

cl

🇨🇱

I'm going to switch this repo over to how we do things in the iD project, where we separate master branch without built files, and a release branch that has the built files (and where we do git tag and npm publish).

We have two main points of entry:

• Forum: https://forum.openstreetmap.org/viewforum.php?id=21
• Telegram: https://t.me/ruosm

And a few secondary channels: IRC, Vkontakte, OSM Diaries.

(I'd add these myself, but I have no idea how this repository is structured and what is needed)

Trying to understand the scope. Everyone using OSM is a 'local' user. Is this supposed to explicitly exclude "global" resources like the OSM wiki, global mailing lists etc?

Happy to work on the README as this becomes clearer to me.

From #16 (comment)
Several lists already exist, we just need to copy them over and add bounding polygons.

https://github.com/osmus/local-wg
https://github.com/osmlab/localgroups

I just saved a changeset in the middle of Chile (well inside Chiles geojson polygon) and iD only shows me the international Reddit

Following up from #1 (comment)
I'm going to add a nice icon for each of the resource types we support, and drop them into dist somehow automatically.

The build script does some automatic processing of the geojson files already to:

• enforce right-hand winding order
• prettify the output

We should also drop the double precision coordinates within the files to make them smaller. 5 decimal places equals about 1 meter resolution at the equator, and is good enough for the purposes of this index.

Most of the files are already pretty small, but this could help shrink germany.geojson and belgium.geojson a lot more.

From https://github.com/osmlab/osm-community-index/blob/master/CONTRIBUTING.md :

All community resources automatically support localization of the name, description, and extendedDescription text. These fields should be written in US English.

Please push only global ressources to transifex to translate to all languages.
Other resources should not be pushed to transifex but translated by the local community.
It is not helpfull to translate community contact information to languages not spoken by the local community. I try to keep the German iD-Translation up to date and i would prefer to see "0 strings to translate" even if strings like "OSM Chattanooga" (Tennesee, less then 200k people) is not translated.

I've decided to automatically prettify all source JSON files on every build.
It makes them easier to look at and scroll through quickly.

I'm using json-stringify-pretty-compact which works great for geojson.

Community Resource Name

OsmCanada

What is it?

Slack,
Website,
Tasking Manager

URL link to the resource

Slack url: osm-ca.slack.com
Self-invite: https://slackinviteosmcanada.herokuapp.com/
Website: https://www.osmcanada.ca/
Tasking Manager: http://tasks.osmcanada.ca/

Points of contact

LogicalViolinist (osm)

Bounding polygon

Canada

Description (optional)

Slack channel

Languages spoken (optional)

EN and FR

Country codes (optional)

ca

Add an emoji flag (optional)

🇨🇦

https://github.com/osmlab/osm-community-index/blob/master/sources/north-america/us/OSM-US-Slack.geojson covers the contiguous 48 states but not Alaska and Hawaii.

Does anyone have any serious objections if I replace the (very few) Javascript scripts in this repository with Python? It would make things so much easier with testing, publishing, dependency management, etc?

Python ate the osm world already, lets just use it. This whole repo is JSON files anyway.

(See also: osmlab/editor-layer-index#168) 😜

Community Resource Name

"OpenStreetMap Bolivia"

What is it?

"mailing list"

URL link to the resource

Mailing list: https://lists.openstreetmap.org/pipermail/talk-bo

Points of contact

name: "Marco Antonio", email: "[email protected]"

Bounding polygon

relation: https://www.openstreetmap.org/relation/252645

Description (optional)

description: "Talk-bo is the official mailing list for the Bolivian OpenStreetMap community"

extendedDescription: 'Mapping in Bolivia? Have questions, want to connect with the community here? Join us at {Url}. All are welcome!'

Languages spoken (optional)

"es"

Country codes (optional)

"bo"

OpenStreetMap Chile Telegram

telegram

https://t.me/OSMcl

Julio Costa, [email protected]

chile

Unete a nuestro grupo en: https://t.me/OSMcl

es

cl

🇨🇱

An example motivation would be https://www.reddit.com/r/openstreetmap/ which is relatively global but overwhelmingly uses English.

OpenStreetMap Chile

Description in spanish for the current four channels (Facebook, Mailing List, Telegram and Twitter in that order)

"description": "Únete a la comunidad de OpenStreetMap Chile en Facebook",
"extendedDescription": "Únete a la comunidad para aprender más sobre OpenStreetMap, realizar preguntas o participar en nuestras reuniones ¡Todos son bienvenidos!",

"description": "Una lista de correos para discutir sobre OpenStreetMap en Chile"

"description": "Únete a la comunidad de OpenStreetMap Chile en Telegram",
"extendedDescription": "Únete a la comunidad para aprender más sobre OpenStreetMap, hacer preguntas o participar en nuestras reuniones ¡Todos son bienvenidos!"

"description": "Síguenos en Twitter en {url}"

cl

Reference contacts: http://telegra.ph/OpenStreetMap-LoCo-channels-in-the-Philippines-02-15

cc @seav @gowin

Community Resource Name

What is it?

URL link to the resource

Points of contact

Bounding polygon

Description (optional)

Languages spoken (optional)

Country codes (optional)

Add an emoji flag (optional)

OpenStreetMap-Vancouver Meetup

What is it?

meetup

URL link to the resource

https://www.meetup.com/OpenStreetMap-Vancouver/

Points of contact

REMOVE FOR PRIVACY

Bounding polygon

Description (optional)

Languages spoken (optional)

Country codes (optional)

ca

Add an emoji flag (optional)

🇨🇦

Community Resource Name

OSM Colombia

URL link to the resource

Twitter: https://twitter.com/OpenStreetMapCo
Blog: https://blog.openstreetmap.co/s657
Mailing list: https://lists.openstreetmap.org/pipermail/talk-co/
Facebook: https://www.facebook.com/groups/OsmCol/about/
Bogota meetup: https://www.meetup.com/Maptime-Colombia-OSM/

Country codes (optional)

"co"

Add an emoji flag (optional)

🇨🇴

Because testing is nice.

See wiki page: https://wiki.openstreetmap.org/wiki/User:UserGroupsBot

A bot automatically creates a kml resource based on User Groups maintained on the Wiki. Essentially this means that everyone is free to add local user group meetings in the Wiki without creating some pull request here.

Results are shown e.g. on different specialized maps, such as https://www.openstreetmap.de/karte.html, see the small icons on the "Lokale Gruppen" (local group) overlay.

Edit: ah, something similar was already discussed before in another repo: osmlab/osm-planning#5 (comment). Everyone maintaining their own list is probably creating extra effort, so leveraging what is already available as much as possible would be a plus.

BTW: https://xkcd.com/927/ anyone? 😎

OSM has a Calendar page to cover community events.

How about a separate section for events, parsed from the OSM events calendar, instead of making it part of resources?

Some groups will have events (like local State of the Map conference, meetups, etc).
Should we add an upcoming events data to this index so that tools like iD can show the user when the group's next event will be?

Kind of similar to how editor-layer-index has a basic live preview - this index should have a map too.

GeoJSON already has a Feature-level field called "id" that we can use rather than adding a property that does the same thing.

If a Feature has a commonly used identifier, that identifier SHOULD be included as a member of the Feature object with the name "id", and the value of this member is either a JSON string or number.

Community Resource Name

OpenStreetMap Sweden

What is it?

• Homepage
• Mail list
• IRC
• Taginfo
• Task manager
• Facebook
• Twitter

URL link to the resource

URL links to the resources

• OSM SE: http://openstreetmap.se/
• Talk SE: https://lists.openstreetmap.org/listinfo/talk-se
• IRC: #osm.se
• Taginfo SE: http://sweden.taginfo.openstreetmap.se/
• OSM Tasking manager SE: http://tasks2.openstreetmap.se/
• Facebook: https://www.facebook.com/groups/osmsweden/
• Twitter: https://twitter.com/openstreetmapse

Points of contact

@magol

Bounding polygon

https://gist.github.com/magol/3fea83f0ae940a6069c442f10206e50e

Description (optional)

Languages spoken (optional)

sv

Country codes (optional)

se

Add an emoji flag (optional)

🇸🇪

Here are contact points for Japanese Community.

• talk-ja: https://lists.openstreetmap.org/listinfo/talk-ja
• Twitter: #osmjp
• Facebook: https://www.facebook.com/groups/osmjapan/

Community Resource Name

"OpenStreetMap Austria Forum"

What is it?

Its a Forum

URL link to the resource

https://forum.openstreetmap.org/viewforum.php?id=89

Points of contact

emga, [email protected]

Bounding polygon

Description (optional)

Das offizielle Forum zu OpenstreetMap Fragen rund um und in Österreich
The official forum to OPenstreetMap questions in and around Austria

Languages spoken (optional)

en, de

Country codes (optional)

AT

Add an emoji flag (optional)

🇦🇹

Community Resource Name

Openstreetmap Peru

What is it?

• Homepage
• Mail list
• Matrix
• Telegram
• Twitter
• Facebook

URL link to the resource

URL links to the resources

• Homepage OSMPE: http://osmpe.ourproject.org/
• Mail list OSMPE: http://lists.openstreetmap.org/listinfo/talk-pe
• Matrix: https://matrix.to/#/#osmpe:matrix.org
• Telegram: https://telegram.me/osmPe
• Twitter: https://twitter.com/osmpe
• Facebook: https://www.facebook.com/Osmpe

Points of contact

@osm-pe Team on GIthub
https://wiki.openstreetmap.org/wiki/ES:Per%C3%BA OSM Wiki

Bounding polygon

• Relation: https://www.openstreetmap.org/relation/288247
• Geojson file: https://gist.github.com/sguinetti/d80c5396b0d8efd22be69e768806a6e7

Description (optional)

Languages spoken (optional)

"es"

Country codes (optional)

"pe"

Add an emoji flag (optional)

🇵🇪

The example community resource has this:

{
  "id": "OSM-US-Slack",
  "name": "OpenStreetMap US Slack",
  "description": "Sign up at {url}",
  "url": "https://osmus-slack.herokuapp.com/",
  ...
}

That description is not great. It's really just a placeholder.
Using my iD mockup below for inspiration - what kinds of things do we want to include in a description?

• How long is reasonable? A few lines?
• Formatting? We could do markdown, but I'd rather not.
• I put that {url} token in there, thinking we might replace it with the real url, but then we also need url text. Thinking about it more, I'd prefer not to do token replacements unless we have a compelling reason.
• That url link goes to the auto-inviter, not to the actual url which is https://osmus.slack.com - is that weird? (maybe need separate signup and visit links?)
• Should we add another field for a more extended description, maybe more suited for an expandable block of text, like these "details" things:
  lots of good stuff in here

OpenStreetMap Chile Twitter

twitter

https://twitter.com/osmCL

Julio Costa, [email protected]

chile

Description (optional)

es

cl

🇨🇱

After my change I got

/r/openstreetmap/ is a great place to learn more about OpenStreetMap. Ask us anything!

message. I think that "/r/openstreetmap/" should be a link leading to this community

From the comment #63 (comment) it sounds like having the extra metadata will show the actual meetup events.

Looking at the Meetup API https://www.meetup.com/meetup_api/docs/find/upcoming_events/ it seems like that meeting info could be periodically scraped. EX: https://api.meetup.com/open-cleveland/events?&sign=true&photo-host=public&page=5&status=upcoming

You might be able to use the Travis CI cron jobs to do this periodically https://docs.travis-ci.com/user/cron-jobs/

We should add a contacts array to each source to track who the points of contact are for each resource..

It could work kind of like the package.json "contributors" property

contacts: [
  { 
    "name" : "Barney Rubble",
    "email" : "[email protected]",
    "url" : "http://barnyrubble.tumblr.com/"
  }
]

The contact properties should have name and email at a minimum.

Can type be expanded to the non-commercial equivalent of slack ? aka, matrix / riot .

It would probably be better to make it a more generic description like 'webchat' instead of brand names unless it's deliberately used like that somewhere for a reason I'm not aware of.

Not all languages have 2-letter language codes. This is especially true for developing countries.

We could experiment putting this community index behind a simple microservice so that any requestor can ask "what are the communities around this lat/long point" and get back an answer.

I've been wanting to play around with up for a while and that might be a fun use of the technology. (It's free up until we hit 1 million requests per month).

cc @mikelmaron

I would like to add two resources for Styria which is a part of Austria which is in Europe. It would help much if I can see in Readme.md how to do that. Do I have to create a folder styria inside the folder at inside Europe? Where do I put the geojson-files etc.

It's already set up to create a source strings a file for Transifex. I just need to add a project for it and type up docs.

Need to fail the build if we detect duplicate id in any of the source files.

Community Resource Name

OpenStreetMap Ghana

URL links to the resources

Ghana: https://twitter.com/osmghana
Cape Coast Youth Mappers: https://twitter.com/YouthmappersUCC
Talk GH: https://lists.openstreetmap.org/pipermail/talk-gh/
Facebook: https://www.facebook.com/OSMGhana/

Country codes (optional)

"gh"

Add an emoji flag (optional)

🇬🇭

OpenStreetMap Chile Facebook

facebook

https://www.facebook.com/OpenStreetMap-Chile-145127198882915/

Julio Costa, [email protected]

chile

¡Síguenos en Facebook! https://www.facebook.com/OpenStreetMap-Chile-145127198882915/

es

cl

🇨🇱

Before we go too wild adding all the things, we should separate the data from the polygons so that we don't run in to the kind of geojson duplication we see in editor-layer-index.

(Example): Wisconsin Wiki mapping practices and ongoing projects (if you don't want to do this state-by-state, perhaps at least the national level Wikiproject page could be linked to: https://wiki.openstreetmap.org/wiki/Wisconsin

Community Resource Name

Wiki suggested mapping guidelines and regional projects

What is it?

Wiki page (and probably 'some' regional Wiki page exists for most places for which an OSM community does - this is particularly true in the US

URL link to the resource

https://wiki.openstreetmap.org/wiki/Wisconsin

Points of contact

If someone edits the Wiki and the page is watched, affected parties will be notified through the Wiki system

Bounding polygon

Description (optional)

Lists projects and suggested standards used to map the state of Wisconsin.

Languages spoken (optional)

en

Country codes (optional)

us

Add an emoji flag (optional)

us