Mapillary is a location-photo-sharing site dedicated to inter-working with OSM & I like it a lot.

Mapillary is the street-level imagery platform that uses computer vision to fix the world’s maps.
450.7 million images; 6.5 million kilometers covered

I am registered on Mapillary since Apr 10, 2016 and it tells me that in that time I have uploaded 6,200 photographs shot whilst walking across 244.7 km of Nottingham’s suburbs. Most of those photos are registered as links with various PoI on the map, which means that someone browsing OSM can find a link attached to a Nottingham point-of-interest that will instantly let them see a blurred photo of what it looks like 32% of the time.

Blurred Photos

At the moment that I am writing these words the following photo has 33 auto-blurs attached to it, 32 of which affect the street-sign on the right (the 33rd is on the brickwork to the right):–

At this moment I am going through each & every one of those 6200 photos removing the stupid-blurs. Nothing will happen until at least next Monday (11 Feb), as all the blur-removals are actually blur-removal requests (a Mapillary admin has to agree/refuse the request).

33 blurs is bad, but not the worst - one photo had more than 40 blurs (a patch of shrubbery) (whilst another just now had 45 all on top of another street sign), all of which were stupid-blurs.

So what is going on?

Mapillary has always edited uploaded images before showing them:–

What Mapillary blurs:

• Faces
• Vehicle license plates
• Inappropriate or private parts of the image

What Mapillary does not blur:

• Whole people
• People from behind when the face is not seen
• Billboards, advertisements, brand labels
• Street, traffic and information signs

So what is the problem?

I have zero problem with Mapillary enforcing privacy blurs. I’ve dealt with too many MPGs spontaneously combusting just because I’m stood outside their house asking if I may take a photo of their house-name not to know that the English have a particular issue with Google StreetView (if you get my drift through all those disparate topics).

In the early days Mapillary kept blurring out street-signs, and it has taken quite a few years for them to stop doing that. Most of the time now it seems to work OK. However, the Blur Algorithm appears to have recently been put onto steroids, in that it is blurring areas so small that they can barely be seen. Worse, the programming has schoolboy-level errors; as just one example, some of the street-sign blurs are quite large yet inside that area may be yet another 5 smaller blurs - what is the point of that?

Look at the photo below; it is the example used in the help-page to illustrate what the privacy-blur edit-page looks like. Those orange/green/white numbered circles locate the presence of a blur enabled by the Mapillary privacy-bot.

Each blur has to be removed one-by-one using a mouse, no keyboard allowed. This is tedium ratched-up to mind-numbing proportions.

1. Hover over a blur
2. Move the mouse up to a combo of green tick✔ + orange cross✘ that then appears
3. Hover over & click on the cross
   (maybe you are hovering over the cross, maybe not)
4. Next blur…

My constant experience across the last two days has included a bunch of 5-or-more of those circles located on top of each other in such a fashion that I cannot click on the ones underneath. Or of circles located under image navigation features (arrows & chevrons, forward/back arrows or attribution-feature); those are all located in top-of-z-order, which means that nothing underneath them can be clicked on. These are what I am calling “stupid-blurs”.

The Modified Date for the Blur Help Page is January 09, 2019 13:01 (there is a set of blurs on all earlier photos in addition to these recent blurs; those earlier blurs are no longer editable). I therefore assume that the blur-bot was very recently unleashed on all 451m Mapillary photos to enforce further blurs. Or, more accurately, further stupid-blurs. Get more intelligent more quickly, please, Mapillary-bot!

Stats

Being a scientist I thought some measure of the problems was required.

I’m working my way from latest to earliest and have already gone through 26 sets of photos. Here are the accumulated stats from the 27ᵗʰ set of 111 photos, shot on 31 January 2017 in the streets near Phoenix Avenue close to Gedling:–

• Total photos: 111
• Contains blurs: 35 (32%)
  (following applies to blurred photos only)
• smallest # blurs: 1
• largest # blurs: 25
• Total blurs: 233 (avg: 7/photo)
• Valid blurs: 19 (8%)
• Stupid blurs: 214 (92%)

Addendum

Tues 12 Feb: Mapillary have sent me an email to say that the team is looking at it.

