OpenStreetMap

Users' diaries

Recent diary entries

OSM的hello world

Posted by 独傲飞扬 on 13 January 2015 in Chinese (China) (‪中文(中国大陆)‬)

为了用osmdroid,所以了解下

Location: 水西社区, 龙岭村, 章贡区, 赣州市, 江西, 中华人民共和国

Convocatoria Reunión OSM-EC

Posted by lomejordejr on 13 January 2015 in Spanish (Español)

Estimados compañeros, quiero extenderles una cordial invitación a la segunda reunión presencial de “Open Street Map Ecuador - Hackem Project” donde discutiremos varios temas importantes sobre el Proyecto.

La fecha está por definirse, para lo cual les solicito por favor llenar la siguiente encuesta: http://goo.gl/YlQTQ0

Algunos de los temas propuestos por parte de la Comunidad Hackem son:

Difundir el uso de OSM a nivel Nacional
1er Mapping Day 2015

Lugar: ASOFIS (Escuela Politécnica Nacional)

Estamos abiertos a sugerencias para cualquier otro tema que consideren importante, contamos con su valiosa presencia.

Saludos,

Luis Reinoso

Quito - Ecuador

New Zealand Data Help

Posted by MapMakinMeyers on 12 January 2015 in English (English)

Vote for this data so the New Zealand Fire Service opens up some gis data to the public: https://diadata.cwp.govt.nz/datasetrequest/show/226

Thanks!

Basemap

Posted by GMHeyes on 12 January 2015 in English (English)

I have tried quite a few of the various maps available for use on my Garmin device, as of yet I have been unable to find one that looks exactly the same as the basemap! is there one available for the uk?

本日の編集

Posted by jo3fdi on 12 January 2015 in Japanese (日本語)

長浜市役所が2015/Jan/05から移転稼働しているのでそのタグを付加。元「市立長浜病院」→「長浜役所東別館」→「長浜市役所」と言う変遷になる。住所は長浜市八幡東町632番地。

その他、市道南田附神前線の八幡東町内供用開始(ずっと前ですが)に伴う車進入止めバリアタグの撤去と長浜楽市側、長が浜赤十字病院側の信号機タグの付加を行いました。また、廃業店舗(竹内書店)のタグを削除しました。

従来の長浜市役所(長浜市高田町12-34)は新しく市の施設が建設されるような構想がありますが、建物が現状のままなのでそのまま放置します。 新市役所の東に隣接する市道は南への延伸計画がかなり以前からあり、現在平方町までの延伸予定ですが、どうなるか判らないので要注意です。 ちなみに長浜市(特に合併前の旧長浜市街)の道路計画は計画後ン十年経ってもそのままと言うのが多すぎます。また街区整備も昭和50年頃以降進んでいません。

気になっている点

私のGPSデータの誤差が大きいため、基盤データからのインポートと大幅にずれているらしきものが結構あるようです。より精緻なデータの取れる方での修正を望みます。

他の地図データからのインポートは誤りもあるため十分確認が必要かと思います。

結構な頻度で道路の付け替えがあります。インポートよりも出来る限り実測が必要かと思います。

道路名称については、国道県道市町道の他に通称が複数あるケースが多々あります。どれが間違いと言うものでもないですが、新住人の中には「誤認」されている方も多いので注意が必要です(旧町名や通称町名なども)。

#dream #dream 부산여행지 맵 만들기

Posted by kimilhwa on 12 January 2015 in Korean (한국어)

#dream 부산여행지 맵 만들기

Location: 기장해안로 (Gijanghaeanno), 기장읍, 기장군, 부산, 대한민국

Teste 01

Posted by Sonatório on 11 January 2015 in Brazilian Portuguese (Português do Brasil)

só testando

Location: Centro, Cachoeira, Bahia, Região Nordeste, Brasil

Learn-a-tag: leisure=fitness_station

Posted by jgpacker on 11 January 2015 in English (English)

Recently in Brazil, a number of cities started adding outdoor fitness stations in public parks. In my city only, there are around 20 of these. After looking for a tag to describe this feature, I found leisure=fitness_station.

