I m here
Ternyata sudah saya petakan setahun yang lalu …
> addr:province Riau > admin_level 5 > boundary administrative > name Kota Dumai > name:en Dumai City > type boundary
https://www.openstreetmap.org/relation/7830590
dan subarea nya (kecamatan) juga sudah
Relation Kecamatan Sungai Sembilan (10359427) as subarea Relation Kecamatan Dumai Barat (10359428) as subarea Relation Kecamatan Dumai Timur (10359429) as subarea Relation Kecamatan Medang Kampai (10359432) as subarea Relation Kecamatan Bukit Kapur (10359435) as subarea
tapi, belum masuk diari ini …
https://www.openstreetmap.org/relation/7830704
Relation Kecamatan Kemuning (10359489) as subarea Relation Kecamatan Keritang (10359770) as subarea Relation Kecamatan Kempas (10359795) as subarea Relation Kecamatan Tempuling (10359802) as subarea Relation Kecamatan Gaung (10359835) as subarea Relation Kecamatan Enok (10359946) as subarea Relation Kecamatan Tembilahan Hulu (10359972) as subarea Relation Kecamatan Batang Tuaka (10360140) as subarea Relation Kecamatan Gaung Anak Serka (10360231) as subarea Relation Kecamatan Pulau Burung (10360420) as subarea Relation Kecamatan Teluk Belengkong (10360516) as subarea Relation Kecamatan Pelangiran (10360538) as subarea Relation Kecamatan Kateman (10360564) as subarea Relation Kecamatan Tanah Merah (10360616) as subarea Relation Kecamatan Kuala Indragiri (10360682) as subarea Relation Kecamatan Tembilahan (10360096) as subarea Relation Kecamatan Congcong (10360792) as subarea Relation Kecamatan Sungai Batang (10360822) as subarea
https://www.openstreetmap.org/relation/7830592
Relation Kecamatan Tapung Hulu (7834727) as subarea Relation Kecamatan Tapung Hilir (7834735) as subarea
Kampar dan Kota Pekanbaru … wew … messi
ini berantakan banget … mau nangis rasanya … sepertinya saya backup lalu saya fix saja ya .. mohon izin buat yang mencoba membuatnya dulu, tetapi tidak menggunakan relasi … hanya main polygon saja …
ngga kek gitu beib .. mudah mudahan bisa saya perbaiki … mungkin pas libur tahun baru ini …
Yesterday I had the pleasure of participating in the Local Chapters and Communities Congress, where we celebrated and Joost Schouppe ceremoniously countersigned new local chapter agreements. At the beginning of 2020, the OSMF had 8 local chapters, all in Europe. Today we have 14 local chapters, on five continents: Europe, South America, North America, Asia, and as of the last OSMF Board meeting, Africa. Joost as Board secretary has done the lion’s share of the work in processing six applications so far this year and deserves kudos for his efforts.
Among other things we discussed what the role of local chapters should be in OSM governance. Nothing has been set in stone, and indeed the conversation in a breakout session on the topic was free-flowing. Rob Nickerson of OSM UK suggested that the local chapters might be asked to help decide on admission of new corporate members, and also to help the Board prioritize paid work (e.g., to help decide when volunteer contributions of labor are not keeping up and OSM needs to pay somebody to fix broken software). I think these are ideas worth considering.
The conversation yielded a suggestion that the OSMF Board assist local chapters and communities with fundraising and perhaps help coordinate fundraising.
I have my own thoughts on this–I don’t think the Board itself should be a source of funds for local chapters and communities, because that could lead to dependency relationships that would undermine the decentralized nature of the OSM community, one of its strengths. That said, there is perhaps a role for the Board in cooperating with the LCCWG to assist local chapters in raising their own funds and to ensure that we don’t interfere with each other in the process.
I’ve added a new page to the switch2osm guide: “Updating your database as people edit OpenStreetMap”.
It’s a bit overdue (it’s based on something I wrote about 4 years ago, and the software it uses predates that by a long way), but I think it is worth making available on the main site.
I’ve tested it both on Debian 11 and on Ubuntu 20.04 LTS, and have tried to make clear what you need to do differently in each case.
For completeness see also Ircama’s excellent guide which is well worth reading as it actually provides a lot more detail about the process, and also suggests how “osmium” may be used instead of “osmosis” to process OSM files.
Боряна 41
Setelah vakum hampir selama 1 tahun, baru saya sadari ternyata Kabupaten Siak, belum saya petakan batas kecamatannya ( admin_level 6 ). Padahal, saya punya bocoran dari pihak BPS hingga admin_level 10.
InsyaAllah saya coba update terus di diary ini progress saya…
BPS:id_provinsi BPS:id_kabkot BPS:id_kec BPS:id nama_kecamatan 14 05 012 1405012 KANDIS 14 05 020 1405020 SIAK 14 05 030 1405030 SUNGAI APIT 14 05 021 1405021 KERINCI KANAN 14 05 031 1405031 BUNGA RAYA 14 05 033 1405033 PUSAKO 14 05 026 1405026 MEMPURA 14 05 022 1405022 TUALANG 14 05 010 1405010 MINAS 14 05 023 1405023 DAYUN 14 05 011 1405011 SUNGAI MANDAU 14 05 032 1405032 SABAK AUH 14 05 025 1405025 KOTO GASIB 14 05 024 1405024 LUBUK DALAM
Pumps cartography is useful in many ways in OSM and currently practiced around water wells. It’s possible to use the pump=* key to state for a pump availability on a given well only. The key actually refers to the pump drivers, a motor or a lever to manually move the pump. It’s an important information as to know if you’ll be able to get water with or without physical effort. For instance, it’s not yet possible to make a significant distinction between pumps running on electricity or gasoline engines among other possibilities.
Pumps are obvious but complex devices. Wikipedia already provides a comprehensive classification with up to 15 different kinds.
Each design have different capabilities and can be driven by numerous different drivers. OSM could get benefits from encouraging mappers to complete such detailed information with appropriate tags if they are knowledgeable to do so. It’s clear that such information will help crisis management or emergency rescue teams to restore water supply if and only if they have appropriate generators or engines. Coming around a gasoline powered pump with a solar panel won’t help. People themselves could be interested in case they have to bring their own material to get water.
A water well in Mali operating with manual piston pump. It’s proposed to use this new tagging, on a node :
Currently, using word ‘‘pump’’ to deal with actual drivers could be confusing and worth a try to change toward a more appropriate terminology. It’s an opportunity to allow pump mapping in many more situations than water wells. Current pump=* really focuses on water wells only. Ability to make a distinction between manual and powered pumps is still possible depending on knowledge level of mappers, using mechanical_driver=powered if necessary.
Here it is a proposal started in early 2020 and now open to vote; It was designed with wikipedia classification in mind
It’s starting to work… https://wiki.openstreetmap.org/wiki/Import/FrenchPostOfficeOpeningHours generated https://www.openstreetmap.org/changeset/94525770, first fully automated upload.
OSM if full of different characters and identities, so I want to know…
Today we have organised a training workshop on OpenStreetMap from Khulna University. Respected, Sawan Shariar ( Regional Ambassador, YouthMappers) conducted this training.
A group of HOT voting members, from across four continents) met on Tuesday evening as part of the HOT board’s strategy committee to discuss perspectives on community definitions and what we mean when we talk about community sustainability. These conversations are really pertinent at the moment as HOT begins to develop and implement the Audacious project, which provides a real opportunity to support local communities to power up as well as generate high quality OSM data in 94 countries.
It was acknowledged that HOT is many different things to different people. It was thought to both be a network or community (including volunteers and contributors, staff, humanitarian data users) and a node in other networks (where it was felt that HOT sometimes plays an important facilitation role). It was also suggested to be a (niche) social network, used for finding and developing information, knowledge, tools and relationships.
It was also perceived as a sub-community of the OpenStreetMap and as an NGO.
Whilst there were many positive attributes associated with HOT (diverse, collaborative, oriented to social good), it was also felt that HOT was sometimes a label applied too easily to contributors and communities in its networks, without thought for how they might define themselves. For example, the use of the phrase ‘HOT community’ to encompass any group doing humanitarian work involving OSM (or ‘HOT edits’ for any OSM contributions through the Tasking Manager) can be perceived as HOT staking an undeserved claim over the work of others and not indicative of a collaborative node in a network.
There was less discussion around this question. Partly, because the group seemed fairly aligned on the definition but also, partly because of my poor phrasing of the question. ‘What is a local OSM community?’ would have been a more accurate question and this was probably a missed opportunity.
In its broadest sense, the definition was contributors and users of OpenStreetMap data but it was agreed that within this definition a myriad of communities and special interest groups exist.
I group these together because the discussions overlapped to a large degree.
There was a strong alignment that Audacious should prioritise support to communities who wanted to use OSM to solve local problems, regardless of whether they were already affiliated to OSM, HOT or other actors in the network.
It was also broadly agreed that priority should be given to supporting existing communities and organisations in trying to solve these problems as this would also lead to greater chance of sustainability in the medium-long term.
It was suggested that data collection or generation needed to take place on the terms of the communities involved in order that it was, firstly, useful and, secondly, sustainable. In the same vein, support to communities should help them develop the power to innovate and evolve in whatever way they see fit (masters of their own OSM destinies).
Data users came up as important in both discussions in the sense that, without an ecosystem in which OSM data was used and valued locally, it could be unlikely that use of OSM would be sustained in the long term (demand being important as well as the supply).
Economic benefits were also discussed, with professional opportunities related to OSM, open data and GIS highlighted as a potential major driver for individuals (e.g. professionals and entrepreneurs) and collectives (e.g. local NGOs, community-based organisations and startups), especially acknowledging that, in the areas where the Audacious project will be focus, unemployment and poverty are significant and interlocking issues.
There was alignment that, for the Audacious project to be successful, tools, systems, networks, strategies, etc need to be grounded in a networked, community approach and not reliant on HOT (the NGO) by the end of the five years (i.e. the term of the Audacious project).
Finally, it was expressed that people involved need to be inspired and excited through engaging with OSM and humanitarian OpenStreetMap communities and networks if they are to continue to develop the OSM project and their part in it!
This was a small group conversation and only the start of this particular conversation. The next iteration will hopefully be hosted by the community working group (to be discussed at next week’s meeting). In the meantime, happy to hear comments, questions, constructive criticisms and alternative points of view.
Якби JOSM був би написаний не на джаві, а на плюсах… Тормозить, зараза
This afternoon I did front & left camera Mapillary capture around the block in Bandar Bukit TInggi near Healthlane Pharmacy. Unfortunately the usual afternoon rain intervened just after I started capturing. Don’t know whether the images are useable, but I’m uploading it first.
Current
Hoe kan ik zien dat een route is geblokkeerd als gevolg van verouderde data? In Middenmeer wordt ik een aantal malen zeer onlogisch weg geleid van logische route alsof de door mij gekozen straat is afgesloten of geblokkeerd. Het betreft hier de Wilgenlaan in Middenmeer tussen de Hoornseweg en de Plataanlaan. I.P.V. de route over te nemen over de Wilgenlaan wordt er een aantal malen heel krampachtig, via de Esdoornlaan en de Meidoornlaan gepoogd om te leiden naar de Dr. Hoogkamerlaan en dat is volstrekt onlogisch en maak de reistijd langer. De standaard begeleiding (gekozen eindpunt is Kokkel 1 Middenmeer) wil dat je via de prof. ter Veenweg en de Prof. Colijnstraat gaat. Als je een iets grotere wagen hebt (busjes e.d.) is dat in elk geval al een heel ongelukkige keuze maar je hebt op deze route via de Colijnstraat en dan de verlengde Breestraat en Plataanlaan veel obstakels en tegenliggers waarvoor je steeds moet stoppen of vertragen en als je via de Wilgenlaan zou gaan heb je dat helemaal niet dus is de reis sneller.
I had trouble using the existing libraries with OAuth. I first started Implementing the methods I directly needed. The size increased and I thought I would be easier to make that a separate Project. Now I’m done Implementing all of the OSM API 0.6 the you find the project at Github or on PyPi I would love to hear some Feedback from you, either here via PM or on github open an Issue.
You can now download a development version of Potlatch 3.0 to run on your desktop.
At https://www.systemed.net/potlatch/download/ , you can download a Mac native app, or an AIR file for use on Windows or (possibly) Linux.
Potlatch 3.0 includes desktop-editing features such as Remote Control support, overview zoom levels, and an OAuth login flow for saving. Rendering is faster and there’s now Overpass API support in the tasks palette.
Installation on Linux is likely to be complex and I’d welcome reports from anyone who has successfully achieved it.
There’s much more to come in future weeks so watch this space. You can report issues at http://github.com/systemed/potlatch2/issues pending the creation of a dedicated 3.0 repository.
https://weeklyosm.eu/ru/archives/13945
Все благодарности Влад a3563 Perm. Спасибо что делаешь переводы.
Вы можете предложить новость в ЕженедельникОСМ!
У вас уже есть логин OpenStreetMap осталось всего 3 шага:
Заметили ли какую-нибудь интересную новость? Откройте наш сайт
Вставьте ссылку в строку поиска и щёлкните “Поиск”. OSMBC проверит вдруг эту ссылку уже добавляли. Далее нужно выбрать категорию для новости и описать о чём статья. Если у вас есть ещё одна ссылка, которую нужно добавить, пожалуйста, добавьте её.
Вы можете предложить текст статьи или нажмите Сохранить.
Готово! В редакционной системе OSMBC есть ваша статья! Затем команда просматривает фильтрует, при необходимости выберет категорию, пишет (если не написано) и переводит статьи на другие языки. Также проведёт окончательную проверку для поддержания качества.
Couple of days ago, one of my fellow undergraduate student told me that Sumatera Island is missing …wew .. looking forward to investigate it …
