OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

Mapeamento de cursos d’água com a participação especial de especialista das Nações Unidas


Tivemos grande satisfação em contar com o geógrafo Séverin Ménard (UN Mappers/UNGSC), realizando a oficina sobre o mapeamento de cursos d’água no OpenStreetMap (OSM), abordando ainda outras feições importantes, como os fords, nos pontos de cruzamento entre waterways e highways; ou as galerias, que permitem a passagem de água sob as vias.

A oficina foi organizada pelo Instituto Virtual para o Desenvolvimento Sustentável - IVIDES.org, que criou um projeto de mapeamento colaborativo no HOT Tasking Manager - https://tasks.hotosm.org/projects/16706/, para apoiar o enfrentamento da aguda crise humanitária, que acomete o estado do Rio Grande do Sul (Brasil), desde o final de abril de 2024. Neste projeto, é possível mapear os edifícios, vias e hidrovias que faltam, especialmente, na porção norte da área de interesse.

O IVIDES.org também disponibilizou um projeto de web map, que está sendo desenvolvido com uMap, com dados sobre os trechos de drenagem da região da Bacia Hidrográfica Taquari-Antas e as poligonais das áreas inundadas pelos principais rios, generalizadas dos dados produzidos pelo Instituto Nacional de Pesquisas Espaciais (INPE), disponíveis na ativação “Flooding in Brazil” no Disaster Charter.

Neste momento, o mapeamento de hidrovias é fundamental, tanto para as atividades de reposta, como as ações de socorro às vitimas do desastre, quanto para a fase da reconstrução e realocação de bairros e cidades inteiros, que foram atingidos pelo maior desastre visto no país.

Nosso agradecimento a Séverin Ménard, o palestrante especial, e a Victor Timotheo (GeoCart-UFRJ), que realizou o apoio técnico da sessão.

A agenda completa das oficinas e os recursos - documentos e vídeos, podem ser encontrados na página do treinamento.

As imagens abaixo foram recuperadas da apresentação realizada e do guia do JOSM, do UN Mappers Learning Hub (CC BY-SA), disponível na pasta virtual. IVIDES.org® é uma marca registrada.


A gravação da sessão pode ser encontrada no canal do IVIDES.org® no YouTube

imagem_desastre_rs


https://ivides.org/wp-content/uploads/2024/05/hot_tm.png

https://ivides.org/wp-content/uploads/2024/05/josm.png

https://ivides.org/wp-content/uploads/2024/05/opentopomap_unmappers.png

https://ivides.org/wp-content/uploads/2024/05/opentopomap.png


IVIDES_logo

Location: Taquari, Região Geográfica Imediata de Lajeado, Região Geográfica Intermediária de Santa Cruz do Sul - Lajeado, Rio Grande do Sul, Região Sul, 95860-000, Brasil
Posted by Akbar-Birbal on 12 May 2024 in English.

Delhi Cantonment is one of the most sparsely mapped area in Delhi. It might be because it is full of military areas. As I live in the cantonment, I hope to map at least the non-sensitive areas, such as Sadar Bazar and Gopinath Bazar. By my current rate, it is likely to take at least 2 months to map these two markets alone. I want to focus on mapping areas in the cantonment. In future I might venture out to map the big Nangal area (gulp).

Location: Gopinath Bazar, Delhi Cantonment, New Delhi, Delhi, 110010, India

Edificio protegido en la subida la Coracha Edificio protegido en la subida a la Coracha, construido en 1820 y declarado patrimonio protegido en 1970, ejemplo típico de la arquitectura malagueña del siglo XIX. Fuente: trabajo propio (CC BY-SA 4.0) disponible en Wikimedia Commons.

El Ayuntamiento de Málaga mantiene un catálogo de edificios protegidos reconocidos en su Plan General de Ordenación Urbana al que se puede acceder a través de la página web de la Gerencia Municipal de Urbanismo. Dado que este catálogo supone un reconocimiento oficial de su valor patrimonial, estos edificios son susceptibles de ser añadidos al mapa de OpenStreetMap bajo la clave heritage.

He creado una nueva sección en la página del wiki dedicada a objetos culturales de Málaga con una propuesta de etiquetado para el mapeado de edificios protegidos con idea de enriquecer el valor informativo del mapa en términos de conservación del patrimonio. Todos los edificios protegidos de Málaga están ya en el mapa, solo habría que añadirles el etiquetado correspondiente a la clave heritage.