Elderly fitness station

Adapted from the wiki page:

A fitness station is an outdoor facility with one or more exercise equipment. This is typically operated by a local government, and free to use for everyone. Often inside a fitness route or a park.

It has a good number of uses right now (1877), but my gut feeling tells me it's not known as much as it could be.

Cheers, John

Honda HRV 2015

Posted by honda jakarta on 11 January 2015 in Indonesian (Bahasa Indonesia)

Kini Honda HRV 2015 sudah hadir di Indonesia, banyak peminat mobil Honda yang menunggu kehadirannya. Meskipun keduanya memiliki platform yang sama namun dari segi design interior dan eksterior tidak ada kemiripan mobil Honda HR-V ini dgn Honda Jazz. Namun mobil ini hampir sama juga dengan Nissan Juke jika dilihat dari tuas pintu yang tersembunyi pada frame kaca pilar C.

Berikut ini daftar harga Honda HRV 2015 *manual A RP. 234.000.000,- *manual S RP. 257.000.000,- *matic S RP. 267.000.000,- *matic E RP. 288.000.000,- *matic 1.8 prestige RP. 355.000.000,-

info lebih lengkap kunjungi : http://www.infohondamobiljakarta.com

Mapping public transport in Belgium

Posted by Polyglot on 10 January 2015 in English (English)

Naamsepoort with line 616 highlighted by MapCSS This article is inspired by http://blog.openstreetmap.de/blog/2014/12/wochenaufgabe-kw-5152-oepnvfahrplanwechsel/ but adapted to how public transport is mapped in Belgium at the moment.

I also recorded an editing session in JOSM:

Add bus route in Antwerp Belgium

Apparently public transport companies do all the major changes to their time tables towards year's end. At least this seems the case for both Germany and Belgium. So we have some changes to process in Belgium as well.

In Germany they have weekly assignments. I guess that, over here, cleaning up the mapping of public transport, will become a task, that takes somewhat longer than a week to accomplish.

We also still have quite a large amount of lines that are mapped in the now deprecated way, using just one route in a futile attempt to describe all its variations. If all you wanted to do, is render on a map where the buses pass, this may be sufficient, but in case you want to describe actual itineraries, that is severely lacking. Those older routes take the longest to convert, but at least there is an approximate indication of the itinerary when they are present.

We have, however, many routes which are already on 'version 2'. The problem with those is that they are prone to change to the timetables/itineraries and they get broken by edits with inferior editors, which don't process relations properly.

This got me thinking about a way to:

  1. detect that these routes are in need of attention?

  2. keep them up-to-date in a practical way?

I've been working on scripts to automate the boring parts of this arduous task. The source code can be found here:

https://github.com/PolyglotOpenstreetmap/Python-scripts-to-automate-JOSM/blob/master/FindWaysBelongingToRoutesStartingFromStops.jy

and here:

https://github.com/PolyglotOpenstreetmap/Python-scripts-to-automate-JOSM/blob/master/compareRoutes.jy

Incidentally those scripts also help when creating routes for bus and tram lines which aren't in OSM yet.

They depend heavily on the availability of PT data from De Lijn and TEC though. So their performance is optimal when such data is available, which isn't the case for the Brussels' operator MIVB/STIB, unfortunately. Those can be added in more traditional ways, but instead of starting from the stops to add an itinerary afterwards, it may make more sense to work the other way around.

On to the translation/adaptation of the German week assignment

Mapping public transport in OSM is a subject which is often poorly understood. The consequence is a multitude broken route relations, which don't get updated. For users of the data this is rather worthless. At the time of writing, it seems like 3, and possibly a few other, mapping schemes are in use (I found out recently that we deviate from what the wiki proscribes in Belgium as well, this article was started to describe at which points in detail).

Research

Before starting to edit, some research might be needed. Does the route_master relation still describe an existing bus/tram line? Do the route relations still describe actual variations accurately?

Sometimes lines get new identifiers (line numbers). This occurred in Beringen recently:

Beringen krijgt nieuw busnet vanaf 14 juli

