[talk-ph] Fwd: [OSM-talk] WeeklyOSM 306

2016-06-03 Per discussione Eugene Alvin Villar
-- Forwarded message --
From: Jinal Foflia 
Date: Fri, Jun 3, 2016 at 4:49 PM
Subject: [OSM-talk] WeeklyOSM 306
To: t...@openstreetmap.org


The weekly round-up of OSM news, issue #306, is now available online in
English, giving as always a summary of all things happening in the
OpenStreetMap world:

http://www.weeklyosm.eu/archives/7593

*Among others:*


   - Love Mapillary? Read in more for detailed article about using
   Mapillary for mapping in OpenStreetMap with JOSM.
   - Mapbox announces that their map related tools are now free for
   humanitarian response.
   - The State of the Map Working Group (WG SotM) published a paper to the
   topic corporate membership. Source: OSMF-talk
   - Rome based architect and designer Mateo Prati showcases his 3D views
   of Manhattan made with Blender and OpenStreetMap data.
   - Try out the knife-tool for JOSM, which makes splitting ways at an
   arbitrary point a breeze.


Cheers,

Jinal Foflia 

___
talk mailing list
t...@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
___
talk-ph mailing list
talk-ph@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ph


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione Philippe Verdy
Peut-être que certains gros clients indistriels gèrent eux-mêmes les postes
de distribution sur leurs sites (et tout le filaire aval), et se branchent
alors ailleurs en amont sur d'autres réseaux de distribution: c'est
peut-être EDF qui les a construits à l'origine, ERDF n'a sans doute même
jamais été concerné par ces postes si la cession a eu lieu avant.


Le 4 juin 2016 à 00:42,  a écrit :

>
>
> Le 2016-06-03 à 22:53, François Lacombe - fl.infosrese...@gmail.com a
> écrit :
>
> Mais quand le terrain va plus vite que les corrections, il faut changer de
> braquet.
>
> +1 et il vaut mieux tout faire d'un coup quand c'est simple plutôt
> qu'attendre que la communauté commence et qu'on arrive à une situation
> mixte (ERDF+Enedis).
> Au fait Enedis comme énergie distribution, ils comptent se diversifier ?
> Acheter GRDF ???
>
> Sur les arrêts : tu mets quoi comme opérateur ? Celui qui gère l'abribus
> (Decaux?) ou la compagnie de bus (une filiale de Keolis probablement) ?
> Effectivement j'aurais tendance à ne pas mettre d'opérateur pour un
> abribus.
> Par contre pour un transfo (power=substation) je ne veux pas récupérer les
> 85 % du réseau BT français pour voir qu'il est concédé à Enedis (relation
> qui n'existe d'ailleurs pas... encore).
>
> http://mc.bbbike.org/mc/?lon=-3.413426=47.745501=18=2=osmfr=mapbox-hybrid=building:yes%3Cbr%3Eoperator:EDF%3Cbr%3Epower:substation%3Cbr%3Eref:MLTVULCA
>
> C'est étrange cet objet, parce que dans cette zone en particulier il y
> a l'utilisateur Libre à Quimperlé qui pousse des infos exhaustives sur
> ces posteshttps://www.openstreetmap.org/way/89855678#map=19/47.86499/-3.54835
>
> La ref MLTVULCA correspond à quoi ?
> Ca pourrait être une régie locale ?
>
> non, c'est le "nom" du poste (le "texte" affiché sur le poste), c'est
> d'ailleurs Libre à Quimperlé qui a entré la version initiale (et la ref
> comme name).
>
> Maintenant je connais un transformateur qui n'appartient pas à ERDF mais qui
> est un poste client marqué EDF si je n'abuse (mais qui n'appartient pas à
> EDF et n'est pas opéré par EDF non plus).
>
> On peut voir ?
>
> François
>
> Pas encore sous OSM, je ferai une photo à l'occasion.
>
> Jean-Yvon
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk-fr] rendus OSM des villes

2016-06-03 Per discussione Philippe Verdy
Note: au niveau 6 il faut du temps pour la mise à jour. Ici, Saint-Avé a
été incorrectement tagué avec un statut plus important ou au moins aussi
important que Vannes, mais c'est corrigé depuis un moment.

Malheureusement avant que le rendu soit mis à jour... (/dirty ne fonctionne
pas au niveau 6, il est bloqué (avec un message d'erreur envoyé retourné en
HTTP au lieu du HTTPS, donc qui merde et ne s'affiche pas, à cause d'un
problème de config sur le serveur de rendu FR)... il faut attendre un mois
ou plus pour un raffraichissement à ce niveau)

Le 4 juin 2016 à 00:48,  a écrit :

> C'est vrai que le rendu OSM-FR est nettement moins mauvais mais lui aussi
> affiche Saint-Avé :
>
> http://b.tile.openstreetmap.fr/osmfr/6/31/22.png
>
> [image: http://b.tile.openstreetmap.fr/osmfr/6/31/22.png]
>
>
> Je parle bien de niveaux auxquels on s'attend à voir des villes par des
> quartiers (ici niveau 6).
>
> Le 2016-06-04 à 00:30, Philippe Verdy - verd...@wanadoo.fr a écrit :
>
> Le rendu Mapnik par défauit d'OSM ne fait aucun classement de priorité des
> libellés. Ou si classement il y a c'est sur des critères complètement
> stupides qui cachent l'essentiel presque partout.
>
> Note: passé un certain niveau de zoom, les villes n'apparaisent plus du
> tout, c'est normal de voir alors les quartiers.
>
> Mais tout ça n'a jamais été correctement réglé sur ce rendu "merdique" (le
> mot est faible).
>
> Comparez avec le rendu FR, ou les autres rendus (Mapquest,... ), c'est
> nettement plus cohérent. Mais les développeurs de la fondation n'ont jamasi
> pris le temps de corriger ça dans leur rendu et se sont concentrés d'abord
> sur des détails avant l'essentiel, qui est ce qui pourtant est le plus
> visible. Cela ne rend pas service du tout à OSM et incite même bien des
> sites à ne PAS utiliser OSM mais encore préférer Google Maps !
>
>
> Le 3 juin 2016 à 21:17,  a écrit :
>
>> Sur la couche transport, c'est même un quartier de Vannes qui se
>> substitue à Vannes :
>>
>> http://www.openstreetmap.org/way/213906166#map=9/47.6575/-2.7383=T
>>
>> Vous voyez quelque chose d'incorrect dans les données ou ce sont les
>> rendus qui ne rendent pas très bien les agglomérations ?
>>
>> Jean-Yvon
>>
>> Le 2016-06-02 à 23:37, osm.sanspourr...@spamgourmet.com a écrit :
>>
>> Vannes  est la préfecture
>> du Morbihan :
>> admin_level
>>  8
>> 
>> capital  6
>> name  Vannes
>> population 
>> 52515
>>
>> Le nœud Vannes  lui-même
>> comporte aussi capital=6 et la population.
>>
>> Un peu au nord se trouve la petite ville de Saint-Avé
>>  :
>> admin_level
>>  8
>> 
>> name 
>> Saint-Avé
>> population 
>> 10385
>> Certains rendus ne semblent utiliser ni le capital (ici 6=préfecture) ni
>> la population mais juste place=town avec affichage de haut à gauche en bas
>> à droite.
>> Résultat : OSM-FR affiche Saint-Avé simple ville dans la banlieue de
>> Vannes, plutôt que Vannes 5 fois plus important et préfecture du Morbihan.
>> Il n'est pas possible d'organiser le tracé par coalesce(capital,15)
>> croissant puis par coalesce(population,0) décroissant ?
>>
>> Jean-Yvon
>>
>>
>> ___
>> Talk-fr mailing 
>> listTalk-fr@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-fr
>>
>>
>>
>> ___
>> Talk-fr mailing list
>> Talk-fr@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-fr
>>
>>
>
>
> ___
> Talk-fr mailing 
> listTalk-fr@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-fr
>
>
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Kevin Kenny
OK, 'residential' if it looks like 'subdivision', 'unclassified'
otherwise (as long as it's drivable in, say, my daughter's car rather
than my 4-wheeler). Got it.

I suspect that 'residential'/'unclassified' right now is almost a
difference without a distinction. I suppose that 'residential' might
be a weak indication to a router to avoid the route, but the
consequences of getting it wrong don't appear to be terribly severe.
Which is a relief.

On Fri, Jun 3, 2016 at 6:56 PM, Richard Welty  wrote:
> On 6/3/16 5:13 PM, Kevin Kenny wrote:
>> Can someone review for me the 'rural residential' problem?
> the short version is that we are supposed to use residential
> in truly residential areas and unclassified for generic town
> roads. in tiger, there is no distinction between the two and so
> everything was imported as residential.
>
> i leave it residential in areas that have a subdivision vibe
> going - multiple closely spaced houses or comparatively small
> building lots, but change it to unclassified if it's just a bunch
> of homes that have been built along old farm roads over the
> years. the section of the road i live on is slightly borderline,
> or would be if the lots were smaller, but most of them are 4 acres
> or more.
>
> richard
>
> --
> rwe...@averillpark.net
>  Averill Park Networking - GIS & IT Consulting
>  OpenStreetMap - PostgreSQL - Linux
>  Java - Web Applications - Search
>
>
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Richard Welty
On 6/3/16 5:13 PM, Kevin Kenny wrote:
> Can someone review for me the 'rural residential' problem?
the short version is that we are supposed to use residential
in truly residential areas and unclassified for generic town
roads. in tiger, there is no distinction between the two and so
everything was imported as residential.

i leave it residential in areas that have a subdivision vibe
going - multiple closely spaced houses or comparatively small
building lots, but change it to unclassified if it's just a bunch
of homes that have been built along old farm roads over the
years. the section of the road i live on is slightly borderline,
or would be if the lots were smaller, but most of them are 4 acres
or more.

richard

-- 
rwe...@averillpark.net
 Averill Park Networking - GIS & IT Consulting
 OpenStreetMap - PostgreSQL - Linux
 Java - Web Applications - Search




signature.asc
Description: OpenPGP digital signature
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [OSM-talk-fr] rendus OSM des villes

2016-06-03 Per discussione osm . sanspourriel
C'est vrai que le rendu OSM-FR est nettement moins mauvais mais lui 
aussi affiche Saint-Avé :


http://b.tile.openstreetmap.fr/osmfr/6/31/22.png

http://b.tile.openstreetmap.fr/osmfr/6/31/22.png


Je parle bien de niveaux auxquels on s'attend à voir des villes par des 
quartiers (ici niveau 6).



Le 2016-06-04 à 00:30, Philippe Verdy - verd...@wanadoo.fr a écrit :
Le rendu Mapnik par défauit d'OSM ne fait aucun classement de priorité 
des libellés. Ou si classement il y a c'est sur des critères 
complètement stupides qui cachent l'essentiel presque partout.


Note: passé un certain niveau de zoom, les villes n'apparaisent plus 
du tout, c'est normal de voir alors les quartiers.


Mais tout ça n'a jamais été correctement réglé sur ce rendu "merdique" 
(le mot est faible).


Comparez avec le rendu FR, ou les autres rendus (Mapquest,... ), c'est 
nettement plus cohérent. Mais les développeurs de la fondation n'ont 
jamasi pris le temps de corriger ça dans leur rendu et se sont 
concentrés d'abord sur des détails avant l'essentiel, qui est ce qui 
pourtant est le plus visible. Cela ne rend pas service du tout à OSM 
et incite même bien des sites à ne PAS utiliser OSM mais encore 
préférer Google Maps !



Le 3 juin 2016 à 21:17, > a écrit :


Sur la couche transport, c'est même un quartier de Vannes qui se
substitue à Vannes :

http://www.openstreetmap.org/way/213906166#map=9/47.6575/-2.7383=T

Vous voyez quelque chose d'incorrect dans les données ou ce sont
les rendus qui ne rendent pas très bien les agglomérations ?

Jean-Yvon


Le 2016-06-02 à 23:37, osm.sanspourr...@spamgourmet.com
 a écrit :


Vannes  est la
préfecture du Morbihan :

admin_level

8

capital
   6
name 
Vannes
population
52515

Le nœud Vannes 
lui-même comporte aussi capital=6 et la population.

Un peu au nord se trouve la petite ville de Saint-Avé
 :

admin_level

8

name 
Saint-Avé
population

10385


Certains rendus ne semblent utiliser ni le capital (ici
6=préfecture) ni la population mais juste place=town avec
affichage de haut à gauche en bas à droite.
Résultat : OSM-FR affiche Saint-Avé simple ville dans la banlieue
de Vannes, plutôt que Vannes 5 fois plus important et préfecture
du Morbihan.
Il n'est pas possible d'organiser le tracé par
coalesce(capital,15)  croissant puis par coalesce(population,0)
décroissant ?

Jean-Yvon


___
Talk-fr mailing list
Talk-fr@openstreetmap.org 
https://lists.openstreetmap.org/listinfo/talk-fr



___
Talk-fr mailing list
Talk-fr@openstreetmap.org 
https://lists.openstreetmap.org/listinfo/talk-fr




___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione osm . sanspourriel