Sugiero aprovechar la ocasión de añadirlos al mapa para tomar algunas fotos de los edificios, subirlas a Wikimedia Commons y enlazarlas con su elemento correspondiente en OpenStreetMap, tal como se está haciendo con los monumentos conmemorativos y arte público de Málaga.

También he creado un predefinido para facilitar el etiquetado de estos edificios en JOSM. Lo iré perfeccionando conforme se vayan añadiendo al mapa y se termine de perfilar la mejor forma de etiquetar estos edificios entre los colaboradores interesados en mapear el patrimonio arquitectónico de Málaga.

Location: Campos Elíseos, Centro, Málaga, Málaga-Costa del Sol, Málaga, Andalucía, España

With 2024 officially being the year of OpenStreetMap vector maps let’s do a deep-dive into vector maps: their history and how the underlying vector tiles work in detail.

img1

Vector Maps History

To understand how revolutionary vector maps were we have to go back in time to the early 2010s. One Direction is raising to international fame and raster maps are at the height of their popularity. Folks creating raster web maps rendering OpenStreetMap data into beautiful 256x256 pixel images.

But raster maps come with limitations: when you rotate the map the labels stop facing you; you can’t customize pre-rendered maps to specific use-cases on the fly; there is no fractional scaling between zoom levels. All of these problems are unthinkable nowadays: here is one example where Jochen wrote about Wikipedia struggling with pre-rendering multilingual maps for over 200 languages because they can’t change their map’s language on the fly.

In December 2010 Google introduced vector maps in Google Maps on Android. I highly recommend you stopping here to go skim their announcement blog post where they show-case what vector maps allow them to do.

img8

With WebGL rendering technology reaching browsers in 2013 folks like Michal Migurski start experimenting with rendering maps in the browser instead of displaying raster images.

img7

In April 2013 the folks at Mapbox release an experimental vector tile format for rendering vector maps followed by a first go at a browser-based canvas and WebGL renderer.

This experimental vector tile format would end up becoming the industry standard Mapbox Vector Tile (MVT) specification and the renderer would end up becoming the state of the art web map renderer Mapbox GL JS and/or Maplibre we all enjoy to this day.

Let’s have a look at this vector tile specification in detail allowing for vector maps.

The Mapbox Vector Tile (MVT) Specification

The Mapbox Vector Tile specification outlines how to encode geographic data into vector tiles. The most common use case is encoding geometries and features from OpenStreetMap for a browser based renderer such as Maplibre. The vector tile specification is not tied to a source such as OpenStreetMap or a renderer in particular.

The specification provides a format for encoding a single vector tile: the vector map is made up of a collection of vector tiles with neighboring tiles and zoom levels exactly as with raster maps and raster tiles.

You can find the Mapbox Vector Tile specification here.

The Mapbox Vector Tile format is based on Protocol Buffers and roughly consists of the following entity hierarchy

  1. A Tile has multiple Layers
  2. A Layer has multiple Features
  3. A Feature has a Geometry and Attributes

As an example: a tile with a “building” layer with multiple feature polygons and height in meters.

Geometries can be points, linestrings, or polygons; attributes are key-value pairs where the key is always a string and the value can be any type (int, float, string, ..). The geometry encoding is mimicking the Canvas API with commands

  1. MoveTo
  2. LineTo
  3. ClosePath

These commands work on a square coordinate system e.g. with extent 4096 where top-left represents the origin at (0, 0).

As an example: the linestring [(2,2), (2,10), (10,10)] would look like the following

  1. MoveTo(+2,+2)
  2. LineTo(+0,+8)
  3. LineTo(+8,+0)

The command’s type, how often to apply the command, and the command’s parameters are all efficiently encoded as varints.

There are two Protocol Buffer core concepts worth understanding here as they’re used heavily throughout the specification: varints and zig-zag encoding. Varints encode numbers in a variable number of bytes such that small numbers take up less space. The most significant bit of a byte acts as a continuation flag, leaving the remaining seven bits per byte for data. That means e.g. numbers such as 0, 1, 42, that are fitting into seven bits only take up one byte instead of e.g. 4 byte with an int32 data type or 8 byte with an int64 data type. Zig-zag encoding allows varints to work with negative numbers, too.