I worked on updating those over the past week (Jan 2015). The changes happened in July 2014 though, I'm working on a way to detect such changes in a more timely way and to present to the community at large through a web interface.

Mapping

To map public transport, you'll need an editor which can work correctly with relations, iD is not up to that task, as it's not possible to influence the order of the members with iD. And the order of relation members is crucially important in public transport route relations. (It is important in our cycle/walking node relations as well, if you want to do automatic validation on them, but that's another story).

JOSM is the only suitable editor to accomplish this task and not only because of the relation editor, but also because it's the only editor which supports the MapCSS to properly visualise the data and a scripting environment to use the scripts I created to help with the task.

Tagging

New routes and all the ones we bring up-to-date, should be mapped according to the 'new' Scheme. For Belgium it's described here:

http://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Bus_and_tram_lines Stops/Stations

In the new scheme a separation is made between where the passengers wait and where the (front of the) bus/tram/train halts on the way. The latter is mapped as a node which is part of the way. Although all stops of De Lijn and TEC are now in OSM, these stop_positions were not always added. Please add them if you are already editing/splitting the way for other purposes.

public_transport=stop_position
for bus stops add bus=yes
for tram stops add tram=yes
for train add train=yes

These nodes don't get extra information like name, ref, route_ref or zone. (at least in Belgium they don't)

When this serves as a terminal/initial stop for some of the served line variations, split the way at this point.

Platforms

In case a platform is present, this can be entered as a way or an area.

public_transport=platform

To get them rendered add:

highway=platform for bus stops

or

railway=platform for tram stops

In case of a closed way for an area add

area=yes

At the moment I haven't found a reason to use multipolygon relations for these.

In Belgium, these platforms don't get any extra tags, except for tactile_paving=yes/no if a way was used to map it and those foot massagers are present.

In case of an area was used for mapping the platform, it's probably better to add a highway=footway with tactile_paving=yes. The imagery of AGIV is good enough to determine where their extremities are. They look like white T's

Platform nodes

To keep things simple and manageable all bus and tram stops in Belgium are mapped on nodes. I never considered moving the details like name, ref, route_ref and zone to platform ways, as that would result in them not being shown anymore by the MapCSS style I created for that purpose.

These nodes can designate the position of the pole, a corner on the shelter where the 'flag' is mounted, or if this is unknown, the position of the B of the word B U S, if visible on the aerial imagery.

In Belgium all bus and tram stops of De Lijn and TEC are now mapped, most of them by yours truly. (Click on the links if you want to download files converted to OSM format for verification). In case the position could not be determined from the aerial imagery these positions are approximate until somebody surveys and moves them.

TEC also provides shapefiles, which I converted to GPX. This is mostly interesting to know which streets the buses are likely to follow and to exclude the streets where they most certainly don't go.

In Brussels we can't seem to get permission to access to the data of MIVB/STIB, but the exact positions of the poles are in the dataset of UrbIS, which we are allowed to use. So we should be able to map the PT network in Brussels the (mostly) traditional way. UrbIS contains the tram rails as well. It's quite an undertaking to integrate them in OSM, but once they're in, it becomes trivial to add the tram lines. If you provide me with GPX files of your bus rides on lines in Brussels, I might even add/update them for you.

Some stops of De Lijn and TEC extend into the Brussels Region, The Netherlands, Germany, Luxembourg and France. All these were added to OSM as well. In fact, I did those first, to find out which was the best way to do so. At first I used dedicated nodes per operator, but that's not the proper way, after all (I was never entirely happy with doing it that way, but it had a few advantages as well in case some fields didn't happen to agree). Now each operator got their own 'namespace' and those nodes should all be merged by now.,

public_transport=platform
for bus stops add bus=yes
for tram stops add tram=yes
for train add train=yes

For backward compatibility and to get them rendered:

add highway=bus_stop or railway=tram_stop

All bus/tram stop nodes have a unique ref to identify them. To make it possible to use a single node for multiple operators, these are mapped as:

ref:De_Lijn ref:TECB ref:TECC ref:TECH ref:TECN ref:TECL ref:TECX

