I haven’t had much experience in performing an import and the Orange County, California buildings and addresses is the first (and at this rate only) import I’ve instigated.
I assisted with a building import for Cupertino when I lived in Silicon Valley. And I added a couple of buildings in support of the Los Angeles County import a few of years ago. But in both cases my contributions were very small.
Most of my experience with imports has been in attempting to clean them up.
Anyone who has edited in the United States will have run into “TIGER deserts” and I’ve spent my time in purgatory in those deserts. And if you‘ve edited in the rural areas of California may have run into some imports from the national hydrological dataset (NHD) which doesn‘t seem to be much better for water than the old TIGER was for roads. The two can interact in annoying ways. At least annoying to someone who has a desire to keep the number of suspect issues reported by Osmose down. For example:
When I moved to Southern California several years back I became aware of problems with an address import that had been done for San Diego County. In attempting to make things better I made a conscious effort to touch as few tags as possible. So there were a lot of is_in:*=* tags I left even though they were deprecated at the time. Well the QA tools have gotten more verbose over time and Osmose started nagging me about those. In addition to a bunch of duplicate addresses and/or address streets not matching street names that I can‘t remotely resolve. My biggest regret on my attempt to clean up the San Diego addresses is that I used my normal OSM ID rather than creating a new “fix it” ID.
When I moved to San Clemente I spent quite a few days walking the streets to collect address data. It gave me a pretty good overview of my new home town, gave me exercise, and allowed me to add what I surveyed to OpenStreetMap. I was able to map the addresses and buildings for nearly everything within a couple of miles of my house.
But there are some gated neighborhoods that I could not access. And there were many more neighborhoods that were too far from my home for easy mapping. So there have been annoying blank spots on the map of my city.
I recently became aware that there is a “Map With AI” layer that contains building outlines that could be imported. I took a look at it and found that the outlines are the ones provided by Microsoft/Bing and are, in my opinion, far too low a quality for OSM.
But that got me to looking around for a dataset that could be imported that was better. It turns out that Orange County has published a dataset with a Public Domain license containing building outlines, addresses and, on some buildings, elevation and height information.
So I decided to set up an import.
I‘ve imported a tiny fraction of the data and it is not easy going.
I don‘t want to have any changeset from this import to be thought of as yet another reason why imports should be discouraged, so it is taking me hours for each little area.
For example, yesterday I noticed an obvious address error. The fact it was an error was obvious but unfortunately the correction was not obvious. So this morning I drove to the area in question to do a survey.
If I actually have to survey each area, then what good is an doing this as an import? And I am not up to walking every street in the county, I‘d never get done.
For San Clemente I will continue to slog though this data and curate and edit it enough that I feel it is adequate for OpenStreetMap. But scaling the building by building corrections up for all of Orange County is way to big a job for me.
I am thinking about centroiding the building outlines into single points and then only importing the addresses for the rest of the county. That would probably be much faster and would provide some benefit to OpenStreetMap.
제가 오픈스트리트맵을 편집하면서 세운 편집기준입니다 최대한 한국기준으로 맟추었습니다 기본적인 기준은
https://wiki.openstreetmap.org/wiki/Ko:Map_Features 를 참고하였지만 오래된 부분이 많았습니다. 편집할때 검색하면 다양한 태그가 나옵니다.
주거도로: 보통 주거용으로 사용되는 도로로 주거용 도로중 차선이 많은 곳이나 주거지로 가는 차량 통행이 많을 경우, 주거용으로 사용되는 경우가 많은경우 사용 (주거도로 태그가 지도에 남발하고 있습니다 모든 도로에 적용되는것은 아닙니다)
접근도로:말그대로 접근하는 용도로 쓰이는 도로. 주로 쓰이는 곳은 아파트 내 도로(주차장이 있는경우 사용하지 말것 아래 주차장 통로 이용),산업 단지(흔히 공단이라 부름),빌딩,시청,군청 내 도로등 건물이나 시설에 접근할수 있는도로에 사용함 논밭에 있는 도로에 사용하라고 나와있지만 접근도로로 쓰이기에는 애매함
주택가 거리:주거 도로 보단 통행량이 적고 주택이 있는곳에 있는도로. 골목길이라고 볼수 있지만 골목길 태그가 따로 있음.
비주요/미분류 도로:이도로는 통행이 무척 적은곳이나 주요한 도로(1차도로,주거도로)가 아닌 도로 저는 보통 논,밭 에 있는 도로와 강,하천,개천 주변 차량이 다닐수 있을만한 곳에 씁니다.
주차장 통로: 주차장에 있는 도로이며 맥락은 접근도로와 비슷하다. 보통 주차장내 도로에 쓰인다.
차도: 역시 접근도로와 맥락이 같다. 그렇지만 다르다. 보통은 주유소 내 도로에 쓰인다.(이태그는 잘모르겠다)
고속화도로:고속도로와 비슷하지만 다르다. 자동차가 고속으로 달릴수 있고 신호등이 없다. 또한 고속도로의 인터체인지(IC,나들목)처럼 입출구가 분리되어 있다. 제한속도는 천차만별이지만 보통 80km 이다. 중앙분리대 로 분리되어 있다. 보통 일방통행이다. 국도에도 이런 구간이 많다.
중앙분리대로 분리가 되있으면 2개로 만든다. 그외는 1개로 해야한다.
주거지역:보통 빌라가 해당된다. 아파트는 따로 있다.
아파트 단지:아파트에 해당한다.
주거건물:보통 빌라 건물에 해당함
주택:보통은 단독주택을 말함
관리사무소 태그가 없어 저는 건물로 지정합니다.
소매 건물:상업 건물이랑 다르다. 보통 상가건물에 해당한다.
상업 건물:업무를 보는 건물.
슈퍼마켓:흔히 말하는 마트를 말한다.
시장:우리나라에선 재래시장을 뜻한다.
서대전역,인천역,종로3가역 같이 이름에 ~~”역” 을 쓰면 안된다.
철도역 건물에 이름을 쓰면 안된다. 정보는 점에다가 쓴다.
I need to collect and fix the memories
Trying to be more positive
“The last remnants of the Amazon rainforest in Mato Grosso”
Amazon, the world’s largest forest, is spread over Brazil, Peru, Venezuela and Ecuador, among other countrie.
The northern part of the state of Mato Grosso has been under more intense pressure in recent years from cattle ranches, soy plantations and gold mining on indigeneous lands.
Indigenous reserves are the fragments of forest that can be observed by aerial imaging.
The state of Mato Grosso is one of the largest in Brazil, and has much to be mapped yet, not only of the Amazon rainforest but also of the Cerrado and the Pantanal.
“Os ultimos remanescentes da floresta Amazonica no Mato Grosso”
A Amazonia é a maior floresta do mundo, espalhando-se pelo Brasil, Peru, Venezuela e Equador entre outros países.
A parte norte do estado do Mato Grosso vem sofrendo nos ultimos anos uma pressão mais intensa por parte das fazendas de criação de gado de corte, soja e o garimpo nas terras indigenas
As reservas indigenas são os fragmentos de floresta que se pode observar pela imagem aérea.
O estado do Mato Grosso é um dos maiores do Brasil, e tem muito a ser mapeado ainda, não só da Floresta Amazonica mas também do Cerrado e o Pantanal.
I have been working recently in the mapping of the following sites:
При спробі знайти на просторах інтернету мапу, на якій би була актуальна інформація по моїй громаді (наявність будівель та їх вірна нумерація, декомунізовані назви вулиць, інфраструктура, бізнес тощо), я так і не знайшов таку, яка б повністю задовільняла мої потреби. Також хотілося б мати можливість вносити певні зміни на мапу. На цьому етапі були відкинуті всі пропрієтарні мапи, і саме так я познайомився з OpenStreetMap.
На той момент я вже певний час працював в програмі QGIS і мав велику ідею створення такої мапи, на якій будуть відображені всі заклади інфраструктури (освіта, культура, медицина і т.д.), класифікація та покриття доріг, банки та банкомати, магазини та кав’ярні, визначні та просто цікаві місця тощо. І щоб на тій мапі можна було побачити всю необхідну інформацію: час відкриття та обідньої перерви, режим роботи в період карантину, наявність Wi-Fi тощо. І найголовніше, щоб це було у відкритому доступі - для всіх і кожного!
Власноруч створені шари:
На жаль ДержГеоКадастр не надає подібні шари векторного формату у відкритому доступі, тож отримані вони були внаслідок кропіткої роботи та дуже великої кількості недоспаних ночей.
На жаль ДержГеоКадастр не надає подібні шари векторного формату у відкритому доступі, тож отримані вони були внаслідок кропіткої роботи та дуже великої кількості недоспаних ночей.
Також на руках були Технічні звіти “Виконання комплексу інженерно-вишукувальних та знімальних робіт для виготовлення генеральних планів” чотирьох населених пунктів громади, які містили дані в векторному форматі shp.
Якщо власноруч створену інформацію можна використовувати як завгодно, то дані отримані в наслідок подібних робіт треба, задля подального використання, оприлюднити.
Зробити це можна на офіційному сайті громади, або ж на спеціальному порталі.
За всі нижченаведені посилання, підказки, консультації, знання та постійну підтримку особлива повага та подяка Ігореві VARVAR master!
За всі нижченаведені посилання, підказки, консультації, знання та постійну підтримку особлива повага та подяка Ігореві VARVAR master!
Модулі: QuickOSM, QuickMapServices, qgis2web.
Підключення кадастрової карти України: http://wikimap.dzk.gov.ua/wiki/Додати_WMS_шар_з_ПКК_до_проекту_QGIS
Модулі: auto_tools, SimplifyArea, terracer, todo, utilsplugin2
Дуже корисні посилання:
Гарячі клавіші: https://josm.openstreetmap.de/wiki/Uk:Shortcuts
Ті гарячі клавіші, які використовував я:
Q - вирівнювання кутів полігону
M - з’єднати точки
C - з’єднати лінії
P - розрізати лінію в точці (-ах)
Shift+I - спільна точка на перетині двох ліній
Ctrl+Shift+G - заміна геометрії (“об’єднання” старих контурів полігонів/ліній з новими та їх тегів)
Shift+B - центрування точки між двома іншими (можна також на лінії)
Ctrl+Shift+Y - вирівнювання ДУЖЕ тупих кутів (видалення зайвих точок)
Shift+T - розрізання полігону на два і більше (автоматично ріже перпендикулярно, при наявності точок - по них)
Моя черговість наповнення населеного пункту:
Дороги + вулиці
Shift+P - створення паралельної копії лінії
Затиснутий Alt + ЛКМ - лінія без тегів
Я робив так: https://josm.openstreetmap.de/wiki/Uk:Help/Action/Parallel
Alt + ЛКМ
this isn’t really about OSM, it’s about how to protect our privacy while on a OSM-centered Telegram group. I manage the Comunidad OSM Panamá Telegram group, and since the Covid-19 struck worldwide, also our group started to be targeted by several types of scammers and spammers, so I looked for options to contrast the events and shield the users of the group from the nuisance.
Initially, I participated in the osmallgroups Rose federation, but I came in disagreement with the most active admins in the federation, as to how aggressively ban potential scammers. My point of view was that, at the first hint of suspicion the person has nothing to do with OSM, with the area, with geography, and is only looking for sources of Telegram user contact details, the correct action is to ban immediately, possibly contacting them with the invitation to tell me that they are legitimate OSM mappers. This was not the shared opinion in that Rose federation, so I left and developed the following protocol.
Each new member gets a message inviting them to mention their OSM user name, and are warned this is an anti-spam measure. Failure to comply results in ban within the first few hours. I then privately write to check the intentions of the user. Up to now I have not had a single false positive. In at least two occasions I saw the person joining and immediately leaving the group.
To reduce the impact of my instructions to Rose in the group, I use a “federation” and a parallel group, where I issue the /fban command to Rose. Rose reacts to that and removes the user from all other federated groups, that includes the Comunidad OSM Panamá. All that people in the real group will see is “Rose removed user Xxx”, something that happens without the Rose avatar. Soon after, this becomes “Rose removed DELETED”.
The other detail that needs to be mentioned, that’s Rose’s ability to log events to a channel. I need that in order to have the necessary user details to invoke the /fban command.
the only remaining problem with Rose is its avatar, which was initially very sexist, has been polished down, but is allegedly still offensive to some members of the OSM communities. Personally, I have no problem with it, and I have not heard direct complains for its presence in the Panama Group.
Cycling highways are a ‘thing’ in Belgium and The Netherlands, or rather, they will be.
Some stretches already exist, others are still in the planning phase.
The intent is to have them as bidirectional ways for cyclists, ideally 4m wide, without car traffic. Often alongside railroads or canals, sometimes instead of disused railways. Where they cross motorways bridges are planned.
Usually they are also open to pedestrians, horseback riders, skeelers, etc. Some were not open to speed_pedelecs, but that is getting resolved.
In practice there will be certain parts that will always be ‘shared’ with car traffic though and where they cross busy national roads the cyclists won’t have priority for obvious reasons. Building bridges and tunnels everywhere is not possible either.
So more than half of them are still in the planning stage. On OpenStreetMap I like the ability to show where they are planned.
I also like to show what the alternative is that can be used today. Obviously we want to avoid unpaved, cobble_stone/sett and even cycle ways along busy car highways. But often that is simply not possible. Things will improve, but it’s going to take time.
I made the mistake of trying to map each cycle highway from beginning to end with a single route relation. It became apparent that that simply does not work.
I also like the route relations to be a continues stream of ways.
So, I came up with the idea of using superroute relations, after asking the JOSM developers to enable showing continuity across ‘sub-routerelations’. They implemented it for superroute relations. (Big thank you!)
It’s a lot of work, but now we are able to show which parts are already usable, which parts are proposed and how to ride today to bypass the stretches that aren’t realised yet.
I will use F78 as an example. It follows Zuid-Willemsvaart for 55 km from somewhere north of Maastricht to Pelt (formerly Neerpelt/Overpelt). For 32 km it’s a rather dull ride along the canal.
Near Tongerlo/Bree things get more complex. Currenty there is a steep staircase of 15m after riders pass a smelly water treatment facility.
(The whole ride is on Mapillary. My task was to follow the planned trajectory as closely as possible, so what I propose through Tongerlo is currently missing on Mapillary. It’s not easy to get there - no train stations in that heck of the woods - so it might take a while before I get a chance to go back)
The plan is to create a more bicycle friendly connection at that point, but it’s simply not there yet. So I propose to ride through the center of Tongerlo as an alternative that can be used today. (It might even be a better alternative long term, but that’s another discussion)
Tagged with state=proposed on the route relation, which makes it display dashed on the cycle map and route planners won’t use it.
The last stretch:
Most cycling highways are not as monotonous as this one. Often it’s a combination of dedicated infrastructure combined with mixed traffic. The plan is for those to become cycle_streets, where cars are not allowed to bypass cyclists and where the maximum speed is 30km/h. Of course speed pedelecs can’t ride 45km/h there either.
So I’m using 2 superroute relations and 4 route relations to describe what is already realised, what is planned and what is the alternative. For most other cycling highways it means a lot more route relations. Flexibility comes at a price.
One could argue that the unrealised stretches shouldn’t be on OpenStreetMap yet. I beg to differ. I think they are interesting enough to map. They will be realised, either soon, or no so soon. Work in progress.
If anyone is interested in how I’m converting the single route relations to 2 superroute relations and many a route relation, I’m always willing to do a Google Hangout or Skype conversation about it.
Ruta para llegar a la estación del ferrocarril desde la plazuela del cristo
Ahead of the State of the Map 2020 conference, which was supposed to take in place in Africa for the first time, but was held online due to COVID-19, OSM Africa surveyed OpenStreetMap community leaders in different countries in Africa, to assess the state of OpenStreetMap in their countries. We heard back from 52 out of the 55 countries in Africa and the results were presented at the conference.
OSM Africa is a network of OpenStreetMap communities from all over Africa working together to grow OpenStreetMap on the continent.
The brightest spots on the map below illustrate substantial amounts of OpenStreetMap node density in different places in Africa.
This visualization shows the total number of mapped buildings per year in each country from 2007 to 2020. Which also shows the history and journey of OpenStreetMap editing in Africa.
By June 2020, there was a total of 57,766,001 mapped buildings in Africa, with Tanzania leading at 11 million, thanks to the work done there by the Humanitarian OpenStreetMap Team (HOT), the World Bank through Ramani Huria and Crowd2Map Tanzania.
We also looked at the population in comparison to the number of mapped objects, to measure map completeness in each country, which shows Eswatini, Lesotho, Seychelles, Botswana and Zimbabwe as the most mapped countries. Map Lesotho is an interesting case where the Government is leading in the use of OpenStreetMap for rural and urban planning.
Sixty-five percent of the countries that participated in the survey indicated there is an OpenStreetMap community in their country, although the levels of activity differ from country to country, from very active to inactive. It is also interesting to note some countries like Egypt and Morocco where there is active mapping but no single community.
For the countries where there are existing OSM communities, we look at some of the factors behind their existence that were pointed out in the survey.
One of the reasons for the growth of OSM communities in Africa is the rise of YouthMappers. Although it only started in 2018, there are now 105 YouthMappers chapters in universities across Africa, which is 50% of the total number globally. Nigeria and Tanzania have the most chapters with 17 and 15 respectively.
YouthMappers is an international network of university student-led chapters who organize, collaborate, and implement mapping activities that respond to development needs around the globe, creating and using geospatial data and information that is made publicly available through OpenStreetMap.
Growing OpenStreetMap through universities is a good model, as the students have a direct incentive to volunteer through mapping and are gaining geospatial skills while at the same time contributing to open data. YouthMappers provide Leadership and Research Fellowships to a number of students per year, who go on to become leaders of OSM communities in their countries.
Since 2015, HOT has run country programs in eight countries in Africa and also supported OSM communities with devices and Microgrants in 19 countries in Africa. In most of the countries where HOT has worked, they have engaged the local communities in different projects, and have helped start up communities.
Open Cities Africa is a World Bank project that promotes collaborative mapping to build resilient societies in 16 cities in 13 countries in Africa. This project collects data, and builds skills and networks to support disaster risk management in Africa and makes the much needed connection for OSM communities and governments to collaborate on projects.
Over the years, the different OSM communities have been growing their membership and it is interesting to see how they define their membership, which is different from country to country.
OpenStreetMap communities in Africa do meetups for mapathons, mapping parties, and planning. Meetups are a good way to keep the community engaged and active. It requires space, an internet connection, a team to organize, and in most cases funds to pay for these resources including snacks and refreshments.
From the survey we found out that 46% of the communities have not met in a long time, meaning that the community is in place but not particularly active. Out of all of the communities, 24% have never had any meetup, which suggests there is not an active network in place. The remaining 30% meet regularly, either weekly, biweekly, or monthly.
The regular Meetups indicate the existence of leadership and the capacity to raise funds or resources through membership fees, through funded projects or through partnerships with a university, NGO, or company that can provide space and internet.
When it comes to communication, most OSM communities in Africa communicate through Facebook and WhatsApp. The other communication channels used are Telegram and the Talk Mailing Lists. Only 34% of the communities have a website.
When reaching out to these communities, it is important to use their preferred channels. Otherwise they may miss out on the information.
Having a leadership and organizational structure for an OSM community is an asset for community growth as it makes it easier to partner with other organizations and even take on a wider scale of projects. Of the 52 countries that responded to the survey, 45% have some kind of leadership structure for the community.
It is also interesting to note that there is no uniform leadership structure. One of the challenges that new communities face is deciding on what kind of leadership or organizational structure to put in place.
In particular, the structure they choose should be able to accommodate different groups promoting OSM in a single country. If not done properly, this choice can lead to divisions within the local OSM community as some groups may feel left out.
For countries that have a leadership structure in place, the following are the examples of structures they have in place.
Depending on how long the community has been in place, each community defined success in a different way.
Growing an OSM community in Africa comes with challenges. The countries which have active communities are the ones who have managed to find solutions to these challenges.
For all the challenges faced, there are solutions which have worked in some countries that can also be applied in the other countries facing the same challenges.
One of the major challenges pointed out in the survey was lack of access to funds for internet access and other things. Yet communities in only 11 countries from Africa applied for the OSMF Microgrants this year.
For the countries with no applications, some had communities that were not aware of the call for applications or no active community to begin with. For others there was just a lack of capacity, with no team to work on a proposal, and a few felt they had no need for a microgrant.
The OSM Foundation has a membership scheme which costs £15 per year. It also has the option of a fee waiver for people who don’t have access to suitable money transfer options or can’t afford the fee because of financial hardship.
Members of the OSM communities in Africa need to become members of the Foundation so they can participate in the decision making process about the future of OpenStreetMap and so they can propose things that work for them within OpenStreetMap.
However, only 32% of the people who responded to the survey are members of the OSMF Foundation.
The following were given as some of the limitations for becoming members.
The lack of awareness shows the need for the foundation to consider using different communication channels when reaching out to the communities in Africa, including Facebook and Whatsapp. Otherwise many will be left out.
The OSM Foundation has different Working Groups through which the Foundation supports OpenStreetMap in specific areas.
It is important for OSM Africa members to also participate in these working groups, not only to support the foundation, but also to be part of the process of shaping OpenStreetMap in a way that works for us.
When asked about participation in the OSMF Working Groups, 36% didn’t know about the existence of Working Groups at all, 41% participate in some way, and 23% were aware but unable to participate.
Reasons for lack of participation in the OSMF Working Groups
Local Chapters are country level or region level organizations affiliated with the OSM Foundation. There are several benefits in becoming a local chapter, among which is being a legal entity representing OpenStreetMap and mappers when dealing with the local government, business, and media.
At the moment there are only 9 official Local Chapters recognized by the OSM Foundation globally and none of those are in Africa. Why are there 33 OSM communities in Africa, yet no local chapters affiliated with the OSM Foundation? We asked the members what steps should be taken to change this.
Lastly, we asked the OSM Africa community leaders about their vision for OpenStreetMap in 10 years time, and this is what they had to say:
The purpose of the survey was to see where we are as OSM Africa, where we need to be, and now we can focus on achieving our goal to map each and every corner of Africa.
looking at making this do my bidding and give me the nautical chart info. not sure if it will work but worth a try.
А вот это просто пародия на наши архитектурные шедевры. Такое надо просто сносить (и делать заново).
hoje cheguei a marca de mil edições no OpenStretMap foram quase 62.913 pontos editados, hoje resolvi não somente escrever sobre como cheguei aqui mas também como vim conhecer o projeto.
Comecei a editar no OSM através de buscas de alternativas ao monopólio da big G e acabei compreendendo a importância dos dados abertos principalmente geográficos, minhas primeiras edições foram pelo meu bairro as vezes em Teresina, como não havia nenhuma informação sobre pontos de interesse aqui, comecei a pegar jeito, já tinha sido mapeador para BigG, então comecei a pensar em projetos para conseguir mais dados e com mais qualidade para inserir e um dos primeiros que consegui realizar foi com a ajuda do Fieldpapers e uma pracheta então fui anotando casa por casa os endereços e depois adicionando ao OSM nisso foram quase 3.862 endereços, outros projetos como a criação de ortofotos ou o campus 3D da UFPI estão parados por conta do Malware Humano, ainda sairão muitas ideais, atualmente estou mapeando a zona rural de minha cidade aqui eu tenho que fazer um pequeno agradecimento ao RapID por ajudar criando a estradas.
Um das grandes motivos para se fazer um governo utilizar o OSM é a de soberania nacional, o que no atual momento geopolítico é realmente preocupante que uma nação tenha sua autonomia sobre o que produz e sobre a tecnologia para produzir.
Agora imaginamos uma pequena cidade no interior que não tenha acesso ou verba para fazer o levantamento geográfico da área, que ainda usa mapas de papel amarelados pelo tempo, como o caso de Timon que não há um arquivo digital, ou no caso de Teresina que disponibiliza seus dados como camadas no GMpas o que eles fazem é usar uma licença para nos tornar dependente e escravos de um serviço em que não tem acesso aos dados, não podem ajustar ou extrair nada
Agora passamos para um cenário hipotético em que esse monopólio de informações tem o acesso proibido a essas prefeituras, ou que seja proibido o uso em território nacional, como ficarmo? e por isso a importância de se usar o OSM não somente pela liberdade com os dados mas sua autonomia de não depender de governos ou empresas para continuar funcionando.
hoje em dia ao usar um aplicativo de GPS saiba que não é o único a saber sua localização a empresa também sabe, e assim aprendendo seus hábitos de consumo e onde frequentas tudo isso em nome do lucro além deles governos também tem acessos.
então se sua cidade falta dados para você navegar considere virar um mapeador, adicionando aquele barzinho de esquina ou aquela igreja que você frequenta, precisamos de você, so assim teremos autonomia de nossos dados e inovação pode ocorrer
se você participa de alguma ONG ou prefeitura o OSM tem varias ferramentas que podem ser utilizadas, também temos vários casos de prefeituras que utilizam.
lembre-se dinheiro publico, software publico!!
I believe I cleared most of east coasts’ osmose warnings a while ago. However, new warnings/errors keep popping up. Either osmose revised their rules, or new (non-local) mappers keep adding stuff that trigger osmose’s detection algorithm.
Also these mappers keep re-aligning existing ways to Maxar, despite there’s no indication that the new imagery is any more accurate than Bing. When 90% of the area was traced to Bing, why shift a portion to Maxar? If that’s the intention, why not shift everything to Maxar while you are at it and make them standardized. It’ll surely do wonders to your KPI, in addition to your ‘smoothing’ of highways.
That and reclassifying highways in a country you never step foot on.
Kratom mixed with Coke sounds good now…
We’ve been keeping busy this summer! Here are the highlights for the July releases.
We completely redesigned the Challenge Creation Wizard, with a focus on gathering the essentials first, and de-emphasizing less-used settings and options. If you have used the Challenge Creation wizard before, we hope you will appreciate the improvements! And if you have never tried to create a MapRoulette Challenge before, give it a try and see how easy it is to create Tasks for fellow mappers to solve!
You can now select a custom date range for the Leaderboard. Existing options like ‘Past Year’, ‘Past 3 Months’, etcetera, will still be available. We also show some more detail about the Challenges most worked on by the top MapRoulette mappers.
Have you ever wanted to see where mappers are solving Tasks in MapRoulette right now? You can now, with the new Global Activity view! You can see new Tasks being solved on a world Map, and a live stream of the activity as well. It’s still experimental and we would love to hear what you think about it!
The MapRoulette community has been hard at work translating the MapRoulette UI into more languages. It is great to see MapRoulette become available in more mappers’ native languages! It’s easy to participate in the localization effort at Transifex.
When you confirm and finish a MapRoulette Task, you will now see a map showing more nearby Tasks to solve. You can select whether you would like to work on a Nearby Task next, or a Random Task. This new interactive map view can help you choose!
To capture additional information from mappers, we introduced MR Tags a while ago. As a Challenge Owner, you can ask mappers to use these tags to, for example, indicate blurry or cloudy imagery. We improved on this system by letting you set Preferred MR Tags, that will show up as pre-filled options when a Mapper completes a Task.
When you set a custom map base layer in your Challenge, mappers will now see this same layer when they’re editing.
En el grupo LatAm estaban hablando de varias amenazas al proyecto, y por mi parte lo que me parece un riesgo real, es la falta de sentido de comunidad, y las contribuciones por maperos que no respetan la propiedad intelectual ajena. A mi manera de ver, son dos aspectos distintos que cuando se junten en la misma persona, pueden causar un daño real a la comunidad OSM.
Me pregunto, sin tener respuesta, cómo prevenir el mapeo de fuente con licencia no compatible con OSM? Digo y subrayo, prevenir en el sentido de evitar que el hecho se concretice.
No tengo respuesta pues si es cierto que he desarrollado una práctica, finalizada a la formación de comunidad y al monitoreo de mapeo “copia ilegal”, igual no creo que mi práctica sea suficiente ni para la primera ni para la segunda cosa.
Lo que por mi parte tengo, es un pequeño script que corre cada lunes y que me envía una alerta si hay actividad en Panamá por maperos con menos de 7 días de experiencia. Reviso sus ediciones, entro en el sistema openstreetmap.org y envío un correo interno a los nuevos maperos, en forma de saludo e invito a unirse al grupo Telegram Panamá.
Esto, por supuesto, con el objetivo “formación de comunidad”, y claro, de las 10 invitaciones quizás 2 sean aceptadas, si es mucho. Pero es que muchos de los nuevos maperos no vuelven a mapear, así que este 20% quizás sea un porcentaje muy alto.
Otro monitoreo lo hago sin ninguna garantía de regularidad, o sea, de vez en cuando si tengo tiempo y ganas, miro en el historial osm buscando cambios por agradecer o por comentar. Pero ya estamos entrando en la sección “corrección”, dejando la sección “prevención”.
Y qué más puedo hacer, no sé. A veces se llega a deber activar el DWG, pero antes que nada, si no entiendo cuál es la fuente de información para un cambio, pregunto, preferiblemente en el grupo, si el autor se asomó, y de todas maneras en forma de comentario al conjunto de cambios, pues es la manera pública aceptada para proporcionar retroalimentación.
A veces uno se queda con la duda, pues de dónde xxxx sacó esta información … y porqué no contesta el autor … y qué hago con un pico o una quebrada, que yo no veo en Bing, que tiene nombre y otros datos, y por ejemplo que es utilizado en una frontera administrativa … de alguna parte debe salir esta información, a no ser que uno invente, pero sí puede ser que el autor supo ver lo que yo no veo en las fotos aéreas, o que estuvo en el lugar … y bueno considerando que cada uno mapea en buena fe, no borro nada, hasta tener la seguridad que el dato es de fuente no admisible.
O si comí y dormí mal, no me aguanto la tercera inconformidad, y activo el DWG. ;-)
Mi punto de vista es: estamos en un proyecto comunitario … no debería ser obvio tener un mínimo de intención de formar comunidad, de querer compartir, trabajar en paralelo, hasta convergir sobre un objetivo … A veces realmente no entiendo.
Dirt Road CR 950
After a large number of delays, mainly to due to late breaking issues with undocumented behaviour changes and other issues due to the androidx migration, I’ve tagged the 15.0.0 release. Installable APKs should be available from google play and the Vespucci github repository in the next couple of days (not from f-droid which is lagging a quarter of a year currently and is unlikely to fix its build problems any time soon).
More information on the future of the app will be announced later.
Version 15 no longer supports devices with Android versions older than 4.0 / API 14. We’ve now migrated the Vespucci code base to use the “androidx” libraries to provide backwards compatibility over multiple Android versions and there is no feasible way to continue to use the old support libraries that would be necessary for older Android versions.
Import note: even though the app will work on Android 4.0 devices, devices with Android version prior to 4.1 do not have TLS 1.2 support that is required for accessing the OpenStreetMap API since August 2nd 2020. If you are experiencing authorization issues on Android versions between 4.1 and 4.4 see Can’t (re-)authenticate - TLS 1.0 / 1.1 issues.
In some circumstances, tags with multiple objects have array-like semantics (that is a fixed number of elements) contrary to being variable length lists. A typical example are lane related tags, which contain the number of elements in the lanes (or lanes:forward and lanes:backward) tag. There is no practical difference for tags that need to have a value for every element, but in the case of tags that have free form, potentially empty values, for example destination:lanes, there was previously no way of indicating this in the preset.
The current support will add empty fields if the number of elements is lower than the required number, and highlight surplus ones if there are more than the relevant tag requires.
See Vespucci preset extensions.
As you may know, Vespucci has used the “Editor Layer Index” as the source of imagery configuration since version 0.9.4 released in March 2014. ELI was one of the few, if not the only, successful, cross editor projects that reduced the amount of work duplicated across editor development, not to mention reducing the effort by community members to contribute. It was used directly by a number of projects and there was even a degree of synchronisation with JOSM.
Unluckily the iD developers have forked their own branch of ELI potentially making ELI longer term untenable. However JOSMs imagery configuration has come a long way since 2014 and now has feature parity with ELI and the JOSM developers have been kind enough to provide their data in an ELI compatible format.
Starting with version 15 we now use JOSMs background layer configuration as the default, manual updates can be pulled from the JOSM repository or you can continue use ELI. As updates replace the whole configuration with the exception of custom layers, this means you can effectively switch back to using ELI if necessary.
The internal layer support has been rewritten to allow multiple layers of the same kind for layers that support this functionality (background and overlay imagery layers, geojson layer). Layers can be moved up and down in the layer stack. It should be pointed out that adding imagery layers uses a lot of resources and should be used sparingly.
A Mapillary layer can now be added to the layer configuration. Clicking on a Mapillary image marker will open the sequence at that marker in a viewer, the forward - backward buttons will navigate along the sequence. On devices with Android 7.0 the viewer starts in a separate activity that can be shown at the same time as the map display if you add them to a multi/split window view.
Mapillary images are cached on device, the size of the cache (default 100MB) can be set in the advanced preferences.
Vespucci now has support for querying WMS servers and adding layers as custom imagery (similar to how this works in JOSM). Additional WMS servers over the pre-configured ones can be added manually. The functionality can be accessed via the layer dialog menus for the background and overlay layers.
Many Android phones support a pressure sensor that can be used instead of GPS data for determining the current elevation. Support can be turned on in the Advanced preferences / Location settings. This will enable using the barometric height in recorded tracks and when creating nodes from the current GPS location.
Android reports elevation as the height about the WGS94 ellipsoid, this is very different (up to many dozens of meters) from what you typically would expect, that is a height above mean sea level. For this reason starting with this release we no longer record the default Android height information in GPX tracks, to get roughly correct data you can either:
in both cases elevation data will then be included in your GPX tracks.
The current WGS84 and related information can now be displayed from the “GPS” menu, the displayed information will automatically update once a second as long as the dialog is shown. As a replacement for the old “create node at current location” functionality such a node can now be created from the dialog.
Every Vespucci user has seen the violet highlighting that indicates that an object may have an issue. Starting with this release the highlighting style can be configured in a limited fashion, see https://github.com/MarcusWolschon/osmeditor4android/blob/master/documentation/docs/tutorials/data_styling.md The default styles use this to highlight potentially out of date objects in orange.
It is now possible to upload only the currently selected objects, useful for example if you want to save part of an ongoing larger editing session. Further you can now update already downloaded data in place without effecting unsaved edits.
On Android 7.0 and later devices the view is run as a separate Android activity, this allows it to be used in split screen or popup window mode together with the main app without having to use an external photo viewer.
GaiaGPS.com seems to rely heavily on OpenStreetMap so I am hoping that by contributing to OpenStreetMap that I can improve the usability of GaiaGPS.com.