img2

Problems with The Mapbox Vector Tile (MVT) Specification

The Mapbox Vector Tile specification is a pragmatic industry standard that has allowed for massive innovation over the last decade. That said, it’s not without problems and limitations.

One of the biggest issues is that there is no sharing of data between vector tiles: not between neighboring tiles and not across zoom levels. If there is a road spanning multiple tiles,

  1. the very same road name will be inefficiently encoded in neighboring tiles on the same zoom level
  2. the very same road name will be inefficiently encoded in tiles up and down the zoom level hierarchy

In contrast the OrganicMaps folks with their home-grown data format efficiently share map data and make use of succinct data structures which is one reason their offline maps so small and efficient.

img3

There are various other inefficiencies, e.g. points are inefficiently encoded to simply store two coordinates.

There has been work on a new Mapbox Vector Tile version v3 trying to overcome some of the problems and limitations and at the same time introduce new features such as: elevation, inline attributes, and splines. You can see the work in progress in the upstream v3.0 branch. There hasn’t been an update since 2019.

I believe it’s fair to say that we’re stuck with the Mapbox Vector Tiles specification v2 for better or worse. The problems and limitations mentioned above are far outweighed by having a stable specification for vector tiles the broader ecosystem agrees on.

From Vector Tiles to Vector Maps

The Mapbox Vector Tile specification described above is a format for encoding and decoding a single vector tile. Vector maps are made up of multiple vector tiles across zoom levels and there are two popular ways to package up individual vector tiles into a vector map.

The first way to package up tiles is the historic MBTiles format which initially was created for jpg and png raster maps in 2011.

The MBTiles format is a sqlite3 database file packaging up z/x/y tiles; you can use the sqlite3 command line tool to have a look at its table definitions

CREATE TABLE tiles (zoom_level integer, tile_column integer, tile_row integer, tile_data blob);

In 2016 the MBTiles format started recognizing the Mapbox Vector Tile format in addition to jpg and png raster tiles.

You can find the MBTiles specification here.

The second way to package up tiles is the more recent PMTiles format from the Protomaps folks.

The PMTiles format bundles up vector tiles in a single file just like MBTiles. But unlike MBTiles, the major benefit of PMTiles is laying out the vector tiles in a clever way such that browsers can make Byte-Range requests against the PMTiles file. What this means in practice is that now we can create Mapbox Vector Tiles, package them up in a single PMTiles file, and host this one file on any static file hoster.

You can find the PMTiles specification here

With vector maps data at our hands what’s missing now is a way to decode, display, and style the vector data e.g. using Maplibre and its Style Specification. Based on the map’s viewport Maplibre fetches vector tiles, decodes the vector tile by parsing the protocol buffers, and then allows us to style the vector tile layers, features, geometries, and attributes however we want.

Create Your Own Vector Maps

Creating your own vector maps from OpenStreetMap has never been easier! To get started I recommend having a look at Maplibre and Protomaps; start for example here for inspiration.

If you want to create your own vector maps from OpenStreetMap data, good first steps are

  1. Download a small .osm.pbf file from Geofabrik
  2. Use tilemaker or planetiles to generate PMTiles
  3. Drop the PMTiles file into the Protomaps PMTiles viewer for debugging
  4. Use Maplibre to visualize the vector map and styling it as you like

and then iterate from here.

Happy year of OpenStreetMap vector maps!

References

Welcome to the sixth OpenStreetMap NextGen development diary.

This week, I continued the preparation of the project for the first development release scheduled for the end of this month 🔨.

🔖 You can read my other development diaries here:
https://www.openstreetmap.org/user/NorthCrab/diary/

📖 This project is open-source and publicly available:
https://github.com/Zaczero/openstreetmap-ng

🛈 This independent initiative is not affiliated with the OpenStreetMap Foundation.

In Case You Missed It…

OpenStreetMap-NG is planned to have its first development release at the end of this month, May. After this milestone, the project will be open for new contributors! My current work focuses on delivering on that promise, finishing the core functionalities, and stabilizing the code.

Originally posted in diary #5.5.

Finishing Up the Elements Sidebar

The elements sidebar has been mostly finished. The “Part of” and “Members/Nodes” sections are now more consistent in design and have received pagination support. The orange-colored map visualization is also now working.