Indeed, each entity of TEC assigned their own identifiers and for buses which wander into another provinces the stops have more than one.

For Veolia, Connexxion, MIVB/STIB, etc we can safely use:

ref

But mostly we don't have identifiers for these.

Sometimes it's necessary to use separate namespaces for name as well:

name:De_Lijn

name:TEC

When 2 entities of TEC don't happen to agree on the name to use, I just picked 1, mostly arbitrarily.

At some point we decided to include the name of the municipality as part of the name:

Blanden Kerk

Haasrode Kerk

Making an exception for the larger cities like Antwerp, Brussels and Ghent. In retrospect I would prefer to start prepending Gent as well. For Charleroi and Liège, I simply included them as part of the name. For stops outside of Belgium this is not customary. For bilingual areas, I also dropped the village/city names, as they become rather long otherwise.

The same applies to route_ref. This tag includes all the lines which serve this bus stop.

For QC purposes one could also include not_served_by for those stops skipped by express buses, or when it's not possible to serve them as the bus makes a left turn across 2 lanes soon after where the halt is located.

It's possible to include

* shelter=yes/no
* covered=yes/no
* bench=yes/no
* bin=yes/no

Or it's possible to map these as separate elements:

* amenity=shelter
    * shelter_type=public_transport
* amenity=bench
* amenity=waste_basket
* building=roof

Stations

for bus stations you can add a node or an area tagged as 

* amenity=bus_station

stop_area relations

All of the above can be collected in a stop_area relation. One stop_area relation for each highway=platform node. So in simple cases one for each side of the road.

stop_area_group Relations

All stop_area relations can be collected in stop_area_group relations. JOSM will complain about these. Let it. The validator may catch up some day, or not. They were in the initial 'new' PT scheme, and then they were dropped for some inexplicable reason.

Once the stops are mapped according to 'PTv2' - we can start adding route relations for all the variations. The good news is that in Belgium almost all stops have been added by now. The exception are those stops in Brussels which don't get served by De Lijn or TEC. Add OSM notes to the map with all their details and send me a link to the note for those, if you don't feel comfortable adding them directly.

Route Relations

In PTv2 there is one route relation per variant. So the simplest lines will have 2 variants, one for each direction (The exceptions confirming the rule are the Ringbus 600 and 601 in Leuven and some school buses like 586). The good news is that we can compile route relations for each of these variants automatically for lines run by De Lijn and TEC.

