Recent diary entries
hello can someone help ? we need to convert osm map to mca extension, what we have to do ?
Recently I noticed that the links that I have been using for heritage:website in Flanders were broken. Since this has been going on for a couple of weeks, it is not just a temporarily hiatus, but a permanent problem. So I have to update them all.
The old format was http://para.ms/relict/<relict-number>
First, I use an Overpass query to find all those listed buildings.
Overpass allows you to open the result in an editor, e.g. Level0.
Level0 is a "simple" editor that allows you to edit OSM data
The editor is so simple that there is no find+replace functionality. So I copied all the data into a text editor on my computer. There, I replaced the wrong URLs with the correct ones. This is a straightforward operation on any text editor. Then I copied all data back into the Level0 editor.
I logged into OSM. You can find the login button just above the data section, on the left. I confirmed the OSM dialog in order to allow Level0 to use my account
The result is that Level0, now knows who I am
After filling in a changeset comment the data is ready to be uploaded
is this a mechanical edit ? Not for me. I added at least 90% of those URLs myself. I checked several URLs myself and found that none of the old URLs were working anymore. So for me this is just a resurvey of data.
I also used this principle to update some fire hydrants that I added without specifying the type of the hydrant. This mechanism was also used to add some wikidata numbers to administrative boundaries in Belgium. Since I manually looked up the wikidata, this was not a mechanical edit neither.
I admit that this can be used to perform mechanical edits, but nevertheless I consider it as a powerful tool to quickly edit some incorrect data.
MapRoulette is wondrous in many ways but has three issues. First, if you're using an online editor, the time taken to open each task is significant - around 3-5s to open a new instance of iD for each task. Second, that online editor has to be iD, so it's not suited for those of us who use P2. Third, the process for creating your own tasks is fairly cumbersome, especially if you're working on a small series of tasks to be completed by one or a few people.
Potlatch 2 now implements a fast, light way of moving through a series of tasks. It's intended for small-scale personal work rather than planet-sized challenges. There's no 'resolve' button - it's just a way of moving between locations efficiently.
It works like this:
Create (or find) a GPX or GeoJSON file containing the locations.
If it's a GPX file, it should contain waypoints. Each one can have a description in a <desc>, <cmt>, or <sym> element.
If it's a GeoJSON file, it should contain Point features. Each one can have a description in the 'name' property (or, failing that, the first property).
Open it in Potlatch 2 with the Tasks button.
You can either load a file from disk, or type a URL and click 'Fetch URL'. (For the latter, note that the usual nonsense about needing a crossdomain.xml file at the root of the server applies, sadly.)
Move from task to task with the palette.
The map will centre on the first location. When you want to go onto the next one, click the forward arrow. To go to the previous one, click the back arrow. And that's it.
Try it for yourself using a GPX file of waypoints. If you don't have one to hand, these files from the Adventure Cycling Association of long-distance cycle routes across the US are fun.
I'd be interested to hear of other formats this could support, and further suggestions for improvement; and it would be lovely if authors of other editors were also interested in exploring the idea.
The tagging mailing list is seen as the main place of discussion when dealing with tag's definition.
However I feel that a mailing list is no longer an appropriate place for that. The tagging mailing list often deals with very specific topics, which most people aren't interested in. The result of this is that a lot of people that could bring value to specific discussions are not subscribed to the list and therefore have a hard time participating because joining such a high traffic mailing list is not worth it to them.
My suggestion is: Let's move the tagging discussion to a forum! This way people can pick some topics they are interested in and discuss to their heart's content without bringing hundreds of email copies to people that aren't as interested. Besides, everyone can participate.
Made it to 1111 changesets. Random and arbitrary, but noteworthy enough to write a diary entry on it.
Happy Holidays, all!
It's a day short of a year since OSM-PHL got a letter from the Philippine Department of Education (DepEd) allowing us to incorporate some attributes of their school database into OpenStreetMap.
DepEd's name for their project "maPaaralan" is a portmanteau of Map+Paaralan (Filipino word for school). I hope to revive this effort and see where we stand right now. The original discussions are here
I promised myself to contribute on more local projects next year, so I hope to make OSMaPaaralan as my first such project for 2015. See my OSMaPaaralan workplan
P.S. Hah! It appears this is actually my first diary entry, too. :D
One of the projects I have been working on since April this year, is adding lanes & turn:lanes information to all motorways, trunk roads and primary roads in Flanders.
The work is far from finished, as you can see on
This is the Overpass Query I used: http://overpass-turbo.eu/s/6zf
I held the first of a series of introductions to OSM today, for my employers members of EWB (Engineers Without Borders).
A great turnout, with 25 people turning up to listen at the head office, and several others tuning in via our video conference system. A great start! Even better, when asked if they wanted to contribute after the presentation, close to everyone was interested. A good promise for future mapathons in the Oslo area and rest of Norway. The presentation was a little bit of everything, since we had only 30 minutes available. We covered topics such as different uses for OSM, where I presented my favorites in terms of mountain biking and historical mapping, and transitioning into humanitarian mapping resources and what we can achieve with very little effort.
Shoutout to Pete Masters and Nick Allen for helping out with some advice and links to good presentations and other material from Missing Maps & HOT, really useful.
Next time we will be addressing actual tasks in the HOT Task Manager, can't wait to get started.
Ho, Ho, Ho
Antlers, what a good idea. If you want to break the ice & chat with a bunch of nice people, try wearing antlers. I hope I haven't given too many people my cold - honestly, it's just been a little nuisance until yesterday when I nearly lost my voice.
I'm certain that the Missing Maps Team deserve a brilliant Christmas for all the hard work they put in making these events run so smoothly - It's a pleasure to work with you guys & Thank You. I'm including all the HOT people who turned up to help - brilliant, you're advice (and waiter service delivering mince pies) is invaluable.
Great progress folks - I can't wait to see the full stats when you've all finished any squares you were working on, but 34% done during the course of one evening, and many more squares started & just needing a little more work - that's impressive!
I'd like to see all of you at future mapathons, it's always amazing how quickly people progress - if you'd like a little light reading, have a read of LearnOSM section for Remote, Armchair or Mapathon mappers which aims to helping you with everything you will need to map remotely for these tasks. Personally I find it displays quite well on my phone.
LearnOSM is something I've become deeply involved in now - it's the 'HowTo' for many things that the Humanitarian OpenStreetMap Team - HOT promote, so it includes many sections on how to map, how to use JOSM & iD, and for NGO's how to extract & use the data that OSM produces. It's worth spending time delving around in there - there's so much information that no index is ever going to do it justice - you just need to spend a little time delving around.
A little help please.
- It would be really great if you could finish the squares you started on - it's much easier for you because you know what you did, and what's still to be done.
- If any of you have got photo's of buildings, huts, roads & any of the other structures that we are mapping in Africa, and you can release them to HOT with no copyright restrictions so I can add them into LearnOSM it would be very helpful - a picture says a thousand words.
- Translation of LearnOSM - always welcome if you fancy having a go. Links are off of the site (click on the pencil). It's amazing how many people all over the world want to help, and if we can give them the information in a language they can understand it makes a big difference.
Have a Happy Christmas & a Terrific New Year,
and I hope to see you all again in the future at another event.
Nick - the Tallguy with antlers, bald head & a cold!
Added yet another list of POI's and Public facilities near Al Ghurair Center and marked the footpath in and around Maktoum Hospital Road and Maktoum Road with all the possible Pedestrian Crossings.
The vast majority of my changesets have still been in and around Houston. I've made various other fixes around the country, sometimes related to notes, sometimes at random, and in a few cases from a trip I made to/from greater Columbus, OH.
With the help of others, a sizable amount of the traffic signals are now mapped in and around Houston. I've also found a few roads that should be tertiary or better that had been left as residential or unclassified. My focus has shifted between road features themselves to building outlines, points of interest (POIs), address data, and occasionally land use if I can see a large parcel of land with e.g. nothing but trees on it. Occasionally I'll map stop signs if I know the area well enough but it can be a considerable pain due to the direction tag required.
I'm now serious enough about mapping that I've switched to JOSM for the vast majority of my editing. I still use iD for the occasional simple edits or when I'm on a computer without JOSM installed, or sometimes to edit turn restrictions. Dualizing roads in iD was a real chore. Actually, it's extremely difficult with iD by itself; usually I would switch to Potlatch 2 at least to add the actual parallel way. The only reason I stuck with the online editors is that my first experience with JOSM was on a computer I had no business trying it on (an old PC with an 800MHz Celeron CPU and a whopping 256M (0.25G) of RAM) with predictable results. The nice things about JOSM that I consider most notable are:
- It's Java, so it runs on just about any computer regardless of operating system (one less reason to dread ditching Windows).
- You can add plugins to make certain tasks easier (I have one specifically to speed drawing rectangular building outlines).
- JOSM has tons of additional features that wouldn't be possible or practical in an online editor.
- The parallel ways tool is much easier to use than the one in Potlatch 2 and makes a more complete copy of the way (nodes with traffic signals, crosswalks, etc. are tagged on the new way). Note: this is mostly good but there are cases where it can be a problem as well.
- The response time of JOSM is much faster than iD ever will be on the same hardware. This is especially true when editing areas like downtown Houston.
- JOSM has search and replace functionality. If, for example, someone added a bunch of McDonald's locations, and misspelled it MacDonnold's or something equally hideous, it's easier to fix and your chances of swearing while doing it are at least a factor of 10 less. Also good for finding and replacing non-conforming highway references (say, the lone SH 6 when everything around it for miles is TX 6) and for quickly de-abbreviating streets (search for "W 1st Street", edit name tag to "West 1st Street" once even if split into 20+ ways aka "road chop suey").
That said, iD and Potlatch 2 have specific roles that they are best at filling. There will always be people who don't want to learn JOSM and are happy using iD (or even Potlatch 2). That's fine, and I believe in having choices so that each mapper can decide for him/herself.
#251 Complete #252-254 need more work
The new Version of OSM-IQ 2go uses the Windows Search contract to integrate a search using Nominatim. This way you can use the Window 8 charmbar to search for a place in the Open Street Map database.
New Version is also available in Portuguese / Agora OSM-IQ também está disponível em Português
and hwo is able to find santa claus?
revenue with month of generation (pay-out two months later)
A small summary
Matching the end-of-year rallies for donations of a lot of institutions I want to have my little share in pointing the people to OpenStreetMap as receiver.
In 2011 I set up an affiliate account for OSM at Amazon.de. Since then a lot of people used the affiliate link to buy their stuff –4315 products– at Amazon so that we had a steady flow of averagely 140 EUR per month. Now for the headline I used: In this very month the 6000 EUR mark will be hit. With the beginning of the new year OSM will have received in total 6.021,25EUR. All numbers in full detail you find at the wiki.
In the name of OpenStreetMap I want to thank everybody who contributed to this sum. Of course I also want to encourage you to continue doing so! ;)
Have some relaxed holidays –
Image credit: AARoads
Here at Telenav, our editing team has been working tirelessly on adding signposts to OSM for the past months. Today, I am happy and excited to report that we have completed this major editing project! We added signpost information to over 9,500 exits across the United States, covering more than 25 major metropolitan areas and a few important connecting freeways as well:
Wait - that is not 'complete', is it? Well, you are right. We haven't covered every exit in the United States, not by a long shot. We have only a limited number of in house mappers, and a lot of things we want to achieve. So we prioritize the areas where we believe most people will benefit from our work. (On a personal note: that leaves me empty-handed out here in Salt Lake City - I guess I have to go out and map myself!)
We have learned a lot in the process, and we hope to contribute some of these learnings back as well. We already made quite a few improvements to the wiki pages for the
destination tags. Now that this project is complete, we will sit down and revisit these pages and add more clarification where needed. If you are interested in more tagging specifics, please see my earlier blog post on
destination. (And don't forget to read through the comments!)
I want to thank a few folks for making this happen. First and foremost our Telenav Mappers team, with lots of guidance from our resident road geek Robert. But also all of you in the community for giving feedback, calling us out on the occasional errors, and working with us to improve signpost mapping conventions. I feel proud to be a member of a great mapping community!
Haiii.. Hari ini kelas gue UAS Survey dan Pemetaan. dengan menggunakan laptop dan harus tersedia ArcGIS dan Google Earth.. eh iseng iseng jelajah google earth nemu ginian. Diary pake petaa. uuuw~ love love dah
Scout (USA) has been powered by OpenStreetMap data for about 5 months now. From day one, Scout users have been able to report navigation errors to us:
We have since received thousands of reports and we have worked hard to review them and learn from the feedback we get from our users. We have manually submitted OSM notes where we could not resolve the issue ourselves, and we have fixed dozens of map issues based on the incoming reports. But we felt that we could do a better job closing the feedback loop between Scout users and the OSM community. We have now taken another big step towards this goal with direct OSM Notes creation from Scout US.
Some Scout Feedback will automatically become OSM Notes
As of last week, certain kinds of feedback we get from our Scout US community will be posted to OSM Notes automatically. We apply a smart filter to make sure that only reports that we think the OSM community can fix get posted. For example, 'Destination Incorrect' reports will not make it to OSM, because Scout does not use OSM data to locate addresses and businesses. And we will only forward reports where the Scout user entered a sensible looking comment.
What happens when a Scout user posts a note that passes our filter? Let me walk you through the process. The screenshots are from an actual note posted by a Scout user a few days ago.
Post to OSM
The report is translated into an OSM note and posted to OSM immediately. We take the location of the report as the note location, and add the report comments as the note text.
The note will also contain a link to another page that contains more information that may help you resolve the issue. We include the a part of the GPS trace of the user before and after they submitted the report (anonymized to remove any personally identifiable information of the user) and the OSM map data version used when the Scout driver submitted their report:
As soon as the report is posted to OSM, we send the Scout user an email telling them that their report is being reviewed by the OSM community. Of course, we also encourage them to fix the problem themselves and include a link to the note.
The Scout report system monitors the OSM notes it posted and kicks in as soon as they are closed. (In this case, I resolved the problem myself by adding a turn restriction and tagging a link road as such.) We will send another email to the Scout user telling them that their note has been closed.
Our objective with this new feedback loop is for the Scout and OpenStreetMap communities to connect. With Scout's switch to OSM last April, all of a sudden we gained many more eyes on the OpenStreetMap data. This is an important step in feeding the intelligence we get out of that back to the OSM community. We plan to continue down this road and find more ways for the Scout community to help out in keeping OSM in great shape!