Preliminary API 0.7 /map Implementation

The data layer is now working and uses the new API 0.7 for map requests. It also utilizes the new rendering algorithm, which will provide much better performance than the current implementation, handling more elements in view. The new map view padding optimization also reduces the number of API requests when panning around, providing a smoother user experience.

Public Feature Ideas

I have also publicized some collected feature ideas on the GitHub Issues tracker. These currently include only medium and long-term ideas. Short-term ideas will be added closer to this month’s deadline. Some features embedded within the code will also be added to this list soon - currently it’s not exhaustive as it covers only my personal notes.

General Code Cleanup

This week, the code has undergone cleanup. The database usage for private structures has also been reduced. By switching from UUID to Snowflake ID-inspired type, the type now takes just 64 bits of space instead of 128 bits.

Project Sponsors 🏅

Time for the weekly appreciation of the current project patrons. Thank you, everyone, for supporting the project, including those who starred it on GitHub! We are making it real 😎.

Currently, the project is sponsored by 14 people!
Five private and four public donors on Liberapay, and five public on GitHub Sponsors.

If you can, please consider supporting the OpenStreetMap-NG development 🦀:

Donate using Liberapay

Posted by bhousel on 8 May 2024 in English.

I’m excited to announce that today we released Rapid v2.3 editor for OpenStreetMap! The Rapid team has been busy working on this for the past few months - here’s 4 new features that we hope you’ll love…

🔙 Esri Wayback imagery

The world never stops changing! We added a new background layer called “Esri Wayback” to let you view historical releases of the Esri World Imagery. This background source also has a date picker to help you choose from dates likely to show changes in the current map view. Open the Background pane to try it out!

Esri Wayback

🔄 Map Rotation

Take Rapid for a spin! Now you can rotate the map to make your editing easier (and avoid straining your neck!). Rapid supports rotating with option+click-drag or shift+←/→ arrows, just like other maps you’ve used before. A new bearing control displays a north arrow, and you can click it to reset the map back to North-up.

Map Rotation control

✅ MapRoulette Integration

You can now complete MapRoulette tasks without ever leaving Rapid. View active MapRoulette tasks in the current map view, or filter the results by challenge id. After making your edits, select the task and click “I fixed it!”, “Can’t Complete”, “Already Fixed”, and “Not an Issue”. When you save your edits, your changeset will automatically include a description about any MapRoulette tasks that you’ve completed.

MapRoulette

🎨 GeoScribbles

GeoScribble is a new service that allows mappers to take field notes while surveying with the EveryDoorOSM mobile app. Your sketches and notes will be waiting for you when you get back to your computer and open Rapid.

GeoScribble


We’ve got lots more planned, and we’re excited to hear how the community is using Rapid to map more efficiently.

  • ☝️ Make Rapid your OSM editor! Bookmark rapideditor.org/edit and make it your daily mapping tool of choice.
  • ✌️ Want to help us make Rapid better? Follow us on Github at https://github.com/facebook/Rapid or find us on any of the various social media or OpenStreetMap community channels. We’d love to hear your thoughts!

Happy Mapping 👍

大家好!这里是monhiko!(/ω\)

这是本人第一次尝试在OSM上写的一篇日志(因为今天才刚刚发现原来我也能写),所以就结合最近我国OSM地图上出现的一些情况对2023版《公开地图内容表示规范》(内容详见:公开地图内容表示规范,以下简称《规范》)进行一个解读,希望相关的mapper们能够在守法的情况下绘制OSM地图,让OSM地图更好的为我们的日常科研服务!

希望各位小伙伴们看完后记得一键三连(bushi)

一、主要解读内容

由于《规范内容》实在太多,涉及到OSM的也就几点,因此此次解读主要针对以下章节点:

第十八条

第十九条

第二十条

第二十一条

第二十二条

好的,下面咱不多说,我们直接走起!

二、具体解读

第十八条

该条规定:“…我国境内公开悬挂标牌的单位可在地图上表示单位名称。用于公共服务的设施,可在地图上表示其名称等可公开属性信息”

这条意思是说,在OSM上只要你看见有关公共服务设施(机关单位)是正式挂了牌的、能够在百度高德上面搜到的,那么就可以在OSM上画出来。

那么“公共服务设施”包括哪些呢?根据《城市居住区规划设计规范》,公共设施主要包括以下几类,下面带你学习/复习一下:

1. 教育设施

主要包括托儿所、幼儿园、小学、中学等,在OSM上对应“幼儿园”(托儿所、幼儿园)及“学校”(小学、中学)两个tag。

大学算什么呢?答:大学基本上算是地市及以上等级的部门管的,小小社区无权独占。

2. 医疗卫生

包括医院、诊所、卫生站等,在OSM上对应“医院”这个tag(精神病院会在后面讲)。

3. 文化体育

包括影剧院、俱乐部、图书馆、老年人活动室、会所等,对应类型详见相关OSMWiki。

4. 商业服务

包括食品店、菜场、服装、药房、理发店等,对应类型详见OSMWiki。

5. 金融邮电

包括银行、储蓄所、邮电局、邮政所、证券交易所、快递驿站等,在OSM上对应“银行”(银行、储蓄所)、“邮局”(邮电局、邮政所、快递驿站)等。

证券交易所咋标?建议去OSMWiki查,因为靖西没有(bushi)

6. 社区服务

包括居民委员会、派出所、物业管理等。居民委员会因分街道居委会和社区居委会,因此对于居委会详见OSMWiki。

物业管理咋标?如果你能确定其位置的话,那就标为“家政服务”之类的。(派出所这块会在后面讲)

7. 市政公用

包括公共厕所、变电所、消防站、垃圾站、水泵房、煤气调压站等。其中,仅允许公共厕所(对应tag为“厕所”)、消防站(对应tag为“消防站”)和垃圾站(对应tag详见OSMWiki)能标。

其他的呢?会在下面讲。

8. 行政管理

包括商业管理、街道办事处等行政管理机构。对于这一类,窃以为谨慎处理,标点、面还是行的,内部的建筑、用地这些的话。。。自己心中要有一杆秤,你经过深思熟虑、参考国内多类型地图后确定认为标这些东西出来不会危及国家安全的话你就画吧。(注意这句话,下文中我会简称为“一杆秤原则”)

综上所述,这八类公共服务设施只要上面中允许标出且能够在国内地图上搜得到,就应标尽标,以充实地图内容。

第十九条

该条规定:“…表现地为我国境内的地图平面精度应当不优于10米(不含),高程精度应当不优于15米(不含),等高线的等高距应当不小于20米(不含)。依法公布的高程点可公开表示”

这条意思是说,你在画OSM时放大精度不得大于10米(对应放大等级20级),毕竟你只是画画,不是来玩测绘的。

第二十条

该条规定:“…表现地为我国境内的地图不得表示下列内容(对社会公众开放的除外):

(一)军队指挥机关、指挥工程、作战工程,军用机场、港口、码头,营区、训练场、试验场,军用洞库、仓库,军用信息基础设施,军用侦察、导航、观测台站,军用测量、导航、助航标志,军用公路、铁路专用线,军用输电线路,军用输油、输水、输气管道,边防、海防管控设施等直接用于军事目的的各种军事设施;

(二)武器弹药、爆炸物品、剧毒物品、麻醉药品、精神药品、危险化学品、铀矿床和放射性物品的集中存放地,核材料战略储备库、核武器生产地点及储备品种和数量,高放射性废物的存放地,核电站;

(三)国家安全等要害部门;

(四)石油、天然气等重要管线;

(五)军民合用机场、港口、码头的重要设施;

(六)卫星导航定位基准站;

(七)国家禁止公开的其他内容;

因特殊原因确需表示的,应当按照有关规定执行”

这一条就直接表明了禁标内容。涉军不能标是我们中国大陆mapper的绝对原则,谁要是违反请积极举报。能源设施属于重大关乎国计民生设施,也是个人型mapper坚决不能标的。机场码头非公开的也绝对不能标。

这里就回过头来补第十八条的几个坑。

1.派出所能不能标呢?

首先说明一个东西,我国的暴力机关(这是个中性名词,只要是个国家都会有)都有哪些:军队、武警、警察,其中武警包括人武部,警察包括公安和派出所。军队和武警务必遵循“涉军不能标”原则,这个是绝对不能改变的。公安局县级和镇级勉强可以按“一杆秤原则”,但是地级及以上就能不标就不标、能标粗就标粗。综上所述,派出所窃以为还是能不要标就不要标为妙。

