Recent diary entries
Just had a look at the map around Doha (Qatar). Strangely, each district name seems to be followed by a number in parenthesis. Out of curiosity, I'm wondering if anyone knows their meaning?
Out of consistency... I'd guess that these numbers should not be there. Unless that's really how local people call these places, the "name" tag should not bear the numbers. The numbers probably belong to another tag. Even better would be to have the name tag being written in Arabic as it's the local language... I'd do it if I was able to write in Arabic ;-)
Vihdoinkin aloitin kartoituksen Tahkomäentien varrella. Siitä voisi sitten laajentaa varsinaiseen Nilsiään asti joskus. Mutta pysytellään tänä vuonna ensin Tahkomäentien ja Syväri-järven välissä.
I have been noticing the removing of the preserved railway line rendering on the standard map. Is this a glich or is no longer going to be rendered as well as Monorail rendering. (Although sidings are still working)
I tried to use Google Maps in my Android phone. I downloaded a android app from But, I think Open Street Map is better than Google Map. :)
Over the last couple of weeks I've done a substantial amount of work on vespucci the OSM editor for Android http://code.google.com/p/osmeditor4android/, with the goal of a new release 0.9.4 some time in March. While a lot of the work is under the hood, there are a couple of new features that will make editing with vespucci a lot easier
- support for overlays (for example the OSM GPS tracks)
- imagery configuration from OSM imagery index hopefully making it easier to keep the available imagery updated
- support for imagery offsets
- multiple simultaneously active presets (vespucci uses JOSM presets)
- support for accessing the API with https and OAuth
and not to forget, you can now zoom out completly without getting sea sick :-).
Und wieder einmal habe ich eine Grundsatzdebatte auf talk-at angezettelt.
Es geht um das Abzeichnen und Eintragen von Gehsteigen (sidewalk). Ich habe das in Innsbruck einmal probiert, das wurde konsequent gelöscht. Die Entscheidung damals meine Einträge zu löschen, waren im Nachhinein richtig gewesen. Es reicht doch, wenn an die Strasseneigenschaft, das "sidewalk" angehängt wird.
Ich frage mich wieder einmal, wann ist zuviel, zuviel?
Da folgt ein Rattenschwanz an Problemen. Wird dann an jedem Knotenpunkt eine Ampel eingezeichnet? Wie verlaufen die Relationen? Werden die Relationen dadurch nicht unnötigerweise verkompliziert?
Muss alles und jedes auf OSM eingetragen werden? Wann und wo ist Schluss damit? Was sagt die OSMF dazu, falls sie überhaupt zuständig dafür ist.
Als nächstes werden alle Oberleitungsmasten bei der Eisenbahn eingezeichnet. Jeder Kanaldeckel, alle Schneestangen entlang einer Strasse, die Gasthäuser mit Speisenangaben und Preisen. Das hat doch nichts mehr mit Navigation oder Stadtplänen zu tun, es ist ein reines füttern und vollfüllen einer Datenbank. Will man Google Konkurrenz machen? Keine Chance! Sinnvoller wäre es, sich auf die Grundlagen bei OSM zu konzentrieren und die Detailverliebtheit etwas einzuschränken bzw. nicht weiter auszubauen.
Ja, ich gebe es zu, dass ich Strassenlaternen, Hundekotsackspender (wer sucht bitte auf seinem Navi danach???) einzeichne. Aber ich bin auch dabei, mehr Hausnummern zu mappen (Bsp. Franking, Einsiedeln)
Die #OpenStreetMap #Straßenlistenauswertung  habe ich heute Abend in die Version 1.0 überführt.
- die Webseiten werden ab jetzt dynamisch erzeugt. Bisher wurden die HTML-Seiten nächtlich erstellt und waren dadurch nicht benutzer- oder aktionsbezogen anpassbar.
- die URL für das Straßenlisten-Wiki hat sich leicht geändert und ist jetzt . Wer auf die Auswertungsseite einer Gemeinde geht, findet dort den Link direkt zur richtigen Straßenlistenseite im Wiki.
- die Optik ist jetzt besser und der Seitenaufbau ist einheitlicher (einige Nebenseiten erhalten in den nächsten Tagen auch das neue Design).
- die meisten Tabellen sind jetzt sortierbar durch Klick auf die Überschriftszeile.
- es gibt eine Suchfunktion, um direkt eine Gemeinde zu finden.
- ein Impressum und meine Kontaktadresse sind jetzt angegeben. Die Seiten für Mitwirkende und Quellenangaben folgen in Kürze.
- es gibt jetzt die Möglichkeit, dynamisch eine neue Auswertung zu beauftragen. Dazu gibt es einen Link auf der Gemeinde Auswertungsseite. Es wird dann die Wikiseite neu gelesen und in zwei Schritten die Gemeindegrenze aktualisiert geholt und die eigentliche Auswertung durchgeführt. Die Seite lädt solange, bis das Ergebnis angezeigt wird (erkennbar in der Zeile "Stand Auswertung"). Der zu frühe Klick bringt aber nichts, wenn die lokale OSM-DB noch nicht aktuell genug ist. Die garantierte Zeit ist bei  ablesbar in GMT-Zeit! Achtung: wenn diese dynamische Aktualisierung zu oft verwendet wird, schalte ich diese wieder ab. Es ist mir dann auch egal, ob es nur ein oder wenige Leute waren, die da zu oft rumgeklickt haben. Diese Auswertungen belasten der Server einfach zusätzlich.
- technische Internas: einige DB-Connection Leaks habe ich entfernt und Frameworks eingesetzt mit Hilfe eines Mitwirkenden, sodaß die Codebasis verbessert wurde.
Fehlende Funktionalität seit Januar
- Das Ranking  der Gemeinden gleicher Größenklasse läuft seit Januar nicht mehr, weil ich beim Gemeindeverzeichnisupdate die Einwohnerzahlen nicht mit importiert habe. Das will ich in den nächsten Wochen nachholen.
Geplante Änderungen in naher Zukunft
- einige Seiten sollen einen FAQ-Link erhalten und auf der Folgeseite werden dann einige, häufiger gestellte, Fragen beantwortet.
- die Abdeckung von benachbarten Gemeinden soll grafisch auf einer OSM-Karte angezeigt werden auf der einzelen Gemeindeseite. Bisher ist immer nur ein Bundesland auf einmal anzeigbar und die Anzeige dauert lange wg. größerer Downloaddatenmenge.
- Zumindest der Frontend-Code könnte in absehbarer Zeit dann auf github veröffentlich werden.
Dietmar aka okilimu
Im harten Mappingalltag bei OpenStreetMap kommt manchmal das schönste der Gefühle viel zu kurz: die Liebe. Das haben wir zum Anlass genommen, der Community etwas Liebe zurückzugeben und haben etwas erschaffen, das uns alle näher rücken lässt. Ein Projekt, in dem wir die Liebe zu Kartographie mit der Liebe zu anderen Menschen zusammenkommen lassen: OpenLoveMap.
Die OpenLoveMap zeigt Euch den Weg zum nächsten Sexshop, Stripclub, Puff oder - falls die Situation das gerade erfordert - zum Standesamt. Egal, ob am heimischen Computer oder unterwegs am Mobiltelefon, der nächste Kondomautomat ist nur einen Handgriff entfernt.
Wenn die nächste Taggingdiskussion frustrierend ist und ziellos scheint, schaut einfach bei der OpenLoveMap vorbei. Wir hoffen, dass Eurer Leben dadurch schöner wird und dass wir auch weiterhin so eine freundliche und ausgeglichene Community sein können.
Dall'Hotel Torino si può fare un'escursione a Lio Piccolo...un gioiello incontaminato nella laguna. Non serve arrivare a Vnezia, dall'Hotel lo si può raggiungere in auto o in bicicletta Una lingue di terra che corre in mezzo alle acque della laguan, in mezzo a piccoli borghi pers nel tempo, nel silenzio ... fuori dal tempo, dallo stress dell'oggi
Out of curiosity I had a look for maxspeed= with values that contain at least one semicolon on taginfo.
It is most likely that this kind of maxspeed values are created by merging at least two highway segments with different maxspeed values.
If you want to have a look yourself click here and type a ";" in the (lower) search box for values.
Accumulating the numbers there are 1058 key-value-pairs containing a semicolon.
Interpolating this one can consider that supposedly at least 2116 highway segments got merged without the mapper taking good care about what he did. Looking at the topic it seems obvious that often more then two segments got united.
I do not know of any Quality Assurance tool which is checking for this kind of errors. If you do, please mention it at the comments.
More important than to fix this data is not to create new errors of this kind.
- Luckily the default behaviour for merging ways in JOSM has been altered from combining the values as "value1;value2" by default. Now the user is forced to select one of the conflicting values.
- In Potlatch2 combined values are shown in red with a warning sign.
- iD merges ways with conflicting tags without complaining. Of course there are no plans for an intrusive warning because "*they run counter to iD's goal of encouraging new users to contribute to the map because they make them feel insecure, even when their edits are perfectly legitimate*"link. Another issue against iD regarding conflicting tags is a year old.
Jeżeli poszukujesz najlepszych tłumaczeń z zakresu języka angielskiego to zapraszam na stronę angielski tłumaczenia Zabrze gdzie znajdziesz tranie biuro tłumaczeń i tanio wykonasz tłumaczenia języka angielskiego. Tłumaczenia z języka angielskiego w taniej cenie wykonasz w naszym biurze. Zapraszamy to tanie tłumaczenia do naszym tłumaczy.
According to osm the Majdan Independence Square, Kiev is empty – there are no barricades.
Hi, nearly all boundaries in Athens, Greece, suddenly disappeared from the Mapnik map layer. It seems that the new method for rendering administrative boundaries seem to have forgotten relation-based boundaries.
What is the fate for the relation-based boundary standard as opposed to tag-based boundaries?
I'm running again this year for the HOT Board, my third election. I sincerely ask HOT Members for their vote and the opportunity to serve them in a fourth year on the HOT Board.
My history with HOT is now getting long, and my dedication to HOT stronger than ever (not difficult, with HOT more amazing than ever). I appreciate Robert Banick's nomination and touching on some of that. I've also recently told the story of my HOT Year, including my time spent directly on HOT Board, which as Heather illustrated, is a substantial time commitment. While it's varied recently with time off for my family, pretty fair to say that I voluntarily dedicate 20% of working time to HOT.
So like many of us, I have so many ideas for HOT, it's hard to know where to start. Here's my priorities for myself over the next year, touching on where I think HOT needs to focus and grow.
Raised many times in discussion lately, our Bylaws need to be updated, to better reflect the shape of our community, and clarify ambiguities. I led the process of developing the HOT Code, and am ready to facilitate the process with all interested members for the Bylaws.
Connected, there are many HOT processes sitting collectively in our heads, that don't need to be enshrined in the Bylaws, but would be good to get these out objectively for us to better coordinate, in lightweight documentation. One recent example, would be a guidelines for administration of the tasking manager. We don't want to over proscribe the process, but as quickly and clearly collectively illustrate the minimum we need to know.
Building on that, the HOT Guide is something I'd like to help move to first version. Ourselves as members, our broad volunteer community, we all have so many skills to contribute, many outside the usual line of the mapping we do so well. Making it easy for everyone to find ways to contribute to HOT is what the HOT Guide is about.
Something we have not done consistently in our project and activation work is evaluation, yet incredibly valuable for us to steer our work. I want to help enshrine this practice. HOT as an organization itself came out of a series of evaluation and strategy building following Haiti. The recent Haiyan OSM Assessment gives one example of ways we can begin to examine our work, and I hope over the coming months, events and groups in Philippines and elsewhere can also contribute to our learning.
Humanitarian partners are what make our mapping work relevant to disaster response and preparedness, and those relationships are a big part of what HOT manages. We've reached a profile and gravity where there are a lot of organizations involved in what we do beyond just using the data, and great potential for coordination. Tapping into this more and figure out what this looks like is something I want to pursue.
Finally, want to step up more in helping our Board be productive, continue to serve in leadership of the Board, and facilitate our process and communication and meetings well. A big part of that will be collectively setting our strategy for the year, and increasing bidirectional communication with members and the community, especially with more frequent reports on our activities and finances.
Thanks for reading all of this, and considering a vote for me.
Ich heiße "Zyras" und schloss mich dem Projekt im November 2008, nach der Lektüre diverser Artikel (z.B. wdr.de and linux-magazin.de) an. Im Jahr 2007 machte mich ein Bekannter neugierig, da er auf seinem Palm Treo 680 OSM verwendete. Also kaufte ich mein erstes Fußgängernavi und steuerte meine GPS-Daten bei. Mit JOSM bearbeitete ich diese und fügte geografische Punkte ein. Ich war infiziert...
La Valle Caudina e' un pezzetto di Campania a sud-ovest di Benevento, fatto di campagne punteggiate di paesi, ognuno con i suoi piccoli tesori, e di bei paesaggi si montagna. Io sono originario di quella zona ma non ci vivo piu', e cosi' quando torno per le vacanze la vivo praticamente da turista, andando in giro in bici a scoprire qualche posto che non conoscevo. E sembra incredibile, ma me ne manca ancora qualcuno. Sono posti sconosciuti a chi non ci vive, e per questo spesso anche dimenticati e mal ridotti. E trovare dati su di essi e' difficilissimo. Un sacco di volte magari ho visto che un vecchio monumento era citato su qualche sito internet, ma arrivare a capire dove fosse e' stato difficilissimo. Cosi' ho deciso di lavorare, per hobby, ad un sito che ho chiamato Caudinia in cui sto cercando di raccogliere tutto quel che di notevole c'e' nella Valle. Per ognuno dei comuni che la compongono sto scrivendo una pagina introduttiva, verso cui si accede a svariate pagine di foto, corredate di informazioni sui luoghi d'interesse (per quel che mi e' possibile rintracciare). Il sito e' in inglese. Cosa c'entra OpenStreetMap? Be', essendo questo sito una specie di esplorazione virtuale, ha bisogno della sua cartografia di appoggio (per chi lo legge, ma anche per me che lo scrivo). Cartografia che Google Maps non mi avrebbe mai potuto dare, e che credo non esista affatto. E' per questo che se da un lato lavoro al mio sito, dall'altro ogni tanto sto curando la mappa della Valle Caudina su OSM. Da ogni edificio, o posto, trattato su Caudinia parte un link verso l'oggetto che lo rappresenta su OSM. Per ora su Caudinia non c'e' molto: 3 comuni su 14, che secondo me non sono neanche i migliori. Ma dateci comunque un'occhiata se vi va!
For the past several months, OSM Philippine data is getting noticed by a good number of people and organizations. This is in part because of our crisis mapping in response to Typhoon Yolanda/Haiyan but, I also think the data is now in a usable state in many areas thanks to the dedication of local mappers.
As I look around the map, there is obviously a lot of inconsistency in data coverage. Some are mapped up to the individual buildings while others just a
place=town node and nothing else.
Two things I consider to be a factor of this situation:
- Most mapping are based on satellite imagery. In the case of my country, while imagery is available over large areas, many areas still don't have hi-res imagery. This makes mapping "stop" at the edges of the imagery. The image below shows roads digitized during Yolanda mapping (map).
- Most local mappers are too focused on improving their own patch. This isn't really bad since you should really map areas you are familiar with but, this leaves behind adjacent areas looking bare and the coverage uneven. Even I am a victim of this micro detail mapping. Just look at Marikina (my mapping patch) on the left and Cainta on the right (map).
I still think we should map in detail our own local area, but we should also keep in mind to look beyond our patch to produce a good level of consistency and evenness of coverage.
Eugene outlined this level of detail concept a few years back. In the document, he proposed 7 LODs based on the following parameters:
- Scale / zoom
- Spatial accuracy
- Completion unit
Re-reading this document, I feel that the current Philippine data isn't even on the first level. So this year, I plan to incrementally work on reaching LOD 1 (while continuously improving my own patch of course!) focusing on the following:
- Check whether all cities and municipalities have at least a
place=town or citynode located within the town/city center;
- Check whether all national roads are mapped and connected to the cities and municipalities (in OSM tagging, the
highway=motorway, trunk, primaryroads);
- Move previously imported
place=islandnodes to each way/polygon (working on this now);
- Map major rivers (
waterway=river) and other large water bodies;
- Fix relations of existing provincial boundaries.
Definitely a big task, but we can always work together.
I've changed that wiki page around a little bit. Before we had a separate events list for winter/summer event series of pubs/mapping marathons. This works OK for resulting in an archive table, and I've kept that page arrangement, but I've now "transcluded" the details onto the main London page. Saves me maintaing two different event lists, and now it's all always at wiki.osm.org/London , which seems like a good fixed location which new folks are more likely stumble upon. Feel free to edit, especially if you want to organise an event!
I've always tried to list various events which are not organised by OSMers and not focussed entirely on OpenStreetMap, but quite strongly related (geo or open data themes). Often OpenStreetMap can benefit from being represented at these events, or to look at it another way, we can piggy-back on these events and use them as hosting for our OpenStreetMap activities. Lately there's been lots of them.
There was a big "Floodhack" event happening last weekend. Lots of hackers coming together to help(?) with UK floods. I was asked by two different people to come along, and to help present H.O.T. style disaster response ideas there. I couldn't make it. I have too much wedding nonsense going on. So instead I wrote out some ideas on a UK Floods wiki page the night before. I tried to think of some specific hack ideas, but only a couple of things came to me, and not really anything helping with UK floods. In fact I sort of agree with Tom Morris that the problems are political and the hack event was some kind of dubious stunt, however hacking which informs political debate (points the finger) may be possible, or just hacks to help everyone understand floods. Here's an OpenStreetMap-based flood heatmap [UPDATE: SK53 points to another nice example. The copernicus emergency management service maps of the foods use OSM data]. As usual for every cool OpenStreetMap hack there's a handful of uncool google maps hacks. The slow death of the Google maps API is a little too slow for my liking. I would say another positive from the event is this: The environment agency, who released some data for the Floodhack event, has come under fire for not releasing enough data openly enough. There's a good write up of the ins and outs of that by Owen Boswarva
Earlier I gave a talk at a private conference event at Arup. That went well, and I got to reuse my slides shortly afterwards as I was asked to run, or help run, one of the Open Knowledge Foundation Open Data Maker nights. This landed on tube strike day, and wasn't massively well attended, but then again, ten or so people is a good sized group, making for more one-on-one idea sharing. I talked them through my OpenStreetMap developer ecosystem slides (newly updated). As open data wranglers they were keen see simple tools for building a map using CSV datasources. This is something google really caters well for with google fusion tables. They were impressed by the simplicity of UMap, but there were a few other tools and tricks I wasn't aware of. OKFN timemapper is powered by google spreadsheets containing timeline data. And this schoolofdata article shows how to use an ImportXML function in a google spreadsheet, to do nominatim geocoding. Cunning! So I learnt a few things myself. I was asked to do a repeat session again some time. Even when it's not an OpenStreetMap theme, Open Data Maker nights are a thing we could piggy-back on to do OSM hacking. In the meantime though, the "Open Data Day" event is an all-day hackathon at the same venue this coming Saturday. Can't make it myself. Too much wedding nonsense going on, but it seemed quite fun last year, and again we can piggy-back on the event and use it to our own advantage ...if people fancy going along.
But people just want to go to the pub right? :-) Last time we had a pub meet-up was at Ye Olde Mitre. Nice old pub which Matt suggested. Very small, and at first it looked like it would be hopelessly crowded. Lots of people standing outside, and the upstairs was booked for an function. But inside downstairs we got a table fairly easily. Maybe by fluke.
Grant took a "photo sphere" of the scene in the pub. Is that online somewhere? Well for now you'll have to make do with this photo of grant making the photo sphere.
We were talking about Grant's mission to go meet the guy who made the 20millionth edit. It made for a great little blog post I thought. Pretty cool that changeset number 20 million turned out to be a genuine new contributor doing something interesting in London, and not some bot spewing changesets.
We also had a fairly long conversation about fairly long street names, and their abbreviated forms. When it comes to abbreviations, as mappers we don't do it, but the reason for that, is that as data users we can do it. And perhaps OSM cartography should do a bit more abbreviating a bit more often. Old paper street atlases will tend to do a lot of abbreviations. See here for example. This cartography was originally designed for paper not the web. With web cartography I think people expect a bit more spacing, and will instinctively zoom in if they can't see the name of the street they're wanting, so we get away with being less clever about it, but on a few occasions when working on printable maps I've noticed that Mapnik renderings will drop an awful lot of street names which could (and for a printout, should) have been included. Font size is another variable which amounts to the same thing. Bigger fonts written on wider roads is better for printing, but means using less space for more information so we need abbreviations.
We talked about various other things. There was mention of a map called the "Uncles Guide To London", a map showing where to take your nieces/nephews on an exciting day out in London. So sort of like a tourist map, but with an interesting niche focus. Looks like interesting cartography there too. Naturally the question is, can we generate an uncles map from OpenStreetMap?
If you have a pro-active do-ocratic answer this question and others like it, then make plans to be at the London OpenStreetMap hack weekend in a couple of weeks (8th/9th March), where such ideas will be do-acratically pro-actively done. But for now perhaps you'd like to just chat about such crazy ideas over a beer or two. That's what the pub is all about!
Come along TONIGHT to the Mucky Pup near Angel from 7pm. All the details on the wiki