Le 2016-06-03 à 22:53, François Lacombe - fl.infosrese...@gmail.com a 
écrit :
Mais quand le terrain va plus vite que les corrections, il faut 
changer de braquet.
+1 et il vaut mieux tout faire d'un coup quand c'est simple plutôt 
qu'attendre que la communauté commence et qu'on arrive à une situation 
mixte (ERDF+Enedis).
Au fait Enedis comme énergie distribution, ils comptent se diversifier ? 
Acheter GRDF ???


Sur les arrêts : tu mets quoi comme opérateur ? Celui qui gère l'abribus 
(Decaux?) ou la compagnie de bus (une filiale de Keolis probablement) ?

Effectivement j'aurais tendance à ne pas mettre d'opérateur pour un abribus.
Par contre pour un transfo (power=substation) je ne veux pas récupérer 
les 85 % du réseau BT français pour voir qu'il est concédé à Enedis 
(relation qui n'existe d'ailleurs pas... encore).

http://mc.bbbike.org/mc/?lon=-3.413426=47.745501=18=2=osmfr=mapbox-hybrid=building:yes%3Cbr%3Eoperator:EDF%3Cbr%3Epower:substation%3Cbr%3Eref:MLTVULCA

C'est étrange cet objet, parce que dans cette zone en particulier il y
a l'utilisateur Libre à Quimperlé qui pousse des infos exhaustives sur
ces postes
https://www.openstreetmap.org/way/89855678#map=19/47.86499/-3.54835

La ref MLTVULCA correspond à quoi ?
Ca pourrait être une régie locale ?
non, c'est le "nom" du poste (le "texte" affiché sur le poste), c'est 
d'ailleurs Libre à Quimperlé qui a entré la version initiale (et la ref 
comme name).

Maintenant je connais un transformateur qui n'appartient pas à ERDF mais qui
est un poste client marqué EDF si je n'abuse (mais qui n'appartient pas à
EDF et n'est pas opéré par EDF non plus).
On peut voir ?

François

Pas encore sous OSM, je ferai une photo à l'occasion.

Jean-Yvon
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk-fr] rendus OSM des villes

2016-06-03 Per discussione Philippe Verdy
Le rendu Mapnik par défauit d'OSM ne fait aucun classement de priorité des
libellés. Ou si classement il y a c'est sur des critères complètement
stupides qui cachent l'essentiel presque partout.

Note: passé un certain niveau de zoom, les villes n'apparaisent plus du
tout, c'est normal de voir alors les quartiers.

Mais tout ça n'a jamais été correctement réglé sur ce rendu "merdique" (le
mot est faible).

Comparez avec le rendu FR, ou les autres rendus (Mapquest,... ), c'est
nettement plus cohérent. Mais les développeurs de la fondation n'ont jamasi
pris le temps de corriger ça dans leur rendu et se sont concentrés d'abord
sur des détails avant l'essentiel, qui est ce qui pourtant est le plus
visible. Cela ne rend pas service du tout à OSM et incite même bien des
sites à ne PAS utiliser OSM mais encore préférer Google Maps !


Le 3 juin 2016 à 21:17,  a écrit :

> Sur la couche transport, c'est même un quartier de Vannes qui se substitue
> à Vannes :
>
> 
> http://www.openstreetmap.org/way/213906166#map=9/47.6575/-2.7383=T
>
> Vous voyez quelque chose d'incorrect dans les données ou ce sont les
> rendus qui ne rendent pas très bien les agglomérations ?
>
> Jean-Yvon
>
> Le 2016-06-02 à 23:37, osm.sanspourr...@spamgourmet.com a écrit :
>
> Vannes  est la préfecture
> du Morbihan :
> admin_level
>  8
> 
> capital  6
> name  Vannes
> population 
> 52515
>
> Le nœud Vannes  lui-même
> comporte aussi capital=6 et la population.
>
> Un peu au nord se trouve la petite ville de Saint-Avé
>  :
> admin_level
>  8
> 
> name  Saint-Avé
> population 
> 10385
> Certains rendus ne semblent utiliser ni le capital (ici 6=préfecture) ni
> la population mais juste place=town avec affichage de haut à gauche en bas
> à droite.
> Résultat : OSM-FR affiche Saint-Avé simple ville dans la banlieue de
> Vannes, plutôt que Vannes 5 fois plus important et préfecture du Morbihan.
> Il n'est pas possible d'organiser le tracé par coalesce(capital,15)
> croissant puis par coalesce(population,0) décroissant ?
>
> Jean-Yvon
>
>
> ___
> Talk-fr mailing 
> listTalk-fr@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-fr
>
>
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione Éric Gillet
Je suis 100% pour l'uniformisation des operator !

Le 3 juin 2016 à 19:28, François Lacombe  a
écrit :

> Bonjour la liste,
>
> comme vous l'avez peut-être vu ces derniers jours, l'opérateur de
> distribution électrique ERDF a changé de nom pour Enedis.
> RFF l'a précédé en 2015 pour donner naissance à SNCF Réseau, pour ne
> citer qu'un cas probablement parmi tant d'autres avec la fusion des
> communes, fusion des régions, etc...
>
> Pourtant dans OSM :
> operator=RFF, 3349 objets
> operator=SNCF Réseau, 3205 objets
> operator=ERDF, 25768 objets
> operator=Enedis, 0 objets
>
> Comme on peut le voir, les objets attribués à RFF migrent
> difficilement vers la nouvelle valeur (si tant est que SNCF Réseau
> soit la valeur à appliquer. La confusion avec Gares & connexion est
> facile et il en va de même avec les autres filiales de la SNCF).
>
> Ça me semble être un problème, et nous avons tout intérêt à avoir un
> ensemble de données cohérentes.
> Il y a un ticket ouvert chez JOSM :
> https://josm.openstreetmap.de/ticket/12914
>
> J'ai déjà commencé à mettre à jour le wiki, mais cela ne suffira
> pourtant pas à obtenir un ensemble cohérent avant un certain nombre
> d'années.
>
> Quid de proposer au DWG de faire une migration en masse ?
> Plutôt facile à réaliser : overpass => query sur operator=ERDF => JSOM
> ctrl+A => operator=Enedis => Upload
>
> Le principal enjeu est l'information de la communauté et la mise à
> jour des scripts de consommation.
>
> A+
>
> François
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Steven Johnson
I typically correct the geometry and delete the 'TIGER:reviewed=no', but
leave the rest because I'm superstitious...

-- SEJ
-- twitter: @geomantic
-- skype: sejohnson8

A serious and good philosophical work could be written consisting entirely
of jokes. --*Ludwig Wittgenstein*

On Fri, Jun 3, 2016 at 5:45 PM, Russell Deffner 
wrote:

> Hi Kevin, I'll try to add some context. Here's a neat use for the new OSM
> Analytics tool developed by HOT:
> http://osm-analytics.org/#/compare/polygon:~lwbS}lpoFipQYwJawGbnQxD/2008...now/highways
>
> If you don't see 'blue' roads, zoom in until you do and then swipe
> left/right - you can see the original TIGER roads were 'relatively
> accurate', i.e. you can follow X road, turn left on Y, etc, etc. but
> position and geometry is 'horrible'. And yes, there's many 'ghost roads',
> etc. which maybe once was a track that the power company or someone used to
> 'get back into the woods/cut-across/etc.' but are not 'roads' as the
> average reasonable person would consider. Definitely take a look at
> Wandcrest Park for a 'what the heck happened there' that took a drive back
> in there to figure out.
>
> FYI, of course anyone is welcome to critique (and several have) my 'home
> area'; i.e. I realized from day 1 I would probably be one of, if not the
> only, OSM-er in Park County, Colorado:
> http://www.openstreetmap.org/relation/439376 - I am basically working it
> from north to south, but as Wolfgang said - some of the things/ways I
> mapped early on, I do very differently now and it will forever be a work in
> progress. One of those things was my first focus was on cleaning up road
> geometry; so no, I didn't add surface or smoothness, etc. tags. Around here
> I can show you a paved road that you might not want to drive your
> high-clearance vehicle down, and a dirt road that people drive their
> low-clearance 'race cars' down at high speeds. Point being, it's not a
> 'simple' equation to show 'quality' of roads.
>
> =Russ
>
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Russell Deffner
Hi Kevin, I'll try to add some context. Here's a neat use for the new OSM 
Analytics tool developed by HOT: 
http://osm-analytics.org/#/compare/polygon:~lwbS}lpoFipQYwJawGbnQxD/2008...now/highways
  

If you don't see 'blue' roads, zoom in until you do and then swipe left/right - 
you can see the original TIGER roads were 'relatively accurate', i.e. you can 
follow X road, turn left on Y, etc, etc. but position and geometry is 
'horrible'. And yes, there's many 'ghost roads', etc. which maybe once was a 
track that the power company or someone used to 'get back into the 
woods/cut-across/etc.' but are not 'roads' as the average reasonable person 
would consider. Definitely take a look at Wandcrest Park for a 'what the heck 
happened there' that took a drive back in there to figure out.

FYI, of course anyone is welcome to critique (and several have) my 'home area'; 
i.e. I realized from day 1 I would probably be one of, if not the only, OSM-er 
in Park County, Colorado: http://www.openstreetmap.org/relation/439376 - I am 
basically working it from north to south, but as Wolfgang said - some of the 
things/ways I mapped early on, I do very differently now and it will forever be 
a work in progress. One of those things was my first focus was on cleaning up 
road geometry; so no, I didn't add surface or smoothness, etc. tags. Around 
here I can show you a paved road that you might not want to drive your 
high-clearance vehicle down, and a dirt road that people drive their 
low-clearance 'race cars' down at high speeds. Point being, it's not a 'simple' 
equation to show 'quality' of roads. 

=Russ 


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione DH

Le 03/06/2016 22:53, François Lacombe a écrit :

Bonsoir Denis

Le 3 juin 2016 à 21:20, DH  a écrit :

Pour les RFF, je les dégomme dès que j'en vois façon
http://www.toupty.com/jeuasteroids.html (ça ne nous rajeunit pas ;-)
note : tagger operator pour chaque tronçon ferroviaire n'est pas l'idée la
plus productive. La relation c'est bien pour cela ; les relations, c'est
bien (point).

C'est bien ce qui est de mise la plupart du temps, à chaque fois qu'on
vois une "erreur", on la corrige.
Mais quand le terrain va plus vite que les corrections, il faut
changer de braquet. Sinon on va revenir sans cesse sur les mêmes
choses.

Pareil dans les transports : quand un opérateur de réseau change en
ville, question de main d’œuvre, mais attendre que tout les arrêts
soient visités... c'est long.

Sur le point de vue de la relation, pourquoi pas
Ça oblige cependant à visiter toutes les relations dont fait partie un
objet donné pour avoir l'info :)


Justement l'idée c'est d'avoir, à terme, une super relation "Réseau 
Ferré National" avec operator=SNCF Réseau (1), dedans toutes les 
relations de lignes composées des relations de voies, composées des 
tronçons, les relations de gares (quoique ça va être rapidement le 
bordel entre RATP, Gare & Connexion et Réseau suivant le contenu de la 
relation), etc.
A chaque niveau ses particularités propres. Cela n'a pas de sens de 
mettre un gauge=1435 ou electrified=no sur le moindre tronçon qui 
appartient à un ensemble homogène. Après il y a les should et les must.
Je comprend que la majorité des contributeurs n'est pas forcément à 
l'aise avec les relations ; il y a un long travail de pédagogie à faire 
et d'initialisation (peur de la page blanche)
Je découvre peu à peu l'ampleur de la diversité des pratiques de matière 
de cartographie ferroviaire. C'est formateur pour écrire de la doc (de 
l'ad hoc et pas de l'haddock).


1. je commence par les versions territoriales (enfin la plus proche ;-): 
http://www.openstreetmap.org/relation/6250218


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Kevin Kenny
Can someone review for me the 'rural residential' problem?

I haven't done a lot of editing away of TIGER tags, although I've
wanted to - a lot of the areas where I've been mapping have had
virtually no TIGER review whatsoever and the garish overlays in JOSM
are annoying. Some of the areas I work on are densely wooded, and the
roads aren't always traceable on aerial photos, so MapRoulette won't
help, but I do gather GPS tracks and check the alignment. A lot of the
TIGER roads are simply hallucinations - roads in places where no road
could exist or ever have existed. The best I ever found went right up
the fall line of a 2000 foot cliff. I think whoever digitized for
TIGER might have had a particular obsolete [1903] USGS topo that
showed a dashed line for a climbing route that once existed in there.
I delete hallucinatory highways..

I haven't worried much about the 'highway=' classification, except
that I downgrade to 'track' if it looks as if I'd want a high-profile
vehicle in anything but the best weather, or to 'path' if you're not
allowed to drive on it.

I suppose that I'm breaking some rule that will screw up someone's
routing?  If so, I'm sorry. Chalk it up to ignorance, and well, I
haven't done very many of these. (I mostly edit other things than
TIGER cleanup.) What should I be looking for with 'residential', and
what is the alternative tagging if I don't find it?