那为什么消防站能标?因为他不是暴力机关。

也就是说,凡是涉及到暴力机关的,建议都不标,除非你“一杆秤原则”用得很好

2. 能源设施包括哪些?

我们常说的能源设施,主要包括“两水一电一气(给水、排水、电力、热力燃料暖气)”,这些关乎国计民生,个人mapper绝对不能标。同时,电讯设施同样重要,因此加上去,就变成“两水两电一气”,这五大类是不能标的。

第二十一条

该条规定:“…表现地为我国境内的地图不得表示下列内容的属性:

(一)军事禁区、军事管理区及其内部的建筑物、构筑物和道路;

(二)监狱、看守所、拘留所、强制隔离戒毒所和强制医疗所(名称除外);

(三)国家战略物资储备库、中央储备库(名称除外);

(四)重要桥梁的限高、限宽、净空、载重量和坡度,重要隧道的高度和宽度,公路的路面铺设材料;

(五)江河的通航能力、水深、流速、底质和岸质,水库的库容,拦水坝的构筑材料和高度,沼泽的水深和泥深;

(六)电力、电讯、通信等重要设施以及给排水、供热、防洪、人防等重要管廊或者管线;

(七)国家禁止公开的其他信息”

这一条同第二十条相同,只是对相关tag进行了细化。

(一)项涉军问题决不能标。

(二)项所列事物关乎社会治安稳定,同样不能标。其中注意,“强制医疗所”里面就包括了精神病院,所以该类医院哪怕你知道也请不要标。这一条可能有人会问:宛平南路那家伙行不行呢?窃以为由于那地块已经知名到快成国家AAAA级旅游景区的程度了,所以像北上广武宁这些城市的精神病院标也不是不行。但建议要说清楚这些地方不是像普通医院能随便进出的就行。

(三)项应该很少有接触,大致包括重要粮仓等等。

(四)项涉及mapper们较多,所以重点讲述。“重要桥梁的限高、限宽、净空、载重量和坡度”,意味着你在画桥梁的时候,桥梁的相关限制数据决不能标(速度例外);“重要隧道的高度和宽度”,这个因为OSM里没有专门标隧道的可以忽略,但有隧道的公路道路宽度(对应“宽度”这个tag)不能标;“公路的路面铺设材料”,意味着任何道路(注意是“任何”,这就包括了郊区公路和城市道路)的“路面铺设”这个tag你是绝对不能填的。

(五)项应该不会有人专门跑去水库要数据画,如果现实中真有人这么做估计早就被抓起来报道了。

(六)项关于能源的在第二十条有相关描述,这里就不再重复。 这里可能会有人问,地下停车库能不能标呢?窃以为按照“一杆秤原则”处理,因为我国地下停车场库的要求是有特殊规定的。

第二十二条

该条规定:“…表现地为我国境内的遥感影像,地面分辨率不得优于0.5米,不得标注涉密、敏感信息,不得伪装处理建筑物、构筑物等固定设施”

这条还是老生常谈的“涉军不能标”的基本原则,所以这一条基本原则请绝对记住。

好了,那么这一次的国家安全小知识解读就到这里,希望大家们能够仔细解读上述条例,自己对照自己曾经画过的东西,有则改之、无则加勉;同时在日常mapping中要多留意自己周边地图,如果有发现违反上述条例且活动积极的mapper请积极举报!

那么,下一次再见了,拜拜!(/ω\)

collaborative live mapping of regions affected by rain in Rio Grande do Sul - Brazil.

Today we are going to map the area that was affected by the rains in the state of Rio Grande do Sul, there will be a live broadcast at 7:00 pm where everyone can map and help with mapping the affected area.

task link. MAPPING OF ROADS IN THE AREA AFFECTED BY THE FLOOD OF THE PARDO RIVER IN CANDELÁRIA-RS https://tasks.hotosm.org/projects/16696

Youtube: https://www.youtube.com/watch?v=3Wm-nTnCRaQ&t=7s

organization: UFV youthmappers UMBRAOSM

live collaborative mapping in the affected areas of RS

Location: Jardim Botânico, Porto Alegre, Região Geográfica Imediata de Porto Alegre, Metropolitan Region of Porto Alegre, Região Geográfica Intermediária de Porto Alegre, Rio Grande do Sul, South Region, Brazil

Greetings!

