Recent diary entries
Registrando rapidamente a atividade, nesta quinta, dia 20/08/2015, visitamos o bairro Barreiro Cabral nas proximidades de onde ficava o bairro Freguesia Velha. Lá se encontram grandes riquezas visuais, naturais e históricas.
Primeiro visitamos o cemitério que foi transferido da Freguesia Velha para construção da fábrica de cimento por volta da década de 70 e a igreja erguida ao seu lado.
Depois fomos um pouco mais na frente até uma mina de ouro abandonada, dos tempos do ciclo do ouro na região, onde existe ao lado uma famosa figueira gigante e logo abaixo, no Rio das Almas, um Encanados, construção de pedra para exploração de ouro apresentando pedras que foram cavadas por intervenção humana.
Mais detalhes sobre essa atividade: http://rede.acessasp.sp.gov.br/blogada/mapeando-mais-locais-historicos
I only recently realised that HOT contributors need to mark at least one task as "done" to be listed as project contributor in the tasking manager. This made me wonder: how many people start contributing to a HOT project but never finish their first task? What proportion of all HOT edits are contributed in this manner?
Summary: about half of all HOT contributors never complete their first task on a project, although they do contribute to the map. These "partial" contributions account for 10-20% of all HOT edits.
Here's a timeline of the number of monthly HOT contributors, compared with the number of those who completed at least one task:
And here the corresponding timeline of the number of edits contributed by both groups of people:
Expressed as percentages:
We don’t know why these contributors never completed the task, we can speculate but really we would need to ask them. Some may have forgotten to close it after they were done, some may not have had the confidence to mark it as "complete" and wanted someone else to have a second look, some may have gotten distracted, or lost motivation, etc.
It's also worth bearing in mind that we can always expect some proportion of tasks to be abandoned early: not everyone is interested in contributing to HOT in the long term. Many people are likely simply curious and try it out for a bit. Many may have come across HOT because a friend sent them a link, or because it was in the news, and we can't expect all of them to stick around.
However we should also be mindful of these early experiences. On one hand we can improve our understanding of what makes people stop early. On the other hand we should also consider the impact these contributions have on our map, and on validation and QA efforts. Where should we send absolute newcomers the next time we're in the news?
Some background info on the analysis...
I’m identifying HOT contributions in the OSM edit history as follows:
- The contribution needs to fall within the geographic boundaries of a HOT project
- The contribution needs to happen within the activity period of the HOT project
- And then...
- EITHER the user is a listed project contributor (they marked at least one task as done),
- OR the changeset is tagged with a valid HOT project ID (the contributor never marked a task as done, but likely did start a task in the tasking manager before contributing edits.)
There are some caveats with this data:
- In this analysis, one completed task by a contributor is enough to regard all their contributions to the same project to be marked as "done". The simple heuristics above do not allow me to distinguish task completion states for all individual changesets of a contributor to a project.
- We can't distinguish contributors who never mark a task as "done" from validators, or expert contributors who manually tag changesets with a project ID. We don’t have the data to distinguish these cases, e.g. there is no published list of validators to compare against.
- We can only reliably track this from Aug 2014 when iD started carrying over project-specific changeset tags from the tasking manager. We won't be able to identify "unsubmitted" contributions before then.
достатньо багато роботи - місцина дуже цікава
I never intended to map the Bay Area. Instead, I typically spend my free time helping to map my hometown of Cincinnati and tame TIGER deserts elsewhere in Ohio from the comfort of my (armless) chair. I always assumed that the middle of Silicon Valley would be full of tech enthusiasts who occupy their time by micromapping every last bench and bush. The map sure looked complete, with lots of
highway=secondarys, landuse areas covering every square inch, and plenty of rail and bike infrastructure.
But then, in April, I zoomed in. I had recently joined Mapbox to work on iOS map software, and the Show My Location function went right to my unmapped doorstep. Around me was an endless parade of outdated street configurations, missing landmarks, test edits, proposed BART stations tagged as the real thing, and GNIS-imported hospitals that had been closed for years. Most of the map hadn’t been touched in six years. In terms of POIs like shops and restaurants, central San José in 2015 was as blank as Cincinnati was in 2008. (San José is the country’s tenth-largest city, with a population 3½ times that of Cincinnati.)
Zoom in all the way to the spot marked San José, and this is what you would’ve found earlier this year.
As I added in pent-up local knowledge, I couldn’t help but notice some unfortunate tagging practices. The Bay Area is (ahem) liberal in its use of
highway=secondary. It wasn’t difficult to find quiet residential roads with speed bumps, Child at Play signs, or unsignalized crosswalks being tagged as
secondary, the same tag often used for heavily-used roads in other cities or 55 mph state highways in rural areas.
Most of the giant landuse areas that blanket the city need to be redrawn. Many
landuse=residential areas conflate distinct neighborhoods or include tree-lined business districts (which look like residential areas from the air). Meanwhile, many industrial areas are being converted into residential areas due to a local housing boom. As much as possible, I’m replacing these generic landuse areas with more specific ones that correspond to individually named subdivisions, office parks, and retail complexes.
I suspect that the highway classifications and generic landuse areas, combined with decent rail data, made the map look a lot more complete than it really was. To a newcomer, the total absence of restaurants, buildings, and non-armchair-mappable information might’ve looked like a limitation of the project rather than a blank slate waiting to be edited. And again, there should be no shortage of visitors from San José, because this is Silicon Valley, where people talk about things like OSM. I’m sure the original mappers were doing their best at the time; unfortunately, six years ago, none of us knew as much about mapping ago as we do now.
San José is looking a lot better after an intense few months of surveying. There are plenty of POIs downtown – too many to fit onto the map at z19, in fact – as well as invisible attributes like speed, weight, height, and turn restrictions. I’m having particular fun mapping the many ethnic enclaves around town, which are very poorly represented on commercial map services.
The San José
place=city POI incorrectly sat 12 blocks away from where it should’ve been, at the site of this church, which incidentally is missing from Apple, Google, and HERE.
Still, that’s only one city. We’ve always known TIGER deserts are a problem, but are other cities similarly languishing after an initial burst of detail, flying under the radar because we all think they’re being taken care of? Maybe we can prevent that from happening in the future by making the map look only as complete as it really is.
Voglio segnalare un bella iniziativa ad opera di Carlo Benini (http://www.openstreetmap.org/user/carlobenini) che ha organizzato per sabato 12 settembre 2015 alle 9.00 presso la biblioteca comunale di Mozzacane (VR) la III edizione Mapping party OpenStreetMap - Mappiamo Mozzecane. Per chi fosse della zona (Verona - Brescia - Mantova) consiglio la partecipazione perché si ha la possibilità di imparare tante nozioni sul collaborative mapping! Il mio invito è a promuovere eventi del genere anche nelle vostre realtà.
Ecco Mozzecane su OpenStreetMap: http://www.openstreetmap.org/#map=16/45.3082/10.8171
Under their Child Rights Governance(CRG) project in Dhaka Save the Children International has taken initiative to share local knowledge in open platform and involving community in the knowledge sharing and using process through available technologies. Save the children has decided to teach OSM knowledge to community youth group including adolescents sothat they can share the updates of the surrounding features in Slum areas where they are living. The knowledge will be then used through community health service apps during the needs of people in slum. Keeping the sustainability in mind Save the Children has taken decision to provide the training same time to more 100 university students along with slum youth groups. This capacity of the student community will contribute not only in CRG project areas but also in the open map data base Bangladesh. Ahasanul Hoque(@ahasan4u), GIS specialist and OSM trainer is conducting the trainings starting from 24th August 2015. All training will be held at Save the Children Office, Dhaka [House CWN (A) 35, Road 43, Gulshan 2, Dhaka 1212, Bangladesh] and the mapping parties in slum areas will be held in Mirpur Sector 13 area of Dhaka city starting from October 3rd, 2015. #hotosm #missingmapsproject #osmbd #osm blogs
Ministry of Road Transport and Highways (India) manuals for standards and specifications for four and six laning of national highways. As seen on National Highways Authority of India (NHAI) website
Specs for four-laning of national highways: Scanned PDF Link - 2.8MB
Specs for six-laning of national highways: Scanned PDF Link - 2.3MB
New NH numbering scheme
Department of Road Transport and Highways (DORTH) published a new numbering system for national highways: Scanned PDF document - 3.3MiB (28th April 2010)
The document reads in English from page #21.
Old numbers: Wikipedia Link
New numbers: Wikipedia Link
Der findes et Stamdataregister for vindmøller
Men de opgiver koordinat i et UTM 32 Euref89 format. Jeg har fundet denne side til at konverter til et brugbart Latitude and Longitude.
(http://www.uwgb.edu/dutchs/UsefulData/ConvertUTMNoOZ.HTM) Når jeg bruger 32 i Zone så virker det. Om 32 kun dur med denne register ved jeg ikke !
It is a truism that software has bugs and while as a developer it would be nice to say that they are all somebodies else's fault, but we are probably are all just as bad as each other with respect to slip-ups. In the case of Vespucci the additional complication is that we are dealing with at least 26 different Android versions and 100s of different devices, each with its own manufacturer tweaks to hard- and software.
So unluckily now and then you might experience a crash. I do have to say outside of provoked crashes and early dev builds I haven't had one for ages, but then I use a relative mainstream device for mapping and don't try to edit gigantic areas, The important thing is to either get the issue fixed, or at least find out how to avoid it in the future.
Those readers that have had the unpleasant experience know that post-crash you will be offered the chance to submit a crash report. We do this with ACRA http://www.acra.ch/ and store the reports on a private acralyser server. ACRA gives us a lot of information on the HW and SW configuration of the device, a short excerpt of the system logfile and a stacktrace indicating what the immediate cause of the crash was and where in the Vespucci or Android code it happened. It does not store any personal information of the user in question, in principle we could ask for an e-mail address, but I would prefer not to for data protection reasons. Note on the side: there are some situations in which we'll produce a stack trace just to document an unusual situation, if you don't get an additional warning in general there is no reason to be concerned.
Now if you experienced a real crash (real: as in Vespucci restarted or stopped completely) please submit the crash report, but further please check our issue tracker and our twitter account. If your problem doesn't seem to be known or not already fixed, please open a new issue pointing out that you submitted a report, this is the only way we can get in direct contact with you. Complaining on googles play store or continuously sending the same crash (don't forget it might be related to your device or your editing habits) wont help.
A Prefeitura Municipal de Itapoá, representada pelo Sr. Luis Carlos Zagonel (Chefe de Gabinete do Prefeito), autorizou em 12/08/2015, a utilização dos dados do município disponibilizados no site municipal para uso no OSM.
Esta valiosa e importante colaboração, me permitiu cadastrar todas as vias urbanas constantes no Mapa Geral 2014, com os seus nomes oficiais.
Agora, as pessoas podem conhecer ou locomover-se por este belo Balneário Catarinense, utilizando as informações do Openstreetmap.
Parabéns ao Prefeito de Itapoá e a sua equipe por esta exemplar atitude.
Ένας καλός άνθρωπος χαρτογράφησε με λατινικούς. Να προστεθούν Ελληνικά. https://www.openstreetmap.org/user/Haack70
Terzo mapping party a Mozzecane! Contribuiamo tutti assieme a mappare Mozzecane con OpenStreetMap. Ci troviamo sabato 12 settembre 2015 alle 9.00 davanti alla biblioteca comunale, l’associazione LinuxLudus darà il supporto per il mapping party.
Cosa abbiamo già fatto? Nelle scorse edizioni abbiamo inserito i dati di tutti negozi e i numeri civici a est della via principale. In questa edizione inseriamo numeri civici e altri dettagli non ancora presenti su OpenStreetMap a ovest della via principale.
Perché questo lavoro? La mappa è usata dal comune per migliorare i servizi al cittadino e con i mapping party la rendiamo sempre più dettagliata per avere un servizio di qualità! Se vuoi unirti a noi compila il form di iscrizione che trovi a questo link: https://docs.google.com/forms/d/1XhGniHvXoZ8vnuhKtV-ESxaTh6JZBgZLw9Oyxu7j_wQ/viewform
Cosa serve portare? Niente! Tutto il materiale e le informazioni che servono ti saranno dati dall’organizzazione. Che aspetti? Iscriviti! Ci vediamo presto
While looking for missing paths to trace using the Strava Routing Errors tool, noticed the heatmap picking up a lot of activity going into one particular office.
On a closer look, turned out to be a tech company by the name Linear Technology (roof logo!).
Here's a thank you map for all those awesome bikers from there contributing to the open map. Keep biking!
Mysore Palace ( Kannada: ಮೈಸೂರು ಅರಮನೆ ) also called as Amba Vilas Palace located in the city Mysuru, Karnataka, India.
The whole building is marked as
building = yes on top of it everything is
building:part = yes. Texturing is another important thing in 3D development. Used Hexadecimal colour codes to building facade and roofs.
Kendzi3d is a useful plugin for JOSM for 3D mapping. It renders the building parts immediately as soon you change the
building:colour... etc tags with out uploading the data to the OSM.
Screen shots from F4 Map
ಅರಮನೆಯ ಒಂದು ನೋಟ ನೋಡಲು ಇಲ್ಲಿ ಕ್ಲಿಕ್ ಮಾಡಿ. 👉 F4 Map link is here
Happy mapping 😀🌎
Je suis mappeur plus ou moins régulier autour de Rennes et dans le sud mayenne. Je me concentre beaucoup autour des cours d'eau bretons ces temps-ci.