On Fri, Jun 3, 2016 at 12:24 PM, Peter Dobratz  wrote:
> JOSM does automatically discard some TIGER:* tags.  There's a list of keys
> in the tags.discardable JOSM preference item.  Among the list of tags that
> JOSM automatically deletes are:
> tiger:source
> tiger:separated
> tiger:tlid
> tiger:upload_uuid
>
> These tags are hidden from the editor so you don't normally see them.  They
> are automatically removed from any objects that you modify.  You may notice
> them if you are looking at the history of an object in JOSM.
>
> That being said, I delete the other tiger:* from roads as I am editing them.
> Usually, I am verifying addr:* tags of things along the road and checking
> that the addr:street matches the name of the road.  I also often remove the
> name_1, name_2, etc tags that came from the TIGER import.  Where
> appropriate, I retain them in alt_name or old_name.
>
> Peter
>
> On Fri, Jun 3, 2016 at 8:51 AM, Steve Friedl  wrote:
>>
>> Ø  Unless something changed, I think both Potlatch and JOSM will remove
>> the ‘junk’ tags from TIGER if you delete the reviewed=no
>>
>>
>>
>> I’ve deleted thousands of tiger:reviewed tags (after proper review) and
>> have never seen JOSM take anything else along for the ride.  JOSM *does*
>> remove the yellow glow around ways once you remove tiger:reviewed, but
>> that’s all I’ve seen.
>>
>>
>>
>> I have very much wanted to dump the tags that have no obvious use for OSM,
>> but had no idea if somebody else, somewhere, might use them: probably not,
>> but it didn’t feel like it was my call to make. I’d love for there to be a
>> consensus on this.
>>
>>
>>
>> So the only things I’ve removed are tiger:reviewed, plus spurious
>> additional tags that duplicate existing ones (tiger:zip_left_1 when it’s the
>> same as tiger:zip_left).
>>
>>
>>
>> Steve
>>
>>
>>
>> From: Russell Deffner [mailto:russdeff...@gmail.com]
>> Sent: Friday, June 03, 2016 8:45 AM
>> To: 'Adam Franco' ; talk-us@openstreetmap.org
>>
>>
>> Subject: Re: [Talk-us] Best practices for dealing with old TIGER tags?
>>
>>
>>
>> Oops, sorry Adam, replied directly to you versus the list; here’s the
>> message:
>>
>>
>>
>> My thoughts:
>>
>>
>>
>> Unless something changed, I think both Potlatch and JOSM will remove the
>> ‘junk’ tags from TIGER if you delete the reviewed=no. Maybe this is not the
>> case with iD?
>>
>>
>>
>> As far as classification; please note that it is not about whether the
>> road is rural or not; it’s the function – there have been people who started
>> changing all ‘dirt roads’ to track around me in rural Colorado – this is NOT
>> correct. Most of the ‘dirt roads’ around here are 100% verifiably
>> “residential”. So please don’t encourage mass changing of classification
>> based on anything but function of the roadway.
>>
>>
>>
>> =Russ
>>
>>
>>
>> From: Adam Franco [mailto:adamfra...@gmail.com]
>> Sent: Friday, June 03, 2016 9:28 AM
>> To: talk-us@openstreetmap.org Openstreetmap
>> Subject: Re: [Talk-us] Best practices for dealing with old TIGER tags?
>>
>>
>>
>> Just some more feedback on the idea of a TIGER rural-residential challenge
>> based on cleanup I've done throughout much of Vermont:
>>
>> Most of the roads in rural areas should have their highway= changed to
>> something other than residential. (well known issue).
>> Surface tags would be GREAT! I've added surface tags to most roads in
>> Vermont, but have not quite gotten to all of them yet.
>> At least here in Vermont, "private road" means that the ownership and
>> maintenance of the road is 

[Talk-at] renaturierung traisen / mündung donau

2016-06-03 Per discussione Rainer Fügenstein
Hi,

ich   war   auf   der  heutigen  radtour  sehr  überascht,  daß  sich
im  bereich  der  mündung  der  traisen  ((wahrscheinlich  im zuge der
renaturierung) in die donau viel geändert hat:

- vom alten treppelweg blieb auf einem stück nur mehr eine insel übrig
- es gibt viel mehr wasserflächen
- die führung des treppelweges / EV6 hat sich dadurch geändert.
- detto die bereits erfassten waldwege

ich  habe  mal  das,  was  ich  auf  die  schnelle  aufnehmen  konnte,
eingetragen, hauptsächlich den neuen abschnitt des treppelweges.

-  nicht  wundern, daß eine brücke mitten im wald eingetragen ist, dort
ist jetzt wasser
-  die neuen wasserflächen sind (erwartungsgemäß) weder auf bing, noch
auf basemap, noch auf geoimage.at luftbildern ersichtlich.

falls also jemand eine idee hat, wie man die aufnehmen kann ...

mfg

https://www.openstreetmap.org/changeset/39787314

  

-- 
Best regards,
 Rainer  mailto:r...@oudeis.org


___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione François Lacombe
Bonsoir Denis

Le 3 juin 2016 à 21:20, DH  a écrit :
>
> Pour les RFF, je les dégomme dès que j'en vois façon
> http://www.toupty.com/jeuasteroids.html (ça ne nous rajeunit pas ;-)
> note : tagger operator pour chaque tronçon ferroviaire n'est pas l'idée la
> plus productive. La relation c'est bien pour cela ; les relations, c'est
> bien (point).

C'est bien ce qui est de mise la plupart du temps, à chaque fois qu'on
vois une "erreur", on la corrige.
Mais quand le terrain va plus vite que les corrections, il faut
changer de braquet. Sinon on va revenir sans cesse sur les mêmes
choses.

Pareil dans les transports : quand un opérateur de réseau change en
ville, question de main d’œuvre, mais attendre que tout les arrêts
soient visités... c'est long.

Sur le point de vue de la relation, pourquoi pas
Ça oblige cependant à visiter toutes les relations dont fait partie un
objet donné pour avoir l'info :)


Le 3 juin 2016 à 21:48,   a écrit :
>
> Ce sont bien des transformateurs HTA (building=yes + power=substation) avec
> operator=EDF. Ceux-ci ne devraient pas, sauf erreur ou exception, être
> attribués à EDF.
>
> Or il y en a 1484+345=1829 objets ainsi décrits
> http://overpass-turbo.eu/s/gC1
>
> Ceux avec operator=ERDF sont au nombre de 4935+114=5049, soit 27 % de
> mauvais operator (OK, 100% depuis le 1er juin).

Ok c'est ca :)

Il y a aussi les poteaux, les lignes, les postes sources, les
isolateurs, les portiques
http://overpass-turbo.eu/s/gC8

>
> http://mc.bbbike.org/mc/?lon=-3.413426=47.745501=18=2=osmfr=mapbox-hybrid=building:yes%3Cbr%3Eoperator:EDF%3Cbr%3Epower:substation%3Cbr%3Eref:MLTVULCA

C'est étrange cet objet, parce que dans cette zone en particulier il y
a l'utilisateur Libre à Quimperlé qui pousse des infos exhaustives sur
ces postes
https://www.openstreetmap.org/way/89855678#map=19/47.86499/-3.54835

La ref MLTVULCA correspond à quoi ?
Ca pourrait être une régie locale ?

>
> Maintenant je connais un transformateur qui n'appartient pas à ERDF mais qui
> est un poste client marqué EDF si je n'abuse (mais qui n'appartient pas à
> EDF et n'est pas opéré par EDF non plus).

On peut voir ?

François

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-us] Western TIGER Roads

2016-06-03 Per discussione Wolfgang Zenker
* Alan Bragg  [160603 21:30]:
> [..]
> Is there any other resource? Maybe some links to well tagged areas.

I have almost finished reviewing the part of Stillwater County, MT
south of the Yellowstone River (residential roads in Absarokee are not
finished yet, and also a little bit of Reed Point).

https://www.openstreetmap.org/#map=14/45.5866/-109.3726 

So far I think my tagging there is ok (but of course I might be wrong:
when I come across areas that I worked on 5 years ago I usually find
quite some things that I do differently today; probably five years
from now that will happen in areas that I worked on now).

Wolfgang

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-at] Wiener Stammtisch?

2016-06-03 Per discussione Andreas

Hallo,

ich muss mich leider auch nachträglich fürn Stammtisch entschuldigen. 
Hatte einen Bandausriss am Linken Fuß und konnte daher nicht das Haus 
verlassen.


würde mich aber auch freuen, wenn es wieder mal einen Stammtisch geben 
würde. Waren immer recht interessante Gespräche und Infos zu erfahren.


lg Andreas

Am 2016-06-02 um 19:53 schrieb Markus Mayr:

Hallo!

Ich bin zur Zeit leider einige Zeit nicht mal in Wien, möchte mich aber
bald wieder mehr um den Stammtisch kümmern. :-)

lg, Markus


Am 2016-06-02 um 16:02 schrieb Robert Kaiser:

Hallo,

Michael Reichert schrieb:

Am 2. Juni 2016 13:57:17 MESZ, schrieb Robert Kaiser :

An sich wär's heute wieder Zeit für einen Wiener Stammtisch, aber ich
hab in den letzten Monaten nichts mehr gehört, ob die jetzt noch
stattfinden oder nicht.
Ist heute einer? Wenn nicht, warum und wann machen wir wieder einen?


Ich komme zwar nicht aus Wien und war noch nie dort, aber OSM hat
einen Kalender den ich als zuverlässig einschätze:

https://wiki.openstreetmap.org/wiki/Current_events


Dort scheint er nicht auf, weil
http://wiki.openstreetmap.org/wiki/Wien/Stammtisch nicht aktualisiert
wurde, obwohl die Liste der "nächsten Stammtische" dort den Termin
aufführt. Deswegen frage ich ja hier auf der Liste.

Grüße,
KaiRo


___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at



___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at




___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-us] How to get open street maps

2016-06-03 Per discussione David Niklas
On Sat, 28 May 2016 06:51:52  wrote:
> Hello,
> I downloaded the maps, but they changed over night, so the md5 sums
> don't match up. I tried using rsync -cav to ftp.spline.de, but the
> connection times out "[Receiver] io timeout after 181 seconds --
> exiting" (return code 30) I know that the port is accessible because I
> used nmap on it. I tried passing the --timeout flags but that made no
> difference. What could I do? I can't download that much data from
> scratch and a subset of the world cannot be resynced with the master?

I'm guessing you guys don't know, can you recommend a better ML to ask
at, OSM has many.

Thanks, David

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione osm . sanspourriel

Bonjour François,

Ma mise en garde va dans le même sens que la tienne.

http://mc.bbbike.org/mc/?lon=-3.413426=47.745501=18=2=osmfr=mapbox-hybrid=building:yes%3Cbr%3Eoperator:EDF%3Cbr%3Epower:substation%3Cbr%3Eref:MLTVULCA

Ce sont bien des transformateurs HTA (building=yes + power=substation) 
avec operator=EDF. Ceux-ci ne devraient pas, sauf erreur ou exception, 
être attribués à EDF.


Or il y en a 1484+345=1829 objets ainsi décrits 
http://overpass-turbo.eu/s/gC1


Ceux avec operator=ERDF sont au nombre de 4935+114=5049, soit 27 % de 
mauvais operator (OK, 100% depuis le 1er juin).


Maintenant je connais un transformateur qui n'appartient pas à ERDF mais 
qui est un poste client marqué EDF si je n'abuse (mais qui n'appartient 
pas à EDF et n'est pas opéré par EDF non plus).


Jean-Yvon

Le 2016-06-03 à 20:35, François Lacombe - fl.infosrese...@gmail.com a 
écrit :

Bonjour Jean-Yvon,

Le 3 juin 2016 à 20:25,   a écrit :

sans compter les transformateurs souvent attribués par erreur à EDF. Et là
le changement massif est sans doute plus douteux.

operator=EDF ne doit être attribué qu'aux équipements (centrales,
générateurs) de production, puisque c'est la seule activité de la
maison mère.

Qu'entends-tu exactement par transformateur ?
Pour moi c'est un appareil, pas un bâtiment alors qu'on trouve souvent
des building=yes + power=transformer au lieu de building=yes +
power=substation.

Il est question de ce genre de chose
http://www.infos-reseaux.com/photos/image/122-poste-de-transformation-hta

cf http://wiki.openstreetmap.org/wiki/FR:Tag:power%3Dtransformer

Attention je ne parlais pas de toucher à operator=EDF, mais uniquement
à operator=ERDF
Pour operator=EDF c'est un travail de longue haleine, puisqu'on ne
sait pas effectivement si c'est de l'EDF, du RTE, de l'Enedis,... sauf
à avoir un objet plus détaillé.



Car si la CRE a demandé à ERDF de changer de nom pour ne plus avoir de
confusion avec sa maison mère à 100% EDF SA, les transformateurs sont encore
marqués de l'ancien nom EDF du temps ou cette entreprise était un service
public.

Les transformateurs en eux-même sont rarement marqué du logo d'EDF
mais plutôt du fabriquant (transfix, cahors,...)
http://www.infos-reseaux.com/photos/image.php?id=48

Par contre sur les postes de transformation (bâtiment), il y a des
plaquettes qui donnent parfois le nom de l'exploitant.
http://wiki.openstreetmap.org/wiki/File:French_substation_id.jpg
C'est un faux ami : comme les plaques en fonte sur le trottoir, les
fournisseurs ont des moules et on utilise le matériel le plus courant.
Même les postes des régies locales peuvent avoir des choses de ce style.



Pour GRDF, c'est la maison mère qui a changé de nom (Engie).

Operator : y a-t-il des boîtes-aux-lettres de rue en France qui se sont pas
de FR:LaPoste ? Sinon pourquoi ne pas faire de même ?

