Recent diary entries
Hello everybody. I just mapping in Peru for add jungle and river via Bing satelite. This to monitor some weather event Also, this help to the citizens for disaster prevention.
Thank you for considering the note.  http://unasolafuerza.pe/
P.S.: Sorry for mapping in Brasil, too.
Hi all, my name is Pete Masters and I am the outgoing Missing Maps coordinator at MSF UK (I change jobs in a few weeks).
I would like to be considered as a HOT board member because I have a lot of respect and admiration for what HOT does in the humanitarian sphere and I think my skills, experience and networks can be of value to HOT on a strategic level. For me, it represents a chance to contribute to a community that I have come to be very proud of in a different way. This would be my first board position and I am eager to prove to myself and to the community that I can operate at this level and help to take HOT forward.
In my eyes, the future of HOT is very interesting. On the one hand, local communities are growing strong in places where previously HOT would have been only mapping remotely. The size and diversity of the community behind the first State of the Map Africa this year is testament to this growth. On the other hand, NGOs, large and small, are coming to rely more and more on OSM data and HOT through activations, and initiatives like Missing Maps. These are serious organisations with short timelines and specific needs. In my opinion, HOT must continue to walk the line between these two vital elements; the bottom-up, grassroots communities and the top-down, humanitarian actors. I do not have the answers to how HOT does this, but I believe I have some good ideas.
The most important in my eyes, and the one I would like to discuss here, is credibility, and this works both ways.
For the NGOs, HOT's activations, both emergency and long term must be impact-focused and appropriate. This means providing data that meets the needs of the situation in a timely fashion. We will need to better able to understand and translate operational needs, prioritise mapping, mobilise resources and motivate current and new community members and mappers effectively. I think my experience with MSF can help HOT to do this. Over the past two and a half years, being the bridge between an extremely operationally-focused NGO and a volunteer community has been my job and translating what an epidemiologist or a logistician or an emergency team needs into mapping projects has been my day-to-day. Through this, I have learnt the importance of understanding of where limitations of humanitarian mapping lie and how expectations need to be managed.
On the other side, I believe HOT needs to stay true to its roots and HOT's roots are in community. The community members and the mappers should be an integral part of what HOT is. This means supporting people to be more proactive in their engagement with the mapping, but also with the decision making. At the heart of this should be information flow. Too often I feel that a lot is asked of the community without them necessarily being offered much in return. For me, the best Missing Maps collaborations have happened where MSF has been able to externalise a problem it faces, volunteers have felt empowered to add value to the medical care being delivered in the field, and where that value has been reported back quickly. I feel I have been able to instill this successfully in the culture of Missing Maps (although improvement is always possible) and would look forward to putting this experience and my background in communications and community building at the disposal of HOT to help try and make this happen at a broader level.
To be honest, whether as a board member or not, I look forward to a long relationship to HOT. I love being a part of this community and love the conversations (easy and hard) that come with it.
I apologise for the brevity and lateness of this post. I have been on the road with MSF for a few weeks now and have only just found the time.... In the interests of transparency, it is important to note that my new job will also be with MSF (as Medical Innovation Advisor).
(If any of the following does not make sense, then read Part #1 first)
It's raining heavily this morning so no field survey (it kills the smartphone), but some most valuable desk-surveys using NLS - OS 1:25k 1st Series 1937-61 imagery within JOSM + a phone-call (+44 (0) 800 783 4444) to Severn Trent Water.
The culvert from Mapperley Golf Course was (badly) mapped using one of the NLS maps — probably NLS - Bartholomew Half Inch, 1897-1907, which is very low resolution and, in any case, few of them help much in accurate mapping. I'm going to trim the line of the culvert from Mapperley Golf a little to match the higher-res NLS maps; one of the reasons for this is that this brings the line of the culvert not only into line with the stream on those maps (one of the points where the earlier mapping went bad) but also with the point where that stream crosses Arnold Lane. At the moment the culvert passes straight through some houses on both The Fairway and High Hazles Close (not very likely) then across Arnold Lane north of the Village boundary. It is far more likely to have followed the original line of the stream, which would also have been Gedling Village boundary at that point. That would have taken it under the line of The Fairway (a private road) and across the bottom of the High Hazles Close’ gardens (that is almost due East-West, with the gardens to the north & a playing field to the south, a line of hedges in between. The old stream/OSM culvert then pops out close to the signpost on Arnold Lane that says “Gedling Village”, which also the lowest point of Arnold Lane on that section of road and thus where you would expect a stream to flow:–
The conversation with STW concentrated on culverts and was considerably complicated by my need to give him X-Y references drawn from the Adopted Highways register map and to keep cross-referencing to my marker points within JOSM. However, I was able to establish that yes, an (almost) East-West culvert joins with the southern man-hole cover and then runs south to the bridge. I've also established the precise location of where the northern spur meets the surface-drain. Most excellent! Final mapping on this section will have to wait for a final survey to establish some GPS tracks for the current drain/Ouse Dyke to the north (hopefully tomorrow).
One feature that I find so very interesting in all this is the way that modern culverts (as just one instance) follow ancient streams. I guess that it is simply engineers taking the line of least resistance (as, indeed, did the stream before them). In this particular case, the meeting point for the two streams in the maps is almost exactly on top of the southern manhole, which makes life very simple.
To try to help keep some eyes on the page, here is a couple of photos showing the bridge for Ouse Dyke across Jessops Lane (originally called “Hanging Lane”, the old road made a dog-leg at this point, although the modern road is straight) and then the stream (plus duck) on the other side as it makes it's way into Willow Park, and finally at the opposite end of Willow Park before it becomes culverted again:–
Looks like a small bridge for pedestrians to cross a drain - that's what I perceived from Bing imagery. Nope! It's an advert sign for an automobile shop.
with the roads they only have one speed. Alot of roads in Australia have different speeds on both sides of the road. Is it possible to have a speed for the left side and right side of the road
Entire Local government
Maproulette challenges have become fairly popular recently, especially due to Jochen's Area fixing project. But it seems this has gotten out of hand now and creates serious damage to the OpenStreetMap project.
In general this kind of tool is prone to inviting mechanical work. But with the recent Island and Shoreline Alignment challenge this really gets over the top. I first saw this when various edits turned up in remote areas of the world by various mappers in very high frequency editing islands in changing locations far apart within minutes, often without factual basis and often factually incorrect.
This challenge does everything wrong that can be done wrong with a fixing effort:
- there are no useful instructions to the mapper what to do and what problems to consider. It only says: ''Align the highlighted island to match imagery''.
- there is no documentation who created this task and how the allegedly misaligned islands are detected.
- and most importantly: the task covers areas where the global images routinely available offer no basis for improving the existing data.
Task: Align the highlighted island to match imagery (link)
Especially the last point is a big practical issue now since the edits made through this challenge misalign and worsen a lot of data in OSM. I commented on two most obvious cases where Bing offers no image at all but mappers none the less blindly followed the task to Align the highlighted island to match none-existing imagery with obvious results. But even in areas where Bing offers low resolution images these hardly ever allow improving existing data. These images in Bing are mostly from >15 years old L1G Landsat 7 images which have positional errors of sometimes more than 100m and rarely allow substantially improving existing mapping. In most cases attempts to do so made within the challenge worsen data which has often been mapped from either better data or with better alignment of the images.
With edits like this the island in question is not necessarily less accurate than before - the mapping before was done based on - if at all - only slightly better aligned images. But it is no improvement since it is likely not more accurate than before in absolute terms and is definitely less accurate relative to the surrounding features.
Yes, these images show a lot of potential to improve mapping here
The least that needs to be done here is
- stop the challenge as it is now
- limit it to areas where high resolution images are available in common sources
- create clear instructions for the mapper advising them to properly check image alignment and find the best quality sources in the area and check if existing mapping might already be of better quality based on other sources. This is not possible to do within a few minutes if you pick random locations all around the world of course.
Of course not all edits made within these challenges even in areas where Bing is poor are bad, there are also some experienced mappers participating here who know how to properly assess and select images.
If whoever created this challenge seriously wants to improve mapping in remote areas the most basic, most productive and most obvious way would be to provide better quality images.
And in general i think we need to put a review regime on organized mapping efforts like maproulette challenges requiring at least basic documentation of the process used to generate the task and ensuring there are proper instructions for the mappers and no nonsense tasks on a larger scale. A lot of thoughtful tasks have been offered in maproulette in the past but apparently this is not something that can be relied upon to be ensured without a QA process for the QA process...
ramyaragupathy asked me recently how well I thought Seattle was mapped. One of the areas was very broad, POI's which makes answering the question very difficult. Thinking about the question lead to what outside data source could we compare to OSM to get a sense of completeness.
I stumbled across the King County Health Department Restaurant Inspections. Every restaurant inspection, going back many years, is available in the counties open data repository.
The data needed some massaging, food inspectors seem to think that they shouldn't limit themselves to just restaurants but any business that serves food, including schools, company cafeterias, the fried chicken (ugh) found in mini marts and food trucks. After removing businesses that didn't match amenity=fast_food or restaurant or cafe it appears that OSM has 1,714 food service businesses vs. 3,680 inspected by the county or 47%, slightly less than half.
The actual results are most likely somewhere near 47% but OSM many have some closed businesses and the county's list may be over stated (I may have keep businesses that should have been excluded.)
That brings up the question - what to do with all of the county's data. It's definitely not something I'd like to see imported, but it would be nice to see better coverage. What are your recommendations?
Here is the latest from the MapRoulette world! If you want to get this newsletter in your mailbox, you can sign up here!
MapRoulette was featured in the JOSM message of the day!
MapRoulette has seen a lot of activity in the past month! A total of 407 mappers have logged on and fixed more than 32000 tasks. That is really cool.
New and notable challenges
Also, lots of new challenges! 539 to be precise created in the last month. I know that challenges can still be hard to discover (working on that, I would welcome ideas and help there!) so I want to just manually highlight some challenges that look interesting. If you want your challenge highlighted in this newsletter, please write to firstname.lastname@example.org!
- Clean up AND import (Netherlands) -- help clean up additional tags on nodes that were added as part of the AND import.
- Add Wikipedia / Wikidata tags in India -- A couple of challenges where you can help add Wikidata tagging to districts and railway stations in India
The latest from Github
- In the newest version of MapRoulette, we re-introduced keyboard shortcuts. There is discussion around which keys to use. What do you think?
- There are new labels
needs-discussionso you can easily see where your opinion is most wanted.
- If you want to contribute to MapRoulette, why not look at the tickets labeled
How to: Task Instructions
Perhaps you have seen that the task instructions do not always fit in the panel.
That is annoying because it can be unclear what you should do. Usually this is caused by hyperlinks that are too long and can't be broken up. If you are a Challenge creator, you can avoid this by using markdown to wrap the hyperlink. Instead of using the raw link in your instruction (
https://long-long-url.org), use this:
[description](https://long-long-url.org)and it will be displayed like this:
Help Wanted: Challenge Administrators
With so many new challenges coming in, it would be great if a few of you would volunteer to help with Challenge maintenance. That means looking at new Challenges that users create to see if they make sense, and helping the Challenge creators to improve them if needed. If you are interested in helping with this, email email@example.com!
That's it for this month. Please write in if you have suggestions for this newsletter. Happy mapping!
Oh yes! History is full of the names of famous Explorers, searching for the source…
- 1804 Captain Meriwether Lewis and Lieutenant William Clark (source of the Missouri River & also the astonishing Lewis and Clark Expedition)
- 1856 Captain Sir Richard Burton and John Hanning Speke (source of the Nile)
- 1866 David Livingstone and Henry Morton Stanley (source of the Nile)
…and so, in honour of these & other, similar noble exploits, on Sunday 26 March 2017 your mapper selflessly set forth into the wildlands of the heights of Gedling Country Park to discover the source of …, erm, Ouse Dyke (I do wish that they could have given it a bit of a more romantic name) and …, erm, got my Clarks muddy. So yes, no trouble nor expense shared to nobly & selflessly bring the wonders of Gedling slag heap to your door.
A short length of Ouse Dyke was marked up in those heights on the Nottingham City Adopted Highways Register, and I'd noticed obvious signs of a bridge across Lambley Lane that should contain Ouse Dyke (although now culverted), plus manhole covers for a culvert North-South across Lambley Lane Recreation Ground, so I was confident of a result.
Here are some highlights of that mapping session, using my new-new smartphone for the first time:–
A northern basin (mapping), fed by culverts & natural drainage from the surrounding hills. As best as I can tell, this is NOT a source for Ouse Dyke, although goodness knows what Severn Trent does if the rainfall is too large:–
As you can tell by the lack of fencing, Gedling Council is rather Spartan towards it's children rather than treating them as soft Athenians. That also shows in the way that it only warns you of the drop as you are about to fall, and the lack of a lifebuoy in the Lifebuoy holder.
Having become an expert on Flood Lagoons, these two look like Retention lagoons, in that there are zero pumping mechanisms in sight. I assume that any excess will have to drain to the west into the trees (to the North, East & South are high-parts formed from spoil dumped from the now-closed Gedling Colliery). Some of the efforts to safely drain & re-green the slag-heap show in the next few pictures, each taken from further to the south & east:–
At the time I thought that I had hit Ouse Dyke pay-dirt but, seeing the pictures in the context of the map, it was clear that these all drained into the Southern Basin, so maybe not.
The amount of efforts taken here by Severn Trent are extreme, and it was viscerally clear to me that Water Engineers such as those employed by ST have taken on-board the horrible lessons of Aberfan from 1966 (a coal slag-heap in Wales, built upon a stream, which washed an avalanche of muck down the hill and into Pantglas Junior School directly below it, killing 116 children and 28 adults).
The following stream seems most likely to directly be the modern source of Ouse Dyke (I have put it on the map but it is hidden by trees & needs proper tracking). It is south & below the southern Basin and is heading south-east. It is a handful of metres north-east of the Information Map (mapping), which itself is a few metres north of where the abandoned mineral railway, older hiking track and proposed Gedling Access Road all pass:–
Addendum 1: I've changed the mapping from waterway=stream to waterway=ditch, as we are dealing with an artificial drain created by Severn Trent rather than a natural stream leaping merrily from rock to rock.
Addendum 2: the following note has been added to the
2017-Mar: Google Earth shows one (sometimes two) rail-tracks on the land; they must have added them afterwards, as none exist.
It is perfectly reasonable to say that a culvert passes between them and, seeing as continuing the line of that culvert towards town that there is a bridge that crosses Lambley Lane (below), I also believe that it is perfectly reasonable to assume that the culvert passes through that bridge across to the other side (although today the ground shows dry, the bridge is at the lowest part of that section of Lambley Lane and therefore the most natural place for a stream to flow out of the higher ground to the north):–
Further mapping on the continuing line of that culvert, plus it's appearance as a stream, will have to wait until I actually map that area (coming soon). However, there is a final oddity within the Recreation Ground…
The photo below was taken on November 27, 2016 and is of a stream that rises within what is now Mapperley Golf Course and exits into a culvert operated by Severn Trent Water at the southern-most point of the Course:–
That culvert was originally found within a NPE map & transferred onto OSM many years ago. After someone raised doubts about it, I spent all the months between November & now trying to find someone to speak about it, but no-one answered my knocks on their door. It finished on NPE within the Recreation Area, close to the southern Manhole cover. I think that it merges with that culvert (but have not moved it).
The final item is to make note of my re-mapping of a
"historic:waterway"="stream" which is mapped but never shows (due to missing tags). Originally it met with & combined with the NPE culvert, and it looks like it is supposed to come from the drain further to the north. I've:
- disconnected it from the NPE Culvert
- connected it with the northern man-hole instead
- have given it
culverttags instead of
(there isn't a stream that wanders across all the football pitches)
And that is the end of the search for the source of Ouse Dyke. It seems very much like it is a combo of a stream coming down from (what is now) Gedling Country Park and a small stream that originates within (what is now) Mapperley Golf Course.
[see part #2 for confirmation of my findings]
El objetivo de este instructivo es explicar de la manera más simple la forma correcta de añadir radares fijos (de velocidad o de semáforo) en OSM.
Importante: Antes de empezar debemos estar 100% seguros de que el radar que vamos a agregar realmente existe. Para eso podemos verificarlo personalmente en el lugar o mediante fotografías a nivel calle compatibles con la licencia de OSM como Mapillary u OpenStreetCam. No debemos usar Google StreetView para mapear en OSM porque su licencia y términos de uso lo impide.
A grandes rasgos, sin importar el editor que usemos, deberemos:
Crear un nodo con la etiqueta highway=speed_camera donde realmente se encuentra ubicado el radar, por ejemplo al costado de la vía (usamos vía como término genérico de camino, calle, avenida, ruta, autovía, autopista, etc.)
Posicionar los nodos de la vía que marcan el comienzo y final de la sección que cubre la cámara.
Crear una relación del tipo enforcement para definir el tipo de radar (de velocidad o semáforo), la velocidad máxima permitida y relacionar el nodo de la cámara con el rol "device" (dispositivo) y los nodos de la vía con los roles "from" (desde) y "to" (hasta).
Nota: Si tenés dudas sobre que es un nodo y etiquetas, te recomiendo que antes de seguir leas la documentación para principiantes de LearnOSM.
Cómo añadir un radar con JOSM, paso a paso
Abrir el editor JOSM (Descargar de https://josm.openstreetmap.de/) y asegurarse de tener instalado el complemento "reltoolbox" desde Editar > Preferencias > Complementos. En caso de no tener el complemento instalado, hay que tildarlo y hacer clic en Aceptar.
Ir a Archivo > Descargar datos desde OSM, seleccionar el área donde se encuentra el radar y hacer clic en el botón Descargar.
Crear un nodo donde realmente se encuentra la cámara y etiquetarlo con la clave highway y el valor speed_camera. Para eso hay que usar la herramienta para dibujar nodos y hacer clic en el botón "Añadir" del panel de etiquetas.
Definir una relación para establecer los detalles del radar. Para eso debemos seleccionar el nodo del radar que creamos en el punto anterior y hacer clic en el botón "Nuevo" de la Caja de herramienta de relaciones (Si no ves ese panel podés activarlo desde Ventana > Caja de herramienta de relaciones).
Elegir el tipo de relación "enforcement".
Con la nueva relación seleccionada, hacer clic en el botón del lápiz para abrir el editor de relaciones.
Al tipo de relación que definimos en el punto 5 (type=enforcement) le agregaremos las siguientes etiquetas con el botón de nueva etiqueta [+] para describir el radar:
- enforcement=maxspeed para indicar que se trata de una cámara de velocidad. Para cámaras de semáforo usar enforcement=traffic_signals.
- maxspeed=80 para indicar la velocidad máxima permitida en ese punto es 80 km/h.
Completar los miembros de la relación para indicar el sentido de circulación que vigila el radar.
- Al nodo del radar le asignamos la función "device" escribiendo a mano ese valor.
- Seleccionamos en el mapa (o lo creamos si no existe) el nodo de la vía desde donde se comenzará a alertar sobre el radar (nodo de entrada) y tocamos el botón "Añadir antes del primer miembro". A continuación le asignamos la función "from".
- Seleccionamos en el mapa (o lo creamos si no existe) el nodo de la vía hasta donde vigila el radar (nodo de salida) y tocamos el botón "Añadir detrás del último miembro". A continuación le asignamos la función "to".
Hacer clic en el botón "Aceptar" para finalizar.
Subir los cambios a OSM. Para eso ir a Archivo > Subir datos. Recordá describir el cambio realizado, por ejemplo "Agrego radar fijo velocidad max 80 sobre Avenida General Paz."
Cómo añadir un radar con iD, paso a paso
Entrar a www.openstreetmap.org, posicionar el mapa donde se encuentra el radar y hacer clic en el botón Editar.
Crear un punto (nodo) donde realmente se encuentra la cámara, elegir el tipo "Punto" y en la sección "Todas las etiquetas" escribir la clave highway y el valor speed_camera como se ve en la imagen a continuación.
Crear una nueva relación para establecer los detalles del radar. Para eso, con el punto seleccionado, bajar el panel lateral hasta que se vea la sección "Todas las relaciones" y hacer clic en el botón [+], seleccionar del menú desplegable la primer opción "Nueva relación..." y a continuación seleccionar el botón "Relación".
Completar los detalles de la relación de la siguiente manera:
- Escribir el nombre de la relación (por ejemplo, "radar")
- Elegir el tipo "enforcement"
En la sección "Todas las etiquetas" agregar las siguientes:
- enforcement=maxspeed para indicar que se trata de una cámara de velocidad. Para cámaras de semáforo usar enforcement=traffic_signals.
- maxspeed=70 para indicar la velocidad máxima permitida en ese punto es 70 km/h.
En la sección "Todos los miembros" definir el rol "device" escribiendo a mano ese valor.
Seleccionar en el mapa (o lo creamos si no existe) el nodo de la vía desde donde se comenzará a alertar sobre el radar (nodo de entrada), elegir el tipo de elemento "Otro" y hacer clic en el botón [+] de la sección "Todas las relaciones". Elegir la relación que creamos en el punto 4 y asignar (escribir) el rol "from".
Seleccionar en el mapa (o lo creamos si no existe) el nodo de la vía hasta donde vigila el radar (nodo de entrada), elegir el tipo de elemento "Otro" y hacer clic en el botón [+] de la sección "Todas las relaciones". Elegir la relación que creamos en el punto 4 y asignar (escribir) el rol "to".
Finalmente hacer clic en el botón "Guardar" para subir los cambios a OSM. Recordá describir el cambio realizado, por ejemplo "Agrego radar fijo velocidad max 70 sobre Avenida 27 de Febrero."
dnes som pridal názov ku kostolu na Hájiku a tiež k bývalej kaplnke pridal som aj názvy ku krížovým cestám v Bitarovej a Lietavskej Závadke, ale nesprávne
Psychotherapie ist ein wissenschaftlich fundiertes Heilverfahren. Sie geht davon aus, dass Körper und Seele eine Einheit sind. PsychotherapeutInnen bauen eine heilsame Vertrauensbeziehung zu ihren PatientInnen auf und erarbeiten mit ihnen gemeinsam Lösungen und leiten Persönlichkeitsentwicklungsprozesse an. Dazu gehören auch die Diagnostik und ein Behandlungsplan. Psychodrama
Psychodrama ist eine in Österreich anerkannte Psychotherapierichtung, die von Jakob Levy Moreno in Wien und ab 1925 in den USA entwickelt wurde. Damit ist sie eine der ältesten Psychotherapieformen und versteht sich als sehr handlungsorientiert. Ursprünglich als Gruppenpsychotherapie gedacht, ist auch Arbeit im Einzelsetting und der Beratung möglich. Leistung
Wir informieren sie gerne per Telefon bzw. Mail über unsere Abrechnungsmodalitäten. Zum gegenseitigen Kennenlernen bieten wir ein kostenloses Erstgespräch. Terminabsagen bitten wir sie uns 24 Stunden vorher bekannt zu geben. Gespräche
Oft hilft es in belastenden Situationen, sich einer neutralen Person in einer vertrauenswürdigen Umgebung anvertrauen zu können. In Gesprächen versuchen wir, die aktuelle Situation zu erfassen und individuelle Hilfestellungen zu erarbeiten. Hilfe Wichtig ist es uns, unser Therapie-Angebot individuell zu gestalten und mit Patientinnen gemeinsam Lösungswege zu erarbeiten. Dies ist natürlich immer von der jeweiligen Diagnose bzw. Situation abhängig. Menschenbild
Das Psychodrama basiert auf dem humanistischen Menschenbild. Wir gehen davon aus, dass jeder Mensch eine ganzheitliche Einheit aus Körper, Geist und Seele mit einem konstruktiven Kern darstellt. Sein Bestreben ist das Leben selbstbestimmt zu leben, der Fokus dabei ist sinn- und zielgerichtet. Wir gehen von Gleichwertigkeit und –berechtigung aus und sind aufeinander eingestellt und angewiesen. Unsere kreativen Fähigkeiten und Kräfte entfalten sich durch die Interaktion mit dem anderen. „Am Du werden wir erst zum Ich.“ Zitat von Martin Buber Voraussetzung dafür ist vertrauensvolle Kommunikation, Einfühlung, authentisches Verhalten und gegenseitiges Annehmen. Psychotherapie Innsbruck
Olivio Di Biasio owner of Carrelage Mozaik which is licensed tilling company based in Greater Montreal Area, Canada. Olivio Di Biasioh having 25 years of experience in the field of tiling and providing their unmatched services in and around the area. They are very experienced and providing work all according to client’s requirements. They are providing work from simple to detail-oriented projects with new technology. They are always focusing on using new technology to provide best work to their client. Olivio Di Biasio is very nice, down to earth, and simple person who is always ready to help people.
The Pokemon Go mappers can strike anywhere, converting buildings into parks or pools of water. Check any changeset with 'Pokemon' in the changeset comment using osmcha.
My current mapping is on the eastern edge of Gedling. Gedling prides itself as a village, with an Anglican church that was established in 678 A.D. (the current church is a youngster at 1089 A.D.). Today, someone that lives in a bungalow at Field Close at the rear of the church was proudly pointing out to me the Peregrines that lodge in the niches of the spire. The tower is 90 feet high (27.4m) and the spire is yet another 90 feet, so that gives those dive-bombers an unrivalled perch for launching their attacks.
In spite of it's history, Gedling is now more or less just another suburb of Nottingham. It does, however, skirt the countryside and I'm mapping on the edge of that country, so here are some views.
Want any Horse Sh.., er, Manure?
Glebe Farm is an abandoned stables just outside of the residential spread that has crept up Lambley Lane. It has suffered decades of blight due to development, the latest of which (“Gedling Access Road”, or “GAR”) looks like it may go ahead. There were some horses in the East fields, a Detectorist scanning the West fields, and below is Milo the dog, an energetic bull terrier that belongs to the lady that looks after the horses. Milo leapt up at me & introduced my buff-coloured trousers to the farm speciality (there are twin piles of the stuff in abundance near the gate if your garden needs any).
Evidence of Strip Farming in Glebe Farm West Fields
A chap in Jessop Lane (the road formerly called “Hanging Lane”, since those due to be legally despatched were marched up that lane to the gallows up on top of the hill) pointed out that Glebe Farm’s West fields still show signs of the way that they were used hundreds of years ago as common-land strip-field farming. That evidence is all due to be lost under tarmac if the proposed developments go ahead (it all looks full-steam at the moment), but can currently still be seen in either Google Earth or Bing (the Bing-tile below has a capture date of 2011/10/1-2012/3/26; the construction at bottom right is a Western Power sub-station):
The Road Less Well Travelled
The next sight may not seem much, and indeed was shot only so that the embedded GPS in the photo could locate the position of the 30/40 mph signs, but it is, for me, also a classic view of English country-roads:–
Doggedly Well Ensconced
This next view of an English country house is also a side-product of the GAR & development, as the couple of acres of grass & trees between this house & Lambley Lane is now owned by the local Council & no building takes place until the future reveals itself:–
As a part of our data transparency efforts at Mapbox. We created osm-edit-report which helps anyone visualize our teams contribution to OSM.
Just to give a measure, the data team added 0.3 Million objects, 0.2 Million tags, and 3 thousand changesets last week.
This is how the numbers look:
Since this data is so huge to grasp at one go, we also have filters which help trim down data and focus on a particular group.
- Filter by users.
- Filter by tags
- Filter by BBox
The user table showcases all edits made by each user over the course of a week. The saturated blue boxes help emphasize huge edits and the chevrons compare today's edits with the weekly average.
Overall this tool helps us benchmark our mapping efforts and visualize out priority areas. Please don't forget to share your views on how to make our mapping efforts more transparent.
Desde el año 2011 se viene trabajando incansablemente en la implementación de una especialidad scout que permita a los jóvenes Scout estar siempre listos para utilizar herramientas útiles en casos de emergencia y que puede compartir sus datos, conocimientos para apoyar a los equipos de reacción en situaciones de crisis con información geográfica de la zona que lo necesite de manera remota o presencial. Nos enfocados principalmente en las ramas mayores, pero sin excluir ningún miembro de asociaciones Scout en el mundo. Inicialmente el programa pionero utilizó walking papers como recurso tecnológico de punta para de levantamiento de datos en campo, con el pasar del tiempo el cierre de la brecha tecnológica a facilitado aun más la especialidad con la utilización de las diferentes aplicaciones disponibles para los dispositivos móviles permite la consolidación de la idea. Los socios estratégicos que han creído en el potencial de la iniciativa en los jóvenes scouts, permitieron que después de muchos trabajos se cristalizara el pasado 27 de Noviembre del 2016 de forma oficial la entrega de la primera insignia a nivel mundial de la iniciativa Scout Mappers, gracias a la donación de la insignias por parte de @mapillary asi como tambien al entrenamiento y colaboración recibida desde la Fundación Openstreetmap Colombia FOSMCol
El Rover Scout Augusto Ibarra es el primer scout en portar orgullosamente su insignia, luego de haber completado sus primeros 5 kms.
También se a logrado participar activamente de la Mapatón de vías terciarias en el municipio de Norte de Santander donde la iniciativa logro un tercer puesto, dentro de la convocatoria de Youthmappers
Se realizan entrenamientos básicos con mapillary con los jóvenes scout en la ciudad de Popayán, donde se crea la iniciativa.
Y también se realizo un entrenamiento a jovenes scout de Guapi quienes participarón activamente del proyecto de generación de datos geográficos libres para el control de la Malaria, participando de la #MapatónXGuapi
Todo inicia hace mucho tiempo atrás, en 2011, cuando los jóvenes Rover del Grupo 9 San Jorge, rodeábamos un mapa impreso desde el desaparecido walking papers para entender y contribuir a openstreetmap la "wikipedia de los mapas"
A new version of Potlatch 2 with several improvements and bugfixes:
- 'New-style' multipolygons are supported, where the tags are placed on the relation rather than the outer way. When you edit such a multipolygon, look at the bottom of the tag editor; you'll see that it's displaying the relation tags rather than the way. If you do want to change the tags on the way, you can choose that from the little dropdown menu there.
- Pop-up dialogue boxes are now generally resizable.
- In the Advanced tag view, long tag values now wrap onto multiple lines.
- The background menu is now usable on smaller screens.
- A 'Clear all' button on the Bookmarks menu.
- Shift-drag to zoom into a particular area; shift-click + or - to zoom three levels at a time; and you can now zoom out beyond zoom level 14, in which case no data will be displayed or loaded.
- Shift-< and > jump 10 nodes at a time along a way.
- Code now compiles with Apache Flex as well as with (older) Adobe Flex.
- Plus a bunch of other small fixes.
Potlatch 2 is somewhere between 'active development' and 'maintenance mode': there's no massive new features that I'm planning, but I intend to keep making small improvements to it along these lines, plus extra features as and when I'm doing some mapping and figure out a way to make it easier or quicker to use. OSM is lucky to have such an excellent default editor in iD, which gives P2 the freedom to develop as an efficient and comfortable editor for those who like its way of doing things.
Vandalism on UP campus
After checking some data of our campus I spot odd additions to the campus map. a User edited some information regarding the name and added some shops that did not exist. I contacted them and asked to revert changes made. Will monitor and follow the steps to correct data if not corrected.