OpenStreetMap

Users' diaries

Recent diary entries

Public Transport Plugin

Posted by Polyglot on 1 July 2016 in English (English)

Mapping public transport routes on OpenStreetMap can be a challenge, keeping them correct and up-to-date even more so.

Last year I mentored the Mapillary plugin for GSoC and the idea started to ripe to do something similar for public transport.

I think automation is key, as without it, it's next to impossible to even find all the problems, let alone fix them. Also the way we're mapping public transport at the moment is very repetitive and fixing all those routes for all variations of the lines gets tedious fast. Which in turn results in very few people interested to do it.

At the moment the plugin is very good at detecting problems with the routes: * going against oneway traffic * gaps that are caused by wrongly ordered ways * routes that don't start/end on a stop_position node * ways that still need to be split on those terminal nodes

The latest addition is a dedicated layer, where the route for which a relation editor window has focus (is on top/active) gets highlighted.

One thing that I was never able to achieve with plain MapCSS is to show sequence numbers for the stops and the platforms. Another thing was showing the refs of the route relations serving those stops. All that becomes trivial if one can simply code it in, and Darya is doing a great job there.

#So, what's next?

The initial idea was to be able to start from a route relation containing just stops in the correct order and have the code figure out which ways to add to the relations. That will still happen, but fixing existing route relations and helping all mappers to keep the route relations 'healthy', when they make changes to the underlying highway/railway infrastructure seemed like a higher priority in May, so we started by integrating the plugin in the validator.

It's amazing how many problems I've already been able to solve with the routes, during beta testing.

#Want to try it?

You can easily install the PT_assistant plugin in JOSM and help with testing.

What I usually do, is File / Download from Overpass API (expert mode needs to be on for it to show in the menu)

Then use the following query:

[out:xml][timeout:125]; ( relation["public_transport:version"="2"]["route"="bus"]; ); (._;>;); out meta;

You can select routes for other modes of transport, of course.

After downloading, I make sure nothing is selected, the press the validate button.

If you have the plugin installed, you'll find several categories that start with PT_

The easiest ones to tackle are

Route contains gaps which can be solved by sorting

For those you can simply press the fix button. Don't select more than, say 5, at a time.

If your stops where not at the beginning of the route, now they will be. The order should be preserved.

Now press the upload button, which will result in a new validation

Usually you'll find there are more problems to solve at this point. For the routes that have ways going against oneway traffic, pressing the fix button will result in removal of that way. It's better to press right mouse button Zoom to problem, select the way(s) that have a yellow casing around them, then press right mouse button edit.

The relation editor will open with those ways selected in blue. Now it's possible to remove them, or to add oneway:bus=no, if that is the proper solution.

If you remove them, you probably want to readd ways from the other side of the dual carriageway or roundabout.

If you notice that there are several variations, which are likely to need the same fix, keep the 'problem ways' selected and open all of them in relation editor windows.

After all are opened select the ways to replace them with, and do this in each editor window.

Be careful not to split ways for which you have relation editor windows open. You'll get 'conflicted with yourself', which is something to avoid at all cost :-)

All this may seem like it's still a lot of manual work and you're right, it is. The intention is to automate all this further. I'll probably write a new diary entry in a few weeks about that.

If you're interested in a hangout about the mapping of public transport and the use of the plugin, get in touch and we'll set one up.

Nottingham in Spring

Posted by alexkemp on 1 July 2016 in English (English)

The photo below was shot in Carlton on the last day of June. Alistair Cooke (the British writer & presenter of Letter from America until his death in 2004) said that America was the best country to be in to witness Autumn/Fall, and Britain the best country for Springtime but, as we all know, in June the flowers do bloom.

Many thanks to the (unknown) householder at #12 for a wonderful display.

a gift from 12 Hasting Street

Location: Carlton, Arnold CP, Gedling, Nottinghamshire, East Midlands, England, United Kingdom

Colocando Nomes de Ruas nos Bairros do Jordão Alto, Jordão Baixo e Jardim Jordão, Bairros de Recife/PE.

Posted by raphaelmirc on 1 July 2016 in Brazilian Portuguese (Português do Brasil)

Bom Dia a todos,

Minha meta para hoje e mapear e adicionar nome de ruas nos bairros do Jordão Alto, Jordão Baixo e Jardim Jordão, todos bairros do Recife, Visitando os Bairros percebi que existe varias ruas sem nome e outras sem estrada, então resolvi mapear as mesmas e deixar esse conjunto de bairros todos com nomes, a outra meta é terminar de mapear o meu bairro e arredores, tendo em vista que são bairros muito próximos um dos outros e isso demora um pouco para ser completado, mais tenho certeza que terminarei e ainda mais com a ajuda dos amigos que estão me ajudando, tanto no grupo como no próprio mapa, corrigindo tudo que está errado e fazendo as melhorias, pois sou iniciante e já estou apaixonado por esse projeto maravilhoso.

Um forte abraço a todos, e mãos a obra.......

Raphaelmirc Recife/PE.

Finally, I've got the Hang of Mapillary

Posted by alexkemp on 1 July 2016 in English (English)

It has taken 4 months, but it seems that finally, yesterday, I may have got the hang of how to photograph a sequence for Mapillary that works.

  1. Photo of the top part of a terrace on Carlton Hill
    (click the down-arrow, twice)
  2. 2nd photo
  3. 3rd photo

With sufficient overlap between the frames Mapillary will stitch them together, then show them in an interesting way. In really slow motion. It's a good facility, which can be used to show stuff in a useful manner.

The terrace seems to be a typical Victorian terrace of 4 houses. However (and as the 1st photo shows below) for some reason it has a small-width extension at the left side which extends at an angle forward to the length of the terrace (scaffolding had been recently erected at that end of the terrace):

a single room extension?

