Recent diary entries
je suis un jeune ivoirien amoureux des TICs et je m'essaie de cartographier mon Quartier.
je voudrais de l'aide pour être au même niveau que vous, des conseils, des formation en cartographie et aussi des logiciel indispensable a la cartographie
Ieri, con l'ultima escursione di 7 km, ho aggiunto gli ultimi numeri civici che mancavano e alcune attività commerciali nell'area agricola NE di Verderio
Da ora in poi si potranno aggiungere solo i dettagli, cosa che farò fondamentalmente basandomi sulle foto aeree e non più su delle escursioni esplorative, ma la parte utile al routing si può definire completa...OSM adesso ha la mappa più completa ed aggiornata del Comune di Verderio e cercherò di fare in modo che rimanga tale per i prossimi anni.
Da adesso comunque il mio impegno si concentrerà nuovamente sull'altra area da me mappata, è cioè il comune di Gela (CL), dove ancora mancano edifici ed aree agricole...anche lì sarà un lavoro da remoto basato sulle foto aeree...ma temo che per i numeri civici, in questo caso e se perdura la situazione di penuria di mappatori locali, dovremo effettuare un import non appena si renderà disponibile un database sotto un adeguata licenza.
I'm not a golfer. When I grew up, golf was a rich person's game. Average Joes like me couldn't afford to play golf. Things have changed. My boys are golfers. I'm just their geek dad, a Free Software nerd and OpenStreetMap obsessive who takes them places. Golf can still be a rich person's game, but it doesn't have to be. The rich kids just have more equipment.
One such piece of equipment is GPS assistance. A little custom-made gadget that knows about golf courses and the features and layout of each hole and assists with things like choosing your club and your line based on where you are and where you need to get to. This, to someone like me, sounds like a challenge. We have this data (or where we don't, we can create it). So, ahead of the first round of the 2015 Derbyshire Futures Tour, I set about mapping the course.
Actually mapping the course, the holes and their features from the Bing imagery was a breeze. But when I got to thinking about how the software would work, I came up short. My idea was something like this:
- The golf club is represented by an area (
name=Name of Club)
- Each course at a club is represented by a relation (
name=Name of Club, Name of Course).
- The relation groups all the ways tagged
golf=hole, and the
reftag on each way represents the hole number.
- The tee boxes (
golf=tee) and greens (
golf=green) are also tagged using
reffor the hole number.
- Bunkers are tagged (
natural=sand); water hazards (
natural=water); lateral water hazards (
natural=water); fairways (
golf=fairway); and woods (
natural=wood) and individual trees (
- Search for a course. This would search Nominatim or similar for relations of
type=golf_coursethat closely match what the user searched for. This could even be automated as a first step, so the user just has to select the course from a list.
- Download the data for the course, render it, show distance to the hole, recommended club, etc. Record strokes and distances. The sky's the limit here.
But there's a problem: tee boxes, fairways and greens are associated with a hole on a course, which is part of a club - but that's not represented in the data. We only have a link from the course relation to its holes - there's nothing linking a tee box to a hole or a green to a hole, and there's nothing linking bunkers and trees to the course. Now for downloading the data, this is not necessarily a problem, as we can figure out the bounding box. But when it comes to "show me an overview of the first hole" then it becomes:
- Select the first item of
role=holein the relation.
- Look at its
- Select all ways in our bounding box with the same
reftag (and probably
- Figure out the hole's bounding box.
- Select anything else in that bounding box.
If instead we had a hierarchy of relations, we could do:
- Select the first item of
role=holein the relation.
- Select the child relations for
- Figure out the hole's bounding box.
- Select anything else in that bounding box.
It's only one step less, but by iterating over the child relations, all the related ways are selected explicitly, rather than having to iterate over every way we've downloaded and discard most of them. I think this would make for more coherent data and more performant applications.
I'm working on the Moderation Queue project as a part of GSoC'15 along with Serge Wroclawski (emacsen), my mentor.
The official starting date of this project was 25th May, about three and a half weeks back but we have been working on it for almost two months now. You can see all our work on github here.
So, over the last two months, we've made some pretty great progress!
Currently, reporting a problem on osm.org is a cumbersome. One needs to actually email an administrator with the concerned issue ( malicious edit, offensive user profiles, offensive note comments etc). Our project involves simplifying this process and allowing users to seamlessly report such problems without any hassle.
Our solution to this problem is the creation of a simple "Report" button, as can be seen in the pictures.
As we can see, users can now simply click on Report to create a complaint against the instance - in this case a Diary Entry or a Changeset.
This leads to a page where the user provides a little detail about the problem. This here is the page for reporting a Diary Entry:
All one needs to do is fill in the form, and that's it! Considerably less work than the current procedure.
We've also made a dashboard for the administrators and moderators to sort out the incoming reports and deal with them more easily than right now.
So basically, we're trying to reduce the amount of effort at both ends - to allow for faster, more efficient and less cumbersome creation and monitoring of reports against problems. We're hoping it helps everyone out.
That's it for this update!
Um guia que fiz sobre como nomear ruas no OpenStreetMap a partir de mapas do IBGE, vejam:
HOT is still at a pivotal time in its growth. We haven't fully put the events the past few board elections behind us. The old debates of what a 'HOT project' is versus what is HOT, the role and responsibilities of the board, and silly conflicts, still go on. HOT must grow out of this current adolescent phase if it is to become truly successful and sustainable. HOT is and will always be a mapping NGO. However, to get HOT to where it needs to be, it needs to be about more than skilled mappers and dedicated activators. HOT needs to improves its fundraising, administration, and visioning to become an accountable organization. I know that there has been some resistance to HOT growing as an organization and that there are those members that see HOT the NGO as being different from the HOT community. I understand the resistance but disagree, HOT the NGO and HOT the community should be the same thing for a variety of reasons, most importantly fundraising. More partners are counting on our work both during activations and normal times.
In my day-to-day professional life as the GIS lead for the American Red Cross, I work a lot with HOT, local OSM communities, governments, other NGOs, and private corporations to strengthen and build OSM communities. I've lead Red Cross GIS teams during several responses over the last couple of years including, Typhoon Haiyan, West Africa Ebola Outbreak, Malawi Floods, Typhoon Pam, and the recent Nepal Earthquake. When I asked the British Red Cross, HOT, and Medicine Sans Frontiers to come together to create the Missing Maps project, all jumped at the chance because of how much they like and support HOT. Missing Maps is a huge accomplishment for HOT. It allows HOT to engage with new stakeholders, local communities, and donors to accomplish HOT's work. I've worked hard since joining the non-profit sector to lend my hand at strengthening HOT: founding Missing Maps, building technology to enable our work (Tasking Manager v2, OpenMapKit, OSM-Meta-API), fundraising for various projects, helping host and plan the first ever HOT Summit, representing HOT and Missing Maps to the media and at conferences, and working behind the scenes in the humanitarian sector to lead the adoption and use of OSM by humanitarian organizations.
My vision for HOT is a continuation and evolution of its current path. I want HOT to have a solid financial foundation that supports both technology and field projects, HOT helps guide other humanitarian organizations to adopt and use OSM, and the old animosities are replaced with a renewed passion and dedication to help HOT grow.
The key areas that I will focus on if elected to the board include:
- Governance: Build upon the momentum created by existing HOT staff and working groups to manage and maintain the governance structures within HOT. This especially includes strengthening the rules around conflicts of interests and holding members and board members accountable or their actions.
- Overhaul Board Terms of Reference: The existing HOT Board is required to oversee the daily management of HOT and does not have enough time to focus on creating and implementing a longer term vision. I will work to empower HOT staff to take a more active part in the daily decision-making process in line with how other NGOs function.
- Partnerships: It is imperative that HOT build better partnerships before disasters. One of the main reasons the American Red Cross uses OpenStreetMap is due to the relationship built prior to, rather than during, a disaster. Pre-established relationships can strengthen the broader applications of HOT to other actors. I will develop and strengthen partnerships with humanitarian relief organizations so that OSM and HOT are embedded into their business operations.
- Fundraising: HOT needs to secure unrestricted funding to support long term projects, technical infrastructure, and increased staff. Many organizations depend on HOT during times of crisis and even during normal operations.
- OSMF: HOT should work to strengthen OSM Foundation to support the underlying infrastructure that it relies on. This includes helping OSMF establish more OSM chapters around the world.
During the normal election last year it was pointed out that I will have some Conflicts of Interest in my role as the GIS Lead for American Red Cross and as a potential board member. First let me state that I will be the first one to acknowledge those conflicts and excuse myself from those conversations. Yes my work overlaps a lot with HOT's day to day. That is a good thing. It shows that partners such as the Red Cross value and care for the HOT community. While ARC has given HOT money in the past for a few small projects the real value of our contribution to HOT is in staff time. I have given tons of personal and work time to supporting HOT. The folks at ARC are very proud to be HOTties, we enjoy making things possible that would otherwise been very difficult such as the HOT Summit. As I have stated before I will recuse myself from any discussions concerning financial matters with HOT and ARC or Missing Maps. This follows not only good board practices but existing ARC and HOT rules.
I will be available on Mumble Monday (7/22 11am-12pm), Wednesday (7/24 10am-12pm), and Thursday (7/25 10am-12pm) USA Eastern Time Zone if you would like to stop by and ask me any questions. I encourage Pierre to be available during the same time so you can ask us both any questions you might have.
This election asks you to make a difficult choice. HOT could remain a small volunteer organization, run by individuals whose work with donors and international agencies—while well meaning—will be around small projects. It could remain mired in the politics of similar small NGOs, where debates over small issues keep the organization from focusing on growing. Or HOT could blossom into its full potential, with a board composed of professional mappers, humanitarians, fund-raisers, and leaders. HOT could scale to offer far more communities a wider range of services than we can now perform with our small base of trainers. I want to help HOT grow. I have the background, network, and management skills to contribute to that vision. It’s your choice. More debates or more impact.
I've added admin boundaries and titles for eastern suburbs of Bundaberg. That's fairly easy for urban suburbs since they're usually smaller in size. However, country suburbs like Rubyanna and Qunaba require more consideration.
I was wondering if i should tag them as place=suburb or place=village, as they have less than 500 in population.
Информация достоверная, там живет мой друг
Na última semana, venho realizando correções na região de Porto das Caixas, bairro do 2° distrito de Itaboraí/RJ. A localidade estava muito desorganizada, com falta de ruas e ruas sem nome, sendo feitos as seguintes atividades:
- Redefinição de traçados;
- Inserção de nomenclatura nas ruas, sendo o nome oficial e o nome local (mais conhecido) entre parênteses.
Áreas de Interesse
- Praças, Campos, Igrejas e o Cemitério do Bairro;
- Pontos de Ônibus;
- Estabelecimentos Comerciais.
Brevemente seguirei para alterações em Visconde de Itaboraí.
ciągłe szlifowanie witnicy
Результаты недели представлены на диаграмме:
Я каждый день выкачивал тайлы 10-го зума OpenRailwayMap для того, чтобы в конце недели показать изменения в виде анимированной картинки. Но готовые картинки получились с разрешением примерно 13000 * 10000 px и... Я не знаю, что с ними делать. Есть идеи? :)
Вместо этого - небольшой интерактив: на странице http://edward17.github.io/WeekTask_14/ вы можете самостоятельно сравнить состояние железнодорожной сети в определённом месте в разный момент времени.
- Чтобы увидеть слой OpenRailwayMap, нужно включить один из слоёв справа вверху.
- Просматривать можно только 10-й зум, потому что это первый зум, на котором OpenRailwayMap показывает все ж/д пути.
- К сожалению, у меня не получилось нормально скачать тайлы с результатами первого дня. Насколько я понимаю, не все они успели перерендириться, когда я их скачивал. Из-за этого в некоторых местах в первом дне может быть устаревшая информация. С другими днями всё хорошо.
- Из-за глюков в OpenRailwayMap на карте иногда возникают непонятные линии, как, например, на этой картинке: Ничего не могу с этим поделать.
В этот раз 4 участника сделали 25 пакетов правок, в которых было около 3 700 изменений.
На этой неделе: домики в Запорожье.
Somewhere in April, I bought a smartphone and installed OsmAnd on it. During my first ride with it, I discovered that someone tagged a stretch of an highway with maxspeed=50. I noticed it, because OsmAnd suddenly warned my that I was speeding.
The same day I changed it back to the normal 120 and I left a changeset comment. Today I got a reply to that comment (in Dutch):
"Deze werd in OSM geplaatst voor een onderzoek naar de temporele kwaliteit van OpenStreetMap. Alle gemaakte fouten, die nog niet verbeterd werden door de gemeenschap, worden vandaag verbeterd."
The translation is something like
"Those errors were placed into OSM for a research in the temporal quality of OpenStreetMap. All deliberately made mistakes, that are not yet corrected by the community, will be corrected today"
Any thoughts ?
In all the noise about MapBox's Series B offering and their successful bid to replace MapQuest's in house map rendering capability, it seems that our dear trade rags missed something.
Likely the most important medium term aspect of the successful bid is that it removed funding and support for a competing vector tile rendering stack that MQ was developing internally.
Anybody that has been following the developments knows that while open source and in principle freely available, the MapBox vector tile stack doesn't work "out of the box" in any reasonable meaning of the words. It follows the trend of the bits and pieces of MapBox's technology becoming increasingly more difficult to use in practice by the community. The other well known example is MapBox studio, the follow up to the widely independently used TileMill.
A recent article actually points to parts that are closed source, a not completly unexpected change of direction.
Now I think we all realize that it is just a matter of time till the open source community catches up on the vector tile front. This will address some of the issues the OSM community has been having with its map rendering and even the playing field a bit. But MapBox has clearly bought themselves some more breathing space for now.
What an interesting Mapathon. A real brainstorm for policy on how to deal with how Neighbourhoods which cross wards will be mapped. Rob Scott showed us how to share 'ways/relations/boundaries' by using Overpass Turbo to export the admin levels into JOSM. Sarah Wise and Tom Hills took up the batten, which was not easy. Rob insisted that we work out these ways of tagging 'Parcels' of land with shared boundaries, and it was true that although little was inputted, we now have clear strategy. Below is a summary from email correspondence:
Hey Tom and Sarah.
Hope the following fits with what Sarah has down from last night here: https://wiki.openstreetmap.org/wiki/Missing_Maps_Epworth_Zimbabwe_Field_Mapping_2015_live
I will double-check once my emails are answered, but please feed back.
Great that you're getting time to do stuff, Tom. This is indeed the issue that we came up against, and which led to that slightly esoteric venture into Ways, Relations and Boundaries. I am adjusting the levels a bit from yesterday. Also, I think it may be good to let those who want to just tag the houses and leave the boundaries. Better for the newbies like me. I'll ask for feedback on this, tooo, from the community.
Sometimes, the away to find and address consists in upper levels, sometimes in lower.
In these cases, indeed the whole case of Epworth, we need to 'live with' gaps in the Address Chain at certain levels. Sometimes occupied by qualifiers, sometimes blank, because admin levels are not consistent in the addressing system. So let them be pushed and let's create the space. Rule of thumb is to 'shunt' the values up or down to line-up and leave gaps in the value fields which become empty. This would be a true rendering. I think my team-mate Kieran would concur. (I will post and hope for confirmation.) So yes, option 3. Create a new level: 'subdistrict'.
So the address chain is: Ward=2, Neighbourhood=Makomo(to be tagged in 'ways/relations' as 'Metropole' level 0), Area=Makomo Extension (to be tagged at 'Metropole' Level 1), Subdistrict/Cell= for example 'M' - a qualifier for the part of the neighbourhood, which is present on some field papers (to be tagged Met. Level 2) Street/Hamlet (to be tagged at Met.Level 3) - for example '=Chinamo', 'Parcel' or Block which is the Proper Name/Number/Identity of the parcel of land. If there is a name, consent has been sought and given, and this is the equivalent of a 'community head', to be included in the 'name'. I will try to link you up with the trello page. Also I will try to post this on there and the HOT mailing list.
Hope this helps.
On 17/06/2015 12:56, Thomas Hills wrote:
Hi Rupert, I hope you're well. Sorry to pester you so soon after yesterday with questions about Missing Maps! I don't have anyone else's email addresses so if you could pass this around everyone else that would be brilliant. I've had a look at my field papers and there seems to be an overlap between Neighbourhood and Area. Roughly half my papers use Makomo Extension as a neighbourhood (i.e. addr:neighbourhood) and half as an area (i.e. addr:hamlet). This wouldn't be such a problem but it then pushes the other designations out of defined categories. An example: Our categories are area\neighbourhood\name. In some papers, I have Makomo\Makomo Ext\name. (e.g. NW M6) In others, I have Makomo Ext\neighbourhood\name. (e.g. NW M9) So we need to determine how to work this out. I think there are three options: 1) Makomo Ext, etc are neighbourhoods. The extra info can be put in as, e.g. "addr:neighbourhood = Makomo Extension/Chinamano." 2) Makomo Ext etc are areas. The extra info can be put in as, e.g. "addr:hamlet = Makomo/Makomo Ext" 3) We create a new level (addr:subdistrict perhaps). Any 'extensions' go in here, and this way all info has a category. I don't mind which method we use - I don't use the maps and I'm not an experiences OSMmer so I'd be reticent to give an opinion, Cheers, Tom
В данный момент проходит сбор средств на новое железо для нашего проекта. Уже собрано £36,540 из £56,000 запланированных.
В общем, как говорится: "С миру по нитке — голому рубаха".
Hoje pela primeira vez, resolvi editar algumas ruas em meu bairro, sendo que é a primeira vez que faço isso. Acredito que estou contribuindo com as correções dos lugares que conheço com detalhes e que estavam com informações ausentes (sem nome nas ruas) ou erradas (ruas com escadas não informadas e rua com nome errado). Também acrescentei mão correta das vias que não tinham estas informações. Espero que este material não se perca e seja incorporado ao mapa de forma definitiva.
Finalized. Additionally, missing areas finalized around Järvenpääntie down to Hyrylä traffic circle. No obvious missing areas in Rantatie, Kirkonkylä or Hyökkälä any more.