Je regarderais du côté de Mediapost, Adrexxo,...


A+

François

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk] ford=no for highways which are known to have no fords?

2016-06-03 Per discussione Richard
On Fri, Jun 03, 2016 at 01:46:41AM -0700, Ben Discoe wrote:
> On Tue, May 31, 2016 at 2:08 PM, Richard  wrote:
> >> FWIW, I simply set the following key mapping in JOSM:
> >>
> >> Shift-D: add bridge=yes, layer=1
> >> Shift-C: add tunnel=culvert, layer=-1
> >
> > nice.. but still need to select or add two nodes, split the
> > ways, and select the correct segment before hitting s-d/s-c.
> 
> I agree, I always intended to add that to make it easier... so this
> evening I took the time to figure it out, and it works great: You can
> select a way, or multiple ways, or a way and two nodes, or just two
> nodes.  I'll write up a diary post soon with my new powerful script.
> :)

great thanks, where do I find the script?

Richard

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


[Talk-us] Western TIGER Roads

2016-06-03 Per discussione Alan Bragg
​I've tried to fix TIGER roads near Show Low AZ
http://www.openstreetmap.org/#map=14/34.3565/-109.7752
where my daughter has a cabin.



I could not reach her cabin in my high clearance van so I called it a
highway=track.

The best roads appear smudgy black because they've been covered with
volcanic ash.

Most of the roads are only drive-able up to the last building.

Many of these roads have signs with name and often a number. I'm told a
number prefixed with a C is maintained by the county and those prefixed
with a N are not.

I have read the wiki
http://wiki.openstreetmap.org/wiki/United_States_Unpaved_Roads_Tagging

Is there any other resource? Maybe some links to well tagged areas.

I'd appreciate someone letting me know how to improve my tagging.

Alan
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione DH

Le 03/06/2016 19:28, François Lacombe a écrit :

Bonjour la liste,

comme vous l'avez peut-être vu ces derniers jours, l'opérateur de
distribution électrique ERDF a changé de nom pour Enedis.
RFF l'a précédé en 2015 pour donner naissance à SNCF Réseau, pour ne
citer qu'un cas probablement parmi tant d'autres avec la fusion des
communes, fusion des régions, etc...

Pourtant dans OSM :
operator=RFF, 3349 objets
operator=SNCF Réseau, 3205 objets
operator=ERDF, 25768 objets
operator=Enedis, 0 objets




Pour les RFF, je les dégomme dès que j'en vois façon 
http://www.toupty.com/jeuasteroids.html (ça ne nous rajeunit pas ;-)
note : tagger operator pour chaque tronçon ferroviaire n'est pas l'idée 
la plus productive. La relation c'est bien pour cela ; les relations, 
c'est bien (point).


Denis


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk-fr] rendus OSM des villes

2016-06-03 Per discussione osm . sanspourriel
Sur la couche transport, c'est même un quartier de Vannes qui se 
substitue à Vannes :


http://www.openstreetmap.org/way/213906166#map=9/47.6575/-2.7383=T

Vous voyez quelque chose d'incorrect dans les données ou ce sont les 
rendus qui ne rendent pas très bien les agglomérations ?


Jean-Yvon


Le 2016-06-02 à 23:37, osm.sanspourr...@spamgourmet.com a écrit :


Vannes  est la 
préfecture du Morbihan :


admin_level 
 	8 


capital    6
name   Vannes
population 
 	52515


Le nœud Vannes  lui-même 
comporte aussi capital=6 et la population.


Un peu au nord se trouve la petite ville de Saint-Avé 
 :


admin_level 
 	8 

name  
Saint-Avé
population 
 	10385



Certains rendus ne semblent utiliser ni le capital (ici 6=préfecture) 
ni la population mais juste place=town avec affichage de haut à gauche 
en bas à droite.
Résultat : OSM-FR affiche Saint-Avé simple ville dans la banlieue de 
Vannes, plutôt que Vannes 5 fois plus important et préfecture du Morbihan.
Il n'est pas possible d'organiser le tracé par coalesce(capital,15)  
croissant puis par coalesce(population,0) décroissant ?


Jean-Yvon


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-it] Mappa Esino Lario

2016-06-03 Per discussione Alessandro

Il 03/06/2016 18:14, Dario Crespi ha scritto:

11 giugno è escluso. C'è la formazione di 100 volontari a Esino.



K, allora 18 e 19.
Datemi qualche conferma così lo segno sulla wiki


Alessandro Ale_Zena_IT

___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione François Lacombe
Bonjour Jean-Yvon,

Le 3 juin 2016 à 20:25,   a écrit :
> sans compter les transformateurs souvent attribués par erreur à EDF. Et là
> le changement massif est sans doute plus douteux.

operator=EDF ne doit être attribué qu'aux équipements (centrales,
générateurs) de production, puisque c'est la seule activité de la
maison mère.

Qu'entends-tu exactement par transformateur ?
Pour moi c'est un appareil, pas un bâtiment alors qu'on trouve souvent
des building=yes + power=transformer au lieu de building=yes +
power=substation.

Il est question de ce genre de chose
http://www.infos-reseaux.com/photos/image/122-poste-de-transformation-hta

cf http://wiki.openstreetmap.org/wiki/FR:Tag:power%3Dtransformer

Attention je ne parlais pas de toucher à operator=EDF, mais uniquement
à operator=ERDF
Pour operator=EDF c'est un travail de longue haleine, puisqu'on ne
sait pas effectivement si c'est de l'EDF, du RTE, de l'Enedis,... sauf
à avoir un objet plus détaillé.


>
> Car si la CRE a demandé à ERDF de changer de nom pour ne plus avoir de
> confusion avec sa maison mère à 100% EDF SA, les transformateurs sont encore
> marqués de l'ancien nom EDF du temps ou cette entreprise était un service
> public.
Les transformateurs en eux-même sont rarement marqué du logo d'EDF
mais plutôt du fabriquant (transfix, cahors,...)
http://www.infos-reseaux.com/photos/image.php?id=48

Par contre sur les postes de transformation (bâtiment), il y a des
plaquettes qui donnent parfois le nom de l'exploitant.
http://wiki.openstreetmap.org/wiki/File:French_substation_id.jpg
C'est un faux ami : comme les plaques en fonte sur le trottoir, les
fournisseurs ont des moules et on utilise le matériel le plus courant.
Même les postes des régies locales peuvent avoir des choses de ce style.


> Pour GRDF, c'est la maison mère qui a changé de nom (Engie).
>
> Operator : y a-t-il des boîtes-aux-lettres de rue en France qui se sont pas
> de FR:LaPoste ? Sinon pourquoi ne pas faire de même ?

Je regarderais du côté de Mediapost, Adrexxo,...


A+

François

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione osm . sanspourriel
sans compter les transformateurs souvent attribués par erreur à EDF. Et 
là le changement massif est sans doute plus douteux.


Car si la CRE a demandé à ERDF de changer de nom pour ne plus avoir de 
confusion avec sa maison mère à 100% EDF SA, les transformateurs sont 
encore marqués de l'ancien nom EDF du temps ou cette entreprise était un 
service public.


Pour GRDF, c'est la maison mère qui a changé de nom (Engie).

Operator : y a-t-il des boîtes-aux-lettres de rue en France qui se sont 
pas de FR:LaPoste ? Sinon pourquoi ne pas faire de même ?


Jean-Yvon

Le 2016-06-03 à 19:28, François Lacombe - fl.infosrese...@gmail.com a 
écrit :

Bonjour la liste,

comme vous l'avez peut-être vu ces derniers jours, l'opérateur de
distribution électrique ERDF a changé de nom pour Enedis.
RFF l'a précédé en 2015 pour donner naissance à SNCF Réseau, pour ne
citer qu'un cas probablement parmi tant d'autres avec la fusion des
communes, fusion des régions, etc...

Pourtant dans OSM :
operator=RFF, 3349 objets
operator=SNCF Réseau, 3205 objets
operator=ERDF, 25768 objets
operator=Enedis, 0 objets

Comme on peut le voir, les objets attribués à RFF migrent
difficilement vers la nouvelle valeur (si tant est que SNCF Réseau
soit la valeur à appliquer. La confusion avec Gares & connexion est
facile et il en va de même avec les autres filiales de la SNCF).

Ça me semble être un problème, et nous avons tout intérêt à avoir un
ensemble de données cohérentes.
Il y a un ticket ouvert chez JOSM : https://josm.openstreetmap.de/ticket/12914

J'ai déjà commencé à mettre à jour le wiki, mais cela ne suffira
pourtant pas à obtenir un ensemble cohérent avant un certain nombre
d'années.

Quid de proposer au DWG de faire une migration en masse ?
Plutôt facile à réaliser : overpass => query sur operator=ERDF => JSOM
ctrl+A => operator=Enedis => Upload

Le principal enjeu est l'information de la communauté et la mise à
jour des scripts de consommation.

A+

François

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


[OSM-talk-fr] ERDF (et RFF) ont changé de nom

2016-06-03 Per discussione François Lacombe
Bonjour la liste,

comme vous l'avez peut-être vu ces derniers jours, l'opérateur de
distribution électrique ERDF a changé de nom pour Enedis.
RFF l'a précédé en 2015 pour donner naissance à SNCF Réseau, pour ne
citer qu'un cas probablement parmi tant d'autres avec la fusion des
communes, fusion des régions, etc...

Pourtant dans OSM :
operator=RFF, 3349 objets
operator=SNCF Réseau, 3205 objets
operator=ERDF, 25768 objets
operator=Enedis, 0 objets

Comme on peut le voir, les objets attribués à RFF migrent
difficilement vers la nouvelle valeur (si tant est que SNCF Réseau
soit la valeur à appliquer. La confusion avec Gares & connexion est
facile et il en va de même avec les autres filiales de la SNCF).

Ça me semble être un problème, et nous avons tout intérêt à avoir un
ensemble de données cohérentes.
Il y a un ticket ouvert chez JOSM : https://josm.openstreetmap.de/ticket/12914

J'ai déjà commencé à mettre à jour le wiki, mais cela ne suffira
pourtant pas à obtenir un ensemble cohérent avant un certain nombre
d'années.

Quid de proposer au DWG de faire une migration en masse ?
Plutôt facile à réaliser : overpass => query sur operator=ERDF => JSOM
ctrl+A => operator=Enedis => Upload

Le principal enjeu est l'information de la communauté et la mise à
jour des scripts de consommation.

A+

François

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-GB] Schools Project

2016-06-03 Per discussione Christian Ledermann
I implemented most of the improvement suggestions I received so far:

* clearer message that something is added to OSM
* display all osm features not just polygons
* import log which prevents double adding and gives feedback to the user
* no import of blank values





On 3 June 2016 at 09:46, Christian Ledermann
 wrote:
> On 3 June 2016 at 09:02, Ed Loach  wrote:
>> Christian asked:
>>
>>> As schools.mapthe.uk is an import project to osm:
>>>
>>>  Does the community `buy in` to this approach?
>>>  Can I go forward to contacting osm imports?
>>>  What would you like to see as improvements?
>>>
>>> As usual silence counts as approval ;-)
>>
>> I missed earlier emails on this subject but have had a quick play now. 
>> Instructions seem very lacking. Why do I get the option to add an OS 
>> OpenData polygon when the school is already mapped? That is likely to lead 
>> to duplication.
>>
>
> I will add as Gregory sugested:
> "The highlighted polygon will be ADDED to OpenStreetMap. If a school
> outline is already shown on the base map behind, then you should
> manually add the tags (& edubase reference manually) to that object."
>
> If there is anything you want to add to the documentation/input form
> your input is very appreciated :-)
>
>> Or is it just because I'm seeing live tiles but we’re using api06 data for 
>> comparison?
>>
>> When I clicked Add to OSM nothing seemed to happen, so I tried again. So I 
>> added it twice:
>> http://api06.dev.openstreetmap.org/changeset/85444
>> http://api06.dev.openstreetmap.org/changeset/85445
>>
>
> Yes good point. I think what is needed is to record which features
> have been add with this tool and if a feature has been added disable
> the 'add to osm' button.
>
>
>> Why is it adding a simple closed way as a multipolygon relation? Why not put 
>> the tags on the way?
>
> Some schools have school grounds that are on either side of a road.
> In this case a multipolygon is needed.
>
>
> If I interpreted
> http://wiki.openstreetmap.org/wiki/Relation:multipolygon and
> http://wiki.openstreetmap.org/wiki/Area/The_Future_of_Areas
> right, a multipolygon is the prefered way of adding an area
>
>> In the example changesets above, it is adding the website key with a blank 
>> value. I'm not sure blank values need adding.
>>
>
> In the future blank values will be omitted.
>
>> The changesets could probably use "source" tags to show where the data has 
>> been added from.
>
> source would be edubase/seed+os-open ?
>
>> When I clicked on "Add to OSM" I thought it might both add the multipolygon 
>> and open my default editor to allow me to trace buildings within the 
>> polygon, and any other details visible from Bing. Is this possible?
>
> It should be possible to open a new tab/window to edit osm in the
> browser - josm is another beast
>
>>
>> Ed
>>
>
>
>
> --
> Best Regards,
>
> Christian Ledermann
>
> Newark-on-Trent - UK
> Mobile : +44 7474997517
>
> https://uk.linkedin.com/in/christianledermann
> https://github.com/cleder/
>
>
> <*)))>{
>
> If you save the living environment, the biodiversity that we have left,
> you will also automatically save the physical environment, too. But If
> you only save the physical environment, you will ultimately lose both.
>
> 1) Don’t drive species to extinction
>
> 2) Don’t destroy a habitat that species rely on.
>
> 3) Don’t change the climate in ways that will result in the above.
>
> }<(((*>



-- 
Best Regards,

Christian Ledermann

Newark-on-Trent - UK
Mobile : +44 7474997517

https://uk.linkedin.com/in/christianledermann
https://github.com/cleder/


<*)))>{

If you save the living environment, the biodiversity that we have left,
you will also automatically save the physical environment, too. But If
you only save the physical environment, you will ultimately lose both.

1) Don’t drive species to extinction