The terrace itself is angled oddly to all the other houses. The extension doesn't appear to be wide enough for more than a set of stairs, yet is 2 floors high & about 10 foot (3m) deep. The strange angle of the extension is mirrored by the line of the gardens at the rear, and those gardens segue into a line of trees several hundred yards long. The whole thing is so mysterious that it's hardly true. I tried all 4 houses to find out more, but no-one was in.

Location: Bakersfield, Nottingham, East Midlands, England, NG12, United Kingdom

Andar por el Parque Natural Montes de Málaga

Posted by dcapillae on 30 June 2016 in Spanish (Español)

He comenzado a cartografiar el Parque Natural Montes de Málaga en OpenStreetMap (OSM), aprovechando tanto mi conocimiento sobre el terreno como la información disponible en Internet. Una de las primeras fuentes de consulta para empezar a cartografiar este espacio protegido son los mapas que proporciona la Junta de Andalucía a través de su red REDIAM: WMS Base cartográfica del mapa guía del Parque Natural Montes de Málaga del año 2012.

Lagar Don Ventura

Imagen: Lagar Don Ventura, en el Parque Natural Montes de Málaga (situación en OSM). Fuente: Wikimedia Commons, trabajo propio, (CC BY-SA 2.0).

Me propongo en primer lugar trazar todos los caminos y arroyos (he comenzado por la parte sur del parque). Paralelamente iré añadiendo otras informaciones, como la localización de caseríos y lagares, los senderos habilitados disponibles, la situación de miradores de interés turístico o paisajístico, zonas recreativas, etc. Una de mis primeras tareas de edición ha consistido en rectificar los límites exteriores del espacio protegido, que figuraban incorrectamente trazados en los mapas OSM.

El Parque Natural Montes de Málaga es un espacio relativamente virgen en OpenStreetMap en cuanto a información cartográfica se refiere, por lo que espero no molestar demasiado ni estropear el trabajo de otros colaboradores de OSM. Mi intención es ir aprendiendo a editar los mapas conforme voy ampliando la información cartográfica del parque. En este sentido, resulta muy útil consultar la OpenStreetMap Wiki para resolver dudas. De hecho, al mismo tiempo que voy editando los mapas, me he propuesto ir traduciendo algunos artículos de la wiki al español, particularmente aquellos relacionados con el senderismo.

Location: Parque Natural de los Montes de Málaga, Málaga, Provincia de Málaga, Andalucía, 29014, España

First entry; really "Hello world!"

Posted by schleuss on 30 June 2016 in English (English)

Hello, OpenStreetMap!

I'm about to write a post covering the community-building effort behind the Great L.A. County Building Import.

But first, an introduction is due.

My name is Jon Schleuss and I'm a reporter and graphic artist at the Los Angeles Times. I spend a lot of time making maps and analyzing data to find better ways to tell new and different stories.

I've been at the Times for about three years now. I've built maps showing where L.A. County's homeless live, where L.A. City's soft-story buildings are, where you can afford to rent or own based on your income and where the dirtiest streets are.

Before moving to the big city I lived briefly in Seattle working at the Seattle Times there. I'm from Arkansas and put in time at the Arkansas Democrat-Gazette and KUAF 91.3 FM, an NPR-affiliated station in Fayetteville.

techlady and Data411 introduced me to editing OpenStreetMap in 2015 and I've been a fiend every since.

My hope is to strengthen the southern California community, using the Times as a labratory and promoter of open-source work.

When I'm not mapping or at work I'm making pies and reading, programming or at the racetrack.

More to come soon!

Location: Historic Core District, Bunker Hill, Los Angeles, Los Angeles County, California, 90014, United States of America

Mapeamento de setores censitários em Santa Maria

Posted by santamariense on 30 June 2016 in Brazilian Portuguese (Português do Brasil)

Terminei já há alguns meses o mapeamento de Setores Censitários no município de Santa Maria, RS, Brasil.

Algumas curiosidades:

  • Muitas delimitações do IBGE estão muito desalinhadas
  • Existem buracos no mapa que não é coberto por nenhum setor censitário
  • Algumas vias do OSM pude então nomear segundo a descrição dos limites de setores censitários.
  • Dois setores censitários tem população Zero.
  • O setor com a maior predominância de homens é o compreendido por um presídio. 548 homens e 58 mulheres.

No próximo recenseamento estarei pegando a delimitação dos setores e exportando para o OpenHistoricalMap, até por que a geographia do hoje pode ser a história do amanhã.

Delimitação dos setores: http://overpass-turbo.eu/s/9zr

Minha meta maior no momento é "terminar" de adicionar todas as sangas, rios, córregos e afins do município.

Quanto mais eu mapeio, mais vejo que há muito o que mapear.

Setores Censitários de SM

Location: Vila Videira, Pains, Santa Maria, Microrregião de Santa Maria, Mesorregião Centro-Ocidental Rio-Grandense, Rio Grande do Sul, Região Sul, Brasil

Weekly roundup - Suspicious mapping

Posted by Maanya on 30 June 2016 in English (English)

Here is a roundup of some suspicious changes to OpenStreetMap from this week (27 to 30 June): ​

  • This changeset an experienced editor changed the value of a major highway in Nepal from highway=trunk to highway=yes making the highway disappear from the map for 15 days. ​
  • This user traced multiple buildings but forgot to tag it as a building. Changeset
  • In this case the user was found adding an amenity on the road. Changeset
  • We also came across an edit where the user was found deleting the tag addr:housenumber from the buildings. Changeset

​ These were some of the inconsistent edits for this week. Do keep an eye and please comment on such changeset, this will help in maintaining the data on OSM accurate and coherent.

OSM - beschissene Datenqualität

Posted by R0bst3r on 30 June 2016 in German (Deutsch)

