I used a couple of services that sent me emails when a change was made in my area

They disappeared

Is there any alternative ?

Italia

1. Pianura e aree collinari della Provincia di Caserta
2. Settore settentrionale della Provincia di Napoli
3. Basso Lazio interno e vallate circostanti
4. Zone appenniniche centrali del Molise
5. Fascia valliva e collinare del Centro-Salernitano
6. Settore occidentale della Basilicata, area appenninica

[PAGINA IN AGGIORNAMENTO]

Usando o mapa do OpenStreetMap através do app OsmAnd para navegação GPS. https://youtu.be/esqo3rh8ka0

Esta recente demanda proseguida por mim consiste em ter a informação detalhada sobre todas as paragens das diferentes operadoras que operam no Terminal Rodoviário do Campo Grande recentemente realocado. Tal como era a situação anterior à deslocação, a este faltava-lhe informação crucial.

Detalhes introduzidos

Teve-se em conta as seguintes informações a introduzir no OSM:

• operadora associadas à paragem (nome completo em operator=*)
• rotas associadas à paragem (através da etiqueta route_ref=* )
• número de cais (recorrendo à etiqueta loc_ref=* )
• abreviatura da operadora em questão (usando a etiqueta ref:operator=* )

Operadoras

Este terminal aloja as seguintes Operadoras de Transportes de Passageiros:

• Joaquim Jerónimo - Santo António (também conhecida por “Santo António - Barraqueiro”)
• Rodoviária de Lisboa
• Isidoro Duarte
• Henrique Leonardo Mota
• Mafrense
• Ribatejana
• Boa Viagem
• Barraqueiro do Oeste
• Rodoviária do Oeste / Rodoviária do Tejo

Sendo as suas abreviaturas, respetivamente:

• JJSA
• RL
• ID
• HLM
• (não usado)
• BV
• BO
• RDO

Nota-se que estas siglas, juntamente com os números de cais e números de rota, foram baseadas em painéis informativos encontrados no terminal e em um survey efectuado no local. Como tal, no caso da Rodoviária do Oeste e da Rodoviária do Tejo, estas partilham a mesma sigla pois no painel a sigla é a mesma apesar de aparentarem ser operadoras distintas. (Para uma possível explicação de assim o ser, ler mais aqui )

Frisa-se também que no caso da Isidoro Duarte e da Henrique Leonardo Mota existem rotas a serem partilhadas pelas duas operadoras (presente neste nodo ) como será o caso da rota Campo Grande -> Guerreiros (a qual ainda não se encontra mapeada).

Uma nota sobre a etiqueta network=*

… See full entry

Larger End Goal: To have a map embedded within an app or a website where people are able to easily view where the nearest postbox or post office is, and also be able to add new post offices and postboxes to the map if they aren’t yet recorded in the map.

Step 1: Display both post offices and post boxes on a uMap, using the Overpass API. These items should be on two separate layers, as the icons need to be styled differently.

Current issue: There are lots of post offices in the world, and even more postboxes. This causes the uMap to time out with a 429 error of “problem in the response.”

The current map: http://umap.openstreetmap.fr/en/map/postboxes_528331#13/53.5705/10.0067

Current suggestions:

• Use an alternative public instance: osm.wiki/Overpass_API#Public_Overpass_API_instances
• Run an Overpass API instance locally (really seems to be overkill for what’s needed for this project
• Download the information of all post_box’s and post_office’s points and store that locally. Not sure what would be the best way to do this though. It looks like you can download all the OS data following the instructions here, but 1.5TB is a bit much to handle.
• Maybe use the Overpass API itself to download the data (perhaps in chunks), although it seems we either already reached some limit or it is perhaps already overloaded and we don’t want to make it worse unless we’re sure it’s ok.

Current Questions:

• What is the best way to get all (amenity=post_box OR amenity=post_office) points from OSM without overloading anyone or downloading the whole OSM dataset?
• If we do go the route of downloading a copy of the data and querying this locally, what is the best way to get a snapshot of the relevant points from OSM without us causing unwelcome load to someone’s server?

What we hope for:

… See full entry

Thanet is a very old place and sometimes it hard to make out individual buildings in built-up areas.

To help solve this, moving forward I will be tagging businesses/addresses on the main entrance node unless it’s easy to say for certain what physical space that address takes up in that structure (houses are a lot easier locally).

I’m starting with Holly Lane area of Northdown Road

When preparing geodata for smaller scales, you need generalisation algorithms. Douglas-Peucker and Visvalingam-Whyatt algorithms are usually used for lines (polygons). Unfortunately those are mathematical/geometrical algorithms which do not take into account cartographic requirements.

Wang–Müller algorithm tries to do exactly that - generalise lines (of natural objects) according to cartographic requirements, such as saving or even exaggerating characteristic features.

Original Wang–Müller article has a quite concise description of the algorithm and as there is no open source implementation of this algorithm (to my knowledge) it is impossible to use this algorithm in wider scale and there are a number of unanswered questions on how some particular aspects should work.

A student of Vilnius University, Motiejus Jakštys, has done a perfect job - he has not only implemented the main part of Wang–Müller algorithm using open technologies, but also described the algorithm in his paper, which you can find here:

https://github.com/motiejus/wm/blob/main/mj-msc-full.pdf

Besides describing the algorithm itself (in more detail that original paper), this paper also includes recommendations on values of parameters to use on different scales, a lot of pictures as well as propositions for future work on finishing and refining the open implementation.

… See full entry

Pe̍h-ōe-jī Pán-pún

Tâi-oân chhun-lí ê chu-liāu in-ūi Wikidata siā-kûn chhú-lí hōe-ji̍p ê sî-chūn, the̍h Chú-kè-chhù 2017-nî ê chu-liāu lâi hōe-ji̍p, chō-sêng 2018-nî sin-tiâu-chèng ê chhun-lí, chhin-chhiūⁿ sī Tâi-lâm-chhī hêng-chèng-khu tōa-chéng-pèng, iáu-koh-ū in-ūi jîn-kháu chōe só͘-í hun-thiah ê lí, pēng bô sin-cheng kàu Wikidata téng-koân. Che tō chō-sêng tī OpenStreetMap chit-pêng ū chhun-lí koan-hē tùi-èng bōe-tio̍h Wikidata ê chōng-hóng.

kóng-tio̍h OpenStreetMap chit-pêng, tong-chho͘ Chìn-hoân sī ēng Lōe-chèng-pō͘ Kok-thó͘ Chhek-hōe Tiong-sim sek-hòng ê shape tóng-àn, lâi chhú-lí tùi-èng Hō͘-e̍k-chèng Hē-thóng Tāi-bé, iáu-koh-ū āu-sio̍k tùi-èng Wikidata sî, chhái-iōng pí-kàu sin jî-chhiáⁿ keng-sin khah kín ê chu-liāu, in-chhú tī OpenStreetMap chia kan-ta chha 一个 2021-nî 2-ge̍h chhoe-it sêng-li̍p ê lí, sī tī-teh Hûn-lîm-koān Táu-la̍k-chhī ê Chèng-sim-lí, só͘-í būn-tê bô-tōa, sin-cheng-ka koan-hē tō ē-sái lah.

Hôe kàu Wikidata chit-pêng, 2019-nî khai-sí ū-chi̍t-kóa Wikidata ê chham-ú-chiá khai-sí hōe-ji̍p chhun-lí, siông-sòe khòaⁿ chhun-lí hāng-bo̍k ka ê chham-khó-chu-liāu, sī ēng Chú-kè-chhù ê chhun-lí tùi-èng Hō͘-e̍k-chèng hē-thóng tāi-bé ê tóng-àn. Chú-kè-chhù ê tóng-àn kan-ta keng-sin kàu 2017-nî 1-ge̍h 31-hō, í-āu tō bô keng-sin lah, ti̍t-chiap iōng Lōe-chèng-pō͘ ê Hō͘-e̍k-chèng hē-thóng tāi-bé. Chin-chōe-lâng chōe chhun-lí hōe-ji̍p ê sî-chūn iōng-tio̍h kū ê chu-liāu, chō-sêng āu-lâi sin-cheng-ka ê chhun-lí pēng bô hōe-ji̍p kàu Wikidata téng-koân, kè-kiong ū 75-ê sin-cheng-ka ê chhun-lí, pēng-bô siu-lio̍k kàu Wikidata.

Wikidata chit-pêng chòe hōe-ji̍p ê lâng, 2020-nî lōng chhun-lí, mā bô-chù-ì tio̍h hit-sî-chūn ū chi̍t-kóa chhun-lí í-keng chéng-pèng siau-sit leh, m̄-koh in-ūi chhái-iōng chú-kè-chhù kū-ê chu-liāu só͘-í bô-hoat-tō͘ hoat-kak kàu būn-tê. Lán mā ē-tàng khòaⁿ-tio̍h chia-ê hōe-ji̍p chhun-lí hāng-bo̍k khiàm-chió Eng-bûn ê chōng-hóng.

… See full entry

Eine kleine Einschaltung, weil das in den Foren oft so vorgeschlagen wird, nämlich dass man, wenn man z.B. einen Bach in die openstreetmap einpflegt, und den Verlauf nach dem Luftbild präzise erfasst, den Anbieter des Luftbildes als “source” des Objektes angibt. Und im nächsten Atemzug das als nicht gangbareren Weg ablehnt, weil das die Anforderungen der häufig an Luftbildern klebenden Creative Commons Lizenzen nicht erfülle.

Vorweg: Es geht hier nicht darum, Grauzonen auszuloten, sondern darum, den richtigen rechtlichen Rahmen zu wählen. Mir erscheinen die Überlegungen unten schlüssig. Rechtsgarantie kann ich keine abgeben.

Das Gesetz in Österreich nimmt “Landkartenwerke des BEV” davon aus, freie Werke zu sein. Im RIS (Gesetze+Urteile) findet sich keine Definition von “Landkartenwerk”, der Ausdruck scheint selbstverständlich? Der Absatz 2 wurde 1953 in UrhG §7 aufgenommen, da gab es schon Luftbilder.

Für mich heißt das, wenn ich mir die basemap in den Editor als Hintergrundbild lege und einen Bach durchpause, dann hab ich eine geschützte Information kopiert. Denn die Information, dass dort ein Bach verläuft, die blaue Linie, die hat jemand vom BEV in die Karte eingetragen.

Detto, wenn ich einen OGD Datensatz “Bäche” importiere, dann wird auch etwas kopiert, das urheberrechtlich geschützt ist. Ich glaub, so etwas ist hier Use of CC BY 4.0 licensed data in OpenStreetMap gemeint?

Dagegen sehe ich Luftbild und Geländemodell nicht als “Karte”, sondern als Rohdaten, wie aufwendig verarbeitet auch immer. Urheberrechtlich gehen die sicher als Foto durch. D.h. ich darf sie nur weiterverbreiten wenn ich eine Lizenz besitze. CC-BY ist da bestens geeignet.

… See full entry

Last week, the U.S. federal government finally agreed to retire a number of racially insensitive names of landforms and bodies of water in Texas, 30 years after the state legislature petitioned the federal government to rename them after accomplished Black Texans. (Most of them had originally been named with an even worse racial slur.) OpenStreetMap has been updated to reflect the new names that are in GNIS, the federal government’s official gazetteer. The corresponding Wikidata items have also been added or updated, to prevent data consumers from overriding OSM names with the offensive old names, but also to link to more information in Wikidata and Wikipedia about the person whom the feature now commemorates.

Most of the features had to be mapped for the first time, because GNIS doesn’t have enough detail about linear features like valleys and creeks to import them, and NHD had only been imported in a few parts of the state. Except for Emancipation Pond, which is in a residential development under construction, a traveler is unlikely to ever stumble upon these remote features in the vast Texas landscape. Even so, much more accessible locations get renamed practically every day. Hopefully these OSM and Wikidata entries will serve as a handy model for mappers to follow as we find more efficient ways to track and respond to name changes.

… See full entry

I use to explore and map the area on the border between North and South Tyrol, and I have noticed that part of the border between Austria and Italy is wrong in openstreetmap. I noticed the error, because some abandoned Itallian military infrastracture had moved into Austrian territory.

Here is an example (before fixing): I know that the house with the geodetical tower is in Italy. The boundary stones are located some meters northern. The border between North and Tyrol runs on the watershed, so the border is exactly on the Sandjöchl Pass.

… See full entry

There is going to be an OSM-Carto map reading workshop run by me at this year’s virtual State of the Map conference on July 11 at 12:15 UTC. This is going to be a new, experimental format i would like to try where i will explain the cartography and the reasoning behind styling decisions of the standard style shown on openstreetmap.org based on case examples you can submit beforehand.

For that purpose i have created a wiki page as well as an Etherpad where you can submit such examples. In the simplest form such an example is just a link with the URL pointing to a certain place on the map you would like to see discussed and explained. Ideally you should add a few words on what specifically you would like to see discussed because often there will be other things visible in the map as well.

I plan to make this an interactive workshop allowing those who submit an example to participate in the discussion if they would like to (though this is strictly optional of course). But to allow me to prepare for the case examples it would still be desirable to submit those in advance.

You can submit your case examples on any topic and any place on the map but of course i reserve the right to pick those examples from the submissions i consider most interesting for a wider audience (and you can also indicate if you are interested in examples submitted by others on the wiki/pad). If there are more examples submitted than can be covered in the workshop i will try to discuss them on the wiki after the conference.

Feel also free to add any comments and thoughts on the workshop idea and format here or on the wiki talk page.

Esta es una guía que pretende sacar dudas cuando te encuentres con una estación de ferrocarril durante tu mapeo. Contiene las etiquetas básicas.

Las estaciones de tren se asignan normalmente con un NODO en el centro o dentro del edificio principal, sin pegar a la vía. En el nodo estarán todos los datos de la estación como el nombre, operador, red, Wikidata, etc. También se puede asignar cómo área, pero generalmente es difícil saber los límites de la misma. El nombre no debe contener la palabra estación. El edificio principal debe estar como building=train_station y no contener los datos de la estación.

Estación con uso de pasajeros

• railway=station (o halt) +
• public_transport=station

Agregar un nodo en el centro de la estación o dentro del edificio principal.

Estación sin uso de pasajeros

• railway=station (o halt)

No usar public_transport

… See full entry

Have a nice day. (For test.)

Pelo Top 500 Brazil, nos últimos 2 meses, 37% dos contribuidores pertencem a corporações, respondendo por 80,29% dos changeset e por 41,83% das modificações no mapa. Parece que o interesse dessas empresas está mais no mapeamento de vias (criação das geometrias, denominação e restrições de conversão),

Fiquei impressionado em como cresceu a participação das empresas no OSM.

As tabelas abaixo foram feitas com as estatísticas de 11 de Junho de 2021.

… See full entry

I have a few passions in life. Two of them overlap in an interesting fashion…

A number of years ago, I decided to look at how engineering (and specifically full-lifecycle analysis) could support improvements in road safety. While many road safety issues are primarily behavioural (speeding, awareness, road rage, etc), I strongly believe that infrastructure should guide road users to making better decisions over time through feedback, reinforcement of good behaviours, etc. Anyway… I decided to buy a dashcam and figure out if there was a way to collect data in a way that would provide strong arguments for change at both a local and national / international level. Due to other commitments and a lack of interest from the general public I haven’t made much progress. :(

My other rationale for getting a dashcam was to allow imagery capture to support mine and others’ OpenStreetMap activities. I drive quite a bit on my way to climb mountains and explore the south coast of Ireland (sometimes to play MMORPG Ingress). Capturing imagery and contributing it to the global community seemed like a good way to get additional “mileage” out of my travels!

But dashcams aren’t setup for sending data to Mapillary I here you say… True… but I never give up!

The OpenStreetMap Ireland community recently decided to capture imagery and authoritatively map the #WildAtlanticWay, a 2500+ km route along the west coast of Ireland. While there is some existing imagery of the route, there are some notable gaps and we wanted to fix that.

Being one of the primary contributors in Cork (Ireland’s largest county by land area), I was motivated to try and contribute more imagery in Co. Cork and Co. Kerry. So I started digging into the tools available for processing and uploading data again (to see what improvements had been made since I last tried).

Processing dashcam videos so they are usable my mapillary

… See full entry

PE̍H-ŌE-JĪ pán-pún:

Góa tī-teh MapComplete Telegram kûn-cho͘ ê liû-giân:

Kí-gōa nî-chêng, Tâi-oân ū-chi̍t-kóa tô͘-kheh khai-sí Lim-chúi tōe-tô͘, chia-ê tô͘-kheh put-chí-sī piáu-sī lim-chúi-tiám, mā siūⁿ-boeh kā Lim-chúi tōe-tô͘ bāng-chām ê têng-sek-bé, ōaⁿ pa̍t-ê chú-tê thui-chhut lēng-gōa ê chú-tê tōe-tô͘, lâi thui-sak Khai-hóng kòe-tō͘. M̄-koh chiâⁿ khó-sioh bô-hoat-tō͘ the̍h-tio̍h chu-goân lâi thui-sak bô-kâng ê chú-tê tōe-tô͘, khip-ín Tâi-oân-lâng lâi chham-ú Khai-hóng koe-tô͘.

Chin-hoaⁿ-hí MapComplete ē-tàng tit-tio̍h Khai-hóng Koe-tô͘ Ki-kim-hōe, Khai-hóng Tì-sek Pí-lī-sî, Trage Wegen, OSGeo Belgium, Jîn-tō Kiù-oān Khai-hóng Koe-tô͘ Sió-cho͘, Ûi-sit Tōe-tô͘ téng-téng ê chi-oān, ē-tàng hō͘ kong-iōng pán-pún ê chú-tê tōe-tô͘ 成為 chi̍t-chióng khó-lêng.

Chìn-chêng choān-siá Lim-chúi Tōe-tô͘ siong-koan ê bûn-chiuⁿ, ē-tàng khah chheng-chhó liáu-kái siā-kûn kah NGO chih-chiap ê būn-tê: 1, 2

Tâi-lô pán-pún:

Guá tī-teh MapComplete Telegram kûn-tsoo ê liû-giân:

Kí-guā nî-tsîng, Tâi-uân ū-tsi̍t-kuá tôo-kheh khai-sí Lim-tsuí tuē-tôo, tsia-ê tôo-kheh put-tsí-sī piáu-sī lim-tsuí-tiám, mā siūnn-bueh kā Lim-tsuí tuē-tôo bāng-tsām ê tîng-sik-bé, uānn pa̍t-ê tsú-tê thui-tshut līng-guā ê tsú-tê tuē-tôo, lâi thui-sak Khai-hóng kuè-tōo. M̄-koh tsiânn khó-sioh bô-huat-tōo the̍h-tio̍h tsu-guân lâi thui-sak bô-kâng ê tsú-tê tuē-tôo, khip-ín Tâi-uân-lâng lâi tsham-ú Khai-hóng kue-tôo.

Tsin-huann-hí MapComplete ē-tàng tit-tio̍h Khai-hóng Kue-tôo Ki-kim-huē, Khai-hóng Tì-sik Pí-lī-sî, Trage Wegen, OSGeo Belgium, Jîn-tō Kiù-uān Khai-hóng Kue-tôo Sió-tsoo, Uî-sit Tuē-tôo tíng-tíng ê tsi-uān, ē-tàng hōo kong-iōng pán-pún ê tsú-tê tuē-tôo 成為 tsi̍t-tsióng khó-lîng.

Tsìn-tsîng tsuān-siá Lim-tsuí Tuē-tôo siong-kuan ê bûn-tsiunn, ē-tàng khah tshing-tshó liáu-kái siā-kûn kah NGO tsih-tsiap ê būn-tê: 1, 2

漢字版本：

我佇咧 MapComplete 群組的留言：

幾偌年前，台灣有一寡圖客開始啉水地圖，遮的圖客希望不止是標示啉水點，嘛想共佮啉水地圖網站的程式碼，換別的主題推出另外的主題地圖，來推捒開放街圖。毋過誠可惜無法度提著資源來推捒無仝的主題地圖，吸引台灣人來參與開放街圖。

… See full entry

我在 MapComplete Telegram Group 留言：

很多年前，台灣有些圖客開始飲水地圖計劃，這些圖客不只想要標示飲地點，還要把製作飲水地圖網站的程式碼，換不同的主題來推出另一個主題地圖，藉此推廣開放街圖。但很可惜無法拿到足夠資源來推展不同主地圖，來吸引台灣大眾參與開放街圖。

很高興 MapComplete 得到開放街圖基金會、開放知識比利時、Trage Wegen、OSGeo Belgium、人道救援開放街圖小組、遺失地圖等等的的支援，讓公用版本的主題地圖成為可能。

先前撰寫有關飲水地圖的文章，可以較較清楚瞭解社群與 NGO 接觸遇到的問題：1、2

Вот продолжение моих попыток вводить POI сразу на месте из OsmAnd. В этот раз я обошёл вокруг квартала Московский-Смоленская-Заозёрная-Обводный. Этот заход оказался относительно успешным. Мне удалось ввести большую часть POI из тех, которые я бы ввёл обычным двухэтапным способом. Одна из причин успеха — в этом месте до меня было отмечено не слишком много POI. Соответственно, практически не возникало проблем сопоставления отмеченного с реальным. Одна из причин этой одной из причин — наличие свежепостроенных зданий, в которых очевидным образом не может быть обозначенных точек десятилетней давности.

Новые здания, как на Смоленской улице, также облегчают задачу сопоставления самих себя со своими образами на карте. Их обычно не строят в упор друг к другу, благодаря чему гадать об их границах не приходится. Зато там, где дома более-менее старые, что в моём случае наблюдается вдоль Московского проспекта, непонятные границы зданий возникают вновь. И, как обычно, далеко идти за ними не приходится. Начав обход с угла Московского проспекта и Обводного канала, прямо на этом углу я обнаружил дом № 62 со своим соседом № 64 или один дом № 62-64. Табличек с номерами там две,¹ но это ещё не значит, что и дома два. Если таблички убрать, то, скорее, покажется, что дом один, если смотреть на него с улицы. Взгляд со стороны двора, возможно, произвёл бы другое впечатление, но я же не буду обходить каждый дом со всех сторон, когда ищу POI на улице. Но это ещё не самый сложный случай, потому что даже и с улицы ясно, какому месту соответствует видимая на карте граница между зданиями. Следующая же граница между домами № 64 и № 66 в том месте, где она нарисована, не видна совсем.

… See full entry

Sziasztok! Június 25-én mit szóltok egy mapping partyhoz Pestújhelyen? A környék nagyon üres POI és házszám ügyben. Gyertek térképezni velünk! Tali helynek a Vanilin Cukrászdát javaslom.

További infók, programok, elérhetőség: https://wiki.openstreetmap.org/wiki/Hungary/2021-06-25-pestujhely-mapping-party