We are thrilled to share some exciting news from OpenStreetMap Bangladesh (OSMBD). For the first time ever, the OSM Bangladesh community has successfully formed an elected Executive Committee, consisting of a team of dedicated individuals who will guide our community’s activities and initiatives.

We are proud to introduce the newly elected Executive Committee:

President: S M Sawan Shariar

Vice-President: Atikur Rahman

Secretary: Samsul Arafin

Treasurer: Nahid Ferdous

Member-at-large: Mehedi Hasan Ovi

Member-at-large: Afia Tahmin Jahin

Member-at-large: Laila Sharmin Nova

Alt text

The committee is committed to upholding OSMBD’s core values of collaboration, community-driven initiatives, openness, and accessibility. Our focus is on promoting the use and development of OpenStreetMap in Bangladesh, building and maintaining a comprehensive map of Bangladesh that is freely accessible, and supporting OSM groups and initiatives through training, events, and more.

We would be delighted to collaborate with you on OSM-related projects in Bangladesh. If you need any assistance or guidance, or if you would like to collaborate on OSM-integrated activities, please do not hesitate to reach out to us at our central email communication address: info.osmbd@gmail.com

For ongoing updates and discussions, we invite you to subscribe to our Talk BD channel through the following link: https://lists.openstreetmap.org/listinfo/talk-bd

We appreciate your support and collaboration in advancing the use of OpenStreetMap in Bangladesh and look forward to working with you to achieve our shared goals.

Thank you for standing with the OpenStreetMap Bangladesh community.

Cheers!

Sawan Shariar

President (Elected), OpenStreetMap Bangladesh

Location: Monipuri Para, Tejgaon, Dhaka, Dhaka Metropolitan, Dhaka District, Dhaka Division, 1215, Bangladesh
Posted by Enock4seth on 6 May 2024 in English.

Hello OSM World,

Welcome to #WOSMinGhana 000

I am starting a series of OSM Diary posts title Worst of OSM in Ghana, inspired by best and worst of OSM posts I have seen. The idea is to share one photo per week (I hope I can keep up, feel free to share any you might have seen in Ghana too :D). i.e. Before and After (if I am able to improve or fix it)

Sometimes you come across very interesting mapping activities and data and you are out of words. Myself and other volunteer mappers have taken screenshots of worst contributions on OSM in Ghana over the years and then proceeded to improve them / notify mappers or organizations.

Why talk about the worst not the best? Highlighting these worst mappings might help create more awareness about what we put out there as part of individual or organized mapping activities.

This is purposely to help improve OSM data in Ghana in these areas by myself or other mappers and for us all to beware of when mapping.

Looking forward to the coming weeks.

Location: Kwameteng, Sekyere Central District, Ashanti Region, Ghana
Posted by TrickyFoxy on 6 May 2024 in Russian (Русский). Last updated on 12 May 2024.

Написал юзерскрипт для Tampermonkey, добавляющий несколько полезных мелочей:

  • Удалятель точек
  • Улучшенная работа с заметками
  • Компактная история объектов
  • HDYC в профиле пользователей
  • Компактная информации о правке
  • Кнопка отката

🔫 Удалятель точек

📝 Улучшенная работа с заметками

  1. При открытии заметок теперь вы можете включить спутниковые снимки
  2. Появилась кнопка с быстрым комментарием к заметке
  3. Появилась кнопка, которая с помощью Overpass показывает состояние карты на момент создания заметки
  4. Убирается мещающая оранжевая обводка около активной заметки

🕒 Компактная история объектов

  1. Показывает на странице истории только изменившиеся теги
  2. Скрывает версии без изменений и скрытые DWG

🪪 HDYC в профиле пользователей

Но только в Firefox и с отключением защиты от отслеживания

🔍 Компактное описание правки и кнопка отката

также компактнее стала вкладка История.


Как установить

  1. Установите расширение Tampermonkey
  2. После откройте файл со скриптом

p.s. Несмотря на то, что юзерскрипты должны работать в любых браузерах одинаково, Chrome отличился: спутниковые снимки и HDYC работать в нём не будут. Переходите на Firefox :)

p.p.s. Функции можно отключать в настройках скрипта, нажав на значок расширения

p.p.p.s. Вы можете использовать расширение в Firefox для Android

upd: в список редакторов добавлена ссылка на Rapid