Krótka prezentacja możliwości OSM. Zdjęcia i dane kontaktowe do firm sklepów restauracji hoteli linki do dokładnych opracowań na temat zabytków w mieście ( nie tylko Wikipedia) , rozkłady jazdy , zdjęcia dowolnego obiektu naniesionego na mapę , murale i graffiti , Filmowe przewodniki po najciekawszych atrakcjach, Filmy z dona przypięte do interesujących budynków i miejsc wszystko to dostępne w prawo-kliku myszy. https://youtu.be/FGANRXZWiYM Można też skorzystać z wyszukiwarki punktów POI które nas interesują http://openpoimap.org/

Following our planned schedule to host a forthrightly webinar training session for all the teams I created and OSMNigeria Community,we successfully held our first webinar today. Agenda for the meeting include: 1 . Briefing from OSMNigeria Coordinator (Victor N.SUnday) 2 . OSM Communities-Local and global 3 . HOT Working Groups 4 . OSM Africa 5 , Mapping Tasks 6 . Brief from HOT Community Staff /Board Representative available 7 . Questions and Answer Session 8 . Review of past topics

It was great having participants and team coordinators/leaders of the various teams/local communities in attendance. Thank you so much Trudy Hope for showing up with a short notice via whatsApp message ,your presence and briefing were inspiring !!! Trudy Hope ,being a board Director of HOT was able to share good ideas to boost our growing community..And to my brother from another country Peter Johannes,you are always amazing ,showing up as a senior mentor so close to OSM activities and progress in Nigeria,thank you for coming on board to make our day. And to my OSMNigeria Community assistant ,Chukwuma Okolie, of Unilagmappersteam,you did a very nice and brief review of our previous webinar training.Thank you @Ikenna of AbsuMappersTeam and Saviour of UniqueMappersTeam Network.You all did a nice job!!! Look forward to working with you guys always to impact and grow #UniqueMappersTeam Network and #OSMNigeria.Cheers

