Polyglot has commented on the following diary entries
|Public Transport Plugin||19 days ago||
Are you working with version 23623? I still need to test with that one, but I also found an inconsistency, when stop_position nodes have the highway=bus_stop tag. I mentioned that this morning, so it could be solved in the latest version. It's still work in progress.
About the first comment. For the first and last ways, I think it makes sense to split them on the stop_position node, as the part before, in case of the first stop, and the part after, in case of the terminal stop, aren't part of the routes.
Checking whether the order of the stops is plausible, wasn't implemented yet.
|Public Transport Plugin||28 days ago||
Oh, that is very interesting indeed! Thanks for that tip. I'll probably work it into the diary entry.
|Belgische Mapper van de Maand: Stijn Rombauts||3 months ago||
Wat de busroutes betreft. Vanavond wordt bekendgemaakt welke student een oplossing mag helpen coderen in het kader van GSoC 2016; een JOSM-plugin die ervoor moet gaan zorgen dat het mappen van bus- en tramlijnen voor iedereen toegankelijk wordt en dat het eenvoudiger wordt om deze up-to-date te houden.
Ik was daar al een tijdje aan bezig, maar dan in Python, wat het minder toegankelijk maakt voor de 'modale' JOSM-gebruiker.
Binnen een maand of 2 zouden de eerste resultaten te zien moeten zijn.
|National Missing Maps mapathon||3 months ago||
Oh look, there is a brand new project for Swaziland:
For those mappers who already start to suffer from withdrawal :-)
|National Missing Maps mapathon||3 months ago||
I guess that's what happens when you give students of cartography a new toy to play with :-)
I agree that it was a big success. Personally I didn't make many pictures. I was busy enough presenting and helping people out. Since I don't know iD, I taught them JOSM right away. Getting started takes a bit longer that way, but I think it's worth it. I really have to get those instructions done by next time though...
|Mapillary||4 months ago||
By not following the wiki, you make life harder for other people who do. Glueing together 2 strings is a trivial thing to do in most programming languages. Now, if people use 2 incompatible formats, you'll have to add logic to figure out whether the url is already complete, or not.
In the wikipedia key we also don't add the full url, neither in wikidata.
Can you elaborate on why this makes things more difficult for you?
|Welcome to the new Missing Maps||5 months ago||
I'm glad to see that Missing Maps is expanding our community here in Belgium. Organise a mapping party and you get 8-15 people. Organise a Mapathon and you get 30+
It's great to see all these people learn about Openstreetmap. It's also great to see so many activities being organised lately. And not only to go and map remotely. We recently had one focusing on facilities for homeless people in Brussels, incorporating data that would otherwise have remained in isolation.
I see what we do remotely as a first step for local groups to build upon and this really works, maybe at a smaller scale than would be desirable (the local mapping happening over there), but at least it's set in motion.
|Setting up JOSM||7 months ago||
I should probably do it once more and this time record sound as well, while at the same time staying more to the point.
Good to know OAuth is already in josm-tested. Now it's not needed anymore to store the password locally.
|Belgian Mapper of the Month: Polyglot||7 months ago||
I'll have to update that map. The itinerary of bus 337 changed on the 1st of January. I already updated it in the OSM data, of course, but it's not reflected in that map at the moment. Ad also created more artwork in the mean time.
This job is never done :-)
|Belgian Mapper of the Month: Polyglot||7 months ago||
There are 2 PT plugins at the moment. I haven't investigated the second one yet, but the functionality I implemented needs the scripting plugin, as it's coded in Python:
|My christmas gift for the OSM Community - JOSM Keyboard Shortcuts Cheat Sheet 300 DPI||7 months ago||
I didn't know about '8' to go back to previous zoom view. That will be really useful in combination with the todo plugin. Sometimes my fingers are faster than my brain and I already used ']' on an element that still needed something done to it (Usually a building that wasn't made with 90 degree corners).
You might want to add ]. That todo list can be quite useful.
I'm also using 'b' all the time, as well as Ctrl-h and Ctrl-Shift-H for history.
Shift-J for making 1 area out of overlapping areas.
Shift-I for adding nodes where ways intersect. The new nodes are then selected, to add ford=yes or railway=level_crossing f.e.
Ctrl-Shift-G is replace geometry. At some point I had mapped that to 't'
Alt-Shift-J extracts a node, mostly important if you care about preserving history of the objects.
Shift-R repeats the tags from the previously selected object, replacing existing ones, keeping the old values for the ones the previous object didn't have.
Ctrl-Shift-E selects all connected ways.
Shift-P Parallel line mode. Interesting for drawing parallel rail tracks, dual carriage ways and islands on roundabouts...
Alt- with a number toggles visibility of layers, which can be handy when working with different background layers
With Mapillary plugin installed: Shift+Comma enables the layer. I tend to keep it in semi-automatic mode, in manual mode Shift-Period will download pictures for the current viewport.
|Belgian Mapper of the Month: Escada||about 1 year ago||
In the mean time my focus moved over to bus routes (since the stops are all in now) and Mapillary, obviously.
This really shows how helping beginning users to get started is a great investment in building the community as well as the map. I should try to do it more often... Of course it doesn't happen each and every time the "apprentices" become wizards themselves, but that's all right.
It's really great to see how Marc improves the lanes mapping, removing the wrongly tagged ones. Some mappers seem to be convinced all lanes need to be mapped as individual ways. I do it too, when I already modify the way for other reasons.
What is also great is the help he was able to provide in setting up a PostGIS database and querying it to help out with the PT related data. That kind of peer review and assistance is invaluable. Especially, as I'm just an amateur with an interest :-)
If Marc had come in a year or so earlier, he would probably have found me mapping and reviewing cycle node networks. I guess the experience built up doing that, helped a lot to explain him how to map the walking node networks that were starting to be rolled out back then.
|Power editing with OverpassTurbo and Level0||about 1 year ago||
I wouldn't mind doing a few Hangout sessions with you to show you the wonders of JOSM and how it works. Once you get used to it, it's very unlikely you'd still be put off by the software. It's just that initial learning curve bump you have to overcome.
There are also many tutorial videos on Youtube, created both by myself and by other contributors.
Having said that, there probably is a use case for level0 as a "quick and dirty", hands-on editor.
With JOSM you could have additionally performed Search At that point you could change tags for all selected objects at once (like you did with Level0), or you could have Added nodes to a todo list, to review them and work on them one by one, which makes the 'mechanical edit' a bit less mechanical Switched on MapCSS rules to highlight village name nodes to compare with nearby ones Or enable filters to hide everything that's not relevant for the task at hand.
|Sneak Preview of the Next Vespucci Release||about 1 year ago||
Indeed great news. I'm mostly using Mapillary to gather raw data while outside lately, but sometimes it's interesting to change something directly in the data. The easier the editor makes this, the bigger the chance that it will be done before it gets forgotten.
|What's your OpenStreetMap story?||about 1 year ago||
To give back to the free software community I've been contributing a lot to Wiktionary. That was fun for a while, until I found I was mostly warding off vandals.
In 2007 I discovered OSM and I thought: oh, I'm so late to have found this. Contributing to OSM is very rewarding. Even back when the map was only rerendered once a week, instead of in a few minutes.
We go out and relive the experience while adding what we saw to the DB. Naturally I started to work on our cycle node networks, then later the hiking node networks as they were rolled out. What's interesting is that it has many facets, going out, converting the survey, programming some scripts for automating the boring parts like checking our fragile route relations.
Over the past few years I got very involved in mapping public transport. Getting on the bus and adding stops little by little, at first. Then, after finally receiving permission, adding all the stops for almost the whole country and having the route relations auto generated (with the correct stop sequences for all variations). Now the job has become to connect the dots between those stops by adding the ways to the route relations.
In the mean time Mapillary came along. This has made it more fun again to go out and 'map' the world the 'photographic way'. Collecting raw source data, which can subsequently be used to more precisely position items on a rainy day (bus stops which can't be seen on the aerial imagery in my case...).
Having said all that, well it's a major time sink. That much is for sure. Still it feels more useful than getting 'addicted' to some on-line game.
Oh, and it's fun, of course. The day it's not fun anymore, or my interests shift once more, it may be game over.
|Public Transport VIENNA||about 1 year ago||
Hier ist ein Overpass Query falls du gerne mit die Routen als Skelett arbeitet:
[timeout:900]; area["name"="Wien"] -> .AT;
( node(area.AT); ) -> .allnodesinArea; ( rel(bn.allnodesinArea) ["type"="route"] ["route"~"bus|tram"] ->.routes; // All bus and tram route relations .routes << ->.route_masters; // Their route_master parent relations // rel(r.route_masters) -> .more_child_routes; // Possibly more route relations //(.routes // .more_child_routes) -> .routes; ( node.allnodesinArea ["highway"="bus_stop"] ->.stops; node.allnodesinArea ["amenity"="bus_station"] ->.busstations; node.allnodesinArea ["railway"="tram_stop"] ->.tstops; node.allnodesinArea ["public_transport"] ->.platforms; node ["highway"="bus_stop"] ["network"~"VOR|ÖBB.*"]; node ["railway"="tram_stop"] ["network"~"VOR|ÖBB.*"]; node ["public_transport"="platform"] ["network"~"VOR|ÖBB.*"]; ) -> .stopsPlatformsAndStopPositions; // All bus_stop, tram_stop, platform nodes // inside of Belgium and some outside of Belgium // in case they are served by De Lijn or TEC ( way(bn.allnodesinArea) ["highway"="bus_guideway"]; way(bn.allnodesinArea) ["railway"]; ) ->.tracks; // all bus_guideways and tram rails node(w.tracks); // and their nodes way(bn.allnodesinArea) ["amenity"="shelter"] ["shelter_type"="public_transport"] ->.shelters; // all PT shelters node(w.shelters); // and their nodes node.allnodesinArea ["amenity"="shelter"] ["shelter_type"="public_transport"] ->.shelternodes; // shelters mapped as nodes node(r.routes); // nodes for all the routes way(bn)->.parentways1; // the ways they belong to node(w.parentways1); // all nodes for those ways rel(bw.parentways1); // and all relations they are members of way(r.routes); // member ways of all the routes node(w); // and their nodes //way(bn); // side ways of these ways //node(w); // and their nodes too way(bn.stopsPlatformsAndStopPositions); // parent ways for platforms and stop_positions rel(bn.stopsPlatformsAndStopPositions) ["type"="public_transport"] -> .stopAttributes; // stop_area relations ( rel(br.stopAttributes) -> .SAG; // stop_area_group relations rel(br.SAG) -> .SAG2; // parents of stop_area_group relations rel(br.SAG2); // grandparents of stop_area_group relations ) -> .stop_areas_and_groups; //r.stop_areas_and_groups >>; node(r.stopAttributes); way(r.stopAttributes); node(w); ); out meta;
Das kannst du direkt in JOSM benutzen wenn du das mirrored_download plugin installierst. Oder in Overpass Turbo.
Ich habe alle HS in Wien die Teil sind vom highway auf public_transport=stop_position umgestellt. Wenn du jetzt die public_transport:version=2 auf die Routen setzt wirst du sehen das automatisch stop und platform Rollen korrekt gesetzt werden.
Ich habe die so gesucht:
public_transport=platform child (type:way -(highway=platform | public_transport=platform | highway=footway ))
|Mapillary-Straßenbahnmapping||about 1 year ago||
Nicht nur 'wegen' Nakaner. Es gibt auch Leute die ein cam unter ihren Sattel auf dem Fahrrad montieren. Für Mapillary ist das wichtigste das die guckrichtung richtig steht.
Ich meine es wäre noch etwas fremder wenn die Sequenzen umgedreht werden.
|Mapillary 1.0 for Android||over 1 year ago||
You found my diary entry before I was quite done with it :-) Usually I change it a few times when rereading. Anyway, glad you like it. I still feel a bit bad that it took 2 weeks to get started on it.
Also glad to hear you're working on that overexposure problem. Looking forward to help with testing that too :-)
|Busroutes in Brugge||over 1 year ago||
The data coming from De Lijn is refreshed 4 to 5 times per month, so I don't see how it can be outdated. Anyway, after the 'dispute' with Peeweeke I've mostly left Bruges alone. More recently I've been checking and updating all the itineraries all over Flanders region though. It would of course be better that somebody with actual local knowledge does this.
That's the reason for writing these and for creating some screencasts:
I hadn't realised I stepped on people's toes back when I was adding/updating those thousands of bus stops and I apologise for the inconvenience caused. When stops were already present, I conflated them manually, mostly keeping the positions from the original mapper. The stops with inaccurate positions were the ones which couldn't be placed based on the aerial imagery available. Each and every one of those stops has been checked manually, so it was certainly not a blind import.
I went digging in my mailbox. Apparently I resurrected a stop that wasn't served anymore for a line that changed. Since this was in 2014 it surprises me that the current data of De Lijn wasn't totally accurate at the time. When I hear about a change around here where I can check the ground truth, it's always accurate.
Anyway, I hope the work I did on the conversion of the data and the scripts can still help you to keep the lines up to date. It's all meant to make things easier, not harder.
The script to help with creating/updating the routes needs some more work to be really useful, but at the moment my interests are shifting toward Mapillary and their recognition of traffic signs, so I don't know when I'll continue to work on the itineraries or on the PT data.
|An idea for making it easier to link external data to OSM||over 1 year ago||
Euhm, osmdata.org doesn't seem to exist!
Concerning wikidata, there is also:
subject:wikidata that's who/what the statue or picture depicts architect:wikidata name:etymology:wikidata for streets or objects named after the wikidata item operator:wikidata=* brand:wikidata=* artist:wikidata=*
So it's rather versatile.
There is the issue of whether wikidata wants entries for, for example camp sites, but they want to include a lot more than just items noteworthy enough to deserve a wikipedia page, so normally that shouldn't be a problem.
It was indeed a bad move to refer from wikidata to OSM relations for named areas. I've been telling them that from the start. The only effect it had is that they didn't create more such properties, I believe.
What they also need on their side, is a way to use the OSM wikidata tag in a Wikipedia page, for example. Overpass is the ideal glue here. Unfortunately they deleted my attempts to create such links:
They kept this one: https://nl.wikipedia.org/wiki/Guido_Gezelle#Tastbare_gedenktekens
Anyway, I think wikidata can get us a long way towards the goal for permanent ids. For the items which really don't fit in their DB, we might still need other types of foreign keys. I'm curious how they would react if I'd start importing 50000 bus stops into wikidata, let alone those of the whole world, but I didn't ask, so maybe it'd be just fine. For the time being I'll keep using ref:OPERATOR=xyzxyz.
Also don't underestimate OSM contributors, we're generally quite an intelligent lot, able to decide whether something deserves to keep the same identifier or not. OTOH, it's also through that those external DBs will need to run Overpass queries to check whether all their identifiers are still present in OSM and if they should be on exactly 1 object only, they'll have to come over and repair occasional damage. At least they'll have a practical way of doing that.
What would be nice is editor support for the wikidata tag, though. Showing the identifier in the user's language and fall back if it isn't, instead of the Q-number.