Recent diary entries
The most fun I have with OSM is making the map better. Adding nodes and ways and tags. Seeing how my puttering around with JOSM or iD leads to a prettier map that is more useful.
Getting folks together in Salt Lake City where I live to have some OSM fun together. For example. A few weeks ago, I started a new thing called the Flash Map Mob. We do them every other week now in SLC and together we map something like 100 shops and restaurants every time.
The map becomes more useful and folks are having fun. That is what OSM is to me!
I don't need to sit on any board to do these things. Heck, I can probably do more of them when I am not on the board! So why do I do this? What value do I add being on the OSM US Chapter board?
I'll tell you and I'll be brief.
OSM is still very good at adding contributors.
(The graphs come from osmstats.)
What we're not so good at is actually getting folks to go out and map. Look at the flat daily active mappers graph for the US:
This is not a US only problem. But I want to start attacking it where I live.
I don't think putting on big conferences like we have makes more people go out and map. I think we should stop doing that as OSM US.
We should direct that energy towards creating smaller OSM gatherings around the country. Gatherings for mappers. I want us to do 4 of those in the next year. They could be like the fantastic event I attended in Seattle for OSM's 10th anniversary. (More photos). Or something else? We should find out. What does an OSM event look like that you would go to?
We should put local mapping groups first. We should step up funding local groups with mini grants. We should do regular sessions to help people get started organizing their group. Gather more data on what works and what doesn't to help direct our energy. Perhaps it's mapping party kits? Perhaps it's changing the web site to be much more community / mapper oriented? I want us to find out.
I work at Telenav on OSM stuff. So I am in a position where I can get a fairly big organization with lots of talented people to do useful things for mappers. Recently we published Missing Roads. It's stuff like that that gets people mapping. As a board we should encourage companies to enable mappers by having them build useful things and share data.
All of this should lead to us getting from ~250 daily active mappers in the US to 2x that in the next year. This is what I want to accomplish with the board on my next term.
I'm Lauren Jacobson and I'm running for the OSM board in order to further strengthen the OSM community through targeted outreach and community building projects.
I'm a geographer from Cleveland Ohio currently living in Washington DC. For years I worked within my company to promote better work with OSM. I recently joined Development Seed, the folks with the really great Lego table at SotM, which has given me the opportunity to be more engaged in the broader community. In the past year, I attended SotM US and SotM LatAM, participated in HOT activations in Chile and Tanzania, and am currently working to import 268,000 building footprints from Zambia. I've also had great experiences doing outreach about OSM at events in DC, from leading GeoDC, a monthly meetup of map and OSM lovers, to teaching an introduction to mapping session at DC's all female hackathon. Through these experiences, I've seen such great potential for growing a more diverse OSM community and am inspired to make a contribution.
As an OSM US Foundation Board Member I would:
- Promote local project creation and involve more community leaders with OSM projects
I recently participated in a Mapping DC event using field papers. We were stopped on the street by numerous people who were genuinely interested in the project and what we were doing. It is clear to me that so many more people would love to get involved with OSM, we just need to create the opportunities. We also have a great network of volunteers who would love to be ambassadors for OSM. I'll extend the resources that are available to OSM members who want to organize mapping parties, set up OSM booths at farmers markets, or neighborhood block parties. I would also work to improve existing tools for event hosting and publicity on the OSM wiki and provide mentorship and guidance to help OSM volunteers find each other on the local level.
- Encourage diverse participation at State of the Map US
State of the Map US has exploded in participation and is now the biggest OSM event. As the numbers have increased, so too has the percentage of participants whose organization or company pays for them to be there. This is good, these groups make great contributions. At the same time we have to work harder to also scale up participation from groups that are likely to be underrepresented, including women, students, minorities, and community volunteers. As we only have the opportunity to convene the community as a whole once a year, it is important that the conference gives as many people the opportunity to participate. As a board member, I will work to expand and promote the State of the Map scholarship program. I'll also work to increase conference attendance among local OSM groups.
- Enhance the benefits of joining the OSM US Foundation
I hope to increase the membership to the OSM US Foundation by encouraging active community participants to join the foundation, and communicating with local hackathons and mapping projects on opportunities to get more involved in leadership positions within the OSM community. Finding new ways in which OSM contributors can add value to the community and the foundation will definitely be a priority if elected.
Thank you so much for your consideration of my position and your time!
My name is Jonathan Witcoski. I am running for 2015 OSM US Board.
I joined OpenStreetMap November 7,2014 as part of a HOT MissingMaps party hosted by the Red Cross at their headquarters in D.C. I have participated in many Missing Maps mapping parties since then. Along with participating with HOT I began mapping my hometown in Northeastern Pa. For the last year I have also dug deeper into the OpenStreetMap and and companies that use it (i.e mapbox, cartodb) API and tutorials. I have also attended the State of the Map 2015 in New York City and presented at HOT Summit 2015 in Washington D.C. I also learned about OpenStreetMap US, joined a few days ago! I would like to play a greater role in OpenStreetMap by being apart of the OSM US Board.
I can bring many of my professional experiences to the table for the OpenStreetMap community. From 2009-2014 I worked on a project known as Homeland Infrastructure Foundation – Level Data HIFLD. The project mimics OpenStreetMap at a inter-federal governmental level in that it focused on capturing federal, state, and local government geospatial information and then distributing it as base data for the federal, state, and local governments to use. This experience has taught me a lot of about data license agreements and the hassle it is to get agencies to change their policies on sharing.
As a board member I would help however possible including:
1.) Encouraging participation from colleges and universities. Training future professional geographers that there is more than just official data sources. Scholarships to conferences, encouraging professors to incorporate it into his curriculum, more meetups.
2.) Living near D.C. I am very close to many federal agencies and could help facilitate discussions with them about openstreetmap and participating.
So far, the results are promising and work received positive feedback in the scientific community. In addition, we received lots of emails, asking for applying that in other countries and places. However, we still need a continuous support and participation from your sides. Visit Grass&Green and contribute. Fun, Challenges, and Active contribution to OSM (increase your profile).
Here we are, look how many people contribute during the last short period of 24 days,
Look how much percentage is people agree of partial agree on our classifications.
Do anybody has an explanation about what happen on the diaries regarding these names of students class?
Over the last few weeks, the data team at Mapbox have been investigating the unusually large number of unconnected highways in Japan which otherwise looked comprehensively mapped.
Broken highways in Japan. Bigger circles indicate highways of higher classification
Looking into the data threw up quite a few interesting findings:
- Most of the data in Japan is the result of the Yahoo Japan import from 2011 and contains over 5 million road segments.
- The road data has positional errors (5-30m) when compared to GPS data and includes incorrect topology that does not match satellite imagery.
- Roads in metropolitan areas have been realigned to the correct position, but large parts of the country are still untouched since 2011.
- Many motorable roads are tagged as paths, and many paths tagged as roads
- Roads are split into small segments between every junction
- The Bing imagery coverage for Japan is comprehensive but does not match the OSM data or Strava GPS data. There is both an offset and orthorectification errors that varies throughout Japan. New mappers end up realigning the data to incorrect Bing imagery using iD causing more inconsistencies.
- Highly detailed maps from Japan GSI is available for tracing into OSM. On a closer look, the major roads are accurate, but the minor roads are not reliable.
- There is high resolution orthorectified imagery for Japan from GSI which perfectly matches Strava GPS data and is the best imagery source available.
- The coverage of orthorectified imagery from GSI is limited to only the major urban areas.
Fixing the map
- The complexities of the data issues in Japan make fixing the data a challenging task. In the 4 years since the import, large parts of the data remains untouched.
- Members of the osm-ja community have expressed how these large scale data inconsistencies make it hard for grassroots mapping to happen
- Our current OSM tools are not ready for a data cleanup of this scale and it requires evolving smart tools and a data cleanup strategy that can empower the local mapping community to fix the map.
The data team was eager to take up this challenge and got inputs from the Japanese community on how to approach the issue. You can follow the remapping trials and our findings in our /mapping repository. In a later post, I'd like to document the cleanup strategy using existing tools and learnings that could help make this a more comprehensive effort.
exporting to sources
I just wanted to tell everyone what a pleasure it was to fulfill the Activation Curriculum Specialist opportunity for the Humanitarian OpenStreetMap Team (HOT) over roughly the last half-a-year. A bit of cut-paste-paraphrase from project docs: ‘The project was one of three priorities the community selected to fulfill a grant awarded by the Hewlett Foundation in order to improve HOT’s ability to achieve its mission, inspired by the response of the community during the West Africa Ebola Epidemic.’ What is always most special to me is meeting and working with other OSM/HOT enthusiasts – especially in person. One aspect of the Activation Curriculum project that was not certain in the beginning was that it would include leading workshops on three continents; I could not be more honored to have had this experience.
The project launched in late April with the ‘Activation Curriculum Sprint’; a 3 day workshop in Washington D.C. attended by 8 core HOT community members. These were also the 3 days prior to the first HOT Summit; somewhere between then and State of the Map – New York I lost track of exactly how many HOT voting members, board, staff and of course the 100s of other HOT/OSM community members and partners I was able to meet in person. The summer then seemed to just disappear; I had a few fun outings, including OSMCO MapCamp! but it was mostly just sleeves up working on the project. In the end we produced the HOT Activation Protocol and Training Center to organize and most importantly, start providing training to those volunteers who coordinate Disaster Mapping for HOT.
Again, what is more exciting to me, and what was only a potential extension at the beginning of the project was having some in-person workshops to ‘beta test’ the training. I can honestly say that there was just not enough time to have a ‘perfect training workshop' (and simulation added toward the end) ready but I actually think in the long-run it was probably best for the project how the workshops turned out. First we needed to identify two locations where we could fairly easily bring HOT community members together. One was quite obvious, since HOT has an office and staff in Jakarta, Indonesia; and the other location chosen was Dar es Salaam, Tanzania; where HOT currently has a community building project/partnership, Dar Ramani Huria.
Almost as soon as we announced that we were organizing the workshop in Dar, our partners at the World Bank basically gave ‘an offer we could not refuse’ – that being to conduct our workshop as part of, and have our workshop participants attend, the first ever Africa Open Data Conference. This limited the time we had to conduct the training and Activation simulation to roughly ½ day each. However, it gave us 5 days together as a group to discuss all kinds of HOT things and ultimately helped complete and improve some key components of the training and simulation before the workshop in Jakarta. Not to forget being able to attend a great conference and create connections among Open advocates from all around the region.
Side note: In between Tanzania and Jakarta, I took a little vacation to Mongolia with a quick meeting/OSM meet and greet with the HOT interns in Ulaanbaatar then toured through the Gobi desert.
For the second Activation Workshop we had much more time dedicated to the training and simulation over 3 days; plus the improvements made to the training center and simulation. This time I think we were able to get a more realistic/collaborative simulation and further explore what needs to happen in the next iteration of the training center and how we might do more simulations, live and/or virtually, in the future. All good things must come to an end and after being on the road for a few weeks with too many hours on a plane to want to remember, I was ready to get home; but it’s always hard to leave another great time spent with amazing people in the HOT/OSM community.
Thank you everyone involved in the project and part of this incredible journey,
Last week during the geo-spatial week that organized by the International Society for Photogrammetry and Remote Sensing (ISPRS). There exist an International Symposium of Spatial Data Quality (ISSDQ). In that event, a Grass&Green tool is presented during the talk about "TOWARDS RULE-GUIDED CLASSIFICATION FOR VOLUNTEERED GEOGRAPHIC INFORMATION".
The tool enhance the classification of grassy entity in Openstreetmap. It is a pilot study on the data set of Germany. Please, participate in the study to help into developing a consistent data classifications.
Two weeks ago the rendering of landuse=conservation was dropped from the default rendering on openstreetmap.org. While the landuse=conservation has problems, it is used quite a lot in near my home. I was originally worried about what it would mean to how the map would look with this tag missing. However, when the landuse=conservation was dropped, other tags were used such as leisure=nature_reserve, and landuse=forest for rendering. To my surprise, the new rendering exposed tagging problems that were not apparent with the older rendering style. I have been fixing them over the past week.
Everybody knows that the default map is a force on how the data looks, and in theory designed for mappers, perhaps we should mix up the rendering style every once in a while to emphasize different kinds of data. For example, November/December can be addresses, January outdoor sports, February public transportation, March railroads, April hiking, May political boundaries, June land use, July coastline, August rivers and lakes, September highways classifications and routes, etc.
Although the "Monumental Flags" program started in 1999, official data regarding their location and size, when available, is disperse and not easily accessible.
The general goal of this projects is:
- Map the "Monumental Flags" data obtained by request (folio # 0000700156115) and now available at the federal government information portal.
The specific goals of this project are:
- Mark and record the specific location of the monumental flags on OSM.
- Add address information to every mark (including street number, street, neighborhood, city, State, zip).
- Add names (official and/or alternative) in Spanish and a translation into English.
- Review current mappings of monumental flags in OSM, to refine, update, or complete location data.
- Add supplementary information when available (construction date, source of data, etc.)
A partial list of monuments is available via the monumental flags entry in Wikipedia. Available in English and Spanish.
Earlier this week, we released the Missing Roads project. Using its tools, every OSM mapper can now easily find roads that are not yet in OSM, based on our years of collected global GPS data from Scout users.
A lot of you have already had some fun with the JOSM plugin and the web tool. I received interesting reports about important roads you have been able to add. But also some questions about how to optimally make use of the Missing Roads tools. So I thought I might write up a Missing Roads Manual of sorts.
Missing Roads consists of two tools: a web tool and a JOSM plugin.
The Web Tool
The web tool is a convenient way to locate missing roads in an area. You can quickly get a sense of the distribution of the missing roads data.
If you zoom in far enough, you can also see the individual tiles.
Colors of tiles and traces
You will notice that there are different colors for both the traces and the tiles themselves.
The blue tiles haven't been touched yet. These are the 'open' tiles.
The green tiles are the ones that you marked as solved. Yay!
The red tiles are marked as invalid.
Looking at the colors of the traces, you will notice purple, yellow and black trace colors.
The purple color means these are probably actual roads.
The yellow trace color means we think it is people looking for parking.
The black traces are 'mixed': some people were driving faster, some slower, so we are not so sure.
You can filter the results both by tile status and by (probable) type.
The web tool is mainly meant for browsing. You cannot change the status of the tiles from the web tool at this time. This can for now only be done in the JOSM plugin. We do however provide convenient links to edit the current map extent in JOSM and iD.
To quickly check if there are actually roads in the area, you can switch between the default OSM layer and an aerial imagery layer, courtesy of ESRI.
The main interface to the Missing Roads data is our JOSM plugin. It offers a similar browsing functionality as the web tool does, but with a slightly different visualization:
The red dots represent clusters of missing road tiles at lower zooms. When you zoom in you see the actual tiles and the point clouds.
Installation and activation
Install the Missing Roads plugin the familiar way, through the JOSM plugin preference pane. When installed, and after a quick JOSM restart, you should see the MissingRoads layer and panel.
Missing Roads Layer
The layer shows up like any other JOSM layer in the layer panel, and of course on the main map canvas showing you the actual missing road tiles / clusters.
As with any layer in JOSM, it needs to be active if you want to interact with it. So if you want to select tile(s) you will need to activate the MissingRoads layer first.
Missing Roads Panel
In the panel, you can interact with the currently selected tile(s). If you don't see the panel, you should be able to reveal it using ctrl-F3 / cmd-F3.
The panel has three tabs with various bits of information about the selected tile. If you have more than one tile selected, you'll see info about the last tile you selected.
The Tile tab shows basic information about the selected tile.
The History tab shows a history of status changes and comments.
The Have a new idea? tab has a link to the Missing Roads ideas forum. Submit your ideas and bugs there please!
The panel also has a number of action buttons on the bottom. These are for filtering, adding comments, and resolving tiles. I will discuss those features in the next sections!
Similar to the web tool, you can decide which tiles you want to see based on their status and (probable) type.
If you want to clear all filters, you can click Reset.
You can only filter on one status or type at a time.
As a bonus, you can also set a trip count threshold. This allows you to filter out tiles that have a low number of trips passing through them. You can see the number of trips for the selected tile in the Tile tab.
Clicking on the comment button opens the Add Comment dialog allowing you to add a comment to the currently selected tiles for your fellow mappers to see.
If you have multiple tiles selected (using Shift while selecting), the comment will be applied to each tile.
Finally, there are three buttons to resolve the selected tile(s).
The 'lock' button solves a tile and marks it as done.
The 'unlock' button marks the tile(s) as un-done or open again.
The '!' button marks the tile(s) as invalid. Use this if there is not actually a road there.
The tiles and the traces have the same color coding as in the web app. To summarize:
- Blue = Open
- Green = Solved
- Red = Invalid
- Purple = Road
- Yellow = Parking
- Black = Mixed
Obviously you shouldn't add roads solely based on the traces. You need a secondary source of validation. Most of the time, this will be an aerial image. The default aerial layer in JOSM is Bing. Bing imagery can be a few years old. For some regions, more recent imagery may be available. Look for aerial layers in the JOSM imagery menu. Note that most imagery layers are location-aware: they will only appear in the menu if they actually have imagery for the area you are currently mapping. So be sure to check the imagery menu again if you're editing in an unfamiliar area.
Here is an example where Bing shows no sign of a new road, but a local imagery layer does show it:
We have spent a lot of time looking over the results and tweaking the algorithm to get rid of as many irrelevant traces as possible. But we know there are still strange traces out there. I have been getting interesting reports already of traces from trains, airplanes, and even cranes.
Source: Flickr Commons
I know this can be frustrating. If you find strange cases, please take a minute to report them through the feedback page. And mark them as invalid. Thank you!
The code for the plugin can be found on GitHub if you're interested.
There are links in the web tool as well as in the JOSM plugin to give feedback and submit ideas. Both links go to the Missing Roads feedback web site. You can also vote on other mapper's ideas there. I look at all incoming ideas together with my colleagues on our OSM team, so be sure your input is heard and very much appreciated!
Also, don't hesitate to just email me at email@example.com or tweet at me (mvexel). Talk to you soon!
Have fun adding missing roads :)
After reading about Mapbox's Distance API I thought "Hmmm... this could be used to QA highways...".
But when using the 3 most populous cities from each state in Brazil we saw that Parintins was isolated from the world (and it seems that it was isolated since always).
boneco forcibly^W kindly fixed it in #34348258.
We still need to test some ideas (and milky needs to code them), but we think that they should bring improvements in detecting broken routes (as we could see with Parintins) and misclassified highways.
Mapillary announced improved navigation through the photos in their on line viewer.
I can now click and hold the picture in https://www.mapillary.com/map/im/vYGu9Nsz8VcueZ4-nRvNiA/photo and see this side of the building !
Unfortunately, it goes wrong on this sequence: https://www.mapillary.com/map/im/5P7E8NTtYCDJkAoJ8TKk4Q/photo.
*Listed out the all features of the tool and marked out the major ones. Later, I prepared mockups.
*A questionnaire about Tool features was prepared to survey the community members.
*Based on that an interactive mockup of the Export Tool was made and a survey to the community was presented for review.
*Analyzed the survey’s feedback, made changes in the mockup accordingly.
*Features like Visual Tag Chooser, Tree structure of Presets etc. were investigated.
*Added content to the Export Tool pages.
*Created Python Tag Lists of HDM/OSM Presets.
*Wrote installation guide for Export Tool.
*Tested various file formats.
*Transifex setup - Internationalisation
*Final Mockup - https://moqups.com/Arvst/4GrXLm9E
*Export Tool Help Documentation
*Naming each functionality, purpose etc. of the Tool.
*Pop-up Info, Github Issues
*Investigating on Styling Files for Qgis.
*Final wrap-up ;)
*Changes in help documentation - screenshots, video etc.
*Promotion of the Export Tool.
*Survey/reviews from the community.
("building:part"=yes or building=apartments or building=residentail or building=house) - (parent "addr:flats"=*)
Вся хитрость в том, что после того как мы выбрали все "жилые" или интересные нам здания, нам нужно исключить (операция "-") те, у которых есть ребёнок с ключом "addr:flats".
Я не опечатался, запрос нужно читать наоборот, ребёнок: для мультиполигона - линия или точка, для линии - только точка. Ещё раз код ниже значит:
- (parent "addr:flats"=*)
- исключить линии, у которых есть хотя бы один ребёнок (точка) с ключом "addr:flats"=
- в добавок к 1, исключить мультиполигоны, у которых есть хотя бы один ребёнок (точка или линия) с ключом "addr:flats"=
PS. Любителям составления запросов предлагаю продолжить как бы выглядел запрос "выбрать жилые здания с отличным от 1, 2, 3, 4, 8 количеством детей addr:flats" в overpass такое сделать будет проще.
New roads are built and opened for traffic around the world every single day. In many places, these are added to OSM by watchful mappers right away. Not everywhere though. There are still many places where there are few local mappers, and new construction goes unseen for a while. Available aerial imagery can be pretty outdated, so armchair mappers are not always able to help out either.
Lots of people drive on these new roads from day 1. And we're in luck - a bunch of them are usually Scout users :) This means that they contribute GPS traces of the missing roads to us. Lots. Of. Traces. Enough for us to come up with a good guess about where new roads might be that are not on OSM yet.
We have done just that! I am excited to announce the Missing Roads project, opening up the aggregated, processed GPS data pointing at missing roads as a convenient JOSM plugin.
Here's how it works. First you download the Missing Roads plugin from right within JOSM. After a restart, you will notice an extra Missing Roads layer. It looks like small and big dots if you're zoomed out, and a grid with point clouds if you're zoomed in.
You will notice different color grid cells and point clouds once you're zoomed further in. The grid colors indicate whether someone has marked that cell as completed or invalid. You can do that from within the plugin. If you find tiles that are done or not actually missing roads, please mark them and help your fellow mappers out.
One thing we noticed pretty soon once we started digging into the results is that lots of people leave Scout on when they're looking for parking. This means that lots of 'results' are actually people driving around parking lots. Interesting, but not as interesting as real new roads. So you can filter those out. We distinguish between the two types based mostly on average speed, so it's not always spot on. But it helps.
Finally, we also have a web map where you can easily browse and explore the data, and check for unfinished cells in your region. It links back to
This is version 1. Let us know what you think. How we can improve the plugin and the web app. Other ways you would like to see this data exposed. Email me at firstname.lastname@example.org or talk to me directly on OSM IRC channels, skype (mvexel) or twitter. There's also a little feedback box in the web app where you can submit ideas.
(Source of historic photo: Flickr Commons)
When you want to do a import, and you start with a SHP file, there are 3 challenges that i had identified :
How do you convert and split the file, in such a way that a way will not be longer then 2000 points ? How do you remove the line duplicates after you explode the file ( at first all of the municipality is a polygon, that means that at common borders, there will actually be 2 ways.
How do you elevate the properties of the shp file, now the information is on the way, and you want to move this information into the relation.
I think it would make sense to see comments in-line with diary entries. This seems a bit obvious, no?
Right now, one has to go to the diary entry page, which breaks the flow of the document and occasionally messes up navigation in the diary entries, forcing one to start at the top again.
And I seem to be losing the thread of a diary entry. Was something put into a message? Or into a comment? And what is the difference between a reply to an entry and a comment on an entry? Is the difference here important enough that there seems to be separate UI for these?
Why does this seem to be more complicated than it needs to be. The UI for reading a list of threaded discussions, even date-ordered discussions, seems to be something that has been done. So, why are we doing this differently and in an unnecessarily complex way?
If I could get the diary in mbox format, a mail reader would be a much more convenient way to reading this. Is that possible? Or does one have to go through this web UI?