Este artículo hace parte de una serie de artículos relacionados con notas:

• Las notas de OpenStreetMap.
• Análisis de notas.
• Tipos de notas.
• Técnicas de creación y resolución de notas.
• Finalización proyecto de cerrado de notas en Colombia.

En el artículo anterior, traté diferentes aspectos de las notas, una funcionalidad core de OpenStreetMap. Hoy voy a plasmar esos conceptos con ejemplos gráficos, principalmente reflejando el flujo de las notas, desde su creación hasta su resolución.

Como expliqué en el artículo anterior, el flujo de las notas es el siguiente:

• Creación.
• Visualización.
• Adición de comentarios – opcional.
• Resolución.
• Reapertura – opcional.

Creación

La creación de las notas se puede hacer desde diferentes aplicaciones. Algunas ofrecen facilidades para escribirlas, y otras tienen algún texto plantilla para solo llenar unos campos.

Antes de crear cualquier nota, lo primero a tener en cuenta es haber identificado algo en terreno que no corresponde a lo que está en el mapa. Esto puede ser:

• La ausencia de algo en el mapa, que existe en realidad. Por ejemplo, falta un comercio de tal tipo, con tal nombre.
• Algún dato que no corresponde entre el mapa y la realidad. Por ejemplo, no es un comercio, sino una oficina.
• La existencia de algo en el mapa que realmente no existe. Por ejemplo, un comercio que ya cerró.

Desde la página de OSM

Una vez hemos identificado lo que queremos reportar en el mapa, vamos y lo buscamos en la página de OpenStreetMap.org haciendo zoom, moviendo el mapa según corresponda.

… See full entry

Well, I just wanted to see what this feature does so I’m posting some useless stuff.

As listed on my profile page I muck with mkgmap and my Garmin Nüvi for the USA. These Nüvis can only handle 4GiB map files. So I look at the diagnostic output of mkgmap and noticed we’ve got a billion live nodes that need to be parsed for just the USA. Not exactly sure when it passed this mark, but it was fairly recent.

1 billion USA nodes, and each node has a longitude and latitude that if were represented by a floating point number (single precision float - 32 bits) would mean 4 bytes per longitude, 4 bytes for latitude. Then an identifier…

This would 8GB by itself, without ways to link the nodes. Impressive that osm.pbf can “compress” all these nodes, ways, relations, and all the tags into a (currently) 8GB file.

But anyway been trying to go through a bunch of the QA issues in the map data. I think I got through one pass of the roundabout routing issues that are shown in mkgmap. I was playing with OSRM and GraphHopper with the errors and with the fixes, I’m surprised that people haven’t found some roundabouts that OSRM/GraphHopper completely refuse to enter… they’re scared of roundabouts! Hopefully OSRM, GraphHopper, and even my Garmin Nüvi will now route through them properly.

Alright that’s enough for now here. If this text is even useful…

I am driven by an intrinsic desire to make the world a better place. Together we can do that by mapping using OpenStreetMap!

Minor mapping on some forests in Ecuador

Certaines communes des départements de la Charente, de la Charente-Maritime, des Deux-Sèvres, de la Vienne ont comme région la Bourgogne-Franche-Comté au lieu de la Nouvelle-Aquitaine Ci-dessous le message de réponse de Heredis puis celui de ma demande ———- Sandra de Heredis (Heredis) 26 juil. 2021 à 16:05 UTC+2 Bonjour, Merci de nous avoir contactés ! Les données internet affichées dans le Monde à la Loupe proviennent de OpenStreetMap. C’est un projet collaboratif, ce qui signifie que vous aussi, vous pouvez y participer. Voici un article très complets pour vous aider à utiliser pleinement cette fonction : Contribuer à OpenStreetMap : https://help.heredis.com/contribuer-a-openstreetmap/ Plus sur help.heredis.com Merci et à bientôt ! L’équipe Heredis vous souhaite un bel été Cordialement, Sandra de Heredis Chargée de clientèle www.heredis.com ———- Didier 25 juil. 2021 à 19:58 UTC+2 Madame, Monsieur, Je vous informe que je viens de constater aujourd’hui même que bon nombre de communes (mais pas toutes) que j’utilise dans ma généalogie concernant le département de la Charente-Maritime, région de la Nouvelle-Aquitaine sont reconnues par vos soins comme faisant partie de la région Bourgogne-Franche-Comté. Cette erreur très gênante pour l’établissement ou la lecture de certains documents nécessite une régularisation assez rapide pour le crédit de votre logiciel. Je vous remercie par avance de l’intérêt que vous voudrez bien porter à ma demande et me tenir informé de la suite que vous comptez y donner. Veuillez agréer, Madame, Monsieur, mes sincères salutations. Didier OLLIVIER

Mon prochain chantier sur OpenStreetMap va être de cartographier le diocèse de Grenoble-Vienne avec toutes les paroisses qui le composent. J’ai déjà ajouté le diocèse, la prochaine étape sera de mettre la paroisse locale, puis toutes les autres, et trouver un moyen de les organiser en doyennés.

I am saving this list here as a to-do-list. Should anyone suggest a proper way to map this stuff, I will try to enter it in OSM. These are places where the owner can fine you with some hundreds euro if you drive through, if you stay more than 15 minutes at the gas station, if don’t spend enough money at the gas station, and so on.

Diese ist eine List von bekannte Besitzstörungsfälle in Wien:

• Shell-Tankstelle, Ecke Katsushikastraße/Leopoldauer Straße 49, 1210 Wien (hinter der Brücke bei McDonalds)
• Sackgasse Breitenleer Straße 50, 1220 Wien
• Liegenschaft Siemensstraße 105A, ident mit Richard-Neutra-Gasse 3, 1210 Wien
• Donaufelder Straße 135, 1210 Wien (zwischen Hofer und Einkaufszeile Schichtweg)
• Franz-Eduard-Matras-Gasse 5-7, 1220 Wien Es handelt sich hier um eine Sackgasse an deren Ende es kein Weiterkommen für mehrspurigen Verkehr gibt. Das Wenden des Fahrzeuges ist nahezu unmöglich. Deshalb nutzen viele Lenker die Möglichkeit und wenden in einem anliegendem Grundstück. Da dieses überwacht wird, kommt es in jedem Fall zu einer Besitzstörungsanzeige.
• Brünner Straße 64, 1210 Wien, FS Tankstelle. Sogar Kunden der bei selber Adresse befindliche Autowerkstatt werden angezeigt.
• Donaufelder Straße 128, Tankstelle, 1210 Wien
• Heiligenstädter Str. 60, Shell
• BP Tankstelle, Gaudenzdorfer Gürtel 77, 1050 Wien

Over 6 months ago, OpenStreetMap (OSM) and OpenStreetMap Foundation (OSMF) members, community supporters, organizations, and allies called for change in how OSM and OSMF conduct themselves.

We asked:

“The OpenStreetMap Foundation (OSMF) and OpenStreetMap (OSM) need to prioritize diversity and inclusion in positions of power and governance. We recommend a renewal and implementation of an OSM Code of Conduct and deliver on the next recommended stages for a diverse and inclusive OSM and OSMF. We want the OSMF to ask itself: who does it exist to serve? How can we be more open?”

Resource: A Call to Take Action and Confront Systemic Offensive Behaviour in the OSM Community »>The original document»>

The Result:

The OSMF board asked the Local Chapters and Community Working Group (LCCWG) to form a subcommittee on “Moderation”. This group has been meeting and coordinating since January 2021 (lead by Maggie Cawley, OSM US).

“In December 2020, the OpenStreetMap Foundation (OSMF) Board set out to “find partners to help instate a moderator team for the OSMF-talk and talk mailing lists” and in their December 2020 meeting requested that the LCCWG take the lead on this initiative. Subsequently, this group has been formed as a subcommittee of LCCWG. The Moderation Subcommittee is a temporary group of OSM community members working on this Scope of Work via this Implementation Plan. Learn more about participants and find links to any draft documents on the Subcommittee’s page. “

The Ask - Give feedback by August 18, 2021:

The LCCWG Moderation Subcommittee solicits community input on its DRAFT Process for Moderation, which would apply to the osm- and osmf-talk mailing lists. Hosted in the OSM wiki, the Discussion page is open for comments until August 18, 2021.

… See full entry

Tatto

I’m a recently retired senior leader/exploration geologist after 23 years working for a major international oil and gas company. I’m familiar with GIS systems, but not an expert by any means.

I spent a large portion of my career mapping remote sensing data in order to determine what lies below the surface of the earth. In my case this was primarily seismic data and well log data, but occasionally magnetic or gravity data.

I’m looking for some fun things to do so I started contributing to OSM.

New to OSM, may make some newbie mistakes, so please comment, send me a msg. Feedback/help always welcome.

Generally using aerial imagery (ESRI World, world clarity, Mapbox, Maxar). I scan through multiple images to get a sense of offset. Also using OSM GPS traces loaded by others

No litoral da BA, Quiepe parece escondida a sete chaves. Mesmo em local estratégico, está fora das rotas de navegação. Busca no Google dá em vazio no mar, em local errado. Mas, com ferramentas livres, paraíso privado foi, enfim, mapeado… https://outraspalavras.net/direitosouprivilegios/a-ilha-dos-odebrecht-que-o-google-maps-esconde/

This diary entry is a bit delayed, but this will contain my progress for the gsoc period so far and what I have been upto during the last 5-6 weeks A detailed description of my work can also be found at Github Wiki

My task was to create an Element History Comparison dialog for Vespucci, which can be provided as a separate library so that it can be useful for other open source projects if they need the same functionality.

What the Element History Comparison Dialog does is what the name suggests, i.e it compares what changes the have been made to a particular OSM element on the map and details them, like providing tag changes and which user has made those changes. It works as something similar to the built in history feature of JOSM.

Right now, I have completed the dialog itself and am currently testing different possible user interfaces for the application, in order to better suit a mobile screen, which has been the most challenging part so far as due to the lack of width on the mobile device certain compromises needed to be made

My Weekly progress has been the following:

Week1

• Created all the required base OSM elements and storage structures
• Created a custom implementation of the OSM parser to parse the XML response
• Added unit tests for the base OSM classes and the parser
• Created the initial library interface
• Setup for the HTTP requests

Week2

• Created the version selection screen UI
• Impl. the version selection logic with radioButtons and groups

Week3

• Created tests for the version selection screen
• Improved UI for the history screen
• Current UI for the selection screen

Week4

• Created the base UI for the comparison screen
• Created the logic for the comparison screen
• Implemented changeset fetching

Week5

• Created logic for the comparison screen
• Added changeSet Details
• Add basic UI for comparison
• Fix test cases

Week6

• Ui testing and improvements

… See full entry

I really hate litter. I have a very vague project in mind which will involve mapping litter in some way. Having information about the location of litter bins seems like it would be helpful, so I am starting with that. Hopefully as I work through this the vague project will take better form - this works in many other endeavors, so why not with this one.

Little Steps !

I mapped the task in order to response to the area vulnerable to flood #GemU2018

Landuse:

Major Cities:

  Phoenix:

     5/15 Urban Villages Semi-Complete

     0/15 Urban Villages Landuse Glue Fixed

   
  Mesa:

  Scottsdale:

  Tempe:

Minor Cities:

0/11 completed

Towns:

0/10 completed   

Unpopulated Districts:

0/19 CDPs completed

0/304 Tracts Completed

Buildings: TBA

wie lösche ich mein Profil?

Részletek kidolgozás alatt, lásd:

https://wiki.osm.org/wiki/Hungary/20210726

Előtte (pl. 16:00) fakultatív séta a Mocsáros-dűlő felé házszámozás.

I am updating accuracy aligning building’s, adding building names , Removing demolished buildings and adding new as they are built.

Test

test