Lektionen eines Pfadfinders:

  • Der Fisch stinkt vom Kopf

  • Verbesserungen werden von Aufpassern in der Regel als Vandalismus betrachtet.

  • Internationale Edits sind unerwünscht, weil das nur lokale Mapper könnnen, welche das "Gesamte" betrachten und beurteilen können.

  • Rechtschreibfehler in Namen und Keys werden nicht verbessert, siehe vorherigen Punkt. Alles andere ist ein automatischer Edit.

  • Dummes Zeug darf jeder eintragen, es zu entfernen ist schwer, und nahe am Rande von Vandalismus oder automatischen Edits, selbst wenn du es von Hand optimierst. Geht wohl darauf zurück: http://wiki.openstreetmap.org/wiki/Any_tags_you_like

  • Qualitätstools sind zwar vorhanden, dürfen aber nicht angewendet werden, siehe vorherige Punkte.

  • Egal wieviel du zu OSM beigetragen hast, gegenüber einem Aufpasser bist du immer der Arsch, selbst wenn du nur bei 0,001% deiner Arbeit nicht 100% der Anforderungen erfüllst. Der Aufpasser hat immer Recht.

  • Die Community ist bereit für Optimierungen, aber sind es die Verantwortlichen auch? Können Sie ihren gewohnten Horizont erweitern? Ich glaub nicht mehr daran.

Disclaimer: Der Anspruch den ich an meine Arbeit und Projekte habe, wird von OSM nicht erfüllt. Die OSM Community macht eine gute Arbeit, die wird aber von machen Leuten mehr als torpedert. Ich kann keinem mit gutem Gewissen die Nutzung von OSM empfehlen.

##Achtung: Satire mit einem Schuss Wahrheit!##

Building tools for LABuildings Import

Posted by manings on 30 June 2016 in English (English)

This is a part of a series of diaries sharing our experience on the ongoing LA Building Import into OpenStreetMap.

In the last 2.5 months we started importing building footprints over Los Angeles from open data available in LA county. Discussions about this import started early last year, after several discussions, planning and trial runs, we finally started the import this April. From its start, the import team agreed that this will be a community managed import. The goal is not only to improve building coverage of OpenStreetMap within the county but also to invite local mappers to actively participate in the whole process.

In this post, I will talk about the tools we built to coordinate this massive import. Many of the processes were based on an earlier buildings and addresses import in New York City with modifications needed due to the difference of data and the context of the local community.

Data sources

3 million buildings in LA County.

The data came from several open data sources provided by the Government of Los Angeles:

  • Building geometry (LA City, LA County) - building footprints digitized using high resolution stereo imagery under the Los Angeles Region Imagery Acquisition Consortium (LARIAC) Program.
  • Building type and use - from the Assessor's parcels database. Each building from has an associated parcel identifier (AIN), This identifier allowed us to link the type and use of each building.
  • Census blocks - this is not directly part of the data to be imported, we simply used the census blocks for dividing the data into manageable chunks.

We combined the building geometry and parcel information using the usual join by attribute GIS operation. This creates a single shapefile of buildings with all the parcel information for each building.

In total, we have >3 million buildings that needs to be checked for quality and a workflow to coordinate a massive community import process.

Data attributes to OSM tags

The Assessor's parcel data contains detailed usage of each property. We used this data to identify the type of building. To do this, we compared each attribute to taginfo and adopted tags already used by the community. For all other attributes that didn't have corresponding tags we used the generic building=yes. A CSV was created as a lookup to convert the shapefile attribute to OpenStreetMap key/value pairs.

From shapefile to .osm format

Like the NYC building import, we scripted the entire process pipeline so that we can execute in a single command. In general, the script performs the following steps:

  • Download and extract data in shapefile format.
  • Reproject from source spatial referencing system to long/lat WGS-84 (EPSG:4326).
  • Split buildings into smaller chunks based on census blocks.
  • Convert attributes to OpenStreetMap tags and export as osm format.
  • Upload to S3.

This automated process allowed us to easily re-run the conversion if we need to. For example, when we discovered data issues specific to buildings in Pasadena, we were able to exclude Pasadena in the next run of the script.

Coordinating the import via the Tasking Manager

To manage the coordination of import by the community, we used a separate instance of the OSM Tasking Manager. By using the Tasking Manager we can:

  • Split the import into smaller TM projects;
  • Track the progress of the import and;
  • Introduce a two-step process of import and validation.

But the current Tasking Manager does not allow downloading of import data from arbitrary polygons. To make this work, we implemented a new feature in the Tasking Manager that allows it to:

  • Upload a GeoJSON file with a property referencing the source URL of the .osm file,
  • When a contributor takes a task, the Extra Instructions section will have download URL for the import data. This URL will automatically download the data into JOSM.

These changes were merged into the main Tasking Manager code so anyone using the latest TM codebase can use this feature as well.

Once we had everything ready, we did a couple of trial runs to evaluate the mapping workflow.

During one of our trial runs, we discovered that since we are using arbitrary polygons instead of the usual square tasks, mappers find it difficult to visualize the edges of the task they are working on. This can introduce data conflicts especially when the imported data is now merged to the current data within OpenStreetMap. To solve this issue we added a background layer of census block boundaries that is automatically loaded when a user downloads the data.

Downloading data for import.

Automated merging of the split buildings

The trials also encountered cases where a small sliver of building was split from the main building.
Upon further investigation, these buildings are cut by the property lines of the assessor, during the LARIAC mapping.

Split buildings.

Since this came directly from the source data, we have no way of fixing this during the data conversion process. This required the user to manually merge the split buildings during the importing process.

While combining overlapping buildings in JOSM works, it requires several mouse clicks to merge two buildings. To make this process faster, we built a plugin in JOSM that merges two buildings and automatically assign the correct tags.

Merge LA buildings in 3 clicks with auto-tools plugin in JOSM.

As of this writing, 105 usernames added ~580K buildings. This is more than half for LA City.

500K buildings added. Map by F4map.

As we go along, we continue to improve the workflow and tooling, let us know how we can make this import better! Head over to labuildingsimport.com/ and grab any task available. If you're a local, join our mapathons happening through MaptimeLA.

MaptimeLA building import mapathon. Photo by MaptimeLA.

In the next post, we will talk about how we interacted with the mapping community and the response by the local LA mappers on this import.

If you're in Seattle next month, catch the team at the SOTM-US where we talk more about this import.

More info about the import is available in the following links:

Location: Jefferson Park, Cienega, Los Angeles, Los Angeles County, California, 90018, United States of America

Splitting intersecting features

Posted by PlaneMad on 30 June 2016 in English (English)

While tracing an area of continuous buildings in India, realized there was no easy way to create such a pattern of features in JOSM.

How does one split a group of ways using an intersecting line. The More Tools>Split Object command comes closes but works only with a single way and line that it encloses and is quite laborious.

untitled2

Terracer plugin does not work well since the area is not a perfect rectangle, so it does not get the axis right. Any other editor/plugin capable of drawing this quickly?

Location: Lakshmipuram, Hoysala Nagar, Bengaluru, Bangalore Urban, Karnataka, 560001, India

Missing Maps - Sierra Leone

Posted by Tallguy on 29 June 2016 in English (English)

Training in Freetown

Missing Maps training involving American Red Cross volunteers in Freetown, Sierra Leone on 3rd June 2016

“Good thanks, and you?”
“Great. How do you fancy a trip to Sierra Leone?” ……………………...

At various times in my life I've ended up training subjects including IT, and when Missing Maps started, training was my main involvement. I've been to many Mapathons, stood out the front, and done my best to make mapping 'happen' for people struggling with software & strange terms.

The trip to Sierra Leone was slightly different. 32 volunteers needed training in how to carry out surveys using software on mobile phones. Essentially they were carrying out a survey of village & health facilities, how many people, what sanitation – all of the things you would expect the American Red Cross would need to know in order to plan their operations. In addition some training would also be given to MSF personnel – similar sort of thing, but each organisation has its own version of the questions.

In 2014 I'd been one of many people trying to remotely map the areas affected by Ebola, tracing from satellite imagery. Sierra Leone, Guinea & Liberia, were mapped remotely, and names added as best we could. Some ground survey information had been added, but when you started looking at the information, you realised that it was lacking in the sort of detail you'd really like to see in a map - when we arrived in Sierra Leone, OSM had one water point mapped for the entire country.

Our first 5 days were in Freetown, planning and then delivering the training. Each morning we were carried by MSF car through heavy traffic in Freetown and I started to understand a little about the city. I could see people carrying water containers, others were having their morning wash at the side of the road. As we descended towards the coast I could look out onto a large open landfill site and its inhabitants – I couldn't see all of it, but it was at least the size of a football pitch. The river we crossed appeared to have many uses.

We concentrated on training the 32 volunteers who were to carry out the surveys. Many knew very little about mobile phones when we started, but we demonstrated, tested and practised until they understood enough to be able to do their surveys. The power cuts, wifi problems & equipment problems were all taken in our stride (we all had missing luggage, but luckily, enough had arrived for us to carry out the training). Our evenings were spent amending training plans, adapting to the changing needs & time scales. I'd even managed a brief trip round the market buying some clothes (When I first arrived I had only what I stood up in – if anyone finds a holdall with clothing for a Tallguy I'd be very interested).

I spent my weekend either travelling or making preparations for the week ahead where I was to be based in Kenema.

Supervising - based in Kenema

Red Cross Staff in Kailahun, Sierra Leone

Monday, Tuesday & Wednesday was spent travelling on a wide mixture of roads, some wide tarmac roads in better condition than the UK, and some roads that had never been surfaced and were so steep and uneven that my driver negotiated them in bottom gear in our 4x4, while we bounced around in the cab bruising our elbows on the doors. We were attempting to find some of our volunteers to make sure that everything was okay with them and their work. Everyone had mobile phones, but this didn't help much as there was very little in the way of signal.

At times we stopped before crossing bridges, walked over them, & jumped up & down to test them before driving over them. A lorry stuck in the mud caused a 4 hour detour. A brief phone call to one of the volunteers, who was surveying habitations with no roads at all, before the signal dropped off went something like….
“Glad you're okay, where are you?”
“I'm walking in the forest being bitten by beasts”
“Which town are you near?”
“I'm walking towards”….. and the call dropped.

My local driver was impressed that I could tell him the name of the villages which were coming up, and advise him of potential routes. He even enjoyed the game of slowing down on the approach to villages so I could take a photograph of the sign. He and his colleagues were even more impressed when I installed OsmAnd on the phones of those who wanted it, and gave them a brief training session. The drivers were an interesting group to talk to – at least one had been a local businessman who had seen his business gradually decline following Ebola.


Alongside the main roads you could see piles of sacks ready for sale. These were often filled with charcoal but had coya leaves in the top. Buy one, put the coya leaves in the bottom of your BBQ, add charcoal and light. You could see the rough shelters the charcoal producers used, in their little patch of cleared vegetation. Heavily used roads ending in piles of sand beside a river where they extracted large amounts of sand by hand – bought by the local builders. I'm not sure if the main aim for the people doing the digging was the sand or the potential diamonds – there were many diamond offices in Kenema.

Started, but not completed buildings with no roofs were a frequent sight.

My final days in Kenema were spent training staff in the potential uses of OSM - paper, phone apps., analysis, and how surveys for such things as water points could be carried out. The amount of detail in OSM was a surprise to all that I trained and I think we can expect lots of use.

In Freetown I found that Pete had been very busy, surveying water points and making contacts with many local organisations. We carried out a mapathon on one day & part of our last day was at a conference where we gave a presentation on Missing Maps, before finishing our packing and catching the ferry & plane.

Excuse me if I’m quiet for a while - still trying to replace all my lost clothes. Oh, and about 200 water points to add, 50+ village names and a few bits of road aligning to do.

Certainly an experience, and one that I’d be happy to repeat.

Most of my gps traces have been uploaded to OSM, so it you’re working on http://tasks.hotosm.org/project/1757 or anything else in Sierra Leone, have a check for downloadable gps traces.

For more info on Missing Maps, please see http://www.missingmaps.org/ If you’re interested in finding out more & learning a little about ‘remote’ mapping, or something more technical, come along to one of the Missing Maps Mapathons - there are events throughout the world - if it’s in London, UK, you might even see me (Tall, bald, grey beard - easy to spot!).

Location: Lower Pipe Line, Wilberforce, Freetown, Western Area Urban, Western Area, Sierra Leone

شركة البيان الهندسي

Posted by Tobbar on 29 June 2016 in Arabic (العربية)

احصل علي حلول عصرية لجميع مشاكلك المنزلية سواء تسربات أو ترميمات أو أو نقل أثاث أو تنظيف فلل وقصور ومكافحة الحشرات وتسليك المجاري وعزل الأسطح وتنظيف الخزانات شركة البيان الهندسي Www.albianalhandsy.com

Location: منطقة الرياض, ‏المملكة العربية السعودية‎

Gedling as Big Brother?

Posted by alexkemp on 29 June 2016 in English (English)

The main trunk roads out of Nottingham are on the West & lead either to or across the M1 (the main English east-coast 6-lane motorway built in the 1970s). On the East side – which is where I live – most of the roads leading out of the town are B-roads, such as the B686 which can eventually take you to Southwell (pronounced locally as ‘suth-ell’) and Newark. That road is better known in Nottingham as Carlton Road then – at the point where Nottingham ends & Gedling begins – as Carlton Hill. At the top of that hill is (surprise, surprise) Carlton + Carlton shops.

If you are getting an impression of small-town & suburban for Carlton, then you are exactly right. The oldest date that I've spotted for a house in Carlton is 1906. The housing is mostly 1920/30s semi-detached with some Victorian (or later) Terraces + detached houses sprinkled amongst them.

The development of the shops is also a classic tale. Carlton is built upon a hill, and Carlton Hill is the road that leads in and out of Carlton on both sides. Enterprising householders at the top of the rise would have begun a shop in their front-room & extended into the back-room if successful.

However, there is not much room; the B686 is just 2 lanes and the maximum width on the pavement is only 3 metres. How very surprising, then, to see (what appear to be) two 10m+ surveillance masts in the middle of the pavement, one at either side + either end of the shopping street:

big brother masts?

I altered them to be mobile-phone masts before uplift, as I did not believe that Gedling council would be so gross as to place such eyesores in the street simply as CCTV cameras. However, after some thought I've reconsidered, and now think that yes, the police really are that insensitive. I've tagged one of them with “Big Brother?” to make it easier to find.

Coda

There were 2 buildings behind the main line of north-side Carlton shops that I needed to recheck (Little Bears nursery + Dolly's Tearoom), and have just returned. Whilst back on-site I took the opportunity to ask about the mast.

The masts were erected at least 8 years ago – the owner of Bella Monty (the mast is outside her shop) moved on to the street in 2008 & the masts were already present. And yes; Gedling Council truly is that crass, because they are CCTV camera masts.

The folks at Dolly's Vintage Tearoom (on the same block as the mast) were most dismissive of it. When they moved in some years ago they initially suffered some minor vandalism, probably from kids. The CCTV neither prevented the vandalism nor helped catch the kids.

I've altered the mast in question back to “man_made:surveillance”, and have removed the ‘?’ from “ref:Big Brother?”.

PS
Counting up, there are 9 hairdressers (out of 45 shops total) on just one side of this street in Carlton:

  1. Strands
  2. Bella Monty
  3. Who's Next Barbers + Rebecca's Hair
  4. Beautiful Nails
  5. Reno & Paul Hairdressing
  6. The Ink House
  7. Kudos Beauty Clinic
  8. Hair Finity
  9. Wallis and Goodrich Hairdressing

That is 1 in every 5 shops in Carlton is a Hairdresser! Astonishing; but, I have to say, normal for Nottingham (I swear that Beeston, in the West of the city, has even more). And yes, I've naughtily included a Nail shop, a beauty clinic & a tatooist in the total, plus one of the shops is down a side-street (just), but I've also included all of the currently closed-down shops in the total number. Nottingham's girls love getting their hair done so much that they are easily able to support an army of other women + some men to attend to their every need. And the council spends thousands of pounds to watch them do it.

Location: Bakersfield, Nottingham, East Midlands, England, NG12, United Kingdom

First Video on OSM

Posted by mmahmud on 29 June 2016 in English (English)

I live in Dhaka, the capital of Bangladesh. It is a densely populated area to live in. Remote Mapping in Dhaka is also difficult because the imagery quality is not that great and the buildings are so dense that it is hard to separate from one another. However, I noticed that the imagery in Dhaka has two layers. Upto zoom level 18, there is one imagery that is quite clear but small to draw from. From zoom level 19, another imagery that is quite unclear, dense and sometimes covered in cloud. So I figured a way out to use the first imagery to draw from. I made a video about it. Here is the link:

https://www.youtube.com/watch?v=gRTnKmbbaTo

So far, this is helping a lot. I am not sure if this trick can be used elsewhere but this is worth a try.

ЕженедельникОСМ №306

Posted by Sadless74 on 29 June 2016 in Russian (Русский)

Замечания по переводу оставляйте в комментариях или исправьте в вики

24/05/2016-30/05/2016

Logo Knife Tool для JOSM от Eliane J. Meneses aka samely и Rúben L. Mendoza aka Rub21

О нас

  • Английская версия ЕженедельникаОСМ рада сообщить, что Alex Sims aka Softgrow из Аделаиды присоединился к команде. Мы приветствуем нашего первого члена команды из Австралии.

Картографирование

  • Benutzer Reclus начал обсуждение (Deutsch) (автоматический перевод) используемого для общественного транспорта в Rhine Ruhr конурбации. Он отмечает проблемы с обеспечением целостности данных в OpenStreetMap и изменениях в представлении данных различными транспортными операторами. Обсуждение следует.
  • Пользователь Blackbird27 написал длинную и подробную статью об использовании Mapillary для отображения в OpenStreetMap с JOSM. Sandra Uddback так же писала об использовании Mapillary в OpenStreetMap в блоге Mapillary.
  • Пользователь Ukundji начал обсуждение (German) (автоматический перевод) об улучшении отображение церквей и мечетей вокруг Берлина, которые затем спровоцировали много дискуссии про тэги зданий, религиозных общин, на линиях и точках.
  • [1] Перуанские члены испанской команды нашего "ЕженедельникаОСМ", Eliane Joyo Meneses и Rubén López Mendoza (оба работают в MapBox Перу) разработали многофункциональный нож для JOSM, который легко делает разделение линий в произвольной точке.
  • MAPS.ME в версии 6.17 для iOS может искать почтовые индексы. Замечания по выпуску предполагают, что пользователи должны добавлять недостающие почтовые индексы в OSM. TheFive твитнул свои сомнения, о том что это не такое хорошее предложение для новичков.
  • Пользователь Maturi0n спрашивает на немецком OSM форуме может ли он удалить детали из частных садов в OSM, которые были нанесены на карту из аэрофотоснимков. Его личное мнение заключается в том, что эти детали являются частными и не надлежат отображению в OSM. Обсуждение становится весьма жарким. (Deutsch) (автоматический перевод)
  • Существует дискуссия в почтовой рассылке Talks (Deutsch) (автоматический перевод) о том, чтобы включать в ОСМ некоторые духовных импровизированных уличных святынь в OpenStreetMap, но есть проблемы, поднятые об их непостоянства.

Сообщество

  • Gregory Marler продолжает свой обзор книги Стива Коста The OSM book со своими комментариями по поводу интервью в первой половине книги.
  • Архитектор и дизайнер Mateo Prati из Рима в Италии показал свои 3D виды Манхеттена сделанные с использованием Blender и данных OpenStreetMap.
  • Сообщество OpenStreetMap в Ирландии написали о том, что наконец достигли 95% выполнения отрисовки населенных пунктов. (townland это наименьшее административное деление земель, используемое в Ирландии, их около 61000 по всей стране.)
  • В Латинской Америке в рамках OSM сообщества появляется ряд каналов в Телеграмм и их количество продолжает увеличиваться. (via: Твит от OSM Аргентина).
  • H. Albrecht задавал (на немецком языке) (автоматический перевод) о своем положительном опыте использования ОСМ и его поездке в Китай.
  • Humberto Yances снова указывает (Spanisch) (автоматический перевод на задание от гуманитарной команды HOT-Task картографирование прибрежных районов Эквадора, поскольку теперь есть новые снимки с беспилотных летательных аппаратов.

Фонд OpenStreetMap

  • Рабочая группа по организации The State of the Map опубликовала статью на тему корпоративного членства. Источник: OSMF-talk
  • Пользователь malenki отчитывается в своем блоге, что совместно с Amazon немецкий партнерский счет OSM заработал около 10 000 евро с момента его создания в мае 2010 года. В то время он также открыл партнерский счет на amazon.com, но сообщество ОСМ США не заинтересовалось в его использовании.

События

  • Peter Neubauer пишет в своем блоге об опыте участия в SOTM Франции и об аввторах Mapillary, которых он встретил там.

Гуманитарный OSM

  • Два доклада об эффективности OSM для ликвидации последствий недавнего землетрясения в Эквадоре:
  • Vistazo (Spanisch) (автоматический перевод)
  • PBS
  • Проект Высокогорные Гориллы будет проводить картографирование 2-3 июня.С помощью HOT и Edirisa они надеются значительно увеличить карту ОСМ на юго-западе Уганды и северо-западной части Руанды.
  • Mapbox объявляет, что их карта и с ними инструменты теперь свободны для оказания гуманитарной помощи.
  • Paul Uithiol сообщает что HOT получает финансовую поддержку через "Grand Challenges Explorations" (GCE) для исследований в области здравоохранения и развития. Инициатива GCE стартовала в 2008 году и поддерживает 1186 проектов в 61 странах мира.
  • Mapbox опубликовал снимок Шри-Ланки с ультра высоким разрешением 7.5cm. Изображения были созданы для Северо-Восточной жилищной реконструкции по программе Всемирного банка (NEHRP).

Карты

  • Kaushik Chatterji описывает эффекты и последствия предлагаемого законопроекта [PDF] в Индии. Существует призыв ко всем о том чтобы сохранить карту в Индии.

Программирование

  • Ladislav Laska объявляет о доступности сборок ночных версий редактора OSM Merkaartor (может быть нестабильными), как для платформ Windows, и OSX. Сообщения об ошибках приветствуются, например через github repository.
  • Обновленный Maproulette уже достиг статуса бета и и заменит предыдущую версию примерно в конце июня. Попробуйте его и дать Мартейн обратную связь.

Программы

Программа Версия Дата релиза Комментарии

OpenLayers 3.16.0 2016-05-23 Новые возможности и исправления 95 замечаний, начиная с версии v3.15.1

iD 1.9.5 2016-05-25

Maps.me iOS 6.1.7 2016-05-25 Доступны почтовые индексы

osmosis 0.45 2016-05-27 Много изменений

А вы знаете …

Другие “гео” события

  • Real Earth выигрывает у Microsoft соревнование по созданию эффективноей карты маркеров внутри помещений 3D с минимумом ошибок.
  • Tagesanzeiger сравнивает самые длинные железнодорожные туннели в мире.
  • Google расширяет свою рекламную прогамму добавлением "оплаченных отметок" на картах Google.
  • Justin O'Beirne пишет об изменениях в картах Google на протяжении многих лет.
  • Terrapattern опубликовала альфа-версию их "поиска похожих изображений". Martin Dittus спрашивает может ли это каким-то образом использовать для Гуманитарного OSM.
  • Lauren Young отписывает 10 методов которые помогут преобразовать наш базу planet в карты.

Предстоящие события

Где Что Когда Страна

Wien 57. Wiener Stammtisch 02/06/2016 austria

Colaboratorio Mapa Comunitario de Activos de Santurce 04/06/2016 puerto rico

Mantova 2016 Mapping party a Volta mantovana 04/06/2016 italy

Bucharest OSM Bucharest Mapping Party 2016 04/06/2016 romania

Bucharest OSM Bucharest Mapping Party 2016 05/06/2016 romania

Brasília Encontro OSM Brasília 05/06/2016 brazil

Brussels Missing Maps Mapathon @Doctors without borders/Handicap international 06/06/2016 belgium

Tokyo OSM Monthly Mappers "M-eat-ing" - Jun 2016 09/06/2016 japan

Besenello Trentino Portobeseno : several talk about OpenStreetMap 10/06/2016-12/06/2016 italy

Edinburgh Edinburgh 14/06/2016 united kingdom

Lyon Rencontre mensuelle mappeurs 14/06/2016 france

  • Примечание: Если вы хотели бы видеть Ваше мероприятие здесь, пожалуйста, поместите его в календарь. Только данные из этого календаря появится в ЕженедельникеОСМ. Пожалуйста проверьте ваше событие в нашем публичном календаре, сделайте предпросмотр и исправьте его в случае изменений, если необходимо..

Этот выпуск подготовлен Hakuch, Laura Barroso, Nakaner, Peda, Rogehm, Softgrow, derFred, escada, jinalfoflia, malenki, mgehling, stephan75, wambacher, widedangel.

DOST - Project NOAH (ISAIAH) finishes mapping building footprints in Cavite

Posted by feyeandal on 29 June 2016 in English (English)

OpenStreetMap contributors, through the initiative of ISAIAH (Integrated Scenario-based Assessment of Impacts and Hazards) component under DOST - Project NOAH (Nationwide Operational Assessment of Hazards), have recently completed mapping the building footprints of Cavite.

gif

One of the objectives of ISAIAH is to map the exposure elements such as buildings and critical facilities. Identifying the critical facilities such as schools, hospitals, and government offices, and other infrastructures will be essential in determining the areas vulnerable to disasters and can be used as a starting point in reducing disaster risk. All of these data will be used in improving community disaster management before, during and after emergencies. This initiative involves a collaborative partnership with the OpenStreetMap community.

Last March to April, Project NOAH conducted a series of OpenStreetMap training to its staff to digitize the building footprints in the selected provinces in the Philippines using the available imagery from Bing and MapBox. The provinces were selected according to the available imagery, land area and population of the provinces, and the available population data we have from the Philippine Statistics Authority as of 2010. Accordingly, Project NOAH created a mapping task on the HOT Tasking Manager for the province of Cavite. Since then, Project NOAH staff and OSM community started contributing to the mapping task.

Cavite Tasking Manager

As of June 28, the mapping task for Cavite is 100% complete and 18% validated. This mapping initiative helped increase the number of building footprints in Cavite from 110,506 to 631,825.

Below is the image of the downloaded building footprints in Cavite as of June 28.

Building footprints mapped in Cavite after NOAH initiative

You may view the map comparison of before-and-after edits here.

The translated building footprints data from OpenStreetMap are being utilized in one of Project NOAH tools, the WebSAFE application. It is used as an impact assessment tool for end-users to be able to readily identify the number of affected people and buildings in case a hazard scenario like flood affected a certain area. Using this tool, local government units can easily identify how many relief goods are needed to be allocated when a severe weather event happens.

WebSAFE for Cavite

Thank you for helping us map Cavite!

Project NOAH recently opened a new task for the province of Zambales. Click here to help us map the province. :)

Mapeamento da vila zumbi do pacheco, vila dois carneiros e Marcos Freire.

Posted by raphaelmirc on 29 June 2016 in Brazilian Portuguese (Português do Brasil)

Ontem eu mapie uma área que faltava na vila Zumbi do Pacheco e o bairro de dois carneiros divisa entre recife e Jaboatão dos Guararapes, os bairros tem uma área com poucos nomes de ruas e com algumas ruas ainda para ser colocado os nomes das mesmas, também mapie uma boa parte do bairro de marcos freire, Cohab, mais precisamente na vila 27 de Novembro, essa foi a minha contribuição de ontem.

Assim vou mapeando os bairros e colocando nomes nas ruas...

Raphael de Assis.

Multi-Light Rendering and Voronoi Diagrams

Posted by Zabot on 29 June 2016 in English (English)

I spoke with B4sti and Tordanik last week about how to best attack shading with multiple light sources. As it stands, OSM2World can only handle a single light source, the sun. Adding any individual light source is not so much of a problem, some tweaks to what information is passed to the graphics card and now you have another light source. The problem is one of scalability. OpenGL breaks the faces of shapes to be rendered up into fragments. Each fragment must have its color calculated individually, based upon several factors, including the lighting. To add a second light source would require every fragment to consider both light sources. As you keep adding lights, each fragment must consider every light. This may not seem so bad, but there may be hundreds of thousands of fragments in a single frame. If each fragment has to consider 10 lights, thats one million calculations, and it only gets worse from there. But one could easily imagine a city scene with more then 10 lights, even just a highway with street lights would have more than that.

We can makes things a little bit easier on ourselves by only considering the closest light to each fragment. While this means we only have to do the lighting calculations for a single light source at each fragment, we still need to test the distance to every light source to find the shortest. We need some method to precompute the closest lighting source to each fragment so we can avoid the timing consuming process of calculating it. Unfortunately, we have no way of knowing where a fragment is ahead of time.

The solution we came up with is similar to the concept of a Voronoi Diagram. A Voronoi diagram is a mapping of points on a continuous plane to a finite set of seed points such that each point is mapped to the closest possible seed point.

Voronoi Diagram

(Each colored region would be affected by the lighting source closest to the vertex in that region)

If we imagine each seed point to be a vertex in our world geometry, then each vertex could be assigned a precomputed closest light source, and every point in the region belonging to that vertex would use that light source for its calculations. Typically, if we were to assign an ID to each vertex, OpenGL would use those values to interpolate the value for a fragment between those vertices. But by tweaking the behavior of this interpolation, we can make a fragment take the value from the closest vertex without interpolating it, and without performing any additional calculations. If we know already know which light is the closest, the calculation no longer depends on how many lights are in the scene, and the number of lights could be much greater.

Better Sunsets!

Posted by Zabot on 29 June 2016 in English (English)

After I had implemented moving the sun a few weeks ago, I realized that things looked out of place without an actual sun. So I busted out the physics textbook (google) and did some research. Sunset

The Physics

You might remember from your physics classes that light does one of three things when it strikes an object. It can be absorbed, reflected, or transmitted into the new medium. In the case of atmospheric scattering, we discount the last possibility because all of the particles are opaque. This leaves us with absorption and reflection. Absorption is fairly self explanatory, the farther light has to travel through the atmosphere, the less light is going to make it. Reflection is not quite as simple. Because the light could be reflected in any direction off of the particle, we further define reflection as in-scattering and out-scattering. Out-scattering is when light originally in a ray is reflected (scattered) away from (out of) the ray, lessening the final brightness. In-scattering is when light not originally out of a ray is scattered into the ray, increasing the final brightness. To define the final color of a fragment to a viewer, these three values most be calculated for every point along a ray from the fragment to the viewer. To see this in action, lets look at a sky without scattering.

If we consider the sun as a directional light source where all rays are parallel (not entirely true, but close enough for most purposes) then for each ray, we need only check if it is perfectly parallel to the sun, if it is then we see a bright sun at that ray, if not then there is no light and we see black. This is what you see if you look at the sun from space (Because the real world sun is not a perfect directional light source, there are several rays which are parallel to the sun, giving it its apparent size).

Absorption

The first atmospheric affect we look at is absorption. During each collision with a particle, there is a probability that the light is absorbed. The further that light has to travel through the atmosphere, the higher the probability of a collision, and the more collisions there are, the more chances there are for that light to be absorbed. If it were possible to observe a planet where the atmosphere only absorbed light, you would still see the sun at a single point, but as it lowered in the sky the point would become dimmer as more light is absorbed by the atmosphere.

Out-Scattering

Next we introduce out-scattering, the effect will be similar to that of absorption, as light is removed from the ray but the process is slightly different. To examine it we need to look at the two types of scattering, Mie scattering and Rayleigh scattering. The two are different names for similar phenomena. Mie scattering is seen when the size of the particles doing the scattering is comparable to the wavelength of the light being scattered, such as water vapor in clouds, or smog and other large particles close to the surface. Rayleigh scattering is when the particles doing the scattering are much smaller than the wavelength of the light, such as the nitrogen in the atmosphere. Going to much further dives into some serious physics, but the important thing to take away is that Rayleigh scattering scatters shorter wavelengths (blue) more than it does longer wavelengths (red), while Mie scattering scatters all wavelength equally. During sunrise and sunset, the light from the sun has more atmosphere to travel through, so much of the blue light is scattered away, giving the dawn and dusk sun its red color. During the day, there is less atmosphere between your eyes and the sun to scatter away the blue light, and we are able to see it as the color of the sky.

Implementation

In reality, every ray of light is eventually absorbed by something. Unfortunately, simulating the lifespan of every individual ray of light, potentially through dozens of bounces through the atmosphere can be incredibly computationally intensive. To make calculations easier, instead of simulating every bounce, we assume that once a ray has been out scattered, it effectively disappears. Now we can combine these two effects into a single factor, extinction, and model it as an exponential decay.

vec3 extinction(float dist, vec3 initial_light, float factor) {
    return initial_light - initial_light * pow(scatter_color, vec3(factor / dist));
}

scatter_color is what really defines the color of the sky, you can modify it in your config file by setting scatterColor = #xxxxxx. This color specifies how the sky scatters different colors of light. The gist of it is that a higher a channel is set, the more of it you will see in day time, and the less you see during sunrise and sunset.

Now we're getting somewhere, but we need some more support equipment if we want to render a sky. To calculate the amount of light that is lost to extinction, we need to know how much atmosphere the light is traveling through. This function is the product of the law of sines from trigonometry and a circular cross section of the atmosphere through the center of the earth, the viewer, and the point where the a ray from the viewer leaves the atmosphere.

float atmospheric_depth(float alt, vec3 dir) {                                                             
    float d = dir.y;
    return sqrt(alt * alt * (d * d - 1) + 1) - alt * d;
}

We have everything we need to define out-scattering and absorption, but we still need a way to define in-scattering. To calculate in-scattering, we use a phase function. This function estimates the probability that a ray will be scattered an angle alpha away from its original direction. This phase function comes from this GPU Gems article.

float phase(float alpha, float g) {
    float a = 3.0 * (1.0 - g * g);
    float b = 2.0 * (2.0 + g * g);
    float c = 1.0 + alpha * alpha;
    float d = pow(1.0 + g * g - 2.0 * g * alpha, 1.5);
    return (a / b) * (c / d);
}

To color the rest of the sky, we sample several points along a vector from the eye to the fragment we are trying to color and calculate the probability that light will be scattered from the sun towards the viewer. We scale the probability by the intensity of the sun to calculate the amount of light being scattered from the sun towards the viewer. But this light isn't done yet, it still has some atmosphere to travel through, so we calculate the amount of light that is lost going from the sample to the viewer. We add together the light from each sample point to find the total light that reaches the viewer. You can read the rest of the code here, and have a look at Florian Boesch's excellent article where I pulled the original algorithm from.

Older Entries | Newer Entries