To keep the number of variants (and the work to keep them up-to-date) limited we only have a variant for the longest sequence of stops for telescopic routes. I believe it makes sense to save contributors' precious time and to limit the number of route relations, ways need to be members of. For rendering there is no difference (except that it means less processing) and for routing, it's relatively easy to cut out the ways sequence which is needed for a shorter sequence of stops. (I know it can be done, as I've scripted exactly that to assist contributors when creating new route relations)

Each route relation has all the stops at the end. These are the platform NODES mentioned higher up. These are the only nodes the conversion scripts know about, so these are the nodes which can be added automatically to the template routes it creates. Their order matters, of course. At some point I made the arbitrary decision to have the ways first, followed by the stops, as that's the way JOSM would sort them (if you were foolish enough to let it do that on all the members of the relation at once. JOSM can sort the ways fine, but it's smarter to give it a subset of just ways. It doesn't cope very well if ways are used more than once (loops, spoons)).

Apparently the wiki contradicts this and proscribes stops first, then ways. Ultimately I don't think it matters much, unless it would cause 'edit wars'. I prefer to have the ways first, as that is what contributors work on. The stops are added by a script, at least in our case.

If the bus uses a way more than once, it will be in the route more than once. The same goes for the stops, which get served more than once by the same variant. This is less common than ways being used more than once.

Master_route Relations

All variant routes belonging to the same line are collected in a master route relation.

Challenge: keep it all up-to-date

I will come up with a script which can make an overview of which routes are in need of attention. Hopefully I can get an account on a dev server to do so.

Location: Domberg, Kobbegem, Asse, Halle-Vilvoorde, Flemish Brabant, Flanders, 1730, Belgium

Mapeando Ciudad Lineal (Madrid) Spain

Posted by Canellone on 10 January 2015 in Spanish (Español)

Mapeando el Distrito de Ciudad Lineal de Madrid.

Más info en el Link: https://wiki.openstreetmap.org/wiki/User_talk:Canellone

Location: San Pascual, Ciudad Lineal, Madrid, Área metropolitana de Madrid y Corredor del Henares, Comunidad de Madrid, 28028, España

Erreur de donnée(navigation)

Posted by Sojea on 9 January 2015 in French (Français)

Bonjour, j'utilise depuis peut vos cartes avec le GPS Be on Road, il se trouve que lorsque je veut me diriger vers le sud à partir de chez il indique qu'il faut tourner à gauche alors que cela est interdit, la Nationale est à deux voies avec interdiction de la couper. Merci de la correction pour les autres utilisateurs. Bien amicalement Sojea.

Location: N 7, Montélimar, Nyons, Drôme, Rhône-Alpes, France métropolitaine, 26200, France

Eksporter billede

Posted by Søren1997-Hadsund on 9 January 2015 in Danish (Dansk)

Hej. Jeg kommer fra den Danske Wikipedia. Jeg har uploadet flere kort her fra OpenSteetMap, blandt andet dette https://commons.wikimedia.org/wiki/File:Omkring_Hadsund_map.png .Det har siden sidst i 2013 være mig umuligt at ekspoter et kort her fra OpenSteetMap, da det ikke er muligt at få filen gemt som .png? Det er nu kun muligt at gemme filen som .osm? Er det nogen der kan forklare hvorfor man ikke længere kan gemme i .png? Mvh Søren

untrue size of Berlin's Memorial of Europe's murdered Jews

Posted by malenki on 9 January 2015 in English (English)

Just realised that the steles forming the Memorial to the Murdered Jews of Europe don't have the correct size. Though I salute to the mapper who mapped the memorial: is there someone who can give the steles their true size? Regarding to wikipedia they are 2.38m to 0.95m (with different height values).
I created one with the exact measures but think that it takes a little more to create all of them in file.

Location: Mitte, Berlin, Germany

Mapillary | Mt. Abu | 27th December 2014

Posted by shravan91 on 9 January 2015 in English (English)

Went biking in the Aravallis. See what I did!!

Mapped using Mapillary and Shot a not so awesome, Downhill Video!

Mapillary - Mapped the hill station!

I shot a video while I was coming Downhill - Here's the Youtube Link.

Here's my STRAVA post.

Location: Main Market, Mount Abu, Sirohi, Rajasthan, 307500, India

Contributor Statistics 2014

Posted by SimonPoole on 9 January 2015 in English (English)

I've updated the statistics that I regularly produce from our changeset dump, see stats page on wiki.openstreetmap.org, to the end of 2014 numbers.

The well known trends continue with growth in every category with a total of 472'925 contributors since 2005.

Looking back on the 10th anniversary celebrations in 2014 it is important to note that was celebrating the birth of the idea, not the start of success.

Success slowly started in 2007 with the project taking off in 2008, for a Web 2.0 undertaking prior to that it was a flop. Perhaps even better than a graph Martijn van Exel's "then and now" map comparision with 2007 illustrated just how much of nothing OSM was back then (unluckily the comparision is no longer available).

It is diffcult to nail down why the sudden change in course happened, likely it was more the pieces of a puzzle falling in place than just one cause. However if asked to point to a single person and event, I would clearly point to Richard Fairhurst and the Potlatch editor being the pivotal person and thing that changed the course of history for OSM.

Building Osm2pgsql for Testing

Posted by pnorman on 9 January 2015 in English (English)

This is a copy of a blog post on my site.

Recently I needed to run a bunch of osm2pgsql tests in a virtual machine, so optimized the process. You would not normally do development in a VM, but it's useful for testing. It's particularly useful for me because my old Ubuntu server uses a development version of PostGIS which doesn't work with the testsuite.

I was using VirtualBox to run the VMs, and started with a base Ubuntu 14.04 server install on a virtual drive of at least 30GB. The flat-nodes tests require a lot of space.

Starting with the base, I updated the OS with

sudo apt-get update && sudo apt-get dist-upgrade && sudo shutdown -r now

This gave me a VM I could clone and use for other projects. Starting from a cloned VM, I installed the dependencies. Copying and pasting into VirtualBox can be a pain, so a bit of clever shell expansion minimizes the text I need to type

sudo apt-get install libtool g++ protobuf-c-compiler postgresql-9.3-postgis-2.1 \
  lib{boost{,-system,-filesystem,-thread},xml2,geos++,pq,bz2,proj,protobuf-c0,lua5.2}-dev \
  python-psycopg2

The osm2pgsql testsuite requires a custom tablespace for some of the tests, as well as normal PostgreSQL setup.

sudo -u postgres createuser -s $USER
sudo mkdir -p /tmp/psql-tablespace
sudo chown postgres.postgres /tmp/psql-tablespace
psql -c "CREATE TABLESPACE tablespacetest LOCATION '/tmp/psql-tablespace'" -d postgres

To get osm2pgsql, I was cloning my own git repo instead of the normal one, but if you wanted to get the source, build the latest version, and run the testsuite, I did it with

git clone https://github.com/openstreetmap/osm2pgsql.git
cd osm2pgsql
./autogen.sh
./configure
make –j4
make check

make check tends to take awhile to run, as it has to do several imports and create a lot of databases for testing. It also has to write a 20GB flat nodes file.

Redirect

Posted by Zian Choy on 9 January 2015 in English (English)

To see more stuff, go to my personal home page at http://www.zianchoy.com.

#MapLesotho - Heading towards a full basemap

Posted by DaCor on 8 January 2015 in English (English)

Its nearly a year since I started working with Fingal County Council on the #MapLesotho project and in that time a number of great milestones and activities have been completed so of which are:

  • Last July a huge mapathon with users from around the world added over half a million nodes of data for Lesotho
  • In Sept we had a mapping party in the Lesotho Embassy in Dublin with the Irish OSM community

Irish OSM community mapping in Lesotho Embassy in Dublin

  • A dedicated website has been setup - http://maplesotho.wordpress.com/
  • A series of classes where held with school children in Dublin teaching them to map and getting them involved in #MapLesotho

Fingal Council & Irish OSM members teaching in a Dublin school

A number of Irish OSM members / Fingal County Council staff are heading to Lesotho for 2 weeks from Feb 06th to 20th to work on the following:

  1. Get the local mappers (there are quite a few now) more involved, editing more frequently and start discussions about them forming a Lesotho OSM group with semi-regular meetups
  2. Train govt. planners (most are mappers) on the use of JOSM and OSM data with QGIS
  3. Conduct a number of mapping sessions at the national university
  4. Meet with govt. data owners to talk about release of (i) data to OSM for imports and (ii) permission to scan, recitfy and derive info from existing maps

We've still got 2 tasks running in the HOT tasking manager since last July's mapathon which we've been silently tipping along on.

With all of this in mind, a number of the folks in Lesotho have set next Friday Jan 16th as a date for the next #MapLesotho mapathon. A large group are coming together in Dublin in the Fingal Council offices to carry out a supporting mapathon.

MapLesotho Poster

We are looking for other groups around the world to again join in with us in our mapathons.

  • Organise you own mapathon / mapping party
  • Although it would be nice, it doesn't have to be on the same date so chose a date that suits you
  • Promote #MapLesotho among your local OSM community. Drop a mail to your local mailing list or see if there are a few folks meeting up, they might like to work on this at their meetup
  • Join in anytime! The 2 tasks listed above have been running since July so feel free to just jump straight in and take a tile or two.

Усть-Качка

Posted by irvadi on 8 January 2015 in Russian (Русский)

Начал прорисовку зданий и улиц своей Родины)

Location: Краснознаменная улица, Усть-Качкинское сельское поселение, Пермский район, Пермский край, Приволжский федеральный округ, 614524, Российская Федерация
Older Entries | Newer Entries