Just finished the first OSM Nigeria in-house webinar meeting Had in attendance: 1. Johannes peter from Tanzania 2. Gertrude Hope from Gambia Amongst others We reviewed all the trainings of 2018 (done by Chukwuma Okolie #UniLagMappersTeam. 1. HOT Tasking manager 2. ODK and OMK 3. Teach OSM etc. An overview of areas where mappers can find relevance 1. Youth mappers 2. OSMF 3. HOT OSM

This past few months I have been noticing the erection of road name signs in the South of Fermanagh, which is great progress if you ignore the outrageous costs involved!

So I decided to ask my Council (Fermanagh and Omagh District Council or FODC for short) if they would consider allowing me access to the list of Roadnames so I could try and improve them on OSM. Needless to say I was shocked and stunned by their offer to release the data under an Open Licence for everyone to use!!

Although this is only the first phase of the project working along A and B class roads in Fermanagh, I am assured that once the next phase is complete they will publish these as well.

I would like to thanks SK53 for his work on converting the Irish grid co-ordinates and displaying the sign data on uMap. You can see his map here.

Please, review https://wiki.openstreetmap.org/wiki/Key:opening_hours before adding the opening_hours=* tag. If you don’t follow the syntax on the wiki, the software that actually uses the data just sees gibberish.

True examples of bad data I’ve just cleaned up today, with my comments after:

• opening_hours=Varies (use “unknown” instead of truly unknown, or open-end syntax if variable beyond a fixed known range)
• opening_hours=MWF 08:00-17:00; TT 10:00-19:00 (this can’t be automatically fixed by JOSM’s validator and has to be fixed by hand)
• opening_hours=Closed since 2008 (nope, this isn’t valid per the syntax either. “closed” by itself, maybe, but in that case the amenity/shop/office should probably just be untagged with a note in description=*).
• opening_hours: 08:00-24:00 pharmacy Mo-Fr 10:00-18:00; Sa 12:00-18:00 (either tag the pharmacy itself on a separate node, or use something like opening_hours:pharmacy=*)

Note that iD will not warn you of opening_hours syntax violations (in fact, as best I remember it will not check anything), it will happily let you put any kind of garbage you want in there. Maybe it should, though? How should we raise awareness that one can’t just slop any old junk in opening_hours in order for it to remain useful?

tl;dr the release notes 🙂

If you go to maproulette.org now, you will be greeted with the latest point release: 3.1.3. This is likely the final public release before 3.2, which will be a bigger one featuring a design refresh among other things! For now though, let me summarize the highlights of the 3.1.3 release.

Translations

MapRoulette is now available in Korean, thanks Dongha Hwang!

The Japanese translation was updated to fix minor typos. MapRoulette is now available in 7 languages. If you want to contribute a translation file, have a look at the pull request for the Korean translation to get started. Don’t hesitate to ask if you get stuck!

Task Styling

Thanks to a pull request by Ilya Zverev, MapRoulette now lets you style the appearance of your tasks on the map using the simplestyle standard devised by Mapbox. They have a simple example in their documentation to give you an idea of how to apply styling using simplestyle.

Leaderboard Updates

Have you been fixing tasks in say, the United Kingdom and feel like you deserve some credit for it? Now you can point your friends to the new country Leaderboard and show off your hard work. We use bounding boxes for the countries, so it’s not an exact science, but pretty close in many cases. Another new thing you can do in the Leaderboards is load more results after you scroll down to the bottom. And you may like that we will now always show your place in the leaderboard even if you’re way down.

Other Updates

As usual, there’s more: new keyboard shortcuts, a new search shortcut, display tweaks. Read the full release notes for that. Happy mapping!

A few days ago, Ivan Seoane showed me weblate - an open source translation management system. Very nice and very suitable for OpenStreetBrowser. I installed it right away, you can find it here: https://weblate.openstreetbrowser.org. Also, Ivan is working on the translation for Galician, which is already available.

Be aware, that authentication is not connected to any other service (like OpenStreetMap, OpenStreetBrowser Dev, Github, Weblate), so you need a separate account there.

Not all parts of OpenStreetBrowser can be translated there, e.g. date formats have their own separate repository, as you have to actually produce code (it’s just too complex).

Moments u4y0u via Twitter umap communication régions & energie régions. ( <- à voir pour autres régions)

pour mémo: Comm.Centre (http://u.osmfr.org/m/229792/) Energie Centre (http://u.osmfr.org/m/235209/) …

Orléans Métropole sécurité

Data center France

This is also published on DEARPAUL24 Facebook Page and DEARPAUL24 Online Portal

Accessibility Status

Under BP 344, it is required for certain buildings and infrastructures to enhance the mobility of Persons with Disabilities by installing facilities and other devices (ramps, elevators/lifts). However, most sidewalks are not maintained and sometimes, wheelchair ramps and sidewalks got obstructed by debris, illegally parked vehicles, and illegal vendors. By mapping sidewalks (alongside highway/roadway) as foot=designated and foot=no for highway/roadway (due to certain Anti-Jaywalking laws where MMDA have even planned to include in the NBI records as derogatory behavior, and for public safety sake), the public will recognize the OSM efforts as humanitarian-friendly, especially in some parts of Metro Manila and Cavite where footbridges are to be mapped accordingly.

Similarly, elevators have to be mapped for easier mobility of Persons with Disabilities, even inside the building structure with the appropriate highway=corridor and indoor=yes footway attribute, and for footbridges, the standard layering will apply.

Bus Routes

Here are the following lists of updated Bus Routes as of 07 February 2019, and may subject to change anytime due to addendum from the Department of Transportation, Land Transportation Office, and Land Transportation Franchising and Regulatory Board:

Commuter Bus (C)

• Makati City - Taguig City/BGC [a la P2P]
• Makati City - Taguig City/McKinley Hill [1] [a la P2P]
• PITX - Bacoor City - Cavite City
• PITX - Dasmarinas City/Pala-Pala [A, B, C]
• PITX - Dasmarinas City - General Trias City/Manggahan [A, B, C]
• PITX - Dasmarinas City - Silang [A, B, C]
• PITX - EDSA - Navotas City [A, B, C]
• PITX - EDSA - Quezon City/Fairview ** via Buendia/Ayala Avenue or Pasay City [A, B, C]
• PITX - EDSA - Quezon City/Grotto [A, B, C]
• PITX - EDSA - Quezon City/Monumento [A, B, C]
• PITX - EDSA - Quezon City/Novaliches [A, B, C]
• PITX - EDSA - Quezon City/Sapang Palay [A, B, C]
• PITX - EDSA - Valenzuela City/Malanday [A, B, C]
• PITX - Lancaster New City [a la P2P]

Light Bus (L)

NOTE: This may be also called Modern Jeep, Modern PUV, or other similar names; and may be equipped with Air Conditioning Unit (ACU) on selected units

• Marikina City/Parang Village - Manila City/Stop and Shop operated by BEEP Program
• Marikina City/Silangan - Quezon City/Cubao operated by BEEP Program
• Marikina City/SSS Village - Manila City/Stop and Shop operated by BEEP Program
• PITX - Bacoor City - Dasmarinas City/Paliparan Site [1] [E]
• PITX - Imus City/Bayan Luma
• PITX - Manila City/Lawton operated by EcoDyip, Inc.
• PITX - Paranaque City/Sucat
• PITX - Pasay City/Buendia operated by SETSCO
• PITX - Pasay City/GSIS Complex operated by SETSCO
• PITX - Tanza [E]
• PITX - Taguig City/Bicutan ** via East or West Service Road
• Quezon City/Eastwood - Pasig City/Capitol Commons operated by EcoDyip, Inc.
• Quezon City/Lagro - Cubao operated by BEEP Program

Point-to-Point Bus (P2P)

• Antipolo City/SM Cherry - Makati City/Greenbelt 5
• Bacoor City - Makati City/CBD [2]
• Bacoor City - Muntinlupa City/Alabang
• Clark - NAIA Terminals
• Clark - Quezon City/North EDSA/Trinoma
• Dasmarinas City - Makati City/CBD [2]
• Dasmarinas City - Muntinlupa City/Alabang
• Las Pinas City - Makati City/CBD
• Makati City/Glorietta 3 - Paranaque City/Sucat/Meralco Road
• Manila City/Robinsons Place - NAIA Terminals
• Masinag/SM - Makati City/Greenbelt 5
• Muntinlupa City/Alabang - Mandaluyong City/Shaw
• Muntinlupa City/Alabang - Taguig City/BGC/Market Market
• Muntinlupa City/Alabang/Town Center - Makati City/Greenbelt 1
• Muntinlupa City/Alabang/Town Center - Manila City/Lawton
• Muntinlupa City/Alabang/Town Center - NAIA Terminals
• Noveleta - Makati City/CBD
• PITX - Makati City
• PITX - NAIA Terminals
• PITX - Quezon City/Ortigas/Robinsons Galleria
• Quezon City/Cubao - NAIA Terminals
• Quezon City/Eastwood - Makati City
• Quezon City/North EDSA/SM - Mandaluyong City/SM Megamall
• Quezon City/Ortigas/Robinsons Galleria - NAIA Terminals
• Quezon City/North EDSA/Trinoma - Ayala Park Square
• Santa Rosa City/Nuvali - Makati City

Provincial Bus/Long-Distance (P)

• PITX - Naic
• PITX - Tagaytay City - Alfonso
• PITX - Tagaytay City - Amadeo
• PITX - Tagaytay City - Balayan
• PITX - Tagaytay City - Calatagan
• PITX - Tagaytay City - Nasugbu-Lian
• PITX - Trece Martires City - Indang
• PITX - Ternate - Nasugbu

Source: Department of Transportation; BEEP Program/1UTAK; Sakay.ph

Rail Routes

Here are the following lists of updated Rail Routes as of 10 February 2019 where the upcoming MRT Lines and ongoing PNR Rehabilitation will revitalize the railway network:

Mega Manila MRT Lines

• LRT-1 (North-South; Niog - Baclaran - Monumento - North EDSA Interchange) -> ongoing South expansion and future interchange construction
• MRT-2 (East-West; Pier 4 - Recto - Santolan - Masinag) -> ongoing East expansion
• MRT-3 (EDSA; Taft - North EDSA) -> ongoing future interchange construction
• LRT-4 (Ortigas - Taytay) -> ongoing proposal
• MRT-5 (Makati City Subway; Ayala Interchange - University of Makati) -> ongoing construction
• LRT-6 (Aguinaldo; Dasmarinas - Niog) -> ongoing proposal
• MRT-7 (Northeast; North EDSA Interchange - San Jose Del Monte) -> ongoing construction, including future interchange
• MRT-8 (East-West; Lerma - UP Diliman) -> ongoing proposal
• MRT-9 (Metro Manila Subway; Dasmarinas - FTI - Mindanao/Quirino - Bulacan with NAIA Spur Line) -> ongoing construction for North EDSA - Mindanao/Quirino, including future interchange

Luzon Rail Network (PNR)

• Northrail (Tutuban - Malolos - Clark) -> ongoing rehabilitation
• Southrail (Tutuban - Calamba - Bicol)

Mindanao Rail Network

• Circumferential Line Phase 1 (Tagum - Davao - Digos)

Source: Department of Transportation; Build Build Build Program

NOTES

[1] - Don’t be confused with the resettlement village and the literal translation to ‘airport’; hence, the grounds for renaming into Bacoor-Dasmarinas National Road by law to avert confusion

[2] - Electronic Payments Only; No Cash Accepted

[E] - Commuter or Express, depending on demand

[a la P2P] - Designated Bus Stops only

[A B C] - Bus Segregation Scheme with Designated Bus Stops

องค์กรที่ก่อตั้งขึ้นโดยการมาแก้ปัญหาด้านต่างๆ ของประชาชนที่ทำอาชีกเกษตรกร

大臺北：

• 819副
• 886
• 846
• 826

基隆北海岸：

• 2025
• 787
• 1061
• 602
• 862

“2019 YouthMappers Leadership Fellowship”, it’s just a simple sentence, but I could not measure its weight because for me, it is immeasurable.

The 2nd bi-annual YouthMappers Leadership Fellowship Workshop was held from 6 -14 January 2019 in Pretoria, South Africa. It was a great feeling to be one of the selected fellows for this unique opportunity. The workshop focused on skill building, increasing youth leadership, enhancing open mapping techniques, data visualization, and professional development. The first half of the week included presentations on the history of YouthMappers, an introduction on OSM in the classroom, and presentations by our hosts at the University of Pretoria on their research that provide local context on South Africa as a collaboratory.

We engaged in discussions, lab exercises, and a field visit to use open mapping platforms. Sessions in the second week focused on professional development training, using data in the real world, mobile applications for development, and reinforcing chapter sustainability. The University of Pretoria organized a team building activity at Maropeng and the Sterkfontein Caves. On this day, we explored early human history & nature and it was unforgettable.

The most important thing that I have learned is to think big in a simple ways because simple is the best. This workshop helped me to widen my range of thinking. And the mantra I liked most is “Teamwork makes the dream work”.

We were provided an agenda before the workshop and received a detailed agenda on the very first day but I have learned much more than what was listed, several times multiplied from that list. I learned something from every single moment and from every single person who was there. Our group was made up of people from different countries, different thoughts, different things, lots of experiences to exchange and this inspired me and motivated me.

I met some fantastic guys who were just awesome. The friendly attitude from the YouthMappers staff was a matter of wonder for me to see. They never made us feel that they are professors or a higher rank person of a prominent organization, they always acted like a friend, advised us about right things, and were always ready to help us if we needed anything. They even played UNO with us (a card game our Colombia Fellow Fabio brought), danced with us, and had fun with us. Every day we had to get up early at 6 am but we up until 11/11:30 pm at night chatting and sharing stories.

And the fellows…. I will say just one word, those guys are just tremendous. We were together just for 9 days but I felt each day as if it was a week. I think I am so lucky that I am a part of this amazing cohort. I will not forget those evenings, each one full of fun and I am especially thankful for their friendship. During the workshop, our friendship came to become so strong that it was hard and emotional on the last day when we were saying bye to each other. I wish to meet you guys again and again. I traveled to South Africa with a small bag but at the time of returning, I was carrying a large package of experience, memories and happiness.

I would like to thank YouthMappers, the University of Pretoria, and the USAIDGeoCenter for organizing such a wonderful workshop!

This is a another small update to a sequence of posts on updating some small leaflets originally produced by Andy Allan:–

1. Fonts missing from OSM Promotional Leaflets
2. Github HowTo: Clone Repository then make a Pull Request
3. Printing OSM Promotional Leaflets
4. Update to OSM Promotional Leaflets due to Padding errors
5. Adding a Preview JPG + crop-marks for printing

This is how to add crop-marks and bleed-marks to a production-PDF for printing (the PDFs within GitHub do NOT currently contain any crop-marks and, whilst they contain 3mm bleed, they do NOT contain bleed marks either):–

1. Load your production-ready SVG into Inkscape
   (see earlier pages for links if you need to install)
2. Under r15371 (the most recent) go Extensions | Render | Layout | Printing Marks…
3. Put ticks in Marks | Crop Marks + Marks | Bleed Marks

4. On Positioning tab set:

     Set crop marks = `Canvas`
     Set       unit = `mm`
     Set     offset = `0.000`
     Bleed Margin
             Top    = `3.000`
             Bottom = `3.000`
             Left   = `3.000`
             Right  = `3.000`    
   

5. Click ✔Apply (and wait a little while it works)

You will see that both options in the JPEG above contain both sets of marks; that is really quick & easy to produce.

This was a temporary edit as I was simply producing two PNGs for a preview image of the 2 options for the leaflet front (the printers had asked for 3mm bleed but NOT for crop-marks). As a final visual guide I added 3 x vertical dotted-lines to show where the leaftet is folded. The next step is to export the finished product as a PNG file.

Exporting is easy, but the range of options is a little terrifying. Fortunately the defaults worked:

1. Select File | Export PNG Image…
   (a dialog appears)
2. Select Drawing as Export area (after checking that dimensions are correct under Page)

After setting a name (I left the default of name.svg.png) all the other defaults proved to be correct. That was NOT a coincidence. I had previously taken every precaution to make the page-size accurate, then apply (internal) 4mm padding + make (external) 3mm margin available (which is the bleed, set when the PDF is produced, although more than that actually exists). Thus, the defaults were all setup accurately.

Finally, push ✔Export and check the result (there is zero confirmation from Inkscape).

I used GIMP to put the two PNGs together and exported as a JPEG. The GIMP master file has been uploaded to try to make it easy for anyone that wants to make changes. The whole thing has been pushed to GitHub as a further commit. I hope that some will find it useful.

Good luck!

PS
This looks like a good link if considering PDFs & crop-marks (the summary is: “PDFs are best for printers, use crop-marks but no others, use 300dpi for raster items”). It also said “Acrobat Reader is the best application to use when opening and viewing a PDF file.”. I almost spat tea all over my monitor when I read that. It points out that printers will probably get in a huff if you include colour registrations, etc. (I thought that they looked splendid, but would not be included in the PDF in any case since they are located outside of the bleed).

Modern SVGs use 96dpi. The ones used by Inkscape r9886 (the latest version available when Andy first designed these leaflets) used 90 dpi. That change from 90dpi to 96dpi caused hours & hours of re-formatting when I updated the whole GitHub package from r9886 to the current r15371.

It makes sense when printing to go down in resolution if needed for some reason, but you cannot go up in resolution and then see any actual difference in the end product. That means that, if the PDF is going to contain any raster images (and PNG are raster images), then the SVG source files will need to reference 300dpi images to get a 300dpi end product.

To try to get a measure of the problem:

$ identify globe_part_halo.png london.png    
globe_part_halo.png PNG 3208x3880 3208x3880+0+0 8-bit sRGB 8.236MB 0.000u 0:00.000
london.png PNG 2479x1356 2479x1356+0+0 8-bit sRGB 2.119MB 0.000u 0:00.000

pixelto conversions at 96dpi + 300dpi
(leaflet pages are 73mm wide x 105mm high):

pixels    96dpi  300dpi
------  -------  ------
 3,880  1,027mm   329mm
 2,479    656mm   210mm

It looks like it should be possible to use the current source files to print at 300dpi but I am unsure of the methodology to get from the current SVG dpi to PDF dpi. Advice appreciated.

He decidido dejar de colaborar con la comunidad OSM España. Dado que OpenStreetMap es un proyecto que se articula en base a comunidades locales, esto supone que mi colaboración con el proyecto se verá reducida notablemente. De hecho, no creo que vuelva a aportar nada al mapa a partir de este momento. También he dejado de colaborar en la traducción del Wiki en español y he abandonado el proyecto de importación de edificios en Málaga.

P. D. (2018-02-08): Para evitar que nadie más tenga que verse obligado a escribirme un mensaje privado para conocer los motivos de mi abandono, adjunto una de mis respuestas, más o menos similares todas ellas, a colaboradores que me han escrito y se han interesado personalmente por conocer los detalles.

Hola, *****. Gracias por tu interés.

Sería largo de explicar. Puedes leer mi último mensaje en el foro de la comunidad o también este otro, aunque el asunto viene de lejos, no es solo por la decisión de ocultar los topónimos en español. Ya ha ocurrido antes con otros temas y bajo los mismos prejuicios y motivaciones políticas. Tienes que ponerte en el contexto de la situación política en España para entender el fondo de estas motivaciones espurias.

No es la primera vez que este tipo de discusiones se producen en el seno de la comunidad en sus distintos canales de contacto. La pasividad de la comunidad en estas discusiones, por no decir la aprobación tácita de estos prejuicios, como en alguna ocasión ha ocurrido, es muy lamentable. Lo último ha sido que me censurasen mensajes en uno de sus canales de contacto. Eliminar mis mensajes injustamente es solo una anécdota, pero es una anécdota grave. Según se me ha dicho, me eliminaron los mensajes por su «contenido político e ideológico». Eso es absolutamente falso.

Yo nunca he compartido comentario político alguno en esos foros, comentarios que por su contenido o por sus motivaciones ajenas al proyecto pudiesen crear división en la comunidad. Nunca es nunca. Fíjate si será así, que otro colaborador criticaba recientemente en este mensaje mi posición radicalmente en contra de mezclar la política con OSM. Pues sí, esa ha sido siempre mi posición: dejar las motivaciones políticas e ideológicas fuera de OSM. Puedes revisar mis comentarios en todos los espacios en los que he participado. No encontrarás nada que cree división en la comunidad en ese sentido, más bien al contrario. Otros no pueden decir lo mismo, y pese a ello, no he visto que se censurasen sus mensajes en ningún momento, ni la ultima vez ni nunca. Por otro lado, prácticamente nadie responde adecuadamente a las afirmaciones prejuiciosas, ya sea sobre cuestiones lingüísticas o sobre cualquier otro tema.

La comunidad española de OSM mantiene una actitud pasiva frente a los prejuicios políticos e ideológicos de algunos de sus miembros. Lo hacen, según me han dicho, para evitar la polémica y favorecer el dinamismo. Permitir que estos prejuicios y estas motivaciones espurias prevalezcan y se reflejen luego en el mapa o en el wiki de OSM no es una buena política. Nos perjudica a todos, al bien común y a la razón. La pasividad de la comunidad, que no es tal, pues censura a quienes se oponen a estos planteamientos prejuiciosos, no es inocente.

He participado intensamente en la edición del mapa y en la edición del wiki intentando colaborar con la comunidad en todo lo que me ha sido posible. No tengo ningún prejuicio contra ninguna lengua. He colaborado particularmente en la traducción del wiki en español porque es la lengua que conozco de entre las que se hablan en España, pero nunca he dejado de animar a otros colaboradores a que traduzcan el wiki al gallego, al catálan o a cualquier otra lengua, oficial o no, de las que se hablan en el marco de nuestro proyecto (sin mucho éxito). Si conociera todas esas lenguas, lo habría hecho yo mismo.

Este abuso sobre lo que se puede o no se puede decir, sobre lo que debe o no debe aparecer en el mapa en según que lenguas, esta malsana inclinación a imponer desde presupuestos políticos e ideológicos, o desde decisiones arbitrarias de una comunidad de mapeadores que no tiene autoridad alguna para hacerlo, la forma en que las personas conocen y reconocen el mundo en su propia lengua (o en la lengua que les dé la gana), incluidos los topónimos (nombres de lugares), es algo que me duele especialmente. En mi opinión, es una atentado contra los derechos más elementales de la persona.

Aunque el proyecto de OSM sea global y multilingüe, se articula a partir de las decisiones que toman sus comunidades locales, en nuestro caso, la comunidad OSM España. No me es posible seguir colaborando con esta comunidad en esta situación, mucho menos después de que se me haya censurado injustamente y sin el menor atisbo de rectificación.

En fin, dadas las explicaciones oportunas, espero que nada de esto te afecte en tu experiencia personal en OSM. Yo he abandonado el proyecto de forma definitiva. No es una decisión impulsiva, lo he pensado mucho. Lo lamento profundamente. No creo que lo que ha ocurrido y está ocurriendo en la comunidad española sea el espíritu que mantiene OSM en su conjunto, es más bien un problema de la comunidad local (espero).

Gracias de nuevo por tú interés, *****.

Feliz mapeo.

Cordialmente,

Daniel

Osm I’d: Abou kachongo Jr Joined Humanitarian open street Team as a digitezer since 2015, I have participated in various mapping project such as Dar es salaam Ramani huria with the propose to provide the basic map that shows all floods prones areas around Dar es salaam city, Tanzania minigrids, Zambia minigrids. Also I have participated in malaria project, Ebola project as well as Refugee’s mapping project and Facebook road import project.

Оказалось, что друг часто бывает в Каратабане. Начали заполнять, процесс пока медленно идёт.

Para ajudar a alinhar as imagens aéreas às trilhas GPS, é bom ter um bocado dessas últimas para que se possa fazer uma média para que os erros de GPS sejam pelo menos diminuídos. No entanto, com o baixo número de trilhas por estrada/rua (uma ou duas, três no máximo), não dá pra reduzir esse erro :/

Se você puder, passe com o carro / bike / a pé (cuidado com um ladrão) por aqui com o GPS ligado e mande essas trilhas para o OSM, por favor. Ajudaria um bocado.

Se puder passar na Av. Prefeito Severino Cabral (ou Av. Brasília, como é localmente conhecida), melhor ainda! (é por ali que eu mapeio, hehe)

Obrigado o/

Opa, pessoal o/

Continuando a atualização das ruas de mão única iniciada aqui…

Andei por aqui pelo bairro, tentando mapear toda a Rua Silva Jardim, que é em boa parte de mão única. No entanto, não me sinto seguro o suficiente para percorrer toda a rua, já que passa por uma parte da cidade meio suspeita. Então andei do ponto que ela se cruza com a Rua Dom Bosco, a sul, até o ponto que ela cruza com a Rua Joana D’arc.

A dúvida que fica é: Devo mapeá-la toda como oneway=yes, mesmo sem ter certeza se ela é completamente de mão única e assim garantir que usuários de gps automotivo, não sejam roteados pelo sentido errado OU ser mais seguro em relação à verdade e só mapear como de mão única o trecho que pude andar e verificar que realmente é de mão única?

Hi :)

Inspired by the ongoing uprising and protesting I started yesterday working on Khartoum to improve a few things. Since I am not a native arabic speaker I learned a few tricks and thought I would share them here.

names

We have a policy of locale names and that means the arabic terms should be in the name= field. This was not the case and a lot of arabic names seems to be missing. I added fixme’s to all the places that lack an arabic name tag. See for yourself on OSMI

Help wanted!

If you know arabic please help add the arabic names to the places linked above.

If you are working in JOSM and want to help with the names I encourage you to do this:

1. enable the expert mode in the settings
2. file->download data
3. switch to the new tab “download from overpass api”
4. click “wizard”
5. enter “place=*” and select khartoum on the area below
6. click “download”

This gives you all the places in the editor of your selected area ignoring all the rest of the data. :D I recommend using search and/or filter to narrow down if you need to.

Viewing a map in a different language

I used these to get an overview of the names:

• https://maps.wikimedia.org/?lang=ar#11/15.5842/32.5815
• https://maps.wikimedia.org/?lang=en#11/15.5842/32.5815

Does anyone know how often they are re-rendered?

landuse

I like to mark the different use of land se the render is able to color the map correctly. I added landuse=residential to existing areas where it made sense and created a few new ones. A lot more work is needed to tag parks, farmland etc.

multipolygons

This is not yet used in many places and the city could really benefit from an overhaul. There are a lot of neighbourhood-areas that overlap etc.

Happy mapping!