2) Don’t destroy a habitat that species rely on.

3) Don’t change the climate in ways that will result in the above.

}<(((*>

___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Peter Dobratz
JOSM does automatically discard some TIGER:* tags.  There's a list of keys
in the tags.discardable JOSM preference item.  Among the list of tags that
JOSM automatically deletes are:
tiger:source
tiger:separated
tiger:tlid
tiger:upload_uuid

These tags are hidden from the editor so you don't normally see them.  They
are automatically removed from any objects that you modify.  You may notice
them if you are looking at the history of an object in JOSM.

That being said, I delete the other tiger:* from roads as I am editing
them.  Usually, I am verifying addr:* tags of things along the road and
checking that the addr:street matches the name of the road.  I also often
remove the name_1, name_2, etc tags that came from the TIGER import.  Where
appropriate, I retain them in alt_name or old_name.

Peter

On Fri, Jun 3, 2016 at 8:51 AM, Steve Friedl  wrote:

> Ø  Unless something changed, I think both Potlatch and JOSM will remove
> the ‘junk’ tags from TIGER if you delete the reviewed=no
>
>
>
> I’ve deleted thousands of tiger:reviewed tags (after proper review) and
> have never seen JOSM take anything else along for the ride.  JOSM **does**
> remove the yellow glow around ways once you remove tiger:reviewed, but
> that’s all I’ve seen.
>
>
>
> I have very much wanted to dump the tags that have no obvious use for OSM,
> but had no idea if somebody else, somewhere, might use them: probably not,
> but it didn’t feel like it was my call to make. I’d love for there to be a
> consensus on this.
>
>
>
> So the only things I’ve removed are tiger:reviewed, plus spurious
> additional tags that duplicate existing ones (tiger:zip_left_1 when it’s
> the same as tiger:zip_left).
>
>
>
> Steve
>
>
>
> *From:* Russell Deffner [mailto:russdeff...@gmail.com]
> *Sent:* Friday, June 03, 2016 8:45 AM
> *To:* 'Adam Franco' ; talk-us@openstreetmap.org
>
> *Subject:* Re: [Talk-us] Best practices for dealing with old TIGER tags?
>
>
>
> Oops, sorry Adam, replied directly to you versus the list; here’s the
> message:
>
>
>
> My thoughts:
>
>
>
> Unless something changed, I think both Potlatch and JOSM will remove the
> ‘junk’ tags from TIGER if you delete the reviewed=no. Maybe this is not the
> case with iD?
>
>
>
> As far as classification; please note that it is not about whether the
> road is rural or not; it’s the function – there have been people who
> started changing all ‘dirt roads’ to track around me in rural Colorado –
> this is NOT correct. Most of the ‘dirt roads’ around here are 100%
> verifiably “residential”. So please don’t encourage mass changing of
> classification based on anything but function of the roadway.
>
>
>
> =Russ
>
>
>
> *From:* Adam Franco [mailto:adamfra...@gmail.com ]
> *Sent:* Friday, June 03, 2016 9:28 AM
> *To:* talk-us@openstreetmap.org Openstreetmap
> *Subject:* Re: [Talk-us] Best practices for dealing with old TIGER tags?
>
>
>
> Just some more feedback on the idea of a TIGER rural-residential challenge
> based on cleanup I've done throughout much of Vermont:
>
>- Most of the roads in rural areas should have their highway= changed
>to something other than residential. (well known issue).
>- Surface tags would be GREAT! I've added surface tags to most roads
>in Vermont, but have not quite gotten to all of them yet.
>- At least here in Vermont, "private road" means that the ownership
>and maintenance of the road is the responsibility of the resident[s], not
>that "access=private". We have many private roads due to low densities of
>residences and Towns generally won't take over ownership/maintenance unless
>there are at least 3 residences and the proposal passes a public vote. The
>TIGER import mistakenly tagged many private-roads as "access=private". It
>would be great to remove this tag if it hasn't been added by a person.
>
> If there is any way to help out with this effort I'd love to lend a hand.
>
>
>
> On Fri, Jun 3, 2016 at 10:18 AM, James Umbanhowar 
> wrote:
>
> Funny, I just looked at the MapRoulette beta and noticed that you were
> already doing this.
>
>
>
>
> On Fri, 2016-06-03 at 10:00 -0400, James Umbanhowar wrote:
> > Minor suggestion for this MapRoulette challenge:  Could you structure
> > it by state (or other geographic region, county?) and do each region
> > sequentially.  I, personally, think it would be neat to see areas get
> > "done" as far as Tiger clean up.
> >
> > Either way, thanks for these.
> >
> > James
> >
> > On Fri, 2016-06-03 at 10:21 +0200, Martijn van Exel wrote:
> > >
> > > Well said. I have space in my basement also.
> > >
> > > I am eager to launch a MapRoulette challenge for untouched rural
> > > ‘residential’ roads - a challenge which will probably take some
> > > time
> > > to complete. If someone can furnish a good Overpass query for this,
> > > please go ahead and do it.
> > >
> > > Martijn
> > >
> > > >
> > > > On Jun 3, 2016, at 

Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Russell Deffner
Yes, ok – so ‘aging myself’ a bit – but I did all my locale TIGER cleanup with 
P2, so my practice was to review/almost always fix geometry, then look at 
‘function’/classification of the roadway, then just delete the reviewed tag and 
automagically those uid tags and such would go away. So it seems now we are 
talking that even more original TIGER tags are ‘useless’ and should be removed, 
which I have no problems with, I’m sure there were several dozen I just deleted 
everything (sometimes the entire way) because the road was actually a driveway 
or otherwise completely wrong.

=Russ

 

From: Harald Kliems [mailto:kli...@gmail.com] 
Sent: Friday, June 03, 2016 10:03 AM
To: Steve Friedl; Russell Deffner; Adam Franco; talk-us@openstreetmap.org
Subject: Re: [Talk-us] Best practices for dealing with old TIGER tags?

 

 

On Fri, Jun 3, 2016 at 10:52 AM Steve Friedl  wrote:

Ø  Unless something changed, I think both Potlatch and JOSM will remove the 
‘junk’ tags from TIGER if you delete the reviewed=no

 

I’ve deleted thousands of tiger:reviewed tags (after proper review) and have 
never seen JOSM take anything else along for the ride.  JOSM *does* remove the 
yellow glow around ways once you remove tiger:reviewed, but that’s all I’ve 
seen.

Russell is probably referring to this: 
https://josm.openstreetmap.de/ticket/7915 

I think most of these are gone by now.

 

 Harald.

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-it] Mappa Esino Lario

2016-06-03 Per discussione Dario Crespi
11 giugno è escluso. C'è la formazione di 100 volontari a Esino.

Dario
Il 03/giu/2016 17:33, "Andrea Lattmann"  ha
scritto:

> s'hà da fare si!
> Allora che decidiamo? 18/19?
>
> Andrea Lattmann
>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Harald Kliems
On Fri, Jun 3, 2016 at 10:52 AM Steve Friedl  wrote:

> Ø  Unless something changed, I think both Potlatch and JOSM will remove
> the ‘junk’ tags from TIGER if you delete the reviewed=no
>
>
>
> I’ve deleted thousands of tiger:reviewed tags (after proper review) and
> have never seen JOSM take anything else along for the ride.  JOSM **does**
> remove the yellow glow around ways once you remove tiger:reviewed, but
> that’s all I’ve seen.
>
Russell is probably referring to this:
https://josm.openstreetmap.de/ticket/7915
I think most of these are gone by now.

 Harald.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


[Talk-us] Los Angeles Building Import mapathon Sunday, June 5

2016-06-03 Per discussione Charlotte Wolter

Hello all in and near LA,

Work continues on the LA County Building 
Import (more than 3 million buildings in LA 
County) Sunday, June 5, at a mapathon in downtown LA.
We will be checking the imported 
building outlines against aerial imagery to 
validate this import, one of the largest building imports ever OSM.
For more information, see 
http://www.meetup.com/MaptimeLA/events/231550324/


We will gather, starting at 1 p.m., at

Angel 
City Brewery


216 Alameda Street (between 2nd and 3rd Streets)
(two blocks south of the Little 
Tokyo/Arts District metro station on the Gold 
Line or about 1/4 mile east from the Pershing Square Red Line metro station)


Be sure to bring
• a laptop (a mouse is also very helpful)
• some experience using JOSM
• a healthy appetite for open-source mapping

There will be lots of friendly people 
there to help if you have never done this sort of 
thing before. See you at Angel City!


Charlotte


Charlotte Wolter
927 18th Street Suite A
Santa Monica, California
90403
+1-310-597-4040
techl...@techlady.com
Skype: thetechlady

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Steve Friedl
*  Unless something changed, I think both Potlatch and JOSM will remove the 
‘junk’ tags from TIGER if you delete the reviewed=no

 

I’ve deleted thousands of tiger:reviewed tags (after proper review) and have 
never seen JOSM take anything else along for the ride.  JOSM *does* remove the 
yellow glow around ways once you remove tiger:reviewed, but that’s all I’ve 
seen.

 

I have very much wanted to dump the tags that have no obvious use for OSM, but 
had no idea if somebody else, somewhere, might use them: probably not, but it 
didn’t feel like it was my call to make. I’d love for there to be a consensus 
on this.

 

So the only things I’ve removed are tiger:reviewed, plus spurious additional 
tags that duplicate existing ones (tiger:zip_left_1 when it’s the same as 
tiger:zip_left).

 

Steve

 

From: Russell Deffner [mailto:russdeff...@gmail.com] 
Sent: Friday, June 03, 2016 8:45 AM
To: 'Adam Franco' ; talk-us@openstreetmap.org
Subject: Re: [Talk-us] Best practices for dealing with old TIGER tags?

 

Oops, sorry Adam, replied directly to you versus the list; here’s the message: 

 

My thoughts:

 

Unless something changed, I think both Potlatch and JOSM will remove the ‘junk’ 
tags from TIGER if you delete the reviewed=no. Maybe this is not the case with 
iD?

 

As far as classification; please note that it is not about whether the road is 
rural or not; it’s the function – there have been people who started changing 
all ‘dirt roads’ to track around me in rural Colorado – this is NOT correct. 
Most of the ‘dirt roads’ around here are 100% verifiably “residential”. So 
please don’t encourage mass changing of classification based on anything but 
function of the roadway.

 

=Russ 

 

From: Adam Franco [mailto:adamfra...@gmail.com] 
Sent: Friday, June 03, 2016 9:28 AM
To: talk-us@openstreetmap.org   Openstreetmap
Subject: Re: [Talk-us] Best practices for dealing with old TIGER tags?

 

Just some more feedback on the idea of a TIGER rural-residential challenge 
based on cleanup I've done throughout much of Vermont:

*   Most of the roads in rural areas should have their highway= changed to 
something other than residential. (well known issue).
*   Surface tags would be GREAT! I've added surface tags to most roads in 
Vermont, but have not quite gotten to all of them yet.
*   At least here in Vermont, "private road" means that the ownership and 
maintenance of the road is the responsibility of the resident[s], not that 
"access=private". We have many private roads due to low densities of residences 
and Towns generally won't take over ownership/maintenance unless there are at 
least 3 residences and the proposal passes a public vote. The TIGER import 
mistakenly tagged many private-roads as "access=private". It would be great to 
remove this tag if it hasn't been added by a person.

If there is any way to help out with this effort I'd love to lend a hand. 

 

On Fri, Jun 3, 2016 at 10:18 AM, James Umbanhowar  > wrote:

Funny, I just looked at the MapRoulette beta and noticed that you were
already doing this.




On Fri, 2016-06-03 at 10:00 -0400, James Umbanhowar wrote:
> Minor suggestion for this MapRoulette challenge:  Could you structure
> it by state (or other geographic region, county?) and do each region
> sequentially.  I, personally, think it would be neat to see areas get
> "done" as far as Tiger clean up.  
>
> Either way, thanks for these.
>
> James
>
> On Fri, 2016-06-03 at 10:21 +0200, Martijn van Exel wrote:
> >
> > Well said. I have space in my basement also. 
> >
> > I am eager to launch a MapRoulette challenge for untouched rural
> > ‘residential’ roads - a challenge which will probably take some
> > time
> > to complete. If someone can furnish a good Overpass query for this,
> > please go ahead and do it.
> >
> > Martijn
> >
> > >
> > > On Jun 3, 2016, at 8:55 AM, Richard Fairhurst  > >  
> > > et
> > > >
> > > > wrote:
> > > There is a special corner of hell/Steve's basement for people who
> > > remove
> > > tiger:reviewed=no on rural unpaved roads without changing the
> > > highway tag or
> > > adding a surface tag.
> > ___
> > Talk-us mailing list
> > Talk-us@openstreetmap.org  
> > https://lists.openstreetmap.org/listinfo/talk-us

___
Talk-us mailing list
Talk-us@openstreetmap.org  
https://lists.openstreetmap.org/listinfo/talk-us

 

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Russell Deffner
Oops, sorry Adam, replied directly to you versus the list; here’s the message: 

 

My thoughts:

 

Unless something changed, I think both Potlatch and JOSM will remove the ‘junk’ 
tags from TIGER if you delete the reviewed=no. Maybe this is not the case with 
iD?

 

As far as classification; please note that it is not about whether the road is 
rural or not; it’s the function – there have been people who started changing 
all ‘dirt roads’ to track around me in rural Colorado – this is NOT correct. 
Most of the ‘dirt roads’ around here are 100% verifiably “residential”. So 
please don’t encourage mass changing of classification based on anything but 
function of the roadway.

 

=Russ 

 

From: Adam Franco [mailto:adamfra...@gmail.com] 
Sent: Friday, June 03, 2016 9:28 AM
To: talk-us@openstreetmap.org Openstreetmap
Subject: Re: [Talk-us] Best practices for dealing with old TIGER tags?

 

Just some more feedback on the idea of a TIGER rural-residential challenge 
based on cleanup I've done throughout much of Vermont:

*   Most of the roads in rural areas should have their highway= changed to 
something other than residential. (well known issue).
*   Surface tags would be GREAT! I've added surface tags to most roads in 
Vermont, but have not quite gotten to all of them yet.
*   At least here in Vermont, "private road" means that the ownership and 
maintenance of the road is the responsibility of the resident[s], not that 
"access=private". We have many private roads due to low densities of residences 
and Towns generally won't take over ownership/maintenance unless there are at 
least 3 residences and the proposal passes a public vote. The TIGER import 
mistakenly tagged many private-roads as "access=private". It would be great to 
remove this tag if it hasn't been added by a person.

If there is any way to help out with this effort I'd love to lend a hand. 

 

On Fri, Jun 3, 2016 at 10:18 AM, James Umbanhowar  wrote:

Funny, I just looked at the MapRoulette beta and noticed that you were
already doing this.




On Fri, 2016-06-03 at 10:00 -0400, James Umbanhowar wrote:
> Minor suggestion for this MapRoulette challenge:  Could you structure
> it by state (or other geographic region, county?) and do each region
> sequentially.  I, personally, think it would be neat to see areas get
> "done" as far as Tiger clean up.  
>
> Either way, thanks for these.
>
> James
>
> On Fri, 2016-06-03 at 10:21 +0200, Martijn van Exel wrote:
> >
> > Well said. I have space in my basement also. 
> >
> > I am eager to launch a MapRoulette challenge for untouched rural
> > ‘residential’ roads - a challenge which will probably take some
> > time
> > to complete. If someone can furnish a good Overpass query for this,
> > please go ahead and do it.
> >
> > Martijn
> >
> > >
> > > On Jun 3, 2016, at 8:55 AM, Richard Fairhurst  > >  
> > > et
> > > >
> > > > wrote:
> > > There is a special corner of hell/Steve's basement for people who
> > > remove
> > > tiger:reviewed=no on rural unpaved roads without changing the
> > > highway tag or
> > > adding a surface tag.
> > ___
> > Talk-us mailing list
> > Talk-us@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-us

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

 

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


[Talk-in] [BLR] Indiranagar tree planting and mapping on world environment day

2016-06-03 Per discussione Arun Ganesh
Hey everyone, there is a massive tree planting drive in Indiranagar
tomorrow for world environment day. More than 100 saplings are going to be
planted at various locations at 1st stage, 2nd stage, BM Kaval and Defence
Colony.

This is being organized by the RWAs with the help of the MLA, and as part
of the efforts we are also going to document the locations of the trees on
OpenStreetMap.

Those interested will be meeting at the cornerstone park opposite KFC from
9AM. Ask the organizers for me or the mapping team.

Details: https://www.facebook.com/events/478058269058618/

-- 
Arun Ganesh
@planemad

___
Talk-in mailing list
Talk-in@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-in


Re: [Talk-it] Mappa Esino Lario

2016-06-03 Per discussione Andrea Lattmann
s'hà da fare si!
Allora che decidiamo? 18/19?

Andrea Lattmann

___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [Talk-it] Mappa Esino Lario

2016-06-03 Per discussione Alessandro Palmas

Scusate, ma alla fine ...
il Mapping Party su "Quel ramo del lago di Como, che volge a mezzogiorno 
.." a furia di parlarne s'hà da fare!


Decidiamo per il 18 e 19 come scriveva Dario? O vediamo di farlo l'11 e 
12 giugno?


Alessandro 'Nibbio' Ale_Zena_IT :-)


___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione James Umbanhowar
Funny, I just looked at the MapRoulette beta and noticed that you were
already doing this.



On Fri, 2016-06-03 at 10:00 -0400, James Umbanhowar wrote:
> Minor suggestion for this MapRoulette challenge:  Could you structure
> it by state (or other geographic region, county?) and do each region
> sequentially.  I, personally, think it would be neat to see areas get
> "done" as far as Tiger clean up.  
> 
> Either way, thanks for these.
> 
> James
> 
> On Fri, 2016-06-03 at 10:21 +0200, Martijn van Exel wrote:
> > 
> > Well said. I have space in my basement also. 
> > 
> > I am eager to launch a MapRoulette challenge for untouched rural
> > ‘residential’ roads - a challenge which will probably take some
> > time
> > to complete. If someone can furnish a good Overpass query for this,
> > please go ahead and do it.
> > 
> > Martijn
> > 
> > > 
> > > On Jun 3, 2016, at 8:55 AM, Richard Fairhurst  > > et
> > > > 
> > > > wrote:
> > > There is a special corner of hell/Steve's basement for people who
> > > remove
> > > tiger:reviewed=no on rural unpaved roads without changing the
> > > highway tag or
> > > adding a surface tag.
> > ___
> > Talk-us mailing list
> > Talk-us@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-us

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione James Umbanhowar
Minor suggestion for this MapRoulette challenge:  Could you structure
it by state (or other geographic region, county?) and do each region
sequentially.  I, personally, think it would be neat to see areas get
"done" as far as Tiger clean up.  

Either way, thanks for these.

James

On Fri, 2016-06-03 at 10:21 +0200, Martijn van Exel wrote:
> Well said. I have space in my basement also. 
> 
> I am eager to launch a MapRoulette challenge for untouched rural
> ‘residential’ roads - a challenge which will probably take some time
> to complete. If someone can furnish a good Overpass query for this,
> please go ahead and do it.
> 
> Martijn
> 
> > On Jun 3, 2016, at 8:55 AM, Richard Fairhurst  > > wrote:
> > 
> > There is a special corner of hell/Steve's basement for people who
> > remove
> > tiger:reviewed=no on rural unpaved roads without changing the
> > highway tag or
> > adding a surface tag.
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-de] tag defaults entfernen Was: zur Info: Bicycle=yes/designated als Anzeige Benutzungspflicht aufgeben

2016-06-03 Per discussione Florian Lohoff
On Thu, Jun 02, 2016 at 10:36:21PM +0200, Guido Scholz wrote:
> Am Wed, 01. Jun 2016 um 11:42:47 +0200 schrieb Florian Lohoff:

> Oder, was sehr wahrscheinlich ist, der tracktype Tag wurde nachträglich
> ergänzt, damit man als Mountainbiker erkennen kann, um welche Art von
> Weg es sich handelt. Die OpenmtbMap stellt nämlich die Wege mit Hilfe
> dieses Tags entsprechend dar.

highway=unclassified + tracktype=grade1 + surface=asphalt ?

Na - Was macht da Sinn? Es ist kein track - es ist eine unclassified -
Also woher kommt der tracktype? Weil irgendjemand mal gemeint hat das
das hinter dem Ortsschild doch bestimmt nur für die Landwirtschaft ist -
also highway=track, tracktype=grade1 - Dann hat jemand den Unsinn
korrigiert auf highway=unclassified + surface=asphalt - Hat aber
das tracktype nicht entfernt.

> > Es gibt tag kombinationen die absolut unsinnig sind die es zu
> > entfernen gilt und es gibt welche die nur redundant sind.
> 
> Na ja, oder halt eben auch nicht, und dann es gibt andersherum noch viel
> zu ergänzen bzw. wieder nachzubessern.

Flo
-- 
Florian Lohoff f...@zz.de
 UTF-8 Test: The  ran after a , but the  ran away


signature.asc
Description: Digital signature
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de


[Talk-es] Semanario Nr. 306

2016-06-03 Per discussione Laura Barroso
Hola, el semanario Nr. 306, el sumario de todo lo que está ocurriendo en
el mundo de openstreetmap está en línea en español.

http://www.weeklyosm.eu/es/archives/7593

¡Disfruta!

Algunos artículos destacados de esta edición:

1.Los miembros peruanos del equipo de Español de nuestra hermana
"weeklyOSM" Eliane Joyo Meneses y Rubén López Mendoza (ambos empleados de
Mapbox Perú) desarrollaron la herramienta knife-tool para JOSM, donde
dividir calles y agregar etiquetas de carriles de giro es una cosa fácil.

2.En Latinoamérica el número de grupos de Telegram dentro de la comunidad
OSM está creciendo establemente

3.Dos reportes de la efectividad de OSM por el reciente terremoto en
Ecuador:Vistazo, PBS.

4.Mapbox anuncia que sus herramientas relacionadas con los mapas son ahora
gratuitas para la respuesta humanitaria.


___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es


[OSM-co] Semanario Nr. 306

2016-06-03 Per discussione Laura Barroso
Hola, el semanario Nr. 306, el sumario de todo lo que está ocurriendo en
el mundo de openstreetmap está en línea en español.

http://www.weeklyosm.eu/es/archives/7593

¡Disfruta!

Algunos artículos destacados de esta edición:

1.Los miembros peruanos del equipo de Español de nuestra hermana
"weeklyOSM" Eliane Joyo Meneses y Rubén López Mendoza (ambos empleados de
Mapbox Perú) desarrollaron la herramienta knife-tool para JOSM, donde
dividir calles y agregar etiquetas de carriles de giro es una cosa fácil.

2.En Latinoamérica el número de grupos de Telegram dentro de la comunidad
OSM está creciendo establemente

3.Dos reportes de la efectividad de OSM por el reciente terremoto en
Ecuador:Vistazo, PBS.

4.Mapbox anuncia que sus herramientas relacionadas con los mapas son ahora
gratuitas para la respuesta humanitaria.


___
Talk-co mailing list
Talk-co@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-co


[Talk-cu] Semanario Nr. 306

2016-06-03 Per discussione Laura Barroso
Hola, el semanario Nr. 306, el sumario de todo lo que está ocurriendo en
el mundo de openstreetmap está en línea en español.

http://www.weeklyosm.eu/es/archives/7593

¡Disfruta!

Algunos artículos destacados de esta edición:

1.Los miembros peruanos del equipo de Español de nuestra hermana
"weeklyOSM" Eliane Joyo Meneses y Rubén López Mendoza (ambos empleados de
Mapbox Perú) desarrollaron la herramienta knife-tool para JOSM, donde
dividir calles y agregar etiquetas de carriles de giro es una cosa fácil.

2.En Latinoamérica el número de grupos de Telegram dentro de la comunidad
OSM está creciendo establemente

3.Dos reportes de la efectividad de OSM por el reciente terremoto en
Ecuador:Vistazo, PBS.

4.Mapbox anuncia que sus herramientas relacionadas con los mapas son ahora
gratuitas para la respuesta humanitaria.


___
Talk-cu mailing list
Talk-cu@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cu


[Talk-cl] Semanario Nr. 306

2016-06-03 Per discussione Laura Barroso
Hola, el semanario Nr. 306, el sumario de todo lo que está ocurriendo en
el mundo de openstreetmap está en línea en español.

http://www.weeklyosm.eu/es/archives/7593

¡Disfruta!

Algunos artículos destacados de esta edición:

1.Los miembros peruanos del equipo de Español de nuestra hermana
"weeklyOSM" Eliane Joyo Meneses y Rubén López Mendoza (ambos empleados de
Mapbox Perú) desarrollaron la herramienta knife-tool para JOSM, donde
dividir calles y agregar etiquetas de carriles de giro es una cosa fácil.

2.En Latinoamérica el número de grupos de Telegram dentro de la comunidad
OSM está creciendo establemente

3.Dos reportes de la efectividad de OSM por el reciente terremoto en
Ecuador:Vistazo, PBS.

4.Mapbox anuncia que sus herramientas relacionadas con los mapas son ahora
gratuitas para la respuesta humanitaria.


___
Talk-cl mailing list
Talk-cl@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cl


[Talk-at] Schanigärten / Gastgärten

2016-06-03 Per discussione Flo Ledermann

Hallo zusammen,

ich hatte neulich die Idee eine Wien-Karte zu machen in der man 
nachsehen kann wo man nett in einem Schanigarten sitzen könnte.


In OpenStreetMap fand ich dazu (für Wien) nichts - weder in den Daten, 
noch im Wiki, noch in der Mailingliste. An sich auch nicht so 
verwunderlich: da Schanigärten temporär sind, fühlt sich die 
OSM-Community wohl eher nicht zuständig und sähe sich alljährlich (oder 
sogar halbjährlich) mit einem Aktualisierungs-Problem konfrontiert. 
Dennoch sind Schanigärten im Stadtbild natürlich relevant, ein eventuell 
wichtiges Kriterium bei der Wahl eines Lokals oder auch einer 
Fussweg-Route, und die meisten werden auch alljährlich wieder an der 
selben Stelle aufgebaut.


Was meint ihr dazu? Würde es Sinn machen, überhaupt darüber nachzudenken 
wie man Schanigäten taggen könnte? (Fürs erste könnte ich mir 
vorstellen, dass sogar ein Tag "schanigarten=summer|all_year|no" zum 
Lokal auch reichen würde) - oder würdet ihr abwinken und ich überlege 
mir wie ich eine parallele Datensammlung zum Thema gestalten würde 
(Shapefile etc.)


Interessanterweise hab ich auch zu permanenten Gastgärten nix gefunden, 
obwohl da das Argument der Flüchtigkeit wegfallen würde und das Level 
von "Micromapping" auch nicht schlimmer wäre also bei manch anderen 
Dingen (Haltestellen-Geometrien, Indoor etc.) - wenn man im Wiki nach 
"Gastgarten" sucht kommt man nur zu den Wiener Stammtisch-Seiten ;)


LG Florian

--
Dipl.-Ing. Florian Ledermann
Cartography Research Group
Department of Geodesy and Geoinformation
TU Wien, Vienna, Austria

http://cartography.tuwien.ac.at/
https://twitter.com/floledermann

___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


[Talk-at] Salzkammergut Kartenmaterial 2015 auf doris.at

2016-06-03 Per discussione martin ringer
Gerade bei der DKM des Landes Oberösterreich gesehen, dass zumindest das 
Salzkammergut mit neuen Orthofotos (Befliegung 2015) ausgestattet ist. Bin 
gespannt, wann das Kartenmaterial bei OSM Verwendung findet.
___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-it] Confini Parco Nazionale Appennino Lucano Val D'Agri Lagonegrese

2016-06-03 Per discussione Martin Koppenhoefer
2016-06-02 9:58 GMT+02:00 Giuseppe Cillis :

> in alcuni tratti il confine è rappresentato dalla strada per cui un po'
> per volta mi sistemerà i vertici



Quando nel testo di legge viene specificato che la strada è il confine,
credo che vuole dire (nel contesto di una riserva naturale) che il parco
cominci al confine della strada (del suolo che legalmente è strada, anche
se si estende oltre l'asfalto), non al centro, quindi sarebbe più corretto
usare una geometria distinta e non quella della strada (nel multipoligono).
Mentre nel contesto di un'area amministrativa vorrebbe dire probabilmente
"centro della strada".

Ciao,
Martin
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [Talk-de] zur Info: Bicycle=yes/designated als Anzeige Benutzungspflicht aufgeben

2016-06-03 Per discussione Martin Koppenhoefer
Am 3. Juni 2016 um 10:02 schrieb Joerg Fischer :

> indem man breite, asphaltierte Radwege als Trampelpfade mappt.  Ist
> sicher nicht so wichtig.
>



das macht ja niemand, vielmehr gibt es 2 unterschiedliche Arten, dasselbe
zu taggen.
M.E. sollten wir nicht, nur weil es derzeit im Ausland (zu) viel Geld
kostet, mobile Daten zu nutzen, und einige der verfügbaren Offlline-Karten
highway=path grundsätzlich als Trampelpfad darstellen, unser Tagging
ändern. Dass das alternative Tagging (unter anderem) auf der "offiziellen
Karte" "richtig" angezeigt wird zeigt ja, dass das Problem eben nicht am
Tagging liegt.

Gruß,
Martin
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de


[Talk-us] WeeklyOSM 306

2016-06-03 Per discussione Jinal Foflia
The weekly round-up of OSM news, issue #306, is now available online in
English, giving as always a summary of all things happening in the
OpenStreetMap world:

http://www.weeklyosm.eu/archives/7593

*Among others:*


   - Love Mapillary? Read in more for detailed article about using
   Mapillary for mapping in OpenStreetMap with JOSM.
   - Mapbox announces that their map related tools are now free for
   humanitarian response.
   - The State of the Map Working Group (WG SotM) published a paper to the
   topic corporate membership. Source: OSMF-talk
   - Rome based architect and designer Mateo Prati showcases his 3D views
   of Manhattan made with Blender and OpenStreetMap data.
   - Try out the knife-tool for JOSM, which makes splitting ways at an
   arbitrary point a breeze.


Cheers,

Jinal Foflia 
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


[OSM-talk] WeeklyOSM 306

2016-06-03 Per discussione Jinal Foflia
The weekly round-up of OSM news, issue #306, is now available online in
English, giving as always a summary of all things happening in the
OpenStreetMap world:

http://www.weeklyosm.eu/archives/7593

*Among others:*


   - Love Mapillary? Read in more for detailed article about using
   Mapillary for mapping in OpenStreetMap with JOSM.
   - Mapbox announces that their map related tools are now free for
   humanitarian response.
   - The State of the Map Working Group (WG SotM) published a paper to the
   topic corporate membership. Source: OSMF-talk
   - Rome based architect and designer Mateo Prati showcases his 3D views
   of Manhattan made with Blender and OpenStreetMap data.
   - Try out the knife-tool for JOSM, which makes splitting ways at an
   arbitrary point a breeze.


Cheers,

Jinal Foflia 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


[Talk-GB] WeeklyOSM 306

2016-06-03 Per discussione Jinal Foflia
The weekly round-up of OSM news, issue #306, is now available online in
English, giving as always a summary of all things happening in the
OpenStreetMap world:

http://www.weeklyosm.eu/archives/7593

*Among others:*


   - Love Mapillary? Read in more for detailed article about using
   Mapillary for mapping in OpenStreetMap with JOSM.
   - Mapbox announces that their map related tools are now free for
   humanitarian response.
   - The State of the Map Working Group (WG SotM) published a paper to the
   topic corporate membership. Source: OSMF-talk
   - Rome based architect and designer Mateo Prati showcases his 3D views
   of Manhattan made with Blender and OpenStreetMap data.
   - Try out the knife-tool for JOSM, which makes splitting ways at an
   arbitrary point a breeze.


Cheers,

Jinal Foflia 
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[Talk-ca] WeeklyOSM 306

2016-06-03 Per discussione Jinal Foflia
The weekly round-up of OSM news, issue #306, is now available online in
English, giving as always a summary of all things happening in the
OpenStreetMap world:

http://www.weeklyosm.eu/archives/7593

*Among others:*


   - Love Mapillary? Read in more for detailed article about using
   Mapillary for mapping in OpenStreetMap with JOSM.
   - Mapbox announces that their map related tools are now free for
   humanitarian response.
   - The State of the Map Working Group (WG SotM) published a paper to the
   topic corporate membership. Source: OSMF-talk
   - Rome based architect and designer Mateo Prati showcases his 3D views
   of Manhattan made with Blender and OpenStreetMap data.
   - Try out the knife-tool for JOSM, which makes splitting ways at an
   arbitrary point a breeze.


Cheers,

Jinal Foflia 
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [OSM-talk] ford=no for highways which are known to have no fords?

2016-06-03 Per discussione Ben Discoe
On Tue, May 31, 2016 at 2:08 PM, Richard  wrote:
>> FWIW, I simply set the following key mapping in JOSM:
>>
>> Shift-D: add bridge=yes, layer=1
>> Shift-C: add tunnel=culvert, layer=-1
>
> nice.. but still need to select or add two nodes, split the
> ways, and select the correct segment before hitting s-d/s-c.

I agree, I always intended to add that to make it easier... so this
evening I took the time to figure it out, and it works great: You can
select a way, or multiple ways, or a way and two nodes, or just two
nodes.  I'll write up a diary post soon with my new powerful script.
:)

-Ben

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


[Talk-in] WeeklyOSM 306

2016-06-03 Per discussione Jinal Foflia
The weekly round-up of OSM news, issue #306, is now available online in
English, giving as always a summary of all things happening in the
OpenStreetMap world:

http://www.weeklyosm.eu/archives/7593

*Among others:*


   - Love Mapillary? Read in more for detailed article about using
   Mapillary for mapping in OpenStreetMap with JOSM.
   - Mapbox announces that their map related tools are now free for
   humanitarian response.
   - The State of the Map Working Group (WG SotM) published a paper to the
   topic corporate membership. Source: OSMF-talk
   - Rome based architect and designer Mateo Prati showcases his 3D views
   of Manhattan made with Blender and OpenStreetMap data.
   - Try out the knife-tool for JOSM, which makes splitting ways at an
   arbitrary point a breeze.


Cheers,

Jinal Foflia 
___
Talk-in mailing list
Talk-in@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-in


Re: [Talk-GB] Schools Project

2016-06-03 Per discussione Christian Ledermann
On 3 June 2016 at 09:02, Ed Loach  wrote:
> Christian asked:
>
>> As schools.mapthe.uk is an import project to osm:
>>
>>  Does the community `buy in` to this approach?
>>  Can I go forward to contacting osm imports?
>>  What would you like to see as improvements?
>>
>> As usual silence counts as approval ;-)
>
> I missed earlier emails on this subject but have had a quick play now. 
> Instructions seem very lacking. Why do I get the option to add an OS OpenData 
> polygon when the school is already mapped? That is likely to lead to 
> duplication.
>

I will add as Gregory sugested:
"The highlighted polygon will be ADDED to OpenStreetMap. If a school
outline is already shown on the base map behind, then you should
manually add the tags (& edubase reference manually) to that object."

If there is anything you want to add to the documentation/input form
your input is very appreciated :-)

> Or is it just because I'm seeing live tiles but we’re using api06 data for 
> comparison?
>
> When I clicked Add to OSM nothing seemed to happen, so I tried again. So I 
> added it twice:
> http://api06.dev.openstreetmap.org/changeset/85444
> http://api06.dev.openstreetmap.org/changeset/85445
>

Yes good point. I think what is needed is to record which features
have been add with this tool and if a feature has been added disable
the 'add to osm' button.


> Why is it adding a simple closed way as a multipolygon relation? Why not put 
> the tags on the way?

Some schools have school grounds that are on either side of a road.
In this case a multipolygon is needed.


If I interpreted
http://wiki.openstreetmap.org/wiki/Relation:multipolygon and
http://wiki.openstreetmap.org/wiki/Area/The_Future_of_Areas
right, a multipolygon is the prefered way of adding an area

> In the example changesets above, it is adding the website key with a blank 
> value. I'm not sure blank values need adding.
>

In the future blank values will be omitted.

> The changesets could probably use "source" tags to show where the data has 
> been added from.

source would be edubase/seed+os-open ?

> When I clicked on "Add to OSM" I thought it might both add the multipolygon 
> and open my default editor to allow me to trace buildings within the polygon, 
> and any other details visible from Bing. Is this possible?

It should be possible to open a new tab/window to edit osm in the
browser - josm is another beast

>
> Ed
>



-- 
Best Regards,

Christian Ledermann

Newark-on-Trent - UK
Mobile : +44 7474997517

https://uk.linkedin.com/in/christianledermann
https://github.com/cleder/


<*)))>{

If you save the living environment, the biodiversity that we have left,
you will also automatically save the physical environment, too. But If
you only save the physical environment, you will ultimately lose both.

1) Don’t drive species to extinction

2) Don’t destroy a habitat that species rely on.

3) Don’t change the climate in ways that will result in the above.

}<(((*>

___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [OSM-talk-be] GRB open data

2016-06-03 Per discussione Glenn Plas
Hey Killian,

On 02-06-16 22:23, Killian De Volder wrote:
> Glenn,
> 
> Geen nood de enige import die ik gedaan heb is diegene die die jij nadien aan 
> het importeren was.
> (Indien zich U het herinnerd, verder heb ik ook de boot afgehouden.)

Oef de pijn is nu over :)  Ik herinner het me idd, je bent vooral actief
in Stekene/Kemzeke hee.   Dat was de test case waarmee ik de tool heb
ontwikkeld omdat daar bijna geen enkel gebouw stond, ik had een streek
nodig om het te testen/ontwikkelen.

> 
> Verder ik ga er vanuit dat er mensen zijn die manueel/semiautomatisch aan het 
> importen zijn.
> Bewijs:
> Ik + Jij (Glenn): http://www.openstreetmap.org/#map=14/51.2189/4.0546
> http://www.openstreetmap.org/way/107808094#map=19/51.07133/4.72699

Yup, Ik kon ook moeilijk anders om te ontwikkelen, waaruit dus bleek dat
er te weinig source data insteekt.   source:entity=* ontbreekt.  Deze is
nodig omdat UUID's niet uniek zijn (Gba, Gbg, Knw... ze kunnen dezelfde
uuid's bevatten).   Tijdens mijn werken op Stekene ben ik erachter
gekomen dat er plots addressen stonden bij import met men tools op
roof's en garage's.  Dus alle gebouwen daar in Stekene moeten nog een
tag bijkrijgen om aan te duiden vanuit welke bron ze komen.

> 
> Verder had bestaande gebouwen heb ik gewoon aangepast.
> "Megablocks" (10 huizen aan elkaar in een slordige import door 3Dshapes) 
> dacht ik wel verwijderd te hebben, of had ik hiervan zoveel mogelijk nodes 
> moeten hergebruiken ?

3Dshapes is meestal rommel , 't was perfect in het prille begin, maar
die dingen zijn achterhaald, van tijd zien ze een vierkant bos als een
building.  Maar dan nog zou je best de plugin gebruiken om geometries te
mergen.

> 
> Maar als jij er mee bezig bent (ook als is het niet op dit moment) is het 
> goed,
> het is niet dat ik (en hopelijk de rest ook) geen geduld heb. Noch zit er 
> druk achter.

Ik ga proberen deze zomervakantie (binnen kleine maand dus) de draad
terug op te pikken en het grootste probleem op te lossen, nml.  Nodes
mergen tussen de entities in de database.  Nu is een roof niet gekoppeld
aan de building omdat ze de nodes niet delen, maar die nodes staan wel
over elkaar, de reden is omdat het gescheiden bronnen zijn, als je dit
importeert krijgen al die nodes aparte id's waardoor ze over elkaar
liggen.  In JOSM kan je dit wel deels fixen,maar dit is echt niet
handig/gemakkelijk.  Vraag maar aan Marc Gemis:  als je met 750
validation warnings op duplicate nodes zit op klein gebied.

> 
> Maar om eerlijke te zijn zou het wel handig zijn als de huisnummers er eens 
> in geraken ;)
> Maar huisnummers vereisen een gebouw tekenen ... welke met de mogelijkheid 
> tot GRB een beetje extra werk lijkt.

De huisnummers komen automatisch mee met de tool ondertussen, ze worden
gematch aan buildings, achteraf moet je wel echt aan de slag met Sanders
zijn tool omdat wat GRB betreft maar 1 adres per building kan bestaan,
de crab toolset heeft hier een grote meerwaarde bij buildings die bv
addressen bevatten van 2 straten (hoekhuizen etc.)

> Is het plan de nummers mee te nemen in deze procedure ?

Dat is al het geval, je kan de popups enablen en dan zie je de
huisnummers.  http://grbtiles.byteless.net/
Die popup kan annoying zijn, maar dit is work in progress, en vooral
handig voor mezelf gemaakt, het uiteindelijk product gaat beter werken.
Beloofd.

Visueel zie je trouwens ook hoe compleet een adres is, de zwarte
contouren op een gebouw worden dikker naarmate je meer addr:* keys hebt
in de data.  Gebouwen zonder zwarte rand hebben geen adres informatie.

> Indien niet het geval, is er een tussen voorlopige manier dat men dit dan 
> best (of gewoon niet) doet ?
> Vierkante huizen die goed aansluiten bij GRB vorm, of gewoon wachten op de 
> huizen ?

Het is in ieder geval gemakkelijker om geen bestaande buildings te
hebben met de semi-automatische import (vermijd je die problemen).  Maar
ik begrijp je drive om die erin te krijgen.

> Ps.: Thanks for osmose !

Np, heel verslavend hee ?  Ik fix ook graag.  Check mss ook deze eens:

http://osmhv.openstreetmap.de/index.jsp

Mvg,

Glenn



> 
> Mvg,
> Killian De Volder
> 
> 
> On 02-06-16 17:44, Glenn Plas wrote:
>> Hallo,
>>
>> Met enige pijn in het hart lees ik dit.
>>
>> Je kan echt nog niet onbezonnen gaan importeren op deze manier.   Voor
>> de volgende redenen alvast:
>>
>>  - Deze semi-automatische import moet goedgekeurd worden en er moet een
>> case voor worden gemaakt.
>>  - gebouwen zijn maar 1 deeltje van de data, er zit veel meer in
>>  - Als je zomaar importeert zonder er over na te denken voor de
>> opvolging, als je buildings in OSM ramt zonder referenties naar GRB op
>> een gestructureerde manier.
>>
>>
>> Als we echt automatische imports hadden gekozen was het nu reeds over,
>> dus er zijn wel degelijk goede redenen om dit niet zo aan te pakken.
>>
>> Je mag bestaande gebouwen niet zomaar wissen.  je moet een josm plugin
>> tool gebruiken om die te mergen zodat historiek niet verloren gaat.
>>
>> 

Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Martijn van Exel
Well said. I have space in my basement also. 

I am eager to launch a MapRoulette challenge for untouched rural ‘residential’ 
roads - a challenge which will probably take some time to complete. If someone 
can furnish a good Overpass query for this, please go ahead and do it.

Martijn

> On Jun 3, 2016, at 8:55 AM, Richard Fairhurst  wrote:
> 
> There is a special corner of hell/Steve's basement for people who remove
> tiger:reviewed=no on rural unpaved roads without changing the highway tag or
> adding a surface tag.

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-it] discutibili cancellazioni, modifiche ed integrazioni

2016-06-03 Per discussione Martin Koppenhoefer
2016-06-01 17:06 GMT+02:00 Paolo Monegato :

> Personalmente non metterei highway=residential ad una strada fuori
> dall'agglomerato urbano. Credo che la soluzione migliore sarebbe
> unclassified, magari aggiungendo il dettaglio surface=*.




+1. Se ti puoi aspettare bambini che giocano, lo vedrei come residential,
se l'aspetto è quello di una strada di campagna, unclassified.

Ciao,
Martin
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [Talk-GB] Schools Project

2016-06-03 Per discussione Ed Loach
Christian asked:

> As schools.mapthe.uk is an import project to osm:
> 
>  Does the community `buy in` to this approach?
>  Can I go forward to contacting osm imports?
>  What would you like to see as improvements?
> 
> As usual silence counts as approval ;-)

I missed earlier emails on this subject but have had a quick play now. 
Instructions seem very lacking. Why do I get the option to add an OS OpenData 
polygon when the school is already mapped? That is likely to lead to 
duplication. 

Or is it just because I'm seeing live tiles but we’re using api06 data for 
comparison?

When I clicked Add to OSM nothing seemed to happen, so I tried again. So I 
added it twice:
http://api06.dev.openstreetmap.org/changeset/85444
http://api06.dev.openstreetmap.org/changeset/85445

Why is it adding a simple closed way as a multipolygon relation? Why not put 
the tags on the way?

In the example changesets above, it is adding the website key with a blank 
value. I'm not sure blank values need adding.

The changesets could probably use "source" tags to show where the data has been 
added from.

When I clicked on "Add to OSM" I thought it might both add the multipolygon and 
open my default editor to allow me to trace buildings within the polygon, and 
any other details visible from Bing. Is this possible?

Ed


___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-de] zur Info: Bicycle=yes/designated als Anzeige Benutzungspflicht aufgeben

2016-06-03 Per discussione Joerg Fischer
Martin Koppenhoefer wrote:

> was haben die Römer je für uns getan?

Sie haben die schönen Straßen über die Alpen gebaut, die wir heute mappen
dürfen.

> Was spricht dagegen, die osm webseite mobil zu betrachten?

Der Datenverbrauch, insbesondere im Ausland.

> Abgesehen davon, dass es egal ist, ob es derzeit bereits eine bestimmte
> Anwendung gibt die einen tag auswertet, oder erst in Zukunft ;-)

Oder niemals. Aber gescheite Darstellung von Rad- und Fußwegen und das
dazugehörige Routing ist ja schließlich nur einer _der_ Vorteile von OSM
gegenüber anderen Kartenanbietern, das kann man schon mal sinnlos kaputt
machen, indem man breite, asphaltierte Radwege als Trampelpfade mappt.  Ist
sicher nicht so wichtig.

Kopfschüttelnde Grüße, Jörg

-- 
There are only 10 types of people in the world:
Those who understand binary, and those who don't...


signature.asc
Description: Digital signature
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de


[OSM-talk-ie] Rectified images

2016-06-03 Per discussione Stephen Roulston
Hello all,

JOSM seems to have changed over the last 24 hours as I can’t now see Irish 
British War Office mapping used for townland boundaries. Instead there is an 
option “Rectified image”. The default imagery layers have also been cleared in 
the preferences. I tried to use the rectified image option to add a link to 
mapwarper (http://mapwarper.net/maps/11918) but it did not work. I have shut 
down JOSM and reopened a number of times with no success. Any ideas?

btw I tried to post on #osm-ie, but I am blocked

Thanks,

Stephen_Co_Antrim



___
Talk-ie mailing list
Talk-ie@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ie


Re: [OSM-talk] Osmose, duplicate housenumber

2016-06-03 Per discussione Martin Koppenhoefer


sent from a phone

> Il giorno 01 giu 2016, alle ore 11:04, Jérôme Seigneuret 
>  ha scritto:
> 
> There is one POI (an unique) with addr:* (this addr poi can be locate on same 
> node as entrance or on building. It depends on choice of schema ) and one or 
> more POI with contact:* . In this case * can be same key=value as addr:* 
> values


a node is a good representation for a spot, but not for a clearly defined area. 
If the housenumber is valid for an area it should be better put on this area, 
and in theory you would only have to put housenumber tags on those objects 
inside this area, that have different values (if any, it's a very rare case) - 
in theory because in a project like osm it can help debugging and quality to 
have the address repeated on a poi (especially if these objects are mapped as 
nodes, whose position is often less obviously off than that of areas. Areas can 
usually/often be associated to features you see in aerial imagery, while this 
is less true for nodes). 

I'm not in favor of using different tags here (contact vs. addr), a housenumber 
is a housenumber, and it is never an object of its own (in the real world), 
it's always a property of something (a site, a house, an apartment, etc.), even 
if in osm this is less clear because most housenumbers are currently tagged on 
nodes with only addressing information, and because routing programs treat 
addresses often as POIs.

cheers,
Martin 



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Richard Fairhurst
Madeline Steele wrote:
> What do you all think about this?

The sine qua non for me is that the absence of a tiger:reviewed= tag (or one
set to =yes) means that you can trust the value of the highway= tag.

This is especially true of rural areas where unreviewed highway=residential
covers a multitude of sins.

There is a special corner of hell/Steve's basement for people who remove
tiger:reviewed=no on rural unpaved roads without changing the highway tag or
adding a surface tag.

cheers
Richard




--
View this message in context: 
http://gis.19327.n5.nabble.com/Best-practices-for-dealing-with-old-TIGER-tags-tp5874640p5874647.html
Sent from the USA mailing list archive at Nabble.com.

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Best practices for dealing with old TIGER tags?

2016-06-03 Per discussione Martijn van Exel
I usually remove all TIGER tags as I update roads. 
Martijn

> On Jun 2, 2016, at 10:59 PM, Madeline Steele  
> wrote:
> 
> Hello all,
> 
> 
> 
> I was hoping to open a discussion on current best practices for dealing with 
> old TIGER tags. I know this has been covered here in the past, but I think 
> it’s been a few years and it seems possible that methods have shifted.
> 
> 
> 
> I’m from Portland (Oregon J) and on many streets, TIGER tags have been 
> completely removed, while on others, people have left only the tiger:county 
> tags. Sometimes, you see tiger:zip_left and tiger:zip_right too, while in 
> other cases there are zip_left and zip_right keys instead. In many cases, the 
> following 6 TIGER tags remain: tiger:cfcc, tiger:county, tiger:name_base, 
> tiger:reviewed, tiger:zip_left, and tiger:zip_right.
> 
> 
> 
> The approach that is preferred at TriMet (where I work) is that if we are 
> able to check the geometry of the street against fairly recent imagery 
> (improving it if needed) and verify the name of the street, from either our 
> local jurisdictional centerlines or the latest TIGER TMS layer, then we 
> remove all of the TIGER tags. We see that as being adequate to remove the 
> TIGER:reviewed tag (especially when multiple mappers have edited the way 
> since the initial import, which is typical). We think that the other TIGER 
> tags are not needed as they’re mostly comprised of information that isn’t 
> really appropriate for the street ways (zip code and county, which take up 
> less space and are easier to keep up-to-date when maintained as separate 
> boundary polygons) and attributes that can be derived from other fields 
> (e.g., prefix, basename, suffix). While it could be handy to have these 
> address components broken out, it adds bulk and requires updating several 
> fields when a name is changed. Further, the TIGER attributes are mostly 
> really outdated at this point as they come from 2005 data and have rarely 
> been updated by mappers.
> 
> 
> 
> What do you all think about this?
> 
> 
> 
> Thanks much,
> 
> 
> 
> Madeline
> 
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [OSM-talk] Osmose, duplicate housenumber

2016-06-03 Per discussione Martin Koppenhoefer


sent from a phone

Il giorno 01 giu 2016, alle ore 10:16, althio  ha 
scritto:

>> Can you explain why Osmose (and does it matter at all) warns about
>> duplicate housnumber when a shop (node) with a set of addr:* tags is
>> created inside a building (area) that is also tagged with addr:*?
> 
> 
> Osmose seems to follow the rule: One feature, one OSM element (or one 
> feature, one tag) and avoids duplicating data.


this "rule" is mostly moot, as it is not clear what a "feature" is (e.g. as 
opposed to a property). Also: "one tag" are often more than one tags (on the 
same object)

cheers,
Martin ___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk