OpenStreetMap

Users' diaries

Recent diary entries

карта для garmin nuvi 2595

Posted by Азат 1985 on 14 November 2014 in Russian (Русский)

Всем доброго время суток!!! Может мне кто нибудь подсказать, как преобразовать карту OSM под навигатор Garmin nuvi 2595. В инете есть много инструкций для конвертирования, но ни одна из них не помогла мне для решения моей проблемы, они в основном предназначены для более ранних версий навигаторов Garmin. Заранее благодарен!!!

Rqst for Change set: http://www.openstreetmap.org/changeset/26767815

Posted by မောင့်-အမျိုးသ္မီးချောကလျာ on 14 November 2014 in English (English)

Somebody fix this one, please. I was unable to do it.Instead of getting a whole area I got lines only. So I dropped a point and described it.

Thank you .

Mapeando novos locais sem imagem de satélite ou outros mapas

Posted by naoliv on 13 November 2014 in Portuguese (Português)

Como mapear um local que não existe na imagem de satélite?
É só dirigir por 1 hora, percorrer 60+ Km e ficar dando volta em uma rotatória que nem um bobo!

Há cerca de uma semana a reforma e duplicação da SPI 274/310 foi entregue. Obviamente este novo traçado ainda não existe nas imagens do Bing, MapBox ou mapas do IBGE.

Antes da duplicação e reforma tínhamos algo assim (eu esqueci de tirar um print dos dados anteriores):

Como eu não tinha nem ideia de como ficou o novo trecho, peguei o carro e fui gravando o trajeto dele, reparando nas novas entradas, saídas e como que eu iria passar pelo menos uma vez por cada local.

Depois de 1 hora dirigindo, cerca de 60 Km percorridos (não tem retorno perto, infelizmente) e várias voltas na rotatória (para tentar definir bem onde ela se posiciona), tinha um arquivo GPX com um trajeto do novo local: http://www.openstreetmap.org/user/naoliv/traces/1832775

Dá para perceber o tanto que tive que andar, por duas vezes, para poder retornar ao novo trecho:

Mas o novo trevo ficou, de certa forma, bem capturado:

Com um pouco de mágica (digo, trabalho):

E finalmente:

O Google não tem este trecho, o Bing também não, mas nós temos!

Location: Altos do Jaraguá, Araraquara, São Paulo, Região Sudeste, Brasil

Changeset analizálás

Posted by Roland Pallai on 13 November 2014 in Hungarian (Magyar)

Ha gyorsan át akarod tekinteni, hogy mit változtatott meg egy changeset, erre jelenleg az egyik legjobb szerszám az achavi.

Így használd: http://nrenner.github.io/achavi/?changeset=25749516 - a changeset számát cseréld le arra amelyk érdekel.

Jó mi? :)

Программка для фотомаппинга

Posted by z-yurets on 13 November 2014 in Russian (Русский)

В статье о фотомаппинге на вики упоминается о трудностях с направлением (азимутом) съемки. Однако же неодноразово натыкался на андроидные программки для геофотографии. Вот например одна и вторая. Каждая наворочена по-своему, я пока не определился какую оставить. Вторая даже позволяет снимать видео, правда, на моем LG P-500 слегка подтормаживает. Но главное что обе пишут в EXIF не только координаты, но и азимут. Еще не пробовал их фотографии в йосме, однако работают :)

Так что есть прекрасная альтернатива фотоаппарату. Главно чтобы в смарте был компас :)

What I want

Posted by Zverik on 12 November 2014 in English (English)

Hi. I often drop hints about what our project misses, and now want to talk some bit more about a part I'm interested in. Since I joined OpenStreetMap, I have been interested in geodata collecting methods. I quickly grasped walking papers, put my GPS and camera to use, and struggled with georeferencing audio recordings. OSM allows for many types of sources, and in past years a lot were invented. But alas, not much in last years.

Walking papers (or field papers) are still produced from tiles. Fieldpapers.org, the "modern" service for generating atlases, is more than two years old and is a slight update to older walking-papers.org, built in 2009. It stiches tiles and produces a PDF file. You have no control over map style, you can't even use your own tiles. "Toner" style, which is the best option, are updated infrequently: you might have to wait a week before traced buildings appear on it. And some of them still won't, since it's hard to grasp how it works and why it hides some features unpredictably. Finally, pages of an atlas will be oriented by cardinal directions, in a grid with 90° angles. Of course, not many towns have such proper road network, so you will have to choose smaller scale, with less effective area for mapping.

I think I can fix this. It is easy, really: most of building blocks for a proper solution are already invented. First, an interactive map, on which you place rectangles for pages. Arbitrarily, not neccessary in a grid. Maybe draw some lines, which would be "pie segments": instead of using MS Paint for making a pie, use some advanced technology. Maybe integrate it with MapCraft. So, a bunch of rectangles on a map. Not 90°-aligned: rotate them as you like. Align with road network, with streams etc, so areas for filling in take as much space as possible, and scale is biggest you can get. When done, just save your work and close the website. Go trace some buildings and tracks.

When a morning of a mapping party comes, open the website and press "Create atlas". It will display the progress, but the atlas will be made on a server asynchronously. First, it downloads an area from OSM API. Yes, not from a local postgis database, only fresh data. An added bonus (for local installation) is that you can use cached osm data, or just bring it from another computer, if an internet connection is weak. Then it applies a MapCSS style (which you can customize, even upload some of your own or josm's) and renders each page, rotating data as needed. Then it joins pages into an atlas and provides a download link. Later the atlas can be rebuild, using fresh data, maybe a different style or with more pages.

I don't believe in scanning pages for using them as a layer in JOSM (Bing/MapBox imagery make for a better reference layer), but georeferencing marks probably can be included. That won't be the greatest feature, because I have some other thoughts. You know the weakest point of the OpenStreetMap mapping in 2014? Updating data. It is quite easy to collect and map new roads, new POIs, new restrictions. But updating it is very, very hard, almost impossible for rich regions. There are no tools. My theoretical walking papers can fix that issue. Since we have full control over data, we can put POIs and relevant tags right on pages. We have a second side: for example, on the map there would be dots with coordinates (A4, D9), and on the reverse side — tags for each dot. And the same for ways and maybe relations (didn't think it all through, obviously). So you can have not only a base map for collecting new data, but also a check list for updating the already rich map.

This solution will make mapping easier not only in thrid-world countries (where internet is sparse and you can't rely on external web services, or spend days installing tile rendering stacks), but in densely mapped cities, where data has not been updated for years, because it already seems well-mapped, why go there again.

The next step would be an Android application for mapping. Why android? Because I again keep in mind mappers in third-world countries, who can get an android phone for $30, but not an iPhone for $300. So, let's take Vespucci. It is a powerful editor, getting better every months thanks to Simon. It can download an area and let you edit it. But can it work without internet and GPS? Not likely. Can it be used on a mapping party, when you are passing 10 points of interest a minute? You'll be exhausted in half an hour. The ideal mapping solution will have to separate data collection and data processing. Step 1: go out and record everything. Take photos, record audio, type a hundred house numbers, draw some crude lines on a touch-screen, like you do on walking papers. The interface should allow for quick mapping, e.g. in a car: you see a sign — you press a button and leave moving a mark to a correct place and tagging it for later. KeypadMapper and OSM Tracker are examples of this approach, but it should be made more streamlined and consistent. You cannot rely on GPS, for it has low precision, and not available on cheaper phones (off go those two apps). You cannot rely on the internet to provide you with tiles (off goes OSMPad). But you can assume you'll have a chance to download 100k of osm data back at home (or 10-20k on the road), to use as a base map for further mapping.

Step 2: Upload collected data somewhere (e.g. on your computer), process it and update the map. Data format can be universal, which means some central server for storing all the information. Audio notes can (and should) be converted to text, GPS trace joined from broken segments, data split between days and so on. Since most of points would be in tags or other non-textual representation, so anybody can use it for mapping, you would have an option of upload it to a server (right from your phone), so someone else could map it in their spare time. Or it could be you, download the data pack in JOSM. And then — map it. Recorded points shown as icons, with copypasteable tags; photos already georeferenced with subsecond precision, notes written on a map, crude drawings also georeferenced as underlying layers, between OSM data and imagery. It would be so much better then trying to remember what you meant by these waypoint titles, or having to read your handwriting on walking papers. And technical requirements would be as low as they get.

I am not a great programmer, or a designer. But I know what and how should be done to drastically improve mapping in OSM. No commercial company would make it, because they make profit not from mapping, but from using already mapped data. Hence loads of geocoders, routers, renderers, data converters, but nothing really good and innovative on editing front (sans iD, which was really lucky and sponsored by a grant). I really really want all I wrote above implemented. I want to push a button and get up-to-date walking papers with POIs for my street, to go out and find new amenities and update opening hours. After a long drive I want to run JOSM and add lane information, cafes, hotels and petrol stations, house numbers and surfaces I collected just hours ago to the map. I want to make OSM better, but I see no way these tools could be made. We all know the main principle of OpenStreetMap: "You want it — you make it". Maybe some wonderful person would start on that, but given my experience with mentoring "OpenSurveyor" on GSoC, it's not an easy task for students or even novices to OSM. Turned out having a 10-page design document means three months won't be enough.

All I know I can program, I know some of these technologies and will have little trouble learning the rest. Eventually I can finish all that. But as a spare-time job, between hosting an osm radio, writing news posts for shtosm, organizing mapping parties, disputing on osmf-talk and so on, progress would be very, excruciatingly slow. Not to mention I have other challenging ideas like writing a proper changeset reverting web service. So can you recommend me any way to make creating these tools my full-time occupation?

update: if some company (Stamen? Mapzen? Mapbox? Enaikoon?) decides to commit to one of these projects, I'd be happy to translate and update specifications.

Fajna pogoda

Posted by sfink65 on 12 November 2014 in Polish (Polski)

Listopad i taka fajna pogoda!

cartographie du département de l'eure

Posted by BESSAT Matthieu on 12 November 2014 in French (Français)

Bonjour à tous, Je voudrait être en contact avec d'autre mappeur du département de l'Eure. J'habite à Aubevoye (27)

merci

Location: Allée des Sources, Aubevoye, Les Andelys, Eure, Haute-Normandie, France métropolitaine, 27940, France

本日の編集

Posted by jo3fdi on 12 November 2014 in Japanese (日本語)

長浜愛児園が移転しているのに旧所在地にタグがあったため削除しました。 現在、長浜愛児園は市営から民営になって運営されています。

今日のデータ取り分もアップ。ロガーの設定が1m毎になっていたのを3mに修正。先日は徒歩のところ今回は自転車でできる限りまっすぐ走ることに専念。 何度も取って平均でも出さないと里道を正確には難しいなぁ。

Radares e radares e de volta às comunidades

Posted by Márcio Vínícius Pinheiro on 11 November 2014 in Brazilian Portuguese (Português do Brasil)

Desde a minha última entrada no diário em maio, dei um tempo com as favelas. Acabei não mapeando o que disse que mapearia no Complexo do Alemão. Fiz um bocado de viagens pelo estado do Rio e acabei me distraindo com as estradas e principalmente radares de velocidade. Confesso que agora cansei de tantos radares, é um trabalho sem fim mapeá-los, tem muitos radares no Rio!

Nesse meio tempo, também acrescentei alguns loteamentos que conheci na Zona Oeste, ainda há muito o que se mapear lá, mas infelizmente acho que não terei oportunidade de fazê-lo tão cedo.

Ainda tenho algumas anotações (fotos e gpx) das viagens, vou fazer os mapeamentos referentes a eles cedo ou tarde. Mas agora a prioridade é voltar para as favelas do Rio. 132 edições depois, volto a dizer que as próximas serão na Joaquim de Queiróz, Morro do Alemão e Itararé no Complexo do Alemão, mas antes vou ao Vidigal.

Hidrografia de Formosa/GO

Posted by Ivaldo on 11 November 2014 in Brazilian Portuguese (Português do Brasil)

Estou trabalhando na hidrografia do mapa da Cidade de Formosa/GO, com o objetivo de deixar o mapa da cidade mais completo. Isso porque os rios, córregos e valas constituem elementos muito importantes na determinação dos limites de bairros, que será o próxima etapa do meu projeto.

Gostaria de interagir com algum usuário mapeador que mora na cidade, para alinharmos as informações.

Etapas:

  • Pesquisa e catalogação dos rios, córregos, valas, riachos, represas e lagoas da cidade;
  • Criação e nomeação desses elementos no OSM;
  • Auditoria dos dados cadastrados;
  • Link para mapa: Formosa.

Quem conhecer a hidrografia da cidade ou tiver informações sobre, fineza entrar em contato.

Fix a Forest - experimental tiles from US Forest Service data

Posted by Richard on 11 November 2014 in English (English)

Klamath Forest

I've created a set of tiles from US Forest Service road data for the 155 US National Forests.

This is to help with TIGER fixup in these rural areas, where tracks, trails and entirely non-existent paths are often tagged with a bare "highway=residential". The US Forest Service data is greatly superior to the original TIGER data and has metadata on surface type/quality, but is unsuitable for automatic import into OSM because it would overwrite mappers' existing work in these areas.

You can access the tiles at:

and they're included in the editor-imagery-index list used by P2, iD and Vespucci. The tiles are available up to z19. Use of Potlatch 2's new floating imagery window mode is recommended, so that you can work from both Bing imagery and these tiles at the same time.

You can also explore from the comfort of your browser at http://osm.cycle.travel/index.html, where there's an "Edit this area in OpenStreetMap" link at the bottom right.

Key

  • Surface:
    • yellow outline = paved
    • grey outline = gravel
  • Road type:
    • white with black casing = paved road
    • dashed grey = gravel road suitable for cars
    • dashed brown = dirt road
    • dotted grey = not maintained for cars
  • Maintenance level:
    • grey dots = 4x4 only
    • green dots = usable by cars
    • black dots = moderately comfortable for cars
    • black frequent dots = very comfortable for cars
  • Points of interest:
    • car = roadside park
    • flag = Forest Service station
    • ski = winter recreation area
    • hiker = trailhead
    • campsite = campsite
    • picnic site = picnic site

(There's some degree of overlap, but this is present in the original USFS data.)

When fixing up data, I would suggest the following tags as a minimum:

  • highway=unclassified - paved road
  • highway=unclassified, surface=unpaved/gravel/dirt - unpaved road suitable for cars
  • highway=service - road to isolated dwelling or other building
  • highway=track - unpaved track or road suitable for 4x4s
  • highway=path - narrow linear clearing, too narrow for motor vehicles
  • [delete entirely] - raw TIGER data with no signs of track or path in either imagery or Forest Service tiles

US Forest Service data is public domain so there's no need for further attribution when using this data, though a source= tag is always good practice.

Hope these are helpful, and let me know of any further suggestions.

Offline Routing on iOS? The Open Source Route Planner GraphHopper is now Available for iOS

Posted by karussell on 11 November 2014 in English (English)

Please read on our blog for the full announcement.

Mesolcina Valley

Posted by venzin77 on 11 November 2014 in Italian (Italiano)

I have build one part of this Valley in Switzerland, city Lostallo. Next day other. I live in Mesolcina Valley ;-)

Ho lavorato ad una parte della mia Valle Mesolcina, paese di Lostallo. Nei prossimi giorni altro materiale. Io vivo in Mesolcina.

Entrenamiento

Posted by Palmitsystem on 11 November 2014 in Spanish (Español)

Recorrido diario en el horario de colación

Location: Barrio Franklin, Santiago, Provincia de Santiago, XIII Región Metropolitana de Santiago, 8940000, Chile

Адама Везурића - Кобишница

Posted by Sasa on 11 November 2014 in Serbian (Српски / Srpski)

Одрађена је и ова улица са кућним бројевима.

Location: Адама Везурића, Кобишница, Борски округ, Централна Србија, Србија

Odrađena ulica Oslobođenja u Bukovču

Posted by Sasa on 11 November 2014 in Serbian (Српски / Srpski)

Ulica Oslobođenja u Bukovču je odrađena sa kućnim brojevima.

Location: Bukovče, Буковче, Општина Неготин, Борски округ, Централна Србија, Србија

Mein Test des OpenStreetMap-Blogs

Posted by uwekeim on 11 November 2014 in German (Deutsch)

Hiermit teste ich, wie flexibel die coole Website OpenStreetMap ist, um beispielsweise auch in den Homepage-Baukasten Zeta Producer integriert zu werden.

Location: Stauferpark, Malerviertel, Göppingen, Vereinbarte Verwaltungsgemeinschaft der Stadt Göppingen, Landkreis Göppingen, Regierungsbezirk Stuttgart, Baden-Württemberg, 73037, Deutschland

"Just watch Taginfo" - doesn't work at all outside En community

Posted by d1g on 11 November 2014 in English (English)

(Please forward this text to right person or place)

There are a lot of problems outside En community when it comes to OSM guideline "just watch Taginfo for popular values". This approach work more or less for EN community, but users outside English-speaking world faced with the challenge to realize the word, not local word with similar letters\sounding.

I do Russian translation at wiki\ID\communicate with ru community and many ru users do no realize that reading tag values by letters in Taginfo doesn't work without meaning of the word. it may sound absurd, but it is not written anywhere. Instead we (English speaking world) promote "just watch the most popular values in Taginfo ". This is serious issue outside GB, USA, Canada, Australia. We have way more countries. Even more if OSM want to grow.

  1. Promote OSM wiki instead of Taginfo across all non-English languages. Possibly notice should be given at langcode:main page@wiki or every single wiki guide/content should be rewritten.
  2. Not Taginfo fault, but Taginfo can fix this. Just add feature to Taginfo to directly show wiki-translated page based on "Accept-Language" header. Force this behavior by default for not-English languages. Yes, '''force displaying wiki pages parallel to previous Taginfo interface'', but let users switch language (and disable this feature).
  3. Everything for English-speaking world stays the same, since this is main language/tagging convention, there no need in changes for GB/USA/Canada/Australia.

OpenStreetMap - yours to cut out and keep

Posted by Hawkeye on 10 November 2014 in English (English)

Globes, gores and geojson (topojson)

osm-world

Been thinking about this for a while. Like maybe two years. How do you make a globe using openstreetmap data? So when I say think, I mean a quick way to hack this together using lots of other peoples hard won code.

According to what I could find, the main thing was to create 'gores' these are the name of the thin oval shapes that make up the outside edge of the classic 'orange' segments.

So I googled it a while back and found a perl script for Gimp that appeared to do the trick. At the time, it seemed very involved and I hardly knew much about writing scripts etc (although reading about again - it now seems more straight forward). So I put the idea on the back burner for a while

The next approach seemed to be using Generic Mapping tools (GMT). Which also has a way to stitch gore projections together. But the first time I attempted using GMT, I had issues installing it. Once I got it running it has a bit of a learning curve and lots of interesting file formats...After a short battle, I abandoned my attempt at trying to get it to work.

So it would be nice to do in QGIS using the proj4 library. But unfortunately, it doesn't work for gores like projections. In the business they are called 'interrupted' projections because the map is not just stretched but split into pieces. It is possible I believe to project one gore at a time and stitch together (sounds like a python script waiting to happen).

By this time, I'd spotted a javascript plugin for D3 that looked promising call d3-geo. Seriously, go there straight away and look at it. Recently a projection called 'gingery' was added. Again, go check it out.

Anyway, the d3-geo has lots of examples and it was easy to use or maybe my knowledge is somewhat more advanced now. It was possible to tweak the examples and see how they work. Although the core projection mathematics is still way out of my league. But thanks to Jason Davies and Mike Bostock who created them - absolutely amazing.

The next stage was to get some OpenStreetMap data. But that was no problem, using openstreetmapdata.com (thanks Jochen Topf). This gave a shapefile of the basic global land polygon using OSM. I decided to simplify this using QGIS - but this step is not really necessary. After simplifying I was left with a file called simpleworld2.shp but D3 required topojson format. So on a linux type system, first you need to installed Node.js (I had this already), then install TopoJSON:

npm install -g topojson

then using the topojson guidance I used this command

topojson -o output2.json simpleworld2.shp

Converting to topojson greatly reduces the file size. You can now reference the output2.json file within the example given on the d3-geo site.

If you want my html/javascript example, osm based world topojson file or the svg of the above image see my repo here

Now get busy with staples and glue!

rough-edges

p.s. looks like there are other ways using Wolfram / Mathematica/ Matlab examples.

Location: 33.578, -34.980
Older Entries | Newer Entries