Recent diary entries
As an active bicycler, I use maps on a day to day basis to help me navigate easily and hence my interest in mapping on OSM platforms. I became interested in OSM through connection from ICT4D conference in Hyderabad and have since have been interested in using maps for development.
I have a passion in using Computer Science to support learning and innovation environments and in my work with She Codes for Change (www.shecodesforchange.org), I am interested in seeing how more girls and boys can learn the power of technologies including GIS and map platforms to solve their problems.
Since Pokemon Go changed their maps from Google to OSM, I find myself living in an empty ugly green wasteland. So, here I am, putting buildings and structure back into my nerdy PoGo live, one edit at a time...
Hi, I am Ilya and I have been uploading changesets 15 days in a row. Not because I'm so into it or somebody makes me: I've made a tool that reminds me to do it. In a year I expect my HDYC activity chart to be completely filled. And you can have the same too.
Introducing OSM Streak: a website that gives you points for submitting changesets each day. You get 1 point for the first changeset, and then you get more: for example, I will receive 4 points for my next changeset tomorrow. And that is not all: it gives you a random task each day, so you don't stare at the map trying to come up with an idea. For completing a task, you get an extra point. And when you map many days in a row, you gain levels, which open more tasks.
Forgetting to visit a website is expectable, so OSM Streak is also a Telegram bot (find the link on the "Connect" page). With the bot, you can forget about the website: it accepts changesets and sends you tasks every day. Alternatively, you can subscribe to e-mail notifications, which will be sent on 1:00 UTC.
All the tasks and the website and the bot can (and should!) be translated into your language. We have English and Russian, and I would be very grateful for more translations.
Finally, there are 26 tasks at the moment, and you can add more by making a pull request or an issue on github. You can also use the source code as an example for writing a telegram bot, doing migrations with peewee ORM, sending e-mails with python or adding i18n with transifex.
derrrrp do not respond
It would appear that the map data used on the OSM Cycle Map overlay is well out of date.in North Yorkshire. Although apparently coming from Sustrans, the data is put onto OpenCycle Map by Andy Allan, and this is then incorporated as the Cycle layer on the Open Street Map. Clearly this stage of the data transfer is subject to massive overload of changing problems and priorities.
I'd like to change the rendering of protected areas on osm-carto (the style which is used as a default map layer on the main OSM.org website). That proved to be a complex problem, however thanks to the comments from the community on the issue tracker and Talk list I see the general plan what to do. This entry is just a slightly edited message I sent to the list.
Exhibit A: Adirondack Park disaster...
TL;DR summary: I think that for now we should render all the existing tags, but make some of them appear earlier to encourage smooth migration to a more precise scheme.
As I currently understand it, nature reserve is always a type of protected area, to begin with.
We were talking on osm-carto ticket with some people about private reserves and even when someone told me "it's not about protection!" this term was used immediately in the same sentence (or in the next one). =} I guess they meant "it's voluntary and not formal", but still it's intended as a protection of nature, so it's just a special, weak type of protection.
The problem seems to be for a mapper to be more precise, since a typical survey can reveal a sign with a name "XYZ nature reserve". However this is not about just a name.
Boundaries are not visible on the ground easily, so a mapper who draw them has to use some other sources and I believe there are more informations available. Otherwise the area shape is probably not verifiable, which would be bad anyway. And I think all of them are areas, not the points (node would mean probably "here is the protection area, but exact shape is not shown at the moment"), so boundary is also a sure thing.
The name tag leisure=nature_reserve states that it's about leisure (which of course might be for a given object), but it's always about protection. So even if the value has merits, this key assumption is wrong in general and misses more important property (boundary=nature_reserve has only 35 uses).
Another problem is lack of coherent definition of protection (other than numbers) and lack of high-level classes.
The numbers seem to be derived from IUCN scheme, but wider: only categories 1-6 are IUCN-based and I don't know about the rest.
Especially class 7 is interesting for us: "nature-feature area: similar to 4. but without IUCN-level.", so i guess it's for all the non-IUCN classified nature reserves. Probably most of the time this should be clear from the boundary shape source.
It would be good to have more standardized subtags for common features:
- "nature" - protection_object=* is the same mess as numbers, when talking about hierarchy levels, so maybe some subtag like "nature_reserve=yes" would be useful
- "private" owner type (not the access type) - governance_type=private_landowner would be great (if really used...)
- "voluntary" - but that might be clear from the lack of government or international authorities influence
In summary, we have 3 popular but overlapping types now:
- leisure=nature_reserve (77 264)
- boundary=national_park (16 583)
- boundary=protected_area (62 016)
Their general properties and relations:
- has a wrong key, but nice value name, and is a subtype of 3.
- has a nice value name and a proper key, it's also subtype of 3.
- is very broad with precise, but not so common name, it also has subtypes, which are useful for official classification, but are not clear for all the other types of conservation
Therefore I would advice to:
Discourage leisure=nature_reserve and make it a subtag of boundary=protected_area (if needed, otherwise just use a protect_class=7 or other class if known), like:
- nature_reserve=yes - 2 uses
- protected_area=nature_reserve - 22 uses
- protected_area=nature - 61 uses
Drop boundary=national_park, since it's easy to identify them all and they are equivalent for boundary=protected_area + protect_class=2 anyway.
For rendering I would show all of them as currently, just using different zoom levels, starting from z8 currently (this might change in the future, of course):
- z8+: national parks and wilderness areas (both are big by definition)
- z9+: important natural protected areas (class 1-6, with hatched 1a probably)
- z10+: other natural protected areas (class 7, maybe also 12, 14 and 97-99)
- z11+: protected areas without class (if we know they're nature related) and leisure=nature_reserve
This is just a rough sketch, however it has some nice properties:
- all the existing schemes are visible (boundary=national_park can be dropped later)
- more important objects are rendered first
- less precise tagging is rendered later
Another important factor might be their size (so for example small national parks wouldn't be shown on z8) and a name (when the name is not tagged, push them later), but it needs a lot of worldwide testing.
(class 4 is the most popular)
Yesterday I created a filter in OSMCha to get all edits made by new users in Brazil, as we are having a new wave of Pokemon motivated edits. Today I spent some time reviewing some of those edits. I sorted the changesets by the number of features created and started by the big ones.
I reviewed 11 edits, six of them had between 132 and 400 elements created, and 5 with 400 to 510. It was a surprise to me that only ONE of those edits was bad (the user created a river that doesn't exist). Some edits had some small errors of course, but nothing very dangerous to the map quality.
So, believe in new users, they also can do amazing things and congratulate them by their good edits!
OpenStreetMap is one of the few open source initiatives that operates without a formal Code of Conduct. Many  of the large open source projects have adopted a Code of Conduct for their mailing lists, forums and conferences.
Why would we want to have a formal standard for contact? OpenStreetMap longevity depends on our being able to attract and keep new mappers, developers and third party users. Good behavior means more people feel comfortable engaging in community discussions. Bad conduct not only drives people away but can lead to giving OSM a bad reputation. Our reputation is key to raising funds needed for operation and growth. The OSMF Board has a fiduciary responsibility to protect our project. Adopting and enforcing a Code of Conduct is a step in that direction.
 Some examples of CoC guidelines are:
- Be respectful
- Be friendly and patient
- Be civil and considerate
- Be collaborative
- Assume good intentions.
- Respect time and attention
- Disclose potential conflicts
- Take responsibility for our words and our actions
- Be welcoming
- Be careful in the words that you choose
- Discriminatory remarks based on stereotypes
- Violent threats or language directed against another person.
- Discriminatory jokes and language.
- Posting sexually explicit or violent material.
- Posting (or threatening to post) other people's personally identifying information ("doxing").
- Personal insults, especially those using racist or sexist terms.
- Unwelcome sexual attention.
- Repeated harassment of others. In general, if someone asks you to stop, then stop.
- Deliberately spreading FUD (Fear, Uncertainty, Doubt)
- Advocating for, or encouraging, any of the above behavior.
Adopting a CoC is just one step in the process. If we only post the CoC when members sign up on a mailing list or attend our conferences, nothing will change. Instead the Board should:
- Define the scope of the policy: may include mailing lists, conferences and other in person gatherings, forums, comments on changesets, IRC,
- Decide who is responsible for responding to reports of abuse
- Determine consequences for violating the CoC
- Provide appropriate avenues to report abuse
- Periodically remind members of our CoC
## Example of Codes of Conduct by Open Source organizations:
- Linux Foundation
- Ada Initiative
- Open Source Initiative
- Climate CoLab (crowdsource climate change)
- Defining and Developing an Effective Code of Conduct for Organizations
- Ada Initiative How to design a code of conduct for your community
- The Geek Feminism CoC Evaluations
I want to thank everyone that contributed to this document. Blake Giradot, Martijn van Exel, Andrew Johnson, Kate Chapman, Ian Dees, Dale Kunce, and Joost Schouppe. If I missed anyone, I apologize in advance.
Hi mappers ! I am happy to be one among youth mappers who contribute in mapping different part of Africa. mapping helps a lot, especially when it comes about saving affected people of specific area. In other words I can say that mapping area helps to reach them easily.I started mapping since June of 2017. I have mapped more than 100 buildings and some high ways of course.
Bonjour, Pour pouvoir utiliser efficacement les cartes d'openStreetMap, j'ai besoin d'identifier certain site sur une carte, est-il possible de créer des cartes "personnalisées" en enregistrant les points dont j'ai besoin ? Si c'est possible, pouvez-vous me dire comment je peux m'y prendre.
Merci pour votre aide.
Here is the letter of resignation that I had sent to the HOT US Inc members on May 5, 2016 (more context can be found in my next diary entry):
I hereby resign from as a HOT US Inc member with immediate effects.
Some recent members may not know me, but I have been active in HOT US Inc, as well as other OSM projects for more than 5 years ago now, both in remote activations, training and field work over more than 20 countries.
My main motivation is that HOT US Inc, despite its storytelling, is not a community driven project, it is a just a very classic Corporation run by a board whose aims are far from openness, truthfulness and respect of differences that should lead an OSM project involved in humanitarian and development fields. And as I do think it even represents a real danger for OpenStreetMap, I do not want to endorse and be in collusion with it. Considering how much I worked to make HOT US Inc successful in some ways, I let this organization totally sickened by what it became. I guess I am not the only one: some huge contributors have already silently stepped out for the exact same reasons.
The triumvirate that quickly emerged within the native English speakers from the 2015 board made the meetings a real pain for a non native EN speaker like me. Talking as fast as they can, which does not allow you to catch everything as you would like or quickly enough to everything that is implied by the decision to make. Not agreeing with them and sometimes opposing their views means disrespectful behaviors being frequently cut when you try to express yourself in their native language, your past contribution totally diminished, your ideas sometimes qualified as ridiculous and every time of the reproach the meetings are unpleasant because of you.
Be really aware of this: you simple members are not informed of the most crucial topics, that are decided and managed backstage. Yes working groups have been really launched in 2014 after 15 members or so cosigned a Manifesto to make things change radically. WG were one of the proposed actions items, but not only. They now do act, but on a limited frame, the one of the Corporation. Nothing that could renew it. And when something is considered as being crucial, comes the incredible point where there is a discussion within the board about how to inform the members the most minimalistic possible way to the point they will not understand what is really at stake. And generally the one and only Corporation adviser so far is requested to provide feedback and rewording on this. Easy to do: since 2014, absolutely no board discussion are opened to anyone outside the board, whatever the matter, the notes are very short to the point you cannot understand well what are all the components at stake and of course, anything that could make react the members (I do not talk about confidential personal matters, but crucial community points) is quickly labeled as confidential. It was really surprising and unpleasant for me to discover that when I have been elected in the board in 2014 that secrecy and lies were core within the board toward the membership.
First example : the HOT trademark. It has been a long time HOT US Inc distorts some basic OSM components, eg with the hot mailing, basically an @openstreetmap.org list that became a corporate list where people can be blacklisted just because their mails (whatever their arguments may have sense or not) could un-please partners of the NGO and not a mailing list depending on the OSMF and ruled by classic mailing rules, this being actually decided by one single person. The HOT Trademark is one big step forward. It has never been discussed or even explained to the members. An initiative of Mikel Maron backed by the majority of the board in 2014. This has not even been presented first to the OSMF, that has been informed when the process was still started. The OSMF has been really upset with it and sent a clear cease letter to the HOT Board. Nonetheless the process has been continued (!), and the majority of the 2015 board confirmed the decision of the 2014 board not to inform the HOT US Inc membership, because it could (obviously, and hopefully!) generate strong reactions. This process has been disclosed only by the OSMF itself on its list inside a thread about HOT US Inc. The people mapping with HOT US Inc tools still do not know they help creating an corporate OSM trademark. With the increase of Hotties in the OSMF board, the tactic seems now to make it adopt from the OSMF itself.
Second example: the budget gap.
If you read the report from the last Membership call you can find these words:
“Found a budget gap in 2015 found, but also note funding gaps are very common and normal, just not ideal”:
It reads as if everything was normal, under control and that the situation would be totally safe for the last and the current years. This is totally typical how HOT US Inc has been building storytellings that do not match the facts. This also does not reflect the current state of HOT US Inc.
Yes the Board had voted a negative budget for 2015, assuming expected grants that would have covered the missing money. But does this have been monitored and under control all along the year? Absolutely not.
On September 11, a big financial issue arose, when basically it has been figured out the org had only a bit of money left in its account, but was supposed to run activities for months with this.
This is not something that can be qualified as “normal”. This is basically, by far far far, the biggest issue HOT US Inc has faced from its beginning. It was totally unexpected, and of course the board was totally freak out and had an exceptional meeting during which two main things were decided:
1 Mitigate the situation as best as possible and drastic cuts have been very quickly decided within paid positions when possible and some expenses canceled. Eg no in person board meeting last year.
2 Inform clearly the membership about the situation. From my experience of how the organization has been communicating with the membership for the last two years, I emphasized that the board should not “hide” it. The triumvirate was almost offended by this word. Unfortunately, this is exactly what happened.
Here is the original message that was supposed to be sent:
We are writing to update you on changes and challenges that are facing the community.
We have a significant cash flow problem that the Board and Executive Director are working hard to solve. Unfortunately, this has lead to some very difficult decisions and hard choices. HOT is releasing some of its staff to get on a better financial foundation. We are also investigating other ways to pay for administration needs to continue to support HOT.
No one involved in the process is happy with the situation, we want and expect this to be a temporary situation and look forward to carrying on our important work in 2016 and beyond. Added: we will be asking for your help to build some plans. It is our dream to have a larger HOT Summit in the coming year. While we are focused on the immediate tasks, we are also keep supporting this amazing global community.
But on October 2, the message eventually sent to the membership was the following:
We are writing to update you on changes and challenges that are facing the HOT community and organization.
NGOs often have times when there are funds to raise and plans to change. HOT is no different. We are working to improve our financial oversight and organizational development. And, we are making some changes to our policies and practices to build a more sustainable organization. Over the past 5 years, HOT has been primarily a project funded organization with no very limited unrestricted funds. This pattern and HOT’s operating costs have made it difficult to grow as quickly as we would like. We have drafted some initial plans on this front, which we hope you will help guide.
This makes quite a difference, isn't it? Significant cash flow problem […] HOT is releasing some of its staff to get on a better financial foundation VS improve our financial oversight and organizational development.
Since, the Operations budget gap has been being mitigated by drastic cuts + the fundraising, that has purposely been made to fill the gap, not for future projects and has never been presented as such. Once the Operation budget mitigation improved, figures have been eventually shared with the membership through the 2016 Operations Budget, along the story it was not ideal but normal, and supposedly everything was under control.
Is the situation safe now? Not really.
Apart the Operations budget, everyone should know that there are also grants for each donor funded tech or field project, and actually this is where the financial gap is the largest. End of September 2015, HOT US Inc should still have approximately USD152,000 for activities still to be done or to be returned for one large multiple years project, while the bank account was around only USD10K. As a former Senior Project Manager for 5 funded projects for HOT US Inc (STM020 in Haiti, EUROSHA in Central and Eastern Africa, CAP103 in Haiti, UB_ICT4D in Mongolia and Lower Shire Community Mapping in Malawi), it will remain amazing for me how such a budget swift may have occurred, representing almost 25% of the total grant. A USD33,000 planned payment by the donor on last November allowed to postpone the cash flow issue and temporarily hide the situation, but as the project will come to its end on October 31 this year, this is obviously a huge issue.
The membership has never been informed about this situation and I guessed it would not be even the case for this board elections,
This is totally unfair and harmful to distort the reality and hide such issues to the membership, because:
1 you do not build common knowledge and experience so that this kind of situation is avoided in the future. Over 2 years the people from the board can completely change and an Executive Director can leave in only two months. And the same lack of minimal financial oversight can occur again. As well, some skilled members could have helped to mitigate the situation (as suggested in the initial informing draft) but the organization lost this potential support.
2 you do not inform the future board candidates about a hard situation they will discover only once after being elected and have to deal with and solve.
3 basically the O of HOT comes from OpenStreetMap that includes Open, seems that many forget this, and completely distort the facts are certainly far from this.
Of course, being involved in such lies has been a real pain for me. Of course, I was in strong disagreement with the way these topics were handled, from the moment I figured out that what was not supposed to be hidden would actually be. But the fast speaking majority imposes its views and you are due to shut your mouth. Otherwise you are wrong, and you are basically a bad person, just because it was a majority board decision, whatever it can be harmful for the OSM project from people with little experience or concern about openness or OSM, that does not matter at all. At all.
You can imagine the dilemma for someone who campaigned very clearly about openness transparency to be involved in such practices. Retrospectively, I would like to have reacted differently, to organize immediately special meetings to make this known immediately.
I eventually reacted this way when I disclosed to someone unaware of a complaint made towards him by the Board president because of concerns made about many Hotties running for the OSMF election and having his case being processed without even being informed of this complaint, in the most amateur, Kafka style way I would never have been able to foresee. This was the motive immediately used by the triumvirate to ask for me being put off the board. I do not regret this disclosure at all, on the contrary I am proud of it: on a personal side, at last I acted as I should have done regarding my declaration when candidate, whatever it costs me; on a community side, this could show to some members how this board violently reacts when its bad behaviors are pointed out. This is just the beginning: the reinforcement of the code of conduct will provide easier possibilities to hammer some discording voices and let the “awesome” storytelling and the big business goes on. So, for whoever would like to renew or simply improve it, good luck. Other tried, and did not manage it, like myself. You will figure out a small group of people with loooong agendas actually run this organization. And they bite hard.
But hopefully HOT US Inc is not the only way to trigger OSM in the humanitarian and development fields. It has actually even quite reduced its potential over the three last years. And basically OSM is a sum of small initiatives. It does not need a mogul Corporation to be effective. Fly with your own wings.
OpenStreetMap.org tile rendering operates on edge of its capacity. It's possible to get more from already existing cluster if rendering queue is not continuously dropped, but instead is preserved and processed during low load hours.
Ttile.OpenStreetMap.org uses mod_tile and renderd to manage rendering queue. mod_tile is currently a core ecosystem project lacking an active maintainer for years. There are currently 19 Pull Requests that nobody merges.
I tweaked values in source code to allow for a longer queue. Pull request is available at https://github.com/openstreetmap/mod_tile/pull/152. In comments there was a proposal to make it a configurable parameter.
I offer 50 USD to person who manages to:
create pull request to mod_tile/renderd that makes queue depth a configurable parameter, and set defaults to preserve the queue to shift day's load to night;
get it depolyed to tile.openstreetmap.org adjusted accordingly.
Shift should be visible on https://munin.openstreetmap.org/openstreetmap/render.openstreetmap/renderd_queue.html graphs, most likely by Dirty queue growing beyond 1000 tiles per server, and being non-empty for the whole day, shortening during the nighttime.
This should make the map browsing experience better for everyone.
Example of use at mountain relief modified by mining and agriculture
Lidar (light radar) is a technique providing a very precise surface scanning. Airborne laser scanning generates a dense point cloud (several points per square metre) representing reflections of light ray. It contains reflections as from the vegetation as from the surface under it. Vegetation and building reflections may be filtered to get relief data only and create a digital elevation model (DEM) of relief. It is usually a raster and each pixel value represents the relief elevation. This raster may be further processed for better visualisation of relief shapes:
- Hillshade raster – grayscale 3D visualisation,
- Slope raster – colour represents the rate of change of elevation,
- Aspect raster – colour represents the downslope direction.
Surface irregularities cause by human activities are clearly recognizable in the high-resolution DEM obtained from Lidar.
My hometown was found in the Middle Ages after discovering a rich silver ore. Old mines were reused after second world war to get uranium. The massive mining activities caused significant changes of relief. Some valleys were filled with mining deposits. Agriculture in mountains was also present. Fields at slopes were divided with little retaining walls and embankments.
Mapping these features may be useful for more purposes. Scientists and some tourists going away from tracks want to avoid demanding walking over mining deposits, which usually consist of rock blocks and are often overgrown with trees and shrubs. Geologists and mineral collectors would appreciate the presence of these features in map to locate old mines and spoil heaps. These mines are an important part of local history and the map would tell more about them to visitors and historians. Tourists get better image about the extent of spoil heaps. Some line relief features like embankments are good for orientation. Moreover, map with such features looks much more attractive.
Spoil heaps covered with vegetation are difficultly mappable from aerial images. Mapping with GPS in mountain terrain would be very demanding. GPS signal under steep slopes and vegetation is less accurate. Spoil heaps in mountain relief are characterized by change of the downslope direction and are well recognizable in the slope raster as in the hillshade raster. Spoil heaps are mapped with polygon and tagged as man_made=spoil_heap or landuse=landfill (I'm not sure which one is better).
Embankments, retaining walls, cliffs and edges of spoil heap terraces are characterized by abrupt change of surface inclination and thus they are well recognizable in the slope raster. Sometimes it is not clear from the slope raster, what is the downslope direction and which one is the upper edge of the slope and the mapping may be confused. I recommend checking all created features with the hillshade or aspect raster.
Line representing embankments (man_made=embankment), retaining walls (barrier=retaining _wall) and cliffs (natural=cliff) should be placed to the upper edge of the slope and the right side of the line should always face downslope. When mapping these features from DEM, you should always know which one is present. In case of old agricultural retaining walls in my hometown, most of them are ruined and can be marked as embankments. Edges between spoil heap terraces and downslopes are marked as embankments as well. Roads and tracks at slopes are mostly placed over embankments. Slope raster is very suitable for mapping roads and tracks as well, especially if the track is covered by vegetation, not visible in the aerial map and the GPS signal was not accurate.
I checked my mapped features in field and must say, that this method is very reliable and accurate, because I made no mistakes. However, I know the area very well and was always sure which features I mapped.
I suppose that getting DEMs from Lidar in most countries is not so easy because it is not available for free. Sometimes it's available as WMS and JOSM allows to add a WMS layer. Always make sure that the provider license is compatible with OSM and you have permission to load the derived data to OSM.
The popular game Pokemon Go now (Dec 1) is using OSM for the base map in the game for (all) the world.
Expect to get a massive increase in the users registering and editing OSM in the coming days/weeks.
Things to look out for:
People adding new roads and paths. People editing/deleting existing roads and paths, especially the small driveways, etc as they lump the mall together in their rendering and look ugly and cluttered so I expect people will be changing these to the wrong type or deleting them altogether so they can veiw there map
So roll up and begin casting an eye on the swarm of edits.
I, for one, welcome our new Pokemon editor overlords..
Vila Buarque em São Paulo completada
- This article gives me a vision of a map, dynamical rendered with the details, I need just now.
- That should be possible by vector tiles and client side rendering, using WebAssembly.
- The autor says: This article stems from my work at www.Mapfit.com - a nice tool. I think they use OSM data but don't have any note to OSM :-(
Liberland is an a "country" founded by a czech person. it is betwen Croatia and Serbia (i think), so...
In 2017, despite the current level of influence that the US NGO "Humanitarian OpenStreetMap Team US Inc" (aka HOT US Inc) has over the OpenStreetMap Foundation (OSMF) thanks to Kate Chapman and Mikel Maron (both OSMF Board directors), Heather Lesson, another former HOT US Inc Board Officer and one of its former President is running for the OSMF Board.
Since 2015, HOT US Inc, is the only organization of the OpenStreetMap ecosystem represented at the OSMF Board with two Directors: Kate Chapman (co-founder / former Board member / former Executive Director; elected at the OSMF Board in 2013) and Mikel Maron (co-founder / former President / actual Chairman of the members; elected at the OSMF Board in 2015).
This state of things provides HOT US Inc with more power of influence over the Foundation than any other organizations which is without precedent in the history of this institution. Consequently, this diminishes the representation of the OSM diversity at the Board of the Foundation.
Extending furthermore this HOT US Inc presence and influence at the OSMF Board and shrinking accordingly the room for the diversity of other perspectives around OSM to be represented in this Body of the organization would be a matter of concerns in terms of : - balance of powers between organizations - diversity of visions, thoughts and practices (including internal democracy and conflict of interests) around OSM - board dynamics: a collective of HOT US Inc Boardees would interact with single individuals
With these above risks in minds, given HOT US Inc current influence, its members (aka “hotties”) would be best advised to support the OSM project at the Foundation outside of the Board through its Working Groups to start with allowing “hotties” to get acquainted with another organization. This would mitigate risks of power games, lower tensions and strengthen OSM diversity by saving room for other perspectives and experiences around OSM to be represented at the OSMF Board.
In 2017, like in 2015, OSMF voting members shall pay attention to representing at best OSM diversity as well as check and balances in terms of organizational powers at the Foundation prior casting their ballot this 2-Dec onwards.
PS : I am Nicolas Chavent, co-founder of HOT US Inc in 2010 and as Acting Project Manager in charge of of its Operations until 2013, co-founder of two French associations Projet Espace OpenStreetMap Francophone (Projet EOF) and Les Libres Géographes (LLG).
Quoting OSM wiki about routing...
"Checking your fix. After you have fixed an error on the map you will need to wait until the revised version of the map propagates into the routing engine you are using. This delay will depend for each engine...",
...one of the problems in Qualty Assurance (QA) is the lag between OSM editing and update of routing databases. As far as I know, implementation takes some hours in Grasshopper and 24+ in Mapzen and OSMRM.
Hence, in trying to solve a routing problen (ie: for an interchange) testing can only be done well beyond editing time :-(
Let's see how we can bypass this delay using an homemade router.
Choosing a router
Routino looks simple, functional and flexible. I picked out this SW because it works flawlessly even on a small device like my OrangeePi: as an example, you can route in Friuli Venezia Giulia with this live instance, updated daily. For larger areas we'd soon experience performance problems; so let's leave global routinig up to above mentioned services and focus on a kind of patchwork on-demand...
Automating patch generation
User should be able to choose the area to debug: to achieve this (and due to my zero experience in html/perl scripts) I create a Telegram bot named Routino Patcher and a bash script to manage content.
What happens is:
- bot ask you for "Location" (from mobile device GPS or thru attachment) and triggers script;
- script runs a query [added barriers] around coordinates received which download an .osm containing highway and restrictions only [e barrier]; preset area is square 0.002° [cos(latitude) TBD];
- script performs some cleaning ops (routino "planetsplitter" tool abort if "meta" and "note" tags are found in .osm input) and updates extents of routable database (which grows upon to accomodate each requested location);
- in 30" or so, bot displays a message which comfirms routing database update (details can be found in routino data page) and a link to routino webGUI map, updated with our "patch".
For each location sent, the related .osm is processed together with other areas previously requested [incremental update TBD]. Since this is a service wich aims to test "fresh" OSM edits, locations older than 24h are purged.
I know my low programming skills leaded to this dirty solution, but I needed it, hoping that in the meantime someone will find/build a service like this, already working and using a single interface :-)