[talk-latam] Fw: [OSM-talk] Apply for a Humanitarian OpenStreetMap Microgrant

[Marco Antonio]

publicación de HOTOSM llamando a quienes quieran postular a
subvenciones para incentivar y fortalecer las comunidades locales.

son como 2000 a 5000 USD, abajo todos los detalles.

abrazos,

Marco Antonio
@51114u9

/

Begin forwarded message:

Date: Fri, 3 Feb 2017 18:08:39 +
From: Rebecca Firth 
To: t...@openstreetmap.org
Subject: [OSM-talk] Apply for a Humanitarian OpenStreetMap Microgrant


Hi All,


This week, we’re excited to launch the Humanitarian OpenStreetMap Team
(HOT) Microgrants programme

!

Many OSM communities around the world are achieving amazing results on
zero or near-zero budgets. HOT wants to support the development of these
communities, through providing funding for basics. For example, GPS
devices, internet access, and training costs. We're looking to provide
up to ten Microgrants between $2,000 - $5,000 USD. Our goal is to
enable the development of local OSM communities, to increase skills,
capacity and experience. We will award grants to projects which broadly
contribute to HOT's mission.

More details on the programme and the application form can be found here
.
HOT support will be provided before, during and after the grants period.
Applications must be received by 12th March 2017.

Please share this to individuals or organisations who might be
interested to apply. We are looking to support communities in Southeast
Asia, South Asia, Latin America/Caribbean and Africa, but will consider
other locations.

Get in touch with any questions, or email microgra...@hotosm.org.

Thanks,

Rebecca

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

[OSM-talk-fr] changement de tag automatique par en France par un contributeur allemand

[Philippe Verdy]

Je vois des changesets comme
https://www.openstreetmap.org/way/42862082

où massivement/automatiquement les tags de références "wikipedia=fr:*" sont
remplacés par un tag non discuté "subject:wikipedia=fr:*"

Je n'ai jamais vu une telle décision de changement, et ce namespace
"subject:" ne correspond à rien. Cela est fait par lui sur divers objets de
tous types (sans réfléchir, visibment de façon totalement automatique)
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[Talk-cz] Kontrola schématu hromadné dopravy

[Jan Macura]

Ahoj,

padlo to na posledním qartálním pivě v Plzni a teď jsem to náhodou našel.
Takže pro všechny, které to zajímá: tenhle nástroj vykreslí libovolnou
linku MHD zmapovanou pomocí nového schématu jako graf.

http://www.overpass-api.de/public_transport.html

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

Re: [Talk-GB] Propose automated edit to update NAPTAN data in the west mids

[Michael Booth]

On a related note, what is the process for getting an import in places 
that don't already have NAPTAN data? I'd be interested in having bus 
stops in Fife imported.


On 03/02/2017 17:52, Brian Prangle wrote:

Hi everyone

We have an opportunity to work with the regional transport authority 
TfWM to update this data which is 8 years old and partially edited by 
OSM users. They have assigned 2 developers to work on this and I'm 
spending a half day each week working with them.


We've agreed and discussed this in our mappa mercia group and also 
contacted a prolific local public transport OSM editor who's not part 
of  our group.


In line with the automated edits policy there's a wikipage 
 
with full details


Comments welcome as this exercise might be useful elswhere as the 
state of NAPTAN data will be in a similar state


regards

Brian


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



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

Re: [OSM-talk] OSM for government

[Michael Andersen]

On fredag den 3. februar 2017 14.44.47 CET joost schouppe wrote:
> Hi,
> 
> With the Belgian community, we're making some careful progress into getting
> government to really integrate OSM/VGI into their data management efforts.
> So not talking about background maps here, real data contribution or
> community engagement.
> 
> There are some very specific issues and opportunities there. I believe the
> Canadian Census is going that way. Are there any other projects in this
> direction? Is there anything like a project catalogue around?

An employee of the Viborg municipality (http://www.openstreetmap.org/relation/
1926898) working on a public "traffic security project" recently added maxspeed 
tags to all roads of his municipality based on data owned by the municipality. 
I spent some time cleaning up after his initial attempts as well guiding him 
the best I could. His plan is to proceed to add maxspeed data to all public 
roads in Denmark and just last night he posted on the danish OSM mailing list 
asking whether there's any way to automatically add all this data (of course 
receiving a bunch of responses to the contrary).

Nordfyn municipality (http://www.openstreetmap.org/relation/2178137) sees 
potential in using OSM for a public project classifying cycleways and footways 
etc based on an internal classification system planned to be used all over 
Denmark. I had to practically roll back their initial attempt (how come they 
are getting employees with practically no computer experience save OSM ditto 
to do stuff like this?) , but I am currently in contact with them and will be 
guiding them as they proceed (they started adding some data again today).

At least 2 public danish bus companies are using OSM for routing (I have been 
in contact with both of them) and both have been adding data to OSM in order 
to aid their efforts.

A long time member of the danish community http://www.openstreetmap.org/user/
Hammershoej is maintaining cycling routes in Denmark on behalf of the national 
danish road administration (based on data he's getting from them).

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

Re: [Talk-cz] OsmHiCheck - nevyuzite fotky

[Marián Kyral]

Dne 31.1.2017 v 09:29 Tom Ka napsal(a):
> Ahoj,
>
> stravil jsem dost casu uklidem nevyuzitych fotek - otagovano spousta
> fotek typu infopanel apod., doplneny chybejici REF do DB aby fungovalo
> parovani nepouzitych fotek. Celkem jsme z puvodnich 1060 na 673 coz je
> pekne :-)
>
> Doplnil jsem i statistiky nevyuzitych fotek podle autora, zkuse se
> mrknout a dostat svuj radek na 0 :-D
>
> http://osm.fit.vutbr.cz/OsmHiCheck/gp/?img  (uplne dole)
>
>

Ahoj,
projel jsem svých 10 fotek a našel jsem dvě duplicity  a jedno starší
provedení rozcestníku:
https://api.openstreetmap.cz/openid/ref/VS244

Vypadá to, že se zároveň změnilo i umístění rozcestníku (sloup vs.
samostatný sloupek), takže zřejmě došlo i k přesunu a fotka je teď dále
než 20 metrů a zobrazuje se jako chybná. Ten rozcestník není zrušený,
jen byl nahrazen novější verzí a bylo upraveno umístění. Takže jej
nechci posunout (původně byl jinde) a nehodí se pro něj štítek
"zruseno". Spíše bych to viděl na něco jako "nahrazeno" nebo
"zastarale". Mohl by jsi nějaký takový štítek přidat k těm, co se
přeskakují?

A pro označení duplicit by se hodilo přidat i štítky "duplicita" a "smazat".

A možná by nebylo od věci přidat volbu zda preferuji openid a v tom
případě by se mi odkazy do api otevíraly jako
https://api.openstreetmap.cz/openid... (namísto
http://api.openstreetmap.cz/table...). Ta volba by se mohla uložit do
cookies.

Díky,
Marián


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

Re: [Talk-us] Blue Ridge Parkway

[Mike Thompson]

On Tue, Jan 31, 2017 at 2:46 PM, Frederik Ramm  wrote:

>   I added the takeaway from this discussion to the wiki:
>
> https://wiki.openstreetmap.org/w/index.php?title=Tag%
> 3Aboundary%3Dnational_park=revision=1424102=1373291
>
> Feel free to amend as necessary.
>
> I made an amendment to state that one of the purposes of a national park
may be to protect the cultural heritage of an area.
https://wiki.openstreetmap.org/w/index.php?title=Tag%3Aboundary%3Dnational_park=revision=1425148=1424249
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-br] Estranho changeset duplicando estradas já existentes

[Daniel d'Andrada Tenório de Carvalho]

Alguém entende o que exatamente ocorreu aqui?

http://openstreetmap.org/browse/changeset/45763739

Bug no editor Potlatch?
___
Talk-br mailing list
Talk-br@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-br

semanarioOSM Nº 341 24/01/2017-30/01/2017

[weeklyteam]

Hola, el semanario Nº 341, 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/8683/

¡Disfruta!

semanarioOSM?
¿Dónde?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
¿Quién?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-cu mailing list
Talk-cu@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cu

semanarioOSM Nº 341 24/01/2017-30/01/2017

[weeklyteam]

Hola, el semanario Nº 341, 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/8683/

¡Disfruta!

semanarioOSM?
¿Dónde?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
¿Quién?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

semanarioOSM Nº 341 24/01/2017-30/01/2017

[weeklyteam]

Hola, el semanario Nº 341, 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/8683/

¡Disfruta!

semanarioOSM?
¿Dónde?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
¿Quién?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-cl mailing list
Talk-cl@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cl

semanarioOSM Nº 341 24/01/2017-30/01/2017

[weeklyteam]

Hola, el semanario Nº 341, 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/8683/

¡Disfruta!

semanarioOSM?
¿Dónde?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
¿Quién?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-co mailing list
Talk-co@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-co

Re: [OSM-talk] OSM for government

[Tomas Straupis]

Hello

2017-02-03 15:44 GMT+02:00 joost schouppe wrote:
> With the Belgian community, we're making some careful progress into getting
> government to really integrate OSM/VGI into their data management efforts.
> So not talking about background maps here, real data contribution or
> community engagement.

 Here's a general idea what we're doing in Lithuania.

  Government has datasets d1, d2... dn. OSM has one big dataset O
which could be split into datasets o1, o2... om. We take datasets dx
and oy which could be mapped (have similar data, like placenames,
roads, lakes, rivers, etc.)

  Automated importing to either direction is impossible (or not wanted
by both sides). Government datasets need strict accountability
(sources, documents) and responsibility. OSM has different data and
simply overwriting it with government data would be bad in a lot of
ways.

  So the way integration between OSM and government (and actually any
other datasets) is done is by synchronisation - checking for
differences and taking action (mostly manual) on them on both
datasets. By doing a comparison both government and OSM datasets are
improved. The point here is that government datasets usually use
official (document) source to update data. OSM uses local knowledge to
update data. None of these methods are perfect, so
synchronisation/comparison helps to get most/best of both.
  (as a separate note: here comes OSM strength that everything is in
one layer - it is much harder to have a road going through a lake or
building or having a street A with address B along it. Government
datasets are usually separate and controlled by different
institutions, so doing such topology checks is much more difficult
there)

  For this to work government must open datasets and appoint a working
contact point where information about problems in government dataset
could be sent and there this information is ACTUALLY used and feedback
given.

-- 
Tomas

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

Re: [Talk-it] OSMit2017 a Genova 8-11 febbraio in FOSS4G

[Alessandro Palmas]

  
  
Ad oggi siamo vicini ai 300 iscritti, 211 dei quali alle due
  giornate di talk. Tra poco dovremo chiedere alla gente di restare
  a casa :-)

Ecco la locandina!

https://pbs.twimg.com/media/C3xD2FkXUAAjHj8.jpg
Sarebbe bello fare una foto in stile SOTM nel giardino della
  villa.

Alessandro Ale_Zena_IT
  


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

[OSM-talk] OpenStreetCam plugin

[James]

I've noticed that the arrow for each segment seems to be a bit random and
not actually pointing in the direction the camera is pointed in which can
make it hard to determine which imagery is which
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-at] Schreibweise der Straßennamen

[Friedrich Volkmann]

On 03.02.2017 18:35, Borut Maricic wrote:

Ich führe gleich die folgende Nomenklatur ein:
  Name Familienname Straße = nfs
Davon leiten sich die zwei Schreibweisen ab:
  n-f-s bzw. n f-s


Ich würde die Abkürzung "v" statt "n" verwenden, denn der Name besteht aus 
Vor- und Familienname.


Die Regel ist ganz einfach:
ohne Vorname: Maiergasse (evtl. auch: Maier-Gasse)
mit Vorname: Franz-Maier-Gasse oder Franz Maier-Gasse

Zum Vergleich: Wenn eine Straße nach einem Ort benannt ist, wird der 
Straßenname meist ohne Bindestrich auseinander geschrieben (Wiener Straße), 
damit man erkennen kann, ob die Straße nach dem Ort Wien oder nach Hugo 
(oder Zelko...) Wiener benannt ist. Irrtümliche Zusammenschreibungen sind 
aber nicht unüblich, und manche Gemeinden haben sich sogar bewusst für die 
Zusammenschreibung entschieden, damit sich die Namen leichter auf den 
Straßentafeln ausgehen ("Mariazellerstr." ist kürzer als "Mariazeller Str.").


Der Duden-Verlag hat seit der Rechtschreibreform 1996 nicht mehr das Monopol 
über die Regeln der deutschen Sprache, und für Österreich hatte das 
Österreichische Wörterbuch sowieso schon immer Priorität. In dessen 35. 
Auflage) steht:


--- Zitat Anfang ---
3.4.2 Straßennamen und geographische Namen

3.4.2.1 Einteilige Namen werden in der Regel mit dem Grundwort 
zusammengeschrieben, zusammengesetzte (mehrgliedrige) jedoch getrennt, wobei 
die einzelnen Wörter durch Bindestriche verbunden sind. Diese Regelung wird 
örtlich verschieden gehandhabt. In Wien z.B. steht in mehrteiligen Namen ein 
Bindestrich nur zwischen dem Grundwort und dem unmittelbar vorhergehenden 
Wort (Namen). Immer gesetzt muss der Bindestrich allerdings werden, wenn er 
Bestandteil des Namens ist, z.B. in Ebner-Eschenbach-Allee [...]


[Beispiele für] Getrenntschreibung:
Theodor-Körner-Straße (in Wien: Theodor Körner-Gasse); 
Abraham-a-Sancta-Clara-Gasse (in Wien: Abaraham a Sancta Clara-Gasse).

--- Zitat Ende ---

Das Problem mit der "Theodor Körner-Gasse" ist, dass der Bindestrich stärker 
bindet (auch visuell) als das Leerzeichen, und dadurch sieht es aus, als 
wäre Theodor der Vorname der Körner-Gasse. Tatsächlich ist Theodor aber der 
Vorname von Körner. "Gasse" ist das Grundwort, "Theodor Körner" das 
zusammengesetzte Bestimmungswort. Der Bindestrich zwischen Theodor und 
Körner hebt die Bindung, verändert jedoch auch das Bestimmungswort. D.h. 
beide Schreibweisen haben jeweils einen Nachteil.


Im Zweifelsfall sollte man den Namen so taggen, wie er auf den Straßentafeln 
steht (abgekürzte Vornamen aber ausschreiben!), außer wenn dort ein 
offensichtlicher Irrtum passiert ist (kommt vor). Wenn verschiedene 
Schreibweisen üblich sind, kann man die andere(n) in alt_name=* setzen.


In den Lehrbüchern noch nicht erwähnt ist, dass die Werbebranche mit ihren 
Deppenleerzeichen schon die Behörden angesteckt hat, und so kommen amtliche 
Autobahn- und Landesstraßennamen wie "Süd Autobahn". Da diese Namen aber auf 
keinen Straßentafeln stehen, sondern nur im Gesetz, gehören in OSM die 
üblichen Schreibweisen (Südautobahn) in name=* und die amtlichen 
Falschschreibungen höchstens in official_name=*. Und im Fall von 
Landesstraßen gehören diese Tags nur auf die Routenrelationen, denn auf die 
Ways direkt kommen die Gemeinde-Straßennamen.


--
Friedrich K. Volkmann   http://www.volki.at/
Adr.: Davidgasse 76-80/14/10, 1100 Wien, Austria

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

[Talk-GB] weeklyOSM #341 24/01/2017-03/02/2017

[weeklyteam]

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

http://www.weeklyosm.eu/en/archives/8683/

Enjoy!

weeklyOSM?
who?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

[Talk-in] weeklyOSM #341 24/01/2017-03/02/2017

[weeklyteam]

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

http://www.weeklyosm.eu/en/archives/8683/

Enjoy!

weeklyOSM?
who?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-in mailing list
Talk-in@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-in

[Talk-ca] weeklyOSM #341 24/01/2017-03/02/2017

[weeklyteam]

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

http://www.weeklyosm.eu/en/archives/8683/

Enjoy!

weeklyOSM?
who?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

[OSM-talk] weeklyOSM #341 24/01/2017-03/02/2017

[weeklyteam]

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

http://www.weeklyosm.eu/en/archives/8683/

Enjoy!

weeklyOSM?
who?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[Talk-us] weeklyOSM #341 24/01/2017-03/02/2017

[weeklyteam]

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

http://www.weeklyosm.eu/en/archives/8683/

Enjoy!

weeklyOSM?
who?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

hebdoOSM Nº 341 24/01/2017-30/01/2017

[weeklyteam]

Bonjour,

Le résumé hebdomadaire n° 341 de l'actualité OpenStreetMap vient de paraître en 
français. Un condensé à retrouver à:

http://www.weeklyosm.eu/fr/archives/8683/

Bonne lecture!

hebdoOSM?
Qui?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

hebdoOSM Nº 341 24/01/2017-30/01/2017

[weeklyteam]

Bonjour,

Le résumé hebdomadaire n° 341 de l'actualité OpenStreetMap vient de paraître en 
français. Un condensé à retrouver à:

http://www.weeklyosm.eu/fr/archives/8683/

Bonne lecture!

hebdoOSM?
Qui?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

semanárioOSM Nº 341 24/01/2017-03/02/2017

[weeklyteam]

Bom dia,

O semanárioOSM Nº 341, o resumo de tudo o que acontece no mundo OpenStreetMap, 
está publicado em português:

http://www.weeklyosm.eu/pb/archives/8683/

Aproveite!

semanarioOSM?
Quem?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Onde?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-br mailing list
Talk-br@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-br

semanárioOSM Nº 341 24/01/2017-03/02/2017

[weeklyteam]

Bom dia,

O semanárioOSM Nº 341, o resumo de tudo o que acontece no mundo OpenStreetMap, 
está publicado em português:

http://www.weeklyosm.eu/pb/archives/8683/

Aproveite!

semanarioOSM?
Quem?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Onde?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-pt mailing list
Talk-pt@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-pt

Re: [Talk-us] Combined parking/bike lanes

[Harald Kliems]

Bradley, in colder climates the difference is more than aesthetic. A lot of
these bike become unusable for people riding bikes in the winter because
they don't get fully plowed to the curb and then parked cars take up the
whole remainder of the lane. Admittedly, this often also happens where
there is a striped bike lane, but the paint seems to keep the bad parking
somewhat in check. Example, also from Madison, of painted separation
between bike lane and parking:
https://www.mapillary.com/map/im/915muSHHc8hk1qgOe6eDlA You can see that
some cars on the left are encroaching to some extent, but it's much better.
But yeah, not sure what a good solution for tagging is.

 Harald.

On Fri, Feb 3, 2017 at 12:12 PM Bradley White 
wrote:

> > Hi all. Has anyone worked out a good tagging scheme for combined
> > bike/parking lanes? I'm not sure how common they are elsewhere but there
> > are a number of such facilities in my city.
> >
> > For reference, you can see an example here:
> >
> https://www.mapillary.com/app/?lat=43.06056159=-89.45121134=17=XByvWxyrk9quLK-noyoB5g=photo=mapbox_streets
> > Notice the bike lane sign above the speed limit sign and the cars parked
> on
> > the side. These are also accompanied with pavement markings indicating it
> > is a bicycle facility. In effect it's like a regular bike lane next to a
> > parking lane, but there's no stripe to separate the two.
>
> These types of lanes are relatively common in parts of northern
> California as well; since the physical space is still set aside for
> both parking and cycling, and the only difference is the inner line of
> paint (which is more a "stylistic" choice on part of the agency), I'm
> not convinced this needs special tagging. The tags suggested earlier
> are what I would use:
>
> > parking:lane:(right/left) = parallel
> > cycleway:(left/right) = lane
>
> ___
> 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-GB] Propose automated edit to update NAPTAN data in the west mids

[Stuart Reynolds]

Hi Brian,

If you are updating the data in OSM from NaPTAN, then I agree that this is long 
overdue.

For the benefit of others, can I just mention some specific stop point types 
that are in NaPTAN that editors may be unfamiliar with (and which I think have 
caused some confusion in the past):


  *   CUS are Custom and Practice stops. Typically ends of farm roads, lay-bys, 
etc where there is no physical marked stop. Given a need to have stopping 
points on the right side of the road, these are also used for the “other side 
of the road” stop where there is a pole marked “buses stop both sides”
  *   HAR are virtual stops denoting a nominal point in a hail and ride 
section. Hail and Ride is a bit cumbersome, but there is a virtual stop and it 
is linked to a start coordinate for the hail and ride section and an end 
coordinate. These aren’t supposed to be long. Typically there will need to be 
one in each direction (as the start and end points are reversed).

Also, there is often some confusion about what name goes into which fields - 
people will insist on compounding names, for example, because that’s what their 
consuming system wants, rather than getting the consumer to read the data 
properly. But that’s too much to go into here, and if reviewing the names is in 
scope then I would be happy to offer to help. One of my other “hats" is as the 
Public Transport Data Standards Advisor / Expert for DfT, which includes 
advising on NAPTAN.

Regards,
Stuart Reynolds
for traveline south east & anglia



On 3 Feb 2017, at 17:52, Brian Prangle 
> wrote:

Hi everyone

We have an opportunity to work with the regional transport authority TfWM to 
update this data which is 8 years old and partially edited by OSM users. They 
have assigned 2 developers to work on this and I'm spending a half day each 
week working with them.

We've agreed and discussed this in our mappa mercia group and also contacted a 
prolific local public transport OSM editor who's not part of  our group.

In line with the automated edits policy there's a 
wikipage
 with full details

Comments welcome as this exercise might be useful elswhere as the state of 
NAPTAN data will be in a similar state

regards

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

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

Re: [OSM-talk] OSM for government (joost schouppe)

[john whelan]

We have something similar in Ottawa, three bits of Government, Gatineau,
Ottawa and a federal body called the NCC.  Each have their own maps that
overlap of their paths for cyclists.  OSM is more complete than anything
but all three do have Open Data with I understand designated cycle paths.
They are difficult to map as many are not signed specifically for cyclists.

Cheerio John

On 3 February 2017 at 13:13, Volker Schmidt  wrote:

> I cannot contribute cases where such a collaboration actually happened,
> but two very practical examples where it would be extremely useful.
>
> Both regard bicycle aspects of OSM.
>
> In my part of the world (Italy) the regional administration has no
> region-wide data on
> - cycling infrastructure (bicycle paths and lanes)
> - signposted touristic bicycle routes
>
> OpenStreetMap has much of this data already, it's not complete and it's
> not always up-to-date, but it is far better than what the regional
> administration has. I am trying to push this as a joint project of bicycle
> associations and OSM individuals.
>
> Volker
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-at] Schreibweise der Straßennamen

[realadry]

Hallo,

In Wien legt die "Wiener Nomenklaturkommission" [1] die richtige 
Schreibweise fest. Normalerweise ist die jeweilige Gemeinde für die 
Vergabe der Namen zuständig und damit auch für die korrekte Schreibweise.


In OSM sollte der offizielle Name (und Schreibweise) gemapped werden. 
Was z.b. auf einem Hausnummernschild steht ist relativ egal, denn das 
Schild selbst kann sich jeder anfertigen inkl. Schreibfehlern.



https://www.wien.gv.at/kultur/archiv/nomenklaturkommission.html
Am 03.02.2017 um 18:35 schrieb Borut Maricic:

Ich führe gleich die folgende Nomenklatur ein:
  Name Familienname Straße = nfs
Davon leiten sich die zwei Schreibweisen ab:
  n-f-s bzw. n f-s

Duden sagt auf [1]: "[...] Abweichende Einzelfestlegungen
durch die jeweils zuständigen Behörden kommen jedoch
vor.[...] 3. Straßennamen, die mit mehrteiligen Namen
zusammengesetzt sind, schreibt man mit Bindestrichen <§ 50>.
Georg-Büchner-Straße[...]"

Ich beteiligte mich vor kurzem an einem kleinen, angenehmen
und privaten Meinungsaustausch über das Thema. Anschließend
dachte ich mir: "OK, letztendlich gilt "We map what we see",
also ab in die Stadt... - dies wird ja dann mein
Superargument sein!"

Oje, vorsicht - was folgt wird nicht angenehm! Name dieser
Stadt ist hier nicht von Bedeutung, wobei die Beispiele, die
folgen, echt sind. Alles spielt sich innerhalb eines Kreises
von ca. 200m Durchmesser ab.

Nehmen wir an:
Erzherzog Johann Straße = ejs
Max Tendler Straße = mts
Peter Tunner Straße = pts
(Kaiser) Franz Josef Straße = fjs

Hausnummer-Tafel = HT
Straßennamen-Tafel = ST

Survey vor Ort ergab...

Für ejs:
HT: anscheinend alle e-j-s
ST: alte e-j-s; neuere e j-s
(sogar an einer Kreuzung gemischt!)

Für mts:
HT: anscheinend alle m-t-s
ST: anscheinend alle m-t-s (auch neuere, sic!)

Für pts:
HT: keine Ahnung - bin nicht soweit gegangen
ST: p t-s (habe aber nicht viele gesehen)
(An einer Säule ist sogar diese Kombination zu
sehen (sic!): m-t-s + p t-s

Für fjs:
HT: anscheinend überall f j-s
ST: keine Ahnung - bin nicht soweit gegangen

basemap.at verwendet für alle vier die "n f-s"-Kombination.

Äh? Bitte, an was soll sich ein armer OSM-Mapper hier
berufen? Ich bitte um Entschuldigung, wenn dies eventuell
Länge-mal-Breite schon diskutiert wurde, was mir nicht
bekannt ist.

Gibt es eventuell ein OSM-at-Konsens über die Vorgehensweise
in solch einer Situation? Wäre ein Konsens eventuell
möglich? Eventuell doch nach Duden (n-f-s)? Oder wie?

[1] http://www.duden.de/sprachwissen/rechtschreibregeln/strassennamen


___
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] tagging rumble-strip-separated road shoulders

[Spencer Gardner]

shoulder(left/right)=yes
shoulder:(left/right):rumble_strip=yes

Would make sense to me.

Just a side note that rumble strips are decidedly not better for cyclists
if the shoulder is narrow enough that the cyclist is left with insufficient
space to navigate without riding over them. It might be good to note the
shoulder width in such cases.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [OSM-talk-be] a new National Mapathon - call for volunteers

[Jo]

I already confirmed to the organiser at KU Leuven, that I'll help out there.

I wouldn't mind extra help, of course!

I'll also figure out whether it's possible to boot the computers in the
class rooms with USB sticks so we can use Linux on them. My preference is
to explain JOSM to the participants. This worked very well last time.

Cheers,

Polyglot








2017-02-03 13:50 GMT+01:00 Jonathan Beliën :

> Hello Joost,
>
>
>
> I’ll be avaibalble the whole day in Brussels (could be in ULB or VUB).
>
>
>
> I can be « around » and help people ;
>
> and validate when nobody needs my help (bouhouho…)
>
>
>
> If I can avoid giving the introduction, I would prefer but if necessery I
> can (try to) do that too !
>
>
>
> \o/
>
>
>
> Jonathan Beliën
>
> GEO-6
>
>
>
> *De :* joost schouppe [mailto:joost.schou...@gmail.com]
> *Envoyé :* vendredi 3 février 2017 08:40
> *À :* OpenStreetMap Belgium 
> *Objet :* [OSM-talk-be] a new National Mapathon - call for volunteers
>
>
>
> Hi,
>
>
>
> Last year, the Interuniversity National Mapathon was a great success:
> about 200 people in seven universities participated, and we got in the 7 pm
> news issue of both VRT and VTM.
>
> OSM-Be volunteers supported all seven events.
>
>
>
> The next national mapathon is being planned right now, and they want our
> help again!
>
>
>
> We will need volunteers at ULB (Brussels), VUB (Brussels), UCL
> (Louvain-la-Neuve), KUL (Leuven), Ugent, ULG (Liege), UNamur. Four more
> cities might still join in the following days.
>
>
>
> Previous experience with humanitarian mapping, iD and the Tasking Manager
> is of course welcome, but we will give you some training too. Last year, it
> wasn't easy finding volunteers for all places, but it is important that
> there is an experienced mapper at all of these places.
>
>
>
> Basically we need you for any or all of these tasks:
>
> - give an introduction about (humanitarian) OSM, a short training
>
> - just being around and helping people with questions
>
> - validating (even from home) during the event, so we can correct newbie
> mappers before they make the same mistake a thousand times
>
>
>
> Just send me a mail with your preferred tasks and city (or cities) and
> we'll be in touch.
>
>
>
> --
>
> Joost Schouppe
>
> OpenStreetMap  |
> Twitter  | LinkedIn
>  | Meetup
> 
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk] OSM for government

[Oleksiy Muzalyev]

Hi,

The website of the Stockholm Public Transport company website: 
http://sl.se/en/ is based on the OSM.


I do not know if they contribute, but the website is really effective. 
I  used it daily recently while in Stockholm, both on a computer and a 
smartphone. The Stockholm Public Transport company is owned by the 
Stockholm County Council (1). In fact, it is the most efficient public 
transport system I ever saw, not only the website, but also electronic 
ticketing, punctuality, etc. But website is a central part. Everything 
is build around it. It even shows in real time minutes before a train or 
bus arrives, also connections, etc.


However, the most impressive is that a bus stop is shown on the map 
where it is really located. So I could find a bus stop without asking 
passersbys. I mean sometimes knowing that a bust stop is on some square 
is not enough, as there could be several ones in different places of 
this square.


(1) https://en.wikipedia.org/wiki/Public_transport_in_Stockholm

Best regards,
Oleksiy


On 03.02.2017 14:44, joost schouppe wrote:

Hi,

With the Belgian community, we're making some careful progress into 
getting government to really integrate OSM/VGI into their data 
management efforts. So not talking about background maps here, real 
data contribution or community engagement.


There are some very specific issues and opportunities there. I believe 
the Canadian Census is going that way. Are there any other projects in 
this direction? Is there anything like a project catalogue around?


--
Joost Schouppe
OpenStreetMap  | 
Twitter  | LinkedIn 
 | Meetup 




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



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

Re: [OSM-talk] OSM for government (joost schouppe)

[Volker Schmidt]

I cannot contribute cases where such a collaboration actually happened, but
two very practical examples where it would be extremely useful.

Both regard bicycle aspects of OSM.

In my part of the world (Italy) the regional administration has no
region-wide data on
- cycling infrastructure (bicycle paths and lanes)
- signposted touristic bicycle routes

OpenStreetMap has much of this data already, it's not complete and it's not
always up-to-date, but it is far better than what the regional
administration has. I am trying to push this as a joint project of bicycle
associations and OSM individuals.

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

Re: [Talk-us] Combined parking/bike lanes

[Bradley White]

> Hi all. Has anyone worked out a good tagging scheme for combined
> bike/parking lanes? I'm not sure how common they are elsewhere but there
> are a number of such facilities in my city.
>
> For reference, you can see an example here:
> https://www.mapillary.com/app/?lat=43.06056159=-89.45121134=17=XByvWxyrk9quLK-noyoB5g=photo=mapbox_streets
> Notice the bike lane sign above the speed limit sign and the cars parked on
> the side. These are also accompanied with pavement markings indicating it
> is a bicycle facility. In effect it's like a regular bike lane next to a
> parking lane, but there's no stripe to separate the two.

These types of lanes are relatively common in parts of northern
California as well; since the physical space is still set aside for
both parking and cycling, and the only difference is the inner line of
paint (which is more a "stylistic" choice on part of the agency), I'm
not convinced this needs special tagging. The tags suggested earlier
are what I would use:

> parking:lane:(right/left) = parallel
> cycleway:(left/right) = lane

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

[OSM-talk] Apply for a Humanitarian OpenStreetMap Microgrant

[Rebecca Firth]

Hi All,


This week, we’re excited to launch the Humanitarian OpenStreetMap Team
(HOT) Microgrants programme

!

Many OSM communities around the world are achieving amazing results on zero
or near-zero budgets. HOT wants to support the development of these
communities, through providing funding for basics. For example, GPS
devices, internet access, and training costs. We're looking to provide up
to ten Microgrants between $2,000 - $5,000 USD. Our goal is to enable the
development of local OSM communities, to increase skills, capacity and
experience. We will award grants to projects which broadly contribute to
HOT's mission.

More details on the programme and the application form can be found here
.
HOT support will be provided before, during and after the grants period.
Applications must be received by 12th March 2017.

Please share this to individuals or organisations who might be interested
to apply. We are looking to support communities in Southeast Asia, South
Asia, Latin America/Caribbean and Africa, but will consider other locations.

Get in touch with any questions, or email microgra...@hotosm.org.

Thanks,

Rebecca

-- 
*Rebecca Firth*
Community Partnerships Manager
rebecca.fi...@hotosm.org 
@RebeccaFirthy
Skype: rebeccafirth

*Humanitarian OpenStreetMap Team*
*Using OpenStreetMap for Humanitarian Response & Economic Development*
web  | twitter  | facebook
 | donate 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-us] tagging rumble-strip-separated road shoulders

[Volker Schmidt]

Hi Paul
Thanks for the quick reaction - I knew you would reply.

>
> Well, the shoulder wouldn't count as a lane (a bicycle lane would,
> however).  Not quite sure how to tag the bicycle use shoulder case (though
> I am aware that it is extremely common in the US), but if it were an
> actual, bicycle-only lane instead, assuming three lanes on a side with the
> right lane being bicycle only, and signage indicating that bicycles must
> use the bicycle lane:
>
> lanes=3
> oneway=yes
> cycleway=lane
> motor_vehicle:lanes=yes|yes|no
> bicycle:lanes=no|no|designated
>

This does not reflect the real situation, which is the presence of an
emergency stop lane for motor vehicles, which may be used by bicycles. It
is different from a dedicated cycle lane, which is what your tagging
describes.  I have seen and ysed a number of bicycle lanes in the US that
"deserve" your tagging.
The shoulder=yes tag is being used a lot in combination with bicycle=yes
http://overpass-turbo.eu/map.html?Q=%2F*%0AThis%20has%20been%20generated%20by%20the%20overpass-turbo%20wizard.%0AThe%20original%20search%20was%3A%0A%E2%80%9Cshoulder%3Dyes%20and%20bicycle%3Dyes%E2%80%9D%0A*%2F%0A%5Bout%3Ajson%5D%5Btimeout%3A25%5D%3B%0A%2F%2F%20gather%20results%0A(%0A%20%20%2F%2F%20query%20part%20for%3A%20%E2%80%9Cshoulder%3Dyes%20and%20bicycle%3Dyes%E2%80%9D%0A%20%20node%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A%20%20way%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A%20%20relation%5B%22shoulder%22%3D%22yes%22%5D%5B%22bicycle%22%3D%22yes%22%5D(33.17434155100208%2C-116.773681640625%2C36.98939086733937%2C-112.48901367187499)%3B%0A)%3B%0A%2F%2F%20print%20results%0Aout%20body%3B%0A%3E%3B%0Aout%20skel%20qt%3B


> This may seem overkill to some people, but I'm aware of quite a few places
> where there's multiple bicycle lanes, where the bicycle lane is not the
> curb lane, and other arrangements that would otherwise just mess up lane
> guidance if you omit this and I've found fun edge cases in almost as many
> places as I've found bicycle lanes.
>

That is OK, but, as I said , is different from the cases I am describing


>
>
>> (2) how to tag longitudinal rumble strips,
>> (situated between motorized-traffic lanes and shoulders, example: [1],
>> not the "sleeping policeman" type that goes across the road nd which is
>> normally tagged as traffic_calming=rumble_strip on a node of the highway)
>> To tag their presence is important because they represent an augmented
>> protection of cyclists on the shoulder from cars invading the shoulder by
>> mistake, i.e. reduced risk of being killed.
>> To note that I have encountered rumble-strip-separated shoulders also on
>> roads below the rank of trunk or motorway
>>
>
> I'm not quite sure how necessary it is at this point.  The kind of example
> you have provided is being phased out in favor of strips with gaps in them
> so bicyclists can get on and off the shoulder without dealing with the
> rumbles, or eliminated on roads with a narrow hard shoulder.  In both
> cases, for the reason for that is that not taking bicycles into account
> does more harm than good.  This is true even on routes that are normally
> closed to bicyclists except when police tell you to use it anyway (like
> Interstate 70 in Kansas).
>
My point maybe was not clear enough: I would like to tag the longitudinal
rumble strips, independently of whether they are continuous or interrupted,
because I want to be able to classify route sections according to their
level of bicycle safety. If I have a stretch of motorway with a shoulder,
this same stretch is safer for bicycle use when a rumble strip is present
than when it is not, because it reduces the risk of a motor vehicle
invading the shoulder.


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

Re: [Talk-us] Combined parking/bike lanes

[Spencer Gardner]

The problem I see with that approach is that it doesn't distinguish between
a road with a striped bike lane next to a parking lane and a road with the
combined lane. In terms of the distribution of space on the road it might
be the same but it's different psychologically and is considered a
different facility from an engineering perspective.

On Fri, Feb 3, 2017 at 11:44 AM, David Chiles  wrote:

>
> Would the following tags work?
>
> parking:lane:(right/left) = parallel
> cycleway:(left/right) = lane
>
> https://wiki.openstreetmap.org/wiki/Key:parking:lane
> https://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dlane
>
> On Fri, Feb 3, 2017 at 9:11 AM, Spencer Gardner 
> wrote:
>
>> Hi all. Has anyone worked out a good tagging scheme for combined
>> bike/parking lanes? I'm not sure how common they are elsewhere but there
>> are a number of such facilities in my city.
>>
>> For reference, you can see an example here:
>> https://www.mapillary.com/app/?lat=43.06056159=-89.45121
>> 134=17=XByvWxyrk9quLK-noyoB5g=photo=mapbox_streets
>> Notice the bike lane sign above the speed limit sign and the cars parked
>> on the side. These are also accompanied with pavement markings indicating
>> it is a bicycle facility. In effect it's like a regular bike lane next to a
>> parking lane, but there's no stripe to separate the two.
>>
>> ___
>> 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-transit] Proposed automated edit for NAPTAN data in the West Midlands

[Brian Prangle]

We have an opportunity to work with the regional transport authority TfWM
to update this imported data which is 8 years old and partially edited by
OSM users. They have assigned 2 developers to work on this and I'm spending
a half day each week working with them.

We've agreed and discussed this in our mappa-mercia local OSM users group
and also contacted a prolific local public transport OSM editor who's not
part of  our group.

In line with the automated edits policy there's a wikipage

with full details and this email informs the relevant specialist talk list

Regards

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

[Talk-GB] Propose automated edit to update NAPTAN data in the west mids

[Brian Prangle]

Hi everyone

We have an opportunity to work with the regional transport authority TfWM
to update this data which is 8 years old and partially edited by OSM users.
They have assigned 2 developers to work on this and I'm spending a half day
each week working with them.

We've agreed and discussed this in our mappa mercia group and also
contacted a prolific local public transport OSM editor who's not part of
our group.

In line with the automated edits policy there's a wikipage

with full details

Comments welcome as this exercise might be useful elswhere as the state of
NAPTAN data will be in a similar state

regards

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

Re: [osm-ve] Cuántos somos?

[Marco Antonio]

On Fri, 3 Feb 2017 10:03:46 -0400 Juan Pablo Rodrigues
 wrote:

> puedo usar mi celular con android?

mapsme es ligero y simple, para cosas básicas como mejorar negocios,
oficinas, turismo es ideal, un resumen →
https://www.youtube.com/watch?v=PT2_lUqxvbw

osmand es más personalizable y potente, tiene perfiles (bici, peatón,
auto) que cambia la forma de ver el mapa. un resumen (tiene 2da parte) →
https://www.youtube.com/watch?v=np16HX61RZM

> como puedo editar o agregar información?

ambos son offline, ambos puedes registrar/editar datos, y en ambos
puedes enviar registros de problemas en el mapa.

en la wiki de vídeos recolecté varios que ayudan desde lo más simple a
cosas complejas. revisa →
https://wiki.openstreetmap.org/wiki/ES:Videotutoriales

abrazos,

Marco Antonio
@51114u9

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

Re: [Talk-us] Combined parking/bike lanes

[David Chiles]

Would the following tags work?

parking:lane:(right/left) = parallel
cycleway:(left/right) = lane

https://wiki.openstreetmap.org/wiki/Key:parking:lane
https://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dlane

On Fri, Feb 3, 2017 at 9:11 AM, Spencer Gardner 
wrote:

> Hi all. Has anyone worked out a good tagging scheme for combined
> bike/parking lanes? I'm not sure how common they are elsewhere but there
> are a number of such facilities in my city.
>
> For reference, you can see an example here:
> https://www.mapillary.com/app/?lat=43.06056159=-89.45121134=17=
> XByvWxyrk9quLK-noyoB5g=photo=mapbox_streets
> Notice the bike lane sign above the speed limit sign and the cars parked
> on the side. These are also accompanied with pavement markings indicating
> it is a bicycle facility. In effect it's like a regular bike lane next to a
> parking lane, but there's no stripe to separate the two.
>
> ___
> 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-at] Schreibweise der Straßennamen

[Borut Maricic]

Ich führe gleich die folgende Nomenklatur ein:
  Name Familienname Straße = nfs
Davon leiten sich die zwei Schreibweisen ab:
  n-f-s bzw. n f-s

Duden sagt auf [1]: "[...] Abweichende Einzelfestlegungen
durch die jeweils zuständigen Behörden kommen jedoch
vor.[...] 3. Straßennamen, die mit mehrteiligen Namen
zusammengesetzt sind, schreibt man mit Bindestrichen <§ 50>.
Georg-Büchner-Straße[...]"

Ich beteiligte mich vor kurzem an einem kleinen, angenehmen
und privaten Meinungsaustausch über das Thema. Anschließend
dachte ich mir: "OK, letztendlich gilt "We map what we see",
also ab in die Stadt... - dies wird ja dann mein
Superargument sein!"

Oje, vorsicht - was folgt wird nicht angenehm! Name dieser
Stadt ist hier nicht von Bedeutung, wobei die Beispiele, die
folgen, echt sind. Alles spielt sich innerhalb eines Kreises
von ca. 200m Durchmesser ab.

Nehmen wir an:
Erzherzog Johann Straße = ejs
Max Tendler Straße = mts
Peter Tunner Straße = pts
(Kaiser) Franz Josef Straße = fjs

Hausnummer-Tafel = HT
Straßennamen-Tafel = ST

Survey vor Ort ergab...

Für ejs:
HT: anscheinend alle e-j-s
ST: alte e-j-s; neuere e j-s
(sogar an einer Kreuzung gemischt!)

Für mts:
HT: anscheinend alle m-t-s
ST: anscheinend alle m-t-s (auch neuere, sic!)

Für pts:
HT: keine Ahnung - bin nicht soweit gegangen
ST: p t-s (habe aber nicht viele gesehen)
(An einer Säule ist sogar diese Kombination zu
sehen (sic!): m-t-s + p t-s

Für fjs:
HT: anscheinend überall f j-s
ST: keine Ahnung - bin nicht soweit gegangen

basemap.at verwendet für alle vier die "n f-s"-Kombination.

Äh? Bitte, an was soll sich ein armer OSM-Mapper hier
berufen? Ich bitte um Entschuldigung, wenn dies eventuell
Länge-mal-Breite schon diskutiert wurde, was mir nicht
bekannt ist.

Gibt es eventuell ein OSM-at-Konsens über die Vorgehensweise
in solch einer Situation? Wäre ein Konsens eventuell
möglich? Eventuell doch nach Duden (n-f-s)? Oder wie?

[1] http://www.duden.de/sprachwissen/rechtschreibregeln/strassennamen


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

[Talk-gb-westmidlands] Automated NAPTAN edit for bus stop data in the West Midlands

[Brian Prangle]

Hi everyone

We discussed this at some length at our February meeting last night and in
conformance with the automated edits policy I've produced a wikipage


Regards

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

Re: [Talk-it] Dubbi vari…..

[Martin Koppenhoefer]

2017-02-03 16:15 GMT+01:00 demon.box :

> proposta1:
> tourism=artwork
> artwork_type=statue
> denomination=catholic
> religion=christian
>
> proposta2:
> historic=memorial
> memorial:type=statue
> denomination=catholic
> religion=christian
>



si, per me si potrebbe anche inventare/aggiungere dei tag specifici per le
categorie ricorrenti come madonne e monumenti di guerra.

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

[Talk-us] Combined parking/bike lanes

[Spencer Gardner]

Hi all. Has anyone worked out a good tagging scheme for combined
bike/parking lanes? I'm not sure how common they are elsewhere but there
are a number of such facilities in my city.

For reference, you can see an example here:
https://www.mapillary.com/app/?lat=43.06056159=-89.45121134=17=XByvWxyrk9quLK-noyoB5g=photo=mapbox_streets
Notice the bike lane sign above the speed limit sign and the cars parked on
the side. These are also accompanied with pavement markings indicating it
is a bicycle facility. In effect it's like a regular bike lane next to a
parking lane, but there's no stripe to separate the two.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [osm-ve] Cuántos somos?

[Sara Carvajal]

Hola! Gracias a todos por responder.

Realmente no uso telegram, pero gracias y ahora me anoto en la wiki.

Otra cosa, les parece buena idea si creamos un grupo en fb o algo?

Juan Pablo para aprender a mapear puedes revisar esto:

learnosm.org

Mapping Instructions and Tips:
https://www.youtube.com/playlist?list=PL54o5PaKgnbJbuv9IrQDODMLpgNo0F4jk

También puedes colaborar en tasks.hotosm.org

Saludos a todos! 
Sara

On Feb 3, 2017 10:04, "Juan Pablo Rodrigues"  wrote:

Hola buenos días como hacer para comenzar hacer aportes, podrían guiarme o
enviarme un enlace que contenga información de como iniciar.
que software usar (que sea libre).
puedo usar mi celular con android?
como puedo editar o agregar información?
se pueden hacer correcciones en caso de ver errores

de antemano muchas gracias

El 3 de febrero de 2017, 9:50, joost schouppe 
escribió:

> Si haces click cuando se muestra la frontera de Venezuela aca:
>
> http://mapbox.github.io/osm-analysis-collab/users-by-country
> ?yearIdx=11=10=365.46/9.472/-68.994
>
> Podras ver que en Venezuela, son unos 15 a nivel diario, 300 anualmente
> (solo los que trabajaron en rutas)
>
>
> (ojo, no es mu rapido en cargar, y parece que los numeros ya son un poco
> viejo, asi que hay que ignorar el numero para 2016)
>
> 2017-02-03 10:51 GMT+01:00 Wladimir Szczerban :
>
>> Hola Sara,
>>
>> Bienvenida a OSM, como ya han comentado en Venezuela no hay mucha gente
>> activa y estamos muy distribuidos por el territorio lo que és bueno y malo.
>> Bueno porque así cada quien mapea su zona y malo porque al estar muy
>> dispersos no podemos hacer quedadas.
>>
>> Estaría bien que los que estamos un poco activos nos apuntemos en la
>> página de la wiki [1] para así poder saber mejor cuantos somos.
>>
>> [1] http://wiki.openstreetmap.org/wiki/Category:Users_in_Venezuela
>>
>>
>> El 3 de febrero de 2017, 2:29, Rolando Algarin 
>> escribió:
>>
>>> Hola Sara, la verdad no somos muchos, por telegram hay una canal de la
>>> comunidad Latinoaméricana en OSM, allí también hay varios venezolanos..
>>> Acá te dejo el canal de Telegram:
>>> t.me/OSMLatam
>>>
>>> También hay canales de otros países pero no de Venezuela por el momento,
>>> sería cuestión de crearlo.
>>>
>>> Saludos.
>>>
>>>
>>> El jue., 2 de feb. de 2017 7:55 PM, Sara Carvajal 
>>> escribió:
>>>
 Hola mappers! Soy relativamente nueva en OSM y quería saber cuántos
 somos en Venezuela y si existe algún grupo en las redes sociales.

 Saludos!
 Sara
 ___
 Talk-ve mailing list
 Talk-ve@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk-ve

>>>
>>> ___
>>> Talk-ve mailing list
>>> Talk-ve@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-ve
>>>
>>>
>>
>>
>> --
>> Saludos,
>>
>> Bolo
>> www.geoinquiets.cat
>>
>> ___
>> Talk-ve mailing list
>> Talk-ve@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ve
>>
>>
>
>
> --
> Joost Schouppe
> OpenStreetMap  |
> Twitter  | LinkedIn
>  | Meetup
> 
>
> ___
> Talk-ve mailing list
> Talk-ve@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ve
>
>


-- 
*Un ingeniero no es una copia, es original y se atreve a cambiar una
realidad, no importa el tiempo o el espacio, todo es posible mientras crea
que es así*

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

Re: [Talk-cz] Fwd: Využití Ortofotomapy pro OpenStreetMap

[Petr Vozdecký]

Velmi zajímavé,

to je skoro výzva pro Brno. Díky i za tu přiloženou komunikaci.

Otázka na Laďu Nešněru - myslíš, že bys toto měl sílu směrem k Brnu 
komunikovat? Nebo se toho má chopit někdo jiný, kdo s nimi je v nějakém 
kontaktu (já nebo Mirek Suchý)?

vop


-- Původní zpráva --
Od: Matej Lieskovský 
Komu: talk-cz@openstreetmap.org
Datum: 3. 2. 2017 14:39:10
Předmět: [Talk-cz] Fwd: Využití Ortofotomapy pro OpenStreetMap

"
Ahoj,

povedlo se mi zařídit něco zajímavého. Cituji:


"IPR Praha souhlasí s využíváním ortofotografií, které poskytuje 
prostřednictvím Geoportálu hl. m. Prahy, za účelem aktualizace a doplňování 
databáze OpenStreetMap, přičemž vzniklá vektorová data smí být vložena do 
OSM pod licencí ODbL za předpokladu, že IPR bude uveden v seznamu 
přispěvatelů do OSM a takto vzniklá data budou mít IPR uveden jako svůj 
zdroj."


Konec citace.

Na http://wiki.openstreetmap.org/wiki/Contributors
(http://wiki.openstreetmap.org/wiki/Contributors) přidám IPR sám, prosím 
uvádějte k zakreslovaným věcem "source=CZ:IPRPraha:ortofoto", ať jsou na IPR
spokojeni.

Rád bych poděkoval Jethrovi, který mi pomáhal formulovat maily.

S pozdravem,
Matej Lieskovský

PS: Přeposílám emailovou konverzaci




-- Forwarded message --
From: Baron Bohdan Mgr. (IPR/SPI) 
Date: 2017-02-03 12:16 GMT+01:00
Subject: RE: Využití Ortofotomapy pro OpenStreetMap
To: Matej Lieskovský 





Dobry den,

 
 
omlouvam se za pozdejsi odpoved, ale mel jsem toho pomerne hodne k reseni.
 
 
 
IPR Praha souhlasí s využíváním ortofotografií, které poskytuje 
prostřednictvím Geoportálu hl. m. Prahy, za účelem aktualizace a doplňování 
databáze OpenStreetMap, přičemž vzniklá vektorová data smí být vložena do 
OSM pod licencí ODbL za předpokladu, že IPR bude uveden v seznamu 
přispěvatelů do OSM a takto vzniklá data budou mít IPR uveden jako svůj 
zdroj.

 
 
S pozdravem
 
Bohdan Baron

 
 
From: Matej Lieskovský [mailto:lieskovsky.ma...@gmail.com
(mailto:lieskovsky.ma...@gmail.com)] 
Sent: Wednesday, February 01, 2017 1:44 PM



To: Baron Bohdan Mgr. (IPR/SPI) 
Subject: Re: Využití Ortofotomapy pro OpenStreetMap






 
 

Dobrý den,
zatím jsem nedostal žádnou odpověď na můj předchozí email. Dostal jste jej?
Opět prosím o zaslání toho souhlasu, ať můžeme začít doplňovat.
S pozdravem,
Matej Lieskovský



 
 

2017-01-25 10:58 GMT+01:00 Matej Lieskovský :
" 

Dobrý den,
pokud Vám to nevadí, asi by bylo lepší poslat tu větu samostatně, ať je to 
jednoznačné.
Statistiky dodáme.
S pozdravem
Matej Lieskovský





 
 

2017-01-25 10:15 GMT+01:00 Baron Bohdan Mgr. (IPR/SPI) :
" 


Dobry den,

 
 
s timto postupem urcite souhlasime a urcite s timto nemame absolutne zadny 
problem. Obdobne jsme uz s ortofoto postupovali i u jinych subjektu. Mam Vam
prosim tedy zaslat Vami zminenou vetu v samostatnem mailu nebo staci, ze Vam
odsouhlasim Vam,i zminene zneni v tomto mailu?

Ten vycet je urcite zajimavy. Jednou za rok by nas to trosku i z profesniho 
hledika zajimalo. :-)

S pozdravem
 
Bohdan Baron

 
 
From: Matej Lieskovský [mailto:lieskovsky.ma...@gmail.com
(mailto:lieskovsky.ma...@gmail.com)] 
Sent: Wednesday, January 25, 2017 9:36 AM




To: Baron Bohdan Mgr. (IPR/SPI) 
Subject: Re: Využití Ortofotomapy pro OpenStreetMap





 
 


Dobrý den,



 
 


souhlas s použitím pro aktualizaci OSM nám naprosto stačí. Licence u Vašich 
originálních dat (tedy ortofotek) se vůbec nebude měnit, potřebujeme pouze 
souhlas s tím, že vektorová data, která za pomoci Vašich ortofotografií 
vytvoříme a přidáme do OSM, smí být šířena pod licencí ODbL, pod kterou 
spadá celá OSM. ODbL (http://opendatacommons.org/licenses/odbl/
(http://opendatacommons.org/licenses/odbl/)) je licence v mnoha ohledech 
podobná CC BY-SA (OSM také původně CC BY-SA používala) ale je více zaměřená 
na použití pro databáze (CC BY-SA je spíše zaměřená na text, fotky, 
audionahrávky a videa). ODbL dovoluje data šířit, adaptovat a vytvářet 
odvozená díla za předpokladu, že je zachována otevřenost dat, stejná licence
a uveden autor. Vzhledem k tomu, že OSM obsahuje data od velkého počtu 
různých přispěvatelů, není prakticky proveditelné, aby na každém kousku mapy
byly uvedeny všechny zdroje - proto OSM používá označení "(c) OpenStreetMap 
Contributors" a IPR Praha by byl uveden na http://wiki.openstreetmap.org/
wiki/Contributors(http://wiki.openstreetmap.org/wiki/Contributors). Současně
jsme ochotni se zavázat (a je možné uvést do souhlasu jakož to podmínku), že
vektorová data odvozená od Vašich ortofotografií budou mít v databázi OSM 
nastaveno "source=CZ:IPRPraha:ortofoto" (jedná se o relativně běžný způsob, 
jak v OSM 

Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

[SK53]

Fire route does not seem to be in use other than in descriptions: I think
it should be avoided in this context because one can envisage a
route=fire_route being used to describe the route to escape a building in
an emergency.

Not can I find actual tagged usage of fire_access_route on taginfo.

Unfortunately the DoT Road Markings manual doesn't mention them either, but
the documented usage in signage & road markings of "Fire Path" covers
Glasgow, Nottingham, and Tolworth (Greater London), so I suspect this is
the official term.

Jerry

On 3 February 2017 at 15:15, Andy Robinson  wrote:

> I think I’ve used “fire_route” to describe these in the past. Or perhaps
> “fire_access_route”. Well you get the drift. Signage is often put up by the
> developer (for housing developments - where you often see these) so I doubt
> there is any common naming convention on the ground.
>
>
>
> Cheers
>
> Andy
>
>
>
> *From:* Paul Berry [mailto:pmberry2...@gmail.com]
> *Sent:* 03 February 2017 14:35
> *To:* SK53
> *Cc:* talk-gb
> *Subject:* Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)
>
>
>
> Thanks again. I'll tag the textured paving as a barrier.
>
>
>
> Also, in the Leeds example I've given, cycling is not permitted because
> there is a No Entry sign at each end of the path. This is something that is
> also picked up on here: http://www.andypreece.
> co.uk/cycling/fac_leverndale.php
>
>
>
> Further browsing has revealed Fire Paths are actually fairly common in the
> Glasgow area: https://www.cyclestreets.net/photomap/tags/firepath
>
>
>
> You learn something new every day.
>
>
>
> Regards,
>
> *Paul*
>
>
>
> On 3 February 2017 at 13:54, SK53  wrote:
>
> I'd think that the rows of raised-textured paving can be mapped as a
> barrier, with access=emergency too.
>
> I'm glad that the photos I added to the wiki confirm my memory that "fire
> path" is the word used on the signs. Was wondering where I got it from.
>
> Cheers,
>
> Jerry
>
>
>
> On 3 February 2017 at 12:20, Paul Berry  wrote:
>
> Thanks, Jerry. I thought the Nottingham features would get your attention
> :)
>
> I'm surprised I missed the Fire Path page on the Wiki, but thanks for the
> confirmation that fire_path=yes is the way to go.
>
>
>
> As for the textured paving, I'm not sure anything surface=
> or traffic_calming= matches it, so I'll not tag it.
>
>
>
> (Out of interest, this Aberdeen one used to be a Fire Path, but the
> emergency/access tags have not been updated accordingly: https://www.
> openstreetmap.org/way/124065409)
>
>
>
> Regards,
>
> *Paul*
>
>
>
>
>
>
>
> On 3 February 2017 at 11:17, SK53  wrote:
>
> Looks like a documented on the wiki: https://wiki.openstreetmap.
> org/wiki/Fire_Path
>
>
>
> On 3 February 2017 at 11:15, SK53  wrote:
>
> The tag that I have used for such things is fire_path=yes.
>
> There are 4 uses of the tag in Nottingham and 2 in Aberdeen. There are
> several others not tagged (including the two recent ones you mention), for
> instance this one  where Suez
> Street joins North Gate outside Port Said Villas (I wonder when these
> streets were built).
>
> The structures involved may be as illustrated by Paul. The older
> Nottingham ones tend to have a zone of the wavy block paving which is
> 10-15ft long and thus not a normal road in any sense. Other fire paths I've
> seen involve two locked boom gates.
>
> Jerry
>
>
>
> On 2 February 2017 at 22:20, Paul Berry  wrote:
>
> Hi everyone,
>
>
>
> Fire roads are an uncommon sight in the UK. They're sometimes signed as
> "fire lanes," but they're nothing to do with the designation in the US (and
> elsewhere) which is a parking restriction: https://wiki.
> openstreetmap.org/wiki/Key:parking:lane and we're also not talking about
> the wide tracks in managed forests that act as a firebreak.
>
>
>
> I mean restricted highways like this one: http://www.openstreetmap.org/
> way/240007969 (whose source links to photo evidence).
>
>
>
> How do we map these? I assume service=emergency_access?
>
>
>
> Also, how is the embedded roughly-textured paving in that photo best
> represented?
>
>
>
> There are some similar ones in Nottingham, notably at Addington Road and
> Wimbourne Road there, though they're not mapped as such.
>
>
>
> Your advice and guidance gratefully received.
>
>
>
> Regards,
>
> *Paul*
>
>
>
>
>
>
>
>
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>
>
>
>
>
>
>
>
>
>
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-cz] Fwd: Využití Ortofotomapy pro OpenStreetMap

[Jan Macura]

Ahoj,

boží! Gratuluji k úspěšnému jednání a zároveň velké díky za zprostředkování!

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

Wochennotiz Nr. 341 24.01.2017–30.01.2017

[Wochennotizteam]

Hallo,

die Wochennotiz Nr. 341 mit vielen wichtigen Neuigkeiten aus der OpenStreetMap 
Welt ist da:

http://blog.openstreetmap.de/blog/2017/02/wochennotiz-nr-341/

Viel Spaß beim Lesen!
___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at

Wochennotiz Nr. 341 24.01.2017–30.01.2017

[Wochennotizteam]

Hallo,

die Wochennotiz Nr. 341 mit vielen wichtigen Neuigkeiten aus der OpenStreetMap 
Welt ist da:

http://blog.openstreetmap.de/blog/2017/02/wochennotiz-nr-341/

Viel Spaß beim Lesen!
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de

Re: [OSM-talk] OSM for government

[Mikel Maron]

Joost
Off the top of my head... The French government led by etalab have a really 
good model of working with OSM and several good projects.In the USG, USAID has 
been working with OSM and universities for data in Malaria spraying 
campaigns.Several resilience programs developed by the World Bank serving local 
governments using OSM.
Let's get a catalog started -- want to create a wiki page Joost?
-Mikel

* Mikel Maron * +14152835207 @mikel s:mikelmaron 

On Friday, February 3, 2017 10:47 AM, john whelan  
wrote:
 
 

 A couple of the city of Ottawa web sites use the osm map.  Ottawa Hydro which 
is owned by the City for example.  I think the UK has imported all the bus 
stops and there are tools to import the GTFS format transit data but that 
depends on the license of course.

Cheerio John

On 3 February 2017 at 10:33, Clifford Snow  wrote:

TRIMet in Portland, Oregon, US is the regional transit operator. They use and 
contribute to OSM. The US National Park Service has been working on a version 
of iD that can feeds users changesets into both OSM and NPS. Last I heard it 
still is waiting to be rolled out. (Now that NPS is in trouble for their 
tweets, not sure if we'll even have national parks.)
If there isn't a catalog there should be. 
Clifford
On Fri, Feb 3, 2017 at 5:44 AM, joost schouppe  wrote:

Hi,
With the Belgian community, we're making some careful progress into getting 
government to really integrate OSM/VGI into their data management efforts. So 
not talking about background maps here, real data contribution or community 
engagement.
There are some very specific issues and opportunities there. I believe the 
Canadian Census is going that way. Are there any other projects in this 
direction? Is there anything like a project catalogue around?

-- 
Joost SchouppeOpenStreetMap | Twitter | Link edIn | Meetup
__ _
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.or g/listinfo/talk





-- 
@osm_seattle
osm_seattle.snowandsnow.usOpenStreetMap: Maps with a human touch
__ _
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap. org/listinfo/talk




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


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

Re: [OSM-talk-fr] traffic_signals changement de schema

[Philippe Verdy]

Je pense que le but n'est pas d'indiquer l'orientation cardinale, mais
d'indiquer dans quel sens le feu s'applique: le but étant de distinguer les
feux d'entrée de carrefour et ceux en sortie de carrefour comme on en
trouve beaucoup à Paris (très rarement ailleurs en France, ce qui donc ne
justifie pas un ajout massif obligatoire). La priorité en France pour
taguer cette direction est donc surtout pour Paris.


Le 3 février 2017 à 16:57, Jérôme Seigneuret 
a écrit :

> Oui en effet l'avantage de ce mode de tag est de pouvoir superposer des
> éléments quand ils sont sur le même point et d'avoir du détail dessus.
> Après pour aller plus loin il y a les angles cardinaux ou en degrées.
>
> Le 3 février 2017 à 16:40, Philippe Verdy  a écrit :
>
>> En principe cela ne concerne pas que les feux de circulation, mais cela
>> devrait aussi s'appliquer aux autres signalisations (dont highway=stop,
>> highway=give_way). Cependant il n'y a généralement pas d'ambiguité, le feu
>> étant généralement très près du noeud central du carrefour le plus proche.
>>
>> Les ambiguités existent dans le cas des feux en sortie de carrefours
>> (notamment à Paris) devant un passage piéton, et quand les carrefours sont
>> très proches les uns des autres voire accolés (on en trouve par exemple en
>> sortie de ronds-points, et même parfois sur les ronds-points, et même quand
>> ce sont des giratoires (notemment ceux qui ont une voie de service centrale
>> utilisée par les bus ou trams qui ne font pas le tour du rond-point ou
>> giratoire).
>> Ces feux sont très souvent accompagnés aussi de stops ou cédez-le-passage
>> tracés au sol (qui servent quand les feux ne fonctionnent pas ou sont à
>> l'orange clignotant).
>>
>> On pourrait aussi l'appliquer à d'autres panneaux et signalisations, ou
>> aux ralentisseurs, aux chicanes avec priorité dans un sens, aux caméras et
>> radars de contrôle...
>>
>> C'est là depuis un moment dans Osmose, mais il y a des tonnes de
>> signalements, alros que la plupart du temps il n'y a pas d'ambiguité.
>> Disons que c'est le plus souvent un détail qui n'est pas très important et
>> peut être précisé. Attention toutefois car certains carrefours ont des feux
>> d'un seul côté du carrefour et le feux s'applique dans les deux sens (il y
>> a bien deux feux sur le même poteau orientés tête-bêche; souvent aussi
>> quand il y a des feux séparés, il y a malgré tout des feux têtes-bêches
>> (affichant un "+" ou lieu d'un "o"), destinés à palier des pannes
>> éventuelles sur un des feux ou des problèmes temporaires de visibilité (on
>> en trouve surtout quand il y a des passages piétons protégés par ces feux
>> sur les voies de grande circulation). Mais maintenant les feux sont très
>> souvent télésurveillés (en même temps qu'ils peuvent être télécommandés) et
>> détectent les cas où aucun courant n'est détecté (ampoule grillée, défaut
>> sur un câble d'alimentation, ou armoire de contrôle noyée par inondation ou
>> givrée, court-circuit/disjonction, feu endommagé par un accident...) et ces
>> feux à contre-sens sont plus rares (d'autant plus que nombre d'entre eux
>> utilisent des LED qui grillent bien moins souvent que les anciennes
>> ampoules à incandescence).
>>
>> Noter aussi que nombre de feux sont maintenant supprimés (construction
>> massive de ronds-points, et pas seulement en France, jugés plus surs et
>> fluidifiant mieux la circulation, avec moins de pollution (gaz, particules,
>> bruit), plus de sécurité et moins d'accidents.
>>
>> On trouve un peu partout aussi des feux mis hors service dans les zones
>> déjà ralenties par d'autres moyens (limites de vitesse abaissée, caméras de
>> surveillance, ralentisseurs divers), ilots de protection de passages
>> piétons, réduction du nombre de voies juste avant un carrefour.
>>
>> Des communes ont décidé de bannir tous les feux et tout convertir en
>> giratoires ou sinon des tas de sens uniques sur les rues résidentielles.
>>
>> Même les "stops" disparaissent en ville contre des laissez-le-passage (et
>> les priorités à droite par défaut, très mal respectées, aussi disparaissent
>> au profit de cédez-le-passage), et on ne trouve plus de "stops" que sur les
>> sorties de voies privées et petits parkings (pour les gros parkings,
>> notamment les centres commerciaux, des giratoires apparaissent même sur les
>> voies privées et des tas de ralentisseurs au sol avec une limite abaissée à
>> 30km/h).
>>
>>
>> Le 3 février 2017 à 15:37, Jérôme Seigneuret > > a écrit :
>>
>>>
>>> Bonjour, suite à l'apparition d'un nouveau schéma  dans le wiki
>>> http://wiki.openstreetmap.org/wiki/FR:Key:traffic_signals:direction pour
>>> la prise en compte des directions sur les sens des feux de circulation,
>>> Osmose propose d'intégrer le sens à prendre
>>>
>>> Si le feu n'a pas de direction il propose :
>>> traffic_signals:direction=backward
>>> traffic_signals:direction=forward
>>>
>>> Cela est en accord 

Re: [OSM-talk-fr] traffic_signals changement de schema

[Jérôme Seigneuret]

Oui en effet l'avantage de ce mode de tag est de pouvoir superposer des
éléments quand ils sont sur le même point et d'avoir du détail dessus.
Après pour aller plus loin il y a les angles cardinaux ou en degrées.

Le 3 février 2017 à 16:40, Philippe Verdy  a écrit :

> En principe cela ne concerne pas que les feux de circulation, mais cela
> devrait aussi s'appliquer aux autres signalisations (dont highway=stop,
> highway=give_way). Cependant il n'y a généralement pas d'ambiguité, le feu
> étant généralement très près du noeud central du carrefour le plus proche.
>
> Les ambiguités existent dans le cas des feux en sortie de carrefours
> (notamment à Paris) devant un passage piéton, et quand les carrefours sont
> très proches les uns des autres voire accolés (on en trouve par exemple en
> sortie de ronds-points, et même parfois sur les ronds-points, et même quand
> ce sont des giratoires (notemment ceux qui ont une voie de service centrale
> utilisée par les bus ou trams qui ne font pas le tour du rond-point ou
> giratoire).
> Ces feux sont très souvent accompagnés aussi de stops ou cédez-le-passage
> tracés au sol (qui servent quand les feux ne fonctionnent pas ou sont à
> l'orange clignotant).
>
> On pourrait aussi l'appliquer à d'autres panneaux et signalisations, ou
> aux ralentisseurs, aux chicanes avec priorité dans un sens, aux caméras et
> radars de contrôle...
>
> C'est là depuis un moment dans Osmose, mais il y a des tonnes de
> signalements, alros que la plupart du temps il n'y a pas d'ambiguité.
> Disons que c'est le plus souvent un détail qui n'est pas très important et
> peut être précisé. Attention toutefois car certains carrefours ont des feux
> d'un seul côté du carrefour et le feux s'applique dans les deux sens (il y
> a bien deux feux sur le même poteau orientés tête-bêche; souvent aussi
> quand il y a des feux séparés, il y a malgré tout des feux têtes-bêches
> (affichant un "+" ou lieu d'un "o"), destinés à palier des pannes
> éventuelles sur un des feux ou des problèmes temporaires de visibilité (on
> en trouve surtout quand il y a des passages piétons protégés par ces feux
> sur les voies de grande circulation). Mais maintenant les feux sont très
> souvent télésurveillés (en même temps qu'ils peuvent être télécommandés) et
> détectent les cas où aucun courant n'est détecté (ampoule grillée, défaut
> sur un câble d'alimentation, ou armoire de contrôle noyée par inondation ou
> givrée, court-circuit/disjonction, feu endommagé par un accident...) et ces
> feux à contre-sens sont plus rares (d'autant plus que nombre d'entre eux
> utilisent des LED qui grillent bien moins souvent que les anciennes
> ampoules à incandescence).
>
> Noter aussi que nombre de feux sont maintenant supprimés (construction
> massive de ronds-points, et pas seulement en France, jugés plus surs et
> fluidifiant mieux la circulation, avec moins de pollution (gaz, particules,
> bruit), plus de sécurité et moins d'accidents.
>
> On trouve un peu partout aussi des feux mis hors service dans les zones
> déjà ralenties par d'autres moyens (limites de vitesse abaissée, caméras de
> surveillance, ralentisseurs divers), ilots de protection de passages
> piétons, réduction du nombre de voies juste avant un carrefour.
>
> Des communes ont décidé de bannir tous les feux et tout convertir en
> giratoires ou sinon des tas de sens uniques sur les rues résidentielles.
>
> Même les "stops" disparaissent en ville contre des laissez-le-passage (et
> les priorités à droite par défaut, très mal respectées, aussi disparaissent
> au profit de cédez-le-passage), et on ne trouve plus de "stops" que sur les
> sorties de voies privées et petits parkings (pour les gros parkings,
> notamment les centres commerciaux, des giratoires apparaissent même sur les
> voies privées et des tas de ralentisseurs au sol avec une limite abaissée à
> 30km/h).
>
>
> Le 3 février 2017 à 15:37, Jérôme Seigneuret 
> a écrit :
>
>>
>> Bonjour, suite à l'apparition d'un nouveau schéma  dans le wiki
>> http://wiki.openstreetmap.org/wiki/FR:Key:traffic_signals:direction pour
>> la prise en compte des directions sur les sens des feux de circulation,
>> Osmose propose d'intégrer le sens à prendre
>>
>> Si le feu n'a pas de direction il propose :
>> traffic_signals:direction=backward
>> traffic_signals:direction=forward
>>
>> Cela est en accord avec la page du wiki.
>>
>> J'ai donc pris en considération les informations et j'ai mis à jour les
>> feux de circulation dans le cas suivant (en ayant pris soin de vérifier les
>> intersections concernés)
>>
>> passage de
>> highway=traffic_signals + direction=forward >  highway=traffic_signals +
>> traffic_signals:direction=forward
>>
>> highway=traffic_signals + direction=backward >  highway=traffic_signals +
>> traffic_signals:direction=backward
>>
>> Pour les cas sans information la proposition d'intégration est toujours
>> proposé par osmose car il n'y a pas de tag 

Re: [OSM-talk] OSM for government

[john whelan]

A couple of the city of Ottawa web sites use the osm map.  Ottawa Hydro
which is owned by the City for example.  I think the UK has imported all
the bus stops and there are tools to import the GTFS format transit data
but that depends on the license of course.

Cheerio John

On 3 February 2017 at 10:33, Clifford Snow  wrote:

> TRIMet in Portland, Oregon, US is the regional transit operator. They use
> and contribute to OSM. The US National Park Service has been working on a
> version of iD that can feeds users changesets into both OSM and NPS. Last I
> heard it still is waiting to be rolled out. (Now that NPS is in trouble for
> their tweets, not sure if we'll even have national parks.)
>
> If there isn't a catalog there should be.
>
> Clifford
>
> On Fri, Feb 3, 2017 at 5:44 AM, joost schouppe 
> wrote:
>
>> Hi,
>>
>> With the Belgian community, we're making some careful progress into
>> getting government to really integrate OSM/VGI into their data management
>> efforts. So not talking about background maps here, real data contribution
>> or community engagement.
>>
>> There are some very specific issues and opportunities there. I believe
>> the Canadian Census is going that way. Are there any other projects in this
>> direction? Is there anything like a project catalogue around?
>>
>> --
>> Joost Schouppe
>> OpenStreetMap  |
>> Twitter  | LinkedIn
>>  | Meetup
>> 
>>
>> ___
>> talk mailing list
>> talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
>>
>
>
> --
> @osm_seattle
> osm_seattle.snowandsnow.us
> OpenStreetMap: Maps with a human touch
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk-fr] traffic_signals changement de schema

[Philippe Verdy]

En principe cela ne concerne pas que les feux de circulation, mais cela
devrait aussi s'appliquer aux autres signalisations (dont highway=stop,
highway=give_way). Cependant il n'y a généralement pas d'ambiguité, le feu
étant généralement très près du noeud central du carrefour le plus proche.

Les ambiguités existent dans le cas des feux en sortie de carrefours
(notamment à Paris) devant un passage piéton, et quand les carrefours sont
très proches les uns des autres voire accolés (on en trouve par exemple en
sortie de ronds-points, et même parfois sur les ronds-points, et même quand
ce sont des giratoires (notemment ceux qui ont une voie de service centrale
utilisée par les bus ou trams qui ne font pas le tour du rond-point ou
giratoire).
Ces feux sont très souvent accompagnés aussi de stops ou cédez-le-passage
tracés au sol (qui servent quand les feux ne fonctionnent pas ou sont à
l'orange clignotant).

On pourrait aussi l'appliquer à d'autres panneaux et signalisations, ou aux
ralentisseurs, aux chicanes avec priorité dans un sens, aux caméras et
radars de contrôle...

C'est là depuis un moment dans Osmose, mais il y a des tonnes de
signalements, alros que la plupart du temps il n'y a pas d'ambiguité.
Disons que c'est le plus souvent un détail qui n'est pas très important et
peut être précisé. Attention toutefois car certains carrefours ont des feux
d'un seul côté du carrefour et le feux s'applique dans les deux sens (il y
a bien deux feux sur le même poteau orientés tête-bêche; souvent aussi
quand il y a des feux séparés, il y a malgré tout des feux têtes-bêches
(affichant un "+" ou lieu d'un "o"), destinés à palier des pannes
éventuelles sur un des feux ou des problèmes temporaires de visibilité (on
en trouve surtout quand il y a des passages piétons protégés par ces feux
sur les voies de grande circulation). Mais maintenant les feux sont très
souvent télésurveillés (en même temps qu'ils peuvent être télécommandés) et
détectent les cas où aucun courant n'est détecté (ampoule grillée, défaut
sur un câble d'alimentation, ou armoire de contrôle noyée par inondation ou
givrée, court-circuit/disjonction, feu endommagé par un accident...) et ces
feux à contre-sens sont plus rares (d'autant plus que nombre d'entre eux
utilisent des LED qui grillent bien moins souvent que les anciennes
ampoules à incandescence).

Noter aussi que nombre de feux sont maintenant supprimés (construction
massive de ronds-points, et pas seulement en France, jugés plus surs et
fluidifiant mieux la circulation, avec moins de pollution (gaz, particules,
bruit), plus de sécurité et moins d'accidents.

On trouve un peu partout aussi des feux mis hors service dans les zones
déjà ralenties par d'autres moyens (limites de vitesse abaissée, caméras de
surveillance, ralentisseurs divers), ilots de protection de passages
piétons, réduction du nombre de voies juste avant un carrefour.

Des communes ont décidé de bannir tous les feux et tout convertir en
giratoires ou sinon des tas de sens uniques sur les rues résidentielles.

Même les "stops" disparaissent en ville contre des laissez-le-passage (et
les priorités à droite par défaut, très mal respectées, aussi disparaissent
au profit de cédez-le-passage), et on ne trouve plus de "stops" que sur les
sorties de voies privées et petits parkings (pour les gros parkings,
notamment les centres commerciaux, des giratoires apparaissent même sur les
voies privées et des tas de ralentisseurs au sol avec une limite abaissée à
30km/h).


Le 3 février 2017 à 15:37, Jérôme Seigneuret 
a écrit :

>
> Bonjour, suite à l'apparition d'un nouveau schéma  dans le wiki
> http://wiki.openstreetmap.org/wiki/FR:Key:traffic_signals:direction pour
> la prise en compte des directions sur les sens des feux de circulation,
> Osmose propose d'intégrer le sens à prendre
>
> Si le feu n'a pas de direction il propose :
> traffic_signals:direction=backward
> traffic_signals:direction=forward
>
> Cela est en accord avec la page du wiki.
>
> J'ai donc pris en considération les informations et j'ai mis à jour les
> feux de circulation dans le cas suivant (en ayant pris soin de vérifier les
> intersections concernés)
>
> passage de
> highway=traffic_signals + direction=forward >  highway=traffic_signals +
> traffic_signals:direction=forward
>
> highway=traffic_signals + direction=backward >  highway=traffic_signals +
> traffic_signals:direction=backward
>
> Pour les cas sans information la proposition d'intégration est toujours
> proposé par osmose car il n'y a pas de tag direction.
> --
> Cordialement,
> Jérôme Seigneuret
>
> ___
> 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] OSM for government

[Clifford Snow]

TRIMet in Portland, Oregon, US is the regional transit operator. They use
and contribute to OSM. The US National Park Service has been working on a
version of iD that can feeds users changesets into both OSM and NPS. Last I
heard it still is waiting to be rolled out. (Now that NPS is in trouble for
their tweets, not sure if we'll even have national parks.)

If there isn't a catalog there should be.

Clifford

On Fri, Feb 3, 2017 at 5:44 AM, joost schouppe 
wrote:

> Hi,
>
> With the Belgian community, we're making some careful progress into
> getting government to really integrate OSM/VGI into their data management
> efforts. So not talking about background maps here, real data contribution
> or community engagement.
>
> There are some very specific issues and opportunities there. I believe the
> Canadian Census is going that way. Are there any other projects in this
> direction? Is there anything like a project catalogue around?
>
> --
> Joost Schouppe
> OpenStreetMap  |
> Twitter  | LinkedIn
>  | Meetup
> 
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>


-- 
@osm_seattle
osm_seattle.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[Talk-it] Dubbi vari…..

[demon.box]

ciao, provo a ri/buttare lì alcuni dubbi che se anche in parte già proposti
non ho mai trovato una soluzione soddisfacente:

1-statua religiosa almeno a grandezza naturale o anche più (classico esempio
statua della Madonna)

proposta1:
tourism=artwork
artwork_type=statue
denomination=catholic
religion=christian

proposta2:
historic=memorial
memorial:type=statue
denomination=catholic
religion=christian


2-scritte su monumenti o memoriali

inscription=riga1;riga2

oppure

inscription1=riga1
inscription2=riga2

oppure meglio lasciar perdere il tag inscription e mettere così?

name="Monumento ai Caduti" oppure name="Monumento ai Marinai"

Grazie.
--enrico



--
View this message in context: 
http://gis.19327.n8.nabble.com/Dubbi-vari-tp5890497.html
Sent from the Italy General mailing list archive at Nabble.com.

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

Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

[Andy Robinson]

I think I’ve used “fire_route” to describe these in the past. Or perhaps 
“fire_access_route”. Well you get the drift. Signage is often put up by the 
developer (for housing developments - where you often see these) so I doubt 
there is any common naming convention on the ground.

 

Cheers

Andy

 

From: Paul Berry [mailto:pmberry2...@gmail.com] 
Sent: 03 February 2017 14:35
To: SK53
Cc: talk-gb
Subject: Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

 

Thanks again. I'll tag the textured paving as a barrier.

 

Also, in the Leeds example I've given, cycling is not permitted because there 
is a No Entry sign at each end of the path. This is something that is also 
picked up on here: http://www.andypreece.co.uk/cycling/fac_leverndale.php

 

Further browsing has revealed Fire Paths are actually fairly common in the 
Glasgow area: https://www.cyclestreets.net/photomap/tags/firepath

 

You learn something new every day.

 

Regards,

Paul

 

On 3 February 2017 at 13:54, SK53  wrote:

I'd think that the rows of raised-textured paving can be mapped as a barrier, 
with access=emergency too.

I'm glad that the photos I added to the wiki confirm my memory that "fire path" 
is the word used on the signs. Was wondering where I got it from.

Cheers,

Jerry

 

On 3 February 2017 at 12:20, Paul Berry  wrote:

Thanks, Jerry. I thought the Nottingham features would get your attention :)

I'm surprised I missed the Fire Path page on the Wiki, but thanks for the 
confirmation that fire_path=yes is the way to go.

 

As for the textured paving, I'm not sure anything surface= or traffic_calming= 
matches it, so I'll not tag it.

 

(Out of interest, this Aberdeen one used to be a Fire Path, but the 
emergency/access tags have not been updated accordingly: 
https://www.openstreetmap.org/way/124065409)

 

Regards,

Paul

 

 

 

On 3 February 2017 at 11:17, SK53  wrote:

Looks like a documented on the wiki: 
https://wiki.openstreetmap.org/wiki/Fire_Path

 

On 3 February 2017 at 11:15, SK53  wrote:

The tag that I have used for such things is fire_path=yes.

There are 4 uses of the tag in Nottingham and 2 in Aberdeen. There are several 
others not tagged (including the two recent ones you mention), for instance 
this one   where Suez Street joins 
North Gate outside Port Said Villas (I wonder when these streets were built).

The structures involved may be as illustrated by Paul. The older Nottingham 
ones tend to have a zone of the wavy block paving which is 10-15ft long and 
thus not a normal road in any sense. Other fire paths I've seen involve two 
locked boom gates.

Jerry

 

On 2 February 2017 at 22:20, Paul Berry  wrote:

Hi everyone,

 

Fire roads are an uncommon sight in the UK. They're sometimes signed as "fire 
lanes," but they're nothing to do with the designation in the US (and 
elsewhere) which is a parking restriction: 
https://wiki.openstreetmap.org/wiki/Key:parking:lane and we're also not talking 
about the wide tracks in managed forests that act as a firebreak.

 

I mean restricted highways like this one: 
http://www.openstreetmap.org/way/240007969 (whose source links to photo 
evidence).

 

How do we map these? I assume service=emergency_access?

 

Also, how is the embedded roughly-textured paving in that photo best 
represented?

 

There are some similar ones in Nottingham, notably at Addington Road and 
Wimbourne Road there, though they're not mapped as such.

 

Your advice and guidance gratefully received.

 

Regards,

Paul

 

 

 


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

 

 

 

 

 

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

[OSM-talk-fr] traffic_signals changement de schema

[Jérôme Seigneuret]

Bonjour, suite à l'apparition d'un nouveau schéma  dans le wiki
http://wiki.openstreetmap.org/wiki/FR:Key:traffic_signals:direction pour la
prise en compte des directions sur les sens des feux de circulation, Osmose
propose d'intégrer le sens à prendre

Si le feu n'a pas de direction il propose :
traffic_signals:direction=backward
traffic_signals:direction=forward

Cela est en accord avec la page du wiki.

J'ai donc pris en considération les informations et j'ai mis à jour les
feux de circulation dans le cas suivant (en ayant pris soin de vérifier les
intersections concernés)

passage de
highway=traffic_signals + direction=forward >  highway=traffic_signals +
traffic_signals:direction=forward

highway=traffic_signals + direction=backward >  highway=traffic_signals +
traffic_signals:direction=backward

Pour les cas sans information la proposition d'intégration est toujours
proposé par osmose car il n'y a pas de tag direction.
-- 
Cordialement,
Jérôme Seigneuret
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

[Paul Berry]

Thanks again. I'll tag the textured paving as a barrier.

Also, in the Leeds example I've given, cycling is not permitted because
there is a No Entry sign at each end of the path. This is something that is
also picked up on here:
http://www.andypreece.co.uk/cycling/fac_leverndale.php

Further browsing has revealed Fire Paths are actually fairly common in the
Glasgow area: https://www.cyclestreets.net/photomap/tags/firepath

You learn something new every day.

Regards,
*Paul*

On 3 February 2017 at 13:54, SK53  wrote:

> I'd think that the rows of raised-textured paving can be mapped as a
> barrier, with access=emergency too.
>
> I'm glad that the photos I added to the wiki confirm my memory that "fire
> path" is the word used on the signs. Was wondering where I got it from.
>
> Cheers,
>
> Jerry
>
> On 3 February 2017 at 12:20, Paul Berry  wrote:
>
>> Thanks, Jerry. I thought the Nottingham features would get your attention
>> :)
>>
>> I'm surprised I missed the Fire Path page on the Wiki, but thanks for the
>> confirmation that fire_path=yes is the way to go.
>>
>> As for the textured paving, I'm not sure anything surface=
>> or traffic_calming= matches it, so I'll not tag it.
>>
>> (Out of interest, this Aberdeen one used to be a Fire Path, but the
>> emergency/access tags have not been updated accordingly:
>> https://www.openstreetmap.org/way/124065409)
>>
>> Regards,
>> *Paul*
>>
>>
>>
>> On 3 February 2017 at 11:17, SK53  wrote:
>>
>>> Looks like a documented on the wiki: https://wiki.openstreetmap.org
>>> /wiki/Fire_Path
>>>
>>> On 3 February 2017 at 11:15, SK53  wrote:
>>>
 The tag that I have used for such things is fire_path=yes.

 There are 4 uses of the tag in Nottingham and 2 in Aberdeen. There are
 several others not tagged (including the two recent ones you mention), for
 instance this one  where
 Suez Street joins North Gate outside Port Said Villas (I wonder when these
 streets were built).

 The structures involved may be as illustrated by Paul. The older
 Nottingham ones tend to have a zone of the wavy block paving which is
 10-15ft long and thus not a normal road in any sense. Other fire paths I've
 seen involve two locked boom gates.

 Jerry

 On 2 February 2017 at 22:20, Paul Berry  wrote:

> Hi everyone,
>
> Fire roads are an uncommon sight in the UK. They're sometimes signed
> as "fire lanes," but they're nothing to do with the designation in the US
> (and elsewhere) which is a parking restriction: https://wiki.open
> streetmap.org/wiki/Key:parking:lane and we're also not talking about
> the wide tracks in managed forests that act as a firebreak.
>
> I mean restricted highways like this one:
> http://www.openstreetmap.org/way/240007969 (whose source links to
> photo evidence).
>
> How do we map these? I assume service=emergency_access?
>
> Also, how is the embedded roughly-textured paving in that photo best
> represented?
>
> There are some similar ones in Nottingham, notably at Addington Road
> and Wimbourne Road there, though they're not mapped as such.
>
> Your advice and guidance gratefully received.
>
> Regards,
> *Paul*
>
>
>
>
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>
>

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

Re: [OSM-talk] OSM for government

[john whelan]

The only OSM based project I know of at Stats Canada is the building
project.  The Census is something completely different.  The sort of issues
that are coming up are questions on data quality and can some Open Data be
integrated into OSM.  Another problem is inconsistent tagging.

At the end of January there were some 204 different users who had touched a
building which has built up over the last few months.  In August 2016 we
had 50,000 building tags by the end of January nearly 150,000 so I think we
are getting new mappers into OSM and the data is being enriched.

 There is some interest in Zambia as well at the moment especially as their
Census data isn't exactly up to date and the population is growing very
quickly.

What appears to be happening is data from OSM is processed then counted
using R from R.org an open source statistical package.

Cheerio John

On 3 February 2017 at 08:44, joost schouppe 
wrote:

> Hi,
>
> With the Belgian community, we're making some careful progress into
> getting government to really integrate OSM/VGI into their data management
> efforts. So not talking about background maps here, real data contribution
> or community engagement.
>
> There are some very specific issues and opportunities there. I believe the
> Canadian Census is going that way. Are there any other projects in this
> direction? Is there anything like a project catalogue around?
>
> --
> Joost Schouppe
> OpenStreetMap  |
> Twitter  | LinkedIn
>  | Meetup
> 
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

[SK53]

I'd think that the rows of raised-textured paving can be mapped as a
barrier, with access=emergency too.

I'm glad that the photos I added to the wiki confirm my memory that "fire
path" is the word used on the signs. Was wondering where I got it from.

Cheers,

Jerry

On 3 February 2017 at 12:20, Paul Berry  wrote:

> Thanks, Jerry. I thought the Nottingham features would get your attention
> :)
>
> I'm surprised I missed the Fire Path page on the Wiki, but thanks for the
> confirmation that fire_path=yes is the way to go.
>
> As for the textured paving, I'm not sure anything surface=
> or traffic_calming= matches it, so I'll not tag it.
>
> (Out of interest, this Aberdeen one used to be a Fire Path, but the
> emergency/access tags have not been updated accordingly: https://www.
> openstreetmap.org/way/124065409)
>
> Regards,
> *Paul*
>
>
>
> On 3 February 2017 at 11:17, SK53  wrote:
>
>> Looks like a documented on the wiki: https://wiki.openstreetmap.org
>> /wiki/Fire_Path
>>
>> On 3 February 2017 at 11:15, SK53  wrote:
>>
>>> The tag that I have used for such things is fire_path=yes.
>>>
>>> There are 4 uses of the tag in Nottingham and 2 in Aberdeen. There are
>>> several others not tagged (including the two recent ones you mention), for
>>> instance this one  where
>>> Suez Street joins North Gate outside Port Said Villas (I wonder when these
>>> streets were built).
>>>
>>> The structures involved may be as illustrated by Paul. The older
>>> Nottingham ones tend to have a zone of the wavy block paving which is
>>> 10-15ft long and thus not a normal road in any sense. Other fire paths I've
>>> seen involve two locked boom gates.
>>>
>>> Jerry
>>>
>>> On 2 February 2017 at 22:20, Paul Berry  wrote:
>>>
 Hi everyone,

 Fire roads are an uncommon sight in the UK. They're sometimes signed as
 "fire lanes," but they're nothing to do with the designation in the US (and
 elsewhere) which is a parking restriction: https://wiki.open
 streetmap.org/wiki/Key:parking:lane and we're also not talking about
 the wide tracks in managed forests that act as a firebreak.

 I mean restricted highways like this one:
 http://www.openstreetmap.org/way/240007969 (whose source links to
 photo evidence).

 How do we map these? I assume service=emergency_access?

 Also, how is the embedded roughly-textured paving in that photo best
 represented?

 There are some similar ones in Nottingham, notably at Addington Road
 and Wimbourne Road there, though they're not mapped as such.

 Your advice and guidance gratefully received.

 Regards,
 *Paul*




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


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

[OSM-talk] OSM for government

[joost schouppe]

Hi,

With the Belgian community, we're making some careful progress into getting
government to really integrate OSM/VGI into their data management efforts.
So not talking about background maps here, real data contribution or
community engagement.

There are some very specific issues and opportunities there. I believe the
Canadian Census is going that way. Are there any other projects in this
direction? Is there anything like a project catalogue around?

-- 
Joost Schouppe
OpenStreetMap  |
Twitter  | LinkedIn
 | Meetup

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

Re: [Talk-us] [Talk-US] tagging rumble-strip-separated road shoulders

[Paul Johnson]

On Fri, Feb 3, 2017 at 7:15 AM, Volker Schmidt  wrote:

> Last fall I travelled by bike the ACA Route 66 westbound. Long stretches
> are on freeway/trunk shoulders.
> I think I know how to map shoulders:
> highway=motorway|trunk
> oneway=yes
> shoulder=right
> shoulder:surface= ...
> shoulder:width= ...
> shoulder:smoothness ...
>
> In the case of undivided roads:
> highway= ...
> oneway=no
> shoulder=right|left|both
> shoulder:surface= ... OR shoulder:right:surface= ... OR
> shoulder:left:surface=
> shoulder:width= ... OR shoulder:right:width= ... OR shoulder:left:width=
> shoulder:smoothness ... OR shoulder:right:smoothness= ... OR
> shoulder:left:smoothness=
>


Two questions arise:
>
>
>
> *(1) How to tag the bicycle access:*
> on the highway with bicycle=yes
> or restricted to the shoulder with the lane= tag: lane:bicycle=no|no|yes
> (in case of a two lane-plus-shoulder highway.
> Problem with the bicycle tagging on the shoulder only is that bicycle
> routing algorithms won't route you across access ramps, which are
> implicitly bicycle=no.
> In fact there is even a legal problem there: many freeways have signs:
> "bicycle use shoulder" which you cannot obey at the ramps.
>

Well, the shoulder wouldn't count as a lane (a bicycle lane would,
however).  Not quite sure how to tag the bicycle use shoulder case (though
I am aware that it is extremely common in the US), but if it were an
actual, bicycle-only lane instead, assuming three lanes on a side with the
right lane being bicycle only, and signage indicating that bicycles must
use the bicycle lane:

lanes=3
oneway=yes
cycleway=lane
motor_vehicle:lanes=yes|yes|no
bicycle:lanes=no|no|designated

This may seem overkill to some people, but I'm aware of quite a few places
where there's multiple bicycle lanes, where the bicycle lane is not the
curb lane, and other arrangements that would otherwise just mess up lane
guidance if you omit this and I've found fun edge cases in almost as many
places as I've found bicycle lanes.


> (2) how to tag longitudinal rumble strips,
> (situated between motorized-traffic lanes and shoulders, example: [1], not
> the "sleeping policeman" type that goes across the road nd which is
> normally tagged as traffic_calming=rumble_strip on a node of the highway)
> To tag their presence is important because they represent an augmented
> protection of cyclists on the shoulder from cars invading the shoulder by
> mistake, i.e. reduced risk of being killed.
> To note that I have encountered rumble-strip-separated shoulders also on
> roads below the rank of trunk or motorway
>

I'm not quite sure how necessary it is at this point.  The kind of example
you have provided is being phased out in favor of strips with gaps in them
so bicyclists can get on and off the shoulder without dealing with the
rumbles, or eliminated on roads with a narrow hard shoulder.  In both
cases, for the reason for that is that not taking bicycles into account
does more harm than good.  This is true even on routes that are normally
closed to bicyclists except when police tell you to use it anyway (like
Interstate 70 in Kansas).
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-cz] Fwd: Využití Ortofotomapy pro OpenStreetMap

[Matej Lieskovský]

Ahoj,

povedlo se mi zařídit něco zajímavého. Cituji:

"IPR Praha souhlasí s využíváním ortofotografií, které poskytuje
prostřednictvím Geoportálu hl. m. Prahy, za účelem aktualizace a doplňování
databáze OpenStreetMap, přičemž vzniklá vektorová data smí být vložena do
OSM pod licencí ODbL za předpokladu, že IPR bude uveden v seznamu
přispěvatelů do OSM a takto vzniklá data budou mít IPR uveden jako svůj
zdroj."

Konec citace.

Na http://wiki.openstreetmap.org/wiki/Contributors přidám IPR sám, prosím
uvádějte k zakreslovaným věcem "source=CZ:IPRPraha:ortofoto", ať jsou na
IPR spokojeni.

Rád bych poděkoval Jethrovi, který mi pomáhal formulovat maily.

S pozdravem,
Matej Lieskovský

PS: Přeposílám emailovou konverzaci

-- Forwarded message --
From: Baron Bohdan Mgr. (IPR/SPI) 
Date: 2017-02-03 12:16 GMT+01:00
Subject: RE: Využití Ortofotomapy pro OpenStreetMap
To: Matej Lieskovský 


Dobry den,



omlouvam se za pozdejsi odpoved, ale mel jsem toho pomerne hodne k reseni.



IPR Praha souhlasí s využíváním ortofotografií, které poskytuje
prostřednictvím Geoportálu hl. m. Prahy, za účelem aktualizace a doplňování
databáze OpenStreetMap, přičemž vzniklá vektorová data smí být vložena do
OSM pod licencí ODbL za předpokladu, že IPR bude uveden v seznamu
přispěvatelů do OSM a takto vzniklá data budou mít IPR uveden jako svůj
zdroj.



S pozdravem

Bohdan Baron



*From:* Matej Lieskovský [mailto:lieskovsky.ma...@gmail.com]
*Sent:* Wednesday, February 01, 2017 1:44 PM

*To:* Baron Bohdan Mgr. (IPR/SPI) 
*Subject:* Re: Využití Ortofotomapy pro OpenStreetMap



Dobrý den,
zatím jsem nedostal žádnou odpověď na můj předchozí email. Dostal jste jej?
Opět prosím o zaslání toho souhlasu, ať můžeme začít doplňovat.
S pozdravem,
Matej Lieskovský



2017-01-25 10:58 GMT+01:00 Matej Lieskovský :

Dobrý den,
pokud Vám to nevadí, asi by bylo lepší poslat tu větu samostatně, ať je to
jednoznačné.
Statistiky dodáme.
S pozdravem
Matej Lieskovský



2017-01-25 10:15 GMT+01:00 Baron Bohdan Mgr. (IPR/SPI) :

Dobry den,



s timto postupem urcite souhlasime a urcite s timto nemame absolutne zadny
problem. Obdobne jsme uz s ortofoto postupovali i u jinych subjektu. Mam
Vam prosim tedy zaslat Vami zminenou vetu v samostatnem mailu nebo staci,
ze Vam odsouhlasim Vam,i zminene zneni v tomto mailu?

Ten vycet je urcite zajimavy. Jednou za rok by nas to trosku i z profesniho
hledika zajimalo. :-)

S pozdravem

Bohdan Baron



*From:* Matej Lieskovský [mailto:lieskovsky.ma...@gmail.com]
*Sent:* Wednesday, January 25, 2017 9:36 AM


*To:* Baron Bohdan Mgr. (IPR/SPI) 
*Subject:* Re: Využití Ortofotomapy pro OpenStreetMap



Dobrý den,



souhlas s použitím pro aktualizaci OSM nám naprosto stačí. Licence u Vašich
originálních dat (tedy ortofotek) se vůbec nebude měnit, potřebujeme pouze
souhlas s tím, že vektorová data, která za pomoci Vašich ortofotografií
vytvoříme a přidáme do OSM, smí být šířena pod licencí ODbL, pod kterou
spadá celá OSM. ODbL (http://opendatacommons.org/licenses/odbl/) je licence
v mnoha ohledech podobná CC BY-SA (OSM také původně CC BY-SA používala) ale
je více zaměřená na použití pro databáze (CC BY-SA je spíše zaměřená na
text, fotky, audionahrávky a videa). ODbL dovoluje data šířit, adaptovat a
vytvářet odvozená díla za předpokladu, že je zachována otevřenost dat,
stejná licence a uveden autor. Vzhledem k tomu, že OSM obsahuje data od
velkého počtu různých přispěvatelů, není prakticky proveditelné, aby na
každém kousku mapy byly uvedeny všechny zdroje - proto OSM používá označení
"(c) OpenStreetMap Contributors" a IPR Praha by byl uveden na
http://wiki.openstreetmap.org/wiki/Contributors. Současně jsme ochotni se
zavázat (a je možné uvést do souhlasu jakož to podmínku), že vektorová data
odvozená od Vašich ortofotografií budou mít v databázi OSM nastaveno
"source=CZ:IPRPraha:ortofoto" (jedná se o relativně běžný způsob, jak v OSM
identifikovat původ dat*), díky čemuž bude mimo jiné možné relativně přesně
určit, co vše bylo díky Vaší vstřícnosti možné zmapovat.



Doufám, že výše uvedené je dostatečné k udělení souhlasu. Nejsem právník,
takže tohle nepovažujte za návrh doslovného znění souhlasu, ale
představovali bychom si přibližně následující: "IPR Praha souhlasí s
využíváním ortofotografií, které poskytuje prostřednictvím Geoportálu
Praha, za účelem aktualizace a doplňování databáze OpenStreetMap, přičemž
vzniklá vektorová data smí být vložena do OSM pod licencí ODbL za
předpokladu, že IPR bude uveden v seznamu přispěvatelů do OSM a takto
vzniklá data budou mít IPR uveden jako svůj zdroj."



Dovolím si zopakovat, že se bude jednat pouze o vektorová data vytvořená za
pomoci Vašich ortofotografií. Vašich ostatních dat se tento souhlas vůbec
nemusí týkat a ani ortofotografie nebude možné šířit pod jinou licencí, než
je ta Vaše. Vektorová data pak navíc budou šířena 

RE: Re: [Talk-dk] Vedr. indl�sning af data vedr. hastigshedsgr�nser

[kim]

Jakob skrev:

> Kan den ikke bruges? Hvad bruger I andre?

Sidst jeg rodede med hastighed, brugte jeg rasher.dk (der var mange gode 
informative layers på den server), og har savnet den meget.

Jeg har ikke prøvet itoworld før, men den ser ud som en god erstatning.

Jeg vil gennemgå lokalområdet og få det rettet op.

/Kim

> Niels skrev:
>  
> > Men vi kan komme langt ved at vise, hvor vi mangler hastighedsgrænser i
> > OSM.
> 
> Jeg mener at kunne huske, at der var et godt værktøj til at vise fartgrænser 
> på http://osm.rasher.dk, men serveren er taget ned - så nu bruger jeg denne:
> 
> http://product.itoworld.com/map/124?lon=11.71158=56.24868=8_sidebar=map_key=true
> 
> Kan den ikke bruges? Hvad bruger I andre?
> 
> -- 
> Jakob
> 
> 
> ___
> Talk-dk mailing list
> Talk-dk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-dk


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

[Talk-us] [Talk-US] tagging rumble-strip-separated road shoulders

[Volker Schmidt]

Last fall I travelled by bike the ACA Route 66 westbound. Long stretches
are on freeway/trunk shoulders.
I think I know how to map shoulders:
highway=motorway|trunk
oneway=yes
shoulder=right
shoulder:surface= ...
shoulder:width= ...
shoulder:smoothness ...

In the case of undivided roads:
highway= ...
oneway=no
shoulder=right|left|both
shoulder:surface= ... OR shoulder:right:surface= ... OR
shoulder:left:surface=
shoulder:width= ... OR shoulder:right:width= ... OR shoulder:left:width=
shoulder:smoothness ... OR shoulder:right:smoothness= ... OR
shoulder:left:smoothness=

Two questions arise:



*(1) How to tag the bicycle access:*
on the highway with bicycle=yes
or restricted to the shoulder with the lane= tag: lane:bicycle=no|no|yes
(in case of a two lane-plus-shoulder highway.
Problem with the bicycle tagging on the shoulder only is that bicycle
routing algorithms won't route you across access ramps, which are
implicitly bicycle=no.
In fact there is even a legal problem there: many freeways have signs:
"bicycle use shoulder" which you cannot obey at the ramps.

(2) how to tag longitudinal rumble strips,
(situated between motorized-traffic lanes and shoulders, example: [1], not
the "sleeping policeman" type that goes across the road nd which is
normally tagged as traffic_calming=rumble_strip on a node of the highway)
To tag their presence is important because they represent an augmented
protection of cyclists on the shoulder from cars invading the shoulder by
mistake, i.e. reduced risk of being killed.
To note that I have encountered rumble-strip-separated shoulders also on
roads below the rank of trunk or motorway

Volker
(Padova, Italy)

[1] https://www.mapillary.com/map/im/4SFBFwxPLQHq2g-FJ2Qaag
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[OSM-talk-be] a new National Mapathon - call for volunteers

[Lionel Giard]

Hi Joost,

I'll be happy to volunteer at *UCL (Louvain-la-Neuve) ! :-)*

I can help to everything as i'm used to work with hotosm/id/... and
mapathon in general (*MSF mapathon T-shirt owner club inside :p*).

Lionel Giard

*De :* joost schouppe [mailto:joost.schou...@gmail.com]
*Envoyé :* vendredi 3 février 2017 08:40
*À :* OpenStreetMap Belgium 
*Objet :* [OSM-talk-be] a new National Mapathon - call for volunteers



Hi,



Last year, the Interuniversity National Mapathon was a great success: about
200 people in seven universities participated, and we got in the 7 pm news
issue of both VRT and VTM.

OSM-Be volunteers supported all seven events.



The next national mapathon is being planned right now, and they want our
help again!



We will need volunteers at ULB (Brussels), VUB (Brussels), UCL
(Louvain-la-Neuve), KUL (Leuven), Ugent, ULG (Liege), UNamur. Four more
cities might still join in the following days.



Previous experience with humanitarian mapping, iD and the Tasking Manager
is of course welcome, but we will give you some training too. Last year, it
wasn't easy finding volunteers for all places, but it is important that
there is an experienced mapper at all of these places.



Basically we need you for any or all of these tasks:

- give an introduction about (humanitarian) OSM, a short training

- just being around and helping people with questions

- validating (even from home) during the event, so we can correct newbie
mappers before they make the same mistake a thousand times



Just send me a mail with your preferred tasks and city (or cities) and
we'll be in touch.



--

Joost Schouppe

OpenStreetMap  |
Twitter  | LinkedIn
 | Meetup


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

Re: [OSM-talk-be] mapper meeting in BXL/reunion de mappeurs à BXL 21/02

[Jonathan Beliën]

Thanks Marc !

 

I updated the Maptime page : http://maptime.io/belgium/

 

See you there.

 

Jonathan Beliën

GEO-6

 

De : Bessières, Marc [mailto:marc.bessie...@mykolab.com] 
Envoyé : vendredi 3 février 2017 12:31
À : OpenStreetMap Belgium 
Objet : [OSM-talk-be] mapper meeting in BXL/reunion de mappeurs à BXL 21/02

 

Hello,

I've just created a meetup for the next meetup in BXL on Tuesday the 21st of 
February at the sister café near the Grand Place

Everybody is more than welcome to come!

https://www.meetup.com/OpenStreetMap-Belgium/events/237424260/

 

Looking forward seeing you there!

Marc

 

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

Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

[Paul Berry]

Thanks, Jerry. I thought the Nottingham features would get your attention :)

I'm surprised I missed the Fire Path page on the Wiki, but thanks for the
confirmation that fire_path=yes is the way to go.

As for the textured paving, I'm not sure anything surface=
or traffic_calming= matches it, so I'll not tag it.

(Out of interest, this Aberdeen one used to be a Fire Path, but the
emergency/access tags have not been updated accordingly:
https://www.openstreetmap.org/way/124065409)

Regards,
*Paul*



On 3 February 2017 at 11:17, SK53  wrote:

> Looks like a documented on the wiki: https://wiki.openstreetmap.
> org/wiki/Fire_Path
>
> On 3 February 2017 at 11:15, SK53  wrote:
>
>> The tag that I have used for such things is fire_path=yes.
>>
>> There are 4 uses of the tag in Nottingham and 2 in Aberdeen. There are
>> several others not tagged (including the two recent ones you mention), for
>> instance this one  where
>> Suez Street joins North Gate outside Port Said Villas (I wonder when these
>> streets were built).
>>
>> The structures involved may be as illustrated by Paul. The older
>> Nottingham ones tend to have a zone of the wavy block paving which is
>> 10-15ft long and thus not a normal road in any sense. Other fire paths I've
>> seen involve two locked boom gates.
>>
>> Jerry
>>
>> On 2 February 2017 at 22:20, Paul Berry  wrote:
>>
>>> Hi everyone,
>>>
>>> Fire roads are an uncommon sight in the UK. They're sometimes signed as
>>> "fire lanes," but they're nothing to do with the designation in the US (and
>>> elsewhere) which is a parking restriction: https://wiki.open
>>> streetmap.org/wiki/Key:parking:lane and we're also not talking about
>>> the wide tracks in managed forests that act as a firebreak.
>>>
>>> I mean restricted highways like this one: http://www.openstreetmap.org/w
>>> ay/240007969 (whose source links to photo evidence).
>>>
>>> How do we map these? I assume service=emergency_access?
>>>
>>> Also, how is the embedded roughly-textured paving in that photo best
>>> represented?
>>>
>>> There are some similar ones in Nottingham, notably at Addington Road and
>>> Wimbourne Road there, though they're not mapped as such.
>>>
>>> Your advice and guidance gratefully received.
>>>
>>> Regards,
>>> *Paul*
>>>
>>>
>>>
>>>
>>> ___
>>> Talk-GB mailing list
>>> Talk-GB@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-gb
>>>
>>>
>>
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-it] R: Utente che modifica confini

[Martin Koppenhoefer]

sent from a phone

> Am 03.02.2017 um 11:46 schrieb Alessandro :
> 
> Un paio di mesi fa se ne discusse ma sembrava che fosse il contrario. Quella 
> dei confini su un corso d'acqua è una regola che vale sempre o ci possono 
> essere eccezioni?


in sostanza un confine è approvato quando entrambe le parti lo accettano

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

[OSM-talk-be] mapper meeting in BXL/reunion de mappeurs à BXL 21/02

[Bessières , Marc]

Hello, 

I've just created a meetup for the next meetup in BXL on Tuesday the
21st of February at the sister café near the Grand Place 

Everybody is more than welcome to come! 

https://www.meetup.com/OpenStreetMap-Belgium/events/237424260/ 

Looking forward seeing you there! 

Marc

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

Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

[SK53]

Looks like a documented on the wiki:
https://wiki.openstreetmap.org/wiki/Fire_Path

On 3 February 2017 at 11:15, SK53  wrote:

> The tag that I have used for such things is fire_path=yes.
>
> There are 4 uses of the tag in Nottingham and 2 in Aberdeen. There are
> several others not tagged (including the two recent ones you mention), for
> instance this one  where Suez
> Street joins North Gate outside Port Said Villas (I wonder when these
> streets were built).
>
> The structures involved may be as illustrated by Paul. The older
> Nottingham ones tend to have a zone of the wavy block paving which is
> 10-15ft long and thus not a normal road in any sense. Other fire paths I've
> seen involve two locked boom gates.
>
> Jerry
>
> On 2 February 2017 at 22:20, Paul Berry  wrote:
>
>> Hi everyone,
>>
>> Fire roads are an uncommon sight in the UK. They're sometimes signed as
>> "fire lanes," but they're nothing to do with the designation in the US (and
>> elsewhere) which is a parking restriction: https://wiki.open
>> streetmap.org/wiki/Key:parking:lane and we're also not talking about the
>> wide tracks in managed forests that act as a firebreak.
>>
>> I mean restricted highways like this one: http://www.openstreetmap.org/w
>> ay/240007969 (whose source links to photo evidence).
>>
>> How do we map these? I assume service=emergency_access?
>>
>> Also, how is the embedded roughly-textured paving in that photo best
>> represented?
>>
>> There are some similar ones in Nottingham, notably at Addington Road and
>> Wimbourne Road there, though they're not mapped as such.
>>
>> Your advice and guidance gratefully received.
>>
>> Regards,
>> *Paul*
>>
>>
>>
>>
>> ___
>> Talk-GB mailing list
>> Talk-GB@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-gb
>>
>>
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-GB] Fire Roads (Leeds, Nottingham, etc)

[SK53]

The tag that I have used for such things is fire_path=yes.

There are 4 uses of the tag in Nottingham and 2 in Aberdeen. There are
several others not tagged (including the two recent ones you mention), for
instance this one  where Suez
Street joins North Gate outside Port Said Villas (I wonder when these
streets were built).

The structures involved may be as illustrated by Paul. The older Nottingham
ones tend to have a zone of the wavy block paving which is 10-15ft long and
thus not a normal road in any sense. Other fire paths I've seen involve two
locked boom gates.

Jerry

On 2 February 2017 at 22:20, Paul Berry  wrote:

> Hi everyone,
>
> Fire roads are an uncommon sight in the UK. They're sometimes signed as
> "fire lanes," but they're nothing to do with the designation in the US (and
> elsewhere) which is a parking restriction: https://wiki.
> openstreetmap.org/wiki/Key:parking:lane and we're also not talking about
> the wide tracks in managed forests that act as a firebreak.
>
> I mean restricted highways like this one: http://www.openstreetmap.org/
> way/240007969 (whose source links to photo evidence).
>
> How do we map these? I assume service=emergency_access?
>
> Also, how is the embedded roughly-textured paving in that photo best
> represented?
>
> There are some similar ones in Nottingham, notably at Addington Road and
> Wimbourne Road there, though they're not mapped as such.
>
> Your advice and guidance gratefully received.
>
> Regards,
> *Paul*
>
>
>
>
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

[Talk-es] Reunión febrero OSM-ES

[Santiago Crespo]

Hola,

La próxima reunión OSM-ES será el próximo martes 7 a las 22:00, en la
sala habitual:
https://riot.im/app/#/room/#osm-es-reuniones:matrix.org

El acta de la última reunión:
http://wiki.osm.org/wiki/ES:Acta_20170103

Si queréis tratar algún tema añadidlo al orden del día:
http://wiki.osm.org/wiki/ES:Orden_del_día_siguiente_reunión_OSM-ES

Saludos,
Santiago Crespo


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

Re: [Talk-it] R: Utente che modifica confini

[Alessandro]

Il 03/02/2017 11:16, Giuseppe Amici ha scritto:

Attenzione:
se anche l'erosione fluviale ha spostato il corso d'acqua,
NON è detto che si sposti il confine ANZI.

Caso pratico:
Tra il confine di Sassuolo provincia di Modena, e Veggia di Casalgrande provincia di RE, 
il comune di Sassuolo è "proprietario" per territorialità di terreno oltre 
alveo fluviale (apparentemente in territorio oltre fluviale)




Un paio di mesi fa se ne discusse ma sembrava che fosse il contrario. 
Quella dei confini su un corso d'acqua è una regola che vale sempre o ci 
possono essere eccezioni?


Alessandro



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

[Talk-it] R: Utente che modifica confini

[Giuseppe Amici]

Attenzione:
se anche l'erosione fluviale ha spostato il corso d'acqua,
NON è detto che si sposti il confine ANZI.

Caso pratico:
Tra il confine di Sassuolo provincia di Modena, e Veggia di Casalgrande 
provincia di RE, il comune di Sassuolo è "proprietario" per territorialità di 
terreno oltre alveo fluviale (apparentemente in territorio oltre fluviale)



-Messaggio originale-
Da: emmexx [mailto:emm...@tiscalinet.it] 
Inviato: giovedì 20 ottobre 2016 12:58
A: openstreetmap list - italiano 
Oggetto: Re: [Talk-it] Utente che modifica confini

On 10/20/2016 11:52 AM, Carlo Stemberger wrote:
> 
> La provincia di Bergamo e quelle di Milano/MB/Lecco in buona parte 
> sono definite dal corso del fiume Adda (fin dai tempi della 
> Serenissima). Se l'Adda erode una sponda, di conseguenza anche il 
> confine tra le province si sposta.

Non so, lungo il Ticino il confine molto spesso non coincide col fiume che ha 
cambiato corso nel tempo. In alcuni casi ci sono spiagge a cui si accede dal 
lato lombardo che sono indicate come appartenenti al Piemonte.

http://www.geoportale.piemonte.it/geocatalogorp/?sezione=mappa

Ma le forze di polizia e la magistratura che criterio usano per stabilire dove 
e' avvenuto un reato? Faranno riferimento a qualche banca dati?

ciao
maxx

___
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-dk] Vedr. indlæsning af data vedr. hastigshedsgrænser

[Jakob Barfod]

Niels skrev:
 
> Men vi kan komme langt ved at vise, hvor vi mangler hastighedsgrænser i
> OSM.

Jeg mener at kunne huske, at der var et godt værktøj til at vise fartgrænser på 
http://osm.rasher.dk, men serveren er taget ned - så nu bruger jeg denne:

http://product.itoworld.com/map/124?lon=11.71158=56.24868=8_sidebar=map_key=true

Kan den ikke bruges? Hvad bruger I andre?

-- 
Jakob


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

Re: [OSM-talk-be] a new National Mapathon - call for volunteers

[Julien Minet]

Hi Joost,

I'm willing to help and I propose to organize a local mapathon section in
Arlon (ULg campus) ONLY IF there is sufficient volunteers for other cities.
Otherwise, I can go to Namur like last year.

I have to talk with some colleagues here in Arlon to see what's possible
(not a lot of students in the 2nd quadrimester).

I let you know,
Julien Minet


On Fri, Feb 3, 2017 at 8:40 AM, joost schouppe 
wrote:

> Hi,
>
> Last year, the Interuniversity National Mapathon was a great success:
> about 200 people in seven universities participated, and we got in the 7 pm
> news issue of both VRT and VTM.
> OSM-Be volunteers supported all seven events.
>
> The next national mapathon is being planned right now, and they want our
> help again!
>
> We will need volunteers at ULB (Brussels), VUB (Brussels), UCL
> (Louvain-la-Neuve), KUL (Leuven), Ugent, ULG (Liege), UNamur. Four more
> cities might still join in the following days.
>
> Previous experience with humanitarian mapping, iD and the Tasking Manager
> is of course welcome, but we will give you some training too. Last year, it
> wasn't easy finding volunteers for all places, but it is important that
> there is an experienced mapper at all of these places.
>
> Basically we need you for any or all of these tasks:
> - give an introduction about (humanitarian) OSM, a short training
> - just being around and helping people with questions
> - validating (even from home) during the event, so we can correct newbie
> mappers before they make the same mistake a thousand times
>
> Just send me a mail with your preferred tasks and city (or cities) and
> we'll be in touch.
>
> --
> Joost Schouppe
> OpenStreetMap  |
> Twitter  | LinkedIn
>  | Meetup
> 
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [Talk-dk] Vedr. indlæsning af data vedr. hastigshedsgrænser

[Niels Elgaard Larsen]

Michael Andersen:
> Hej Morten
> 
> Der er med hensyn til opdatering af hastighedsgrænser i OSM ikke nogen reel 
> vej udenom det manuelle arbejde.

Jeg tror godt, at vi kunne lave noget lidt automatisk.

Fx starte med kun at vise afvigelser mellem OSM kommunernes
hastighedsgrænser. Og måske senere håndtere forskelle een ad gangen.

Nogle steder ville man så vide hvor man skulle checke Mapillary efter
skilte. Andre steder ville det give sig selv.

Jeg har rettet en del steder hvor mellemstore veje går gennem små byer.
De fleste steder er hastighedsgrænsen 50 km/t i byzonen, men ikke alle
steder. Det ville være en stor hjælp at kunne se hvor OSM afviger. Og
ret nemt så at det rette manuelt.

110/130 km/t grænser på motorveje er jeg ikke sikker på er helt med i
OSM. Og de ændrer sig over tid, så det ville rart at se hvor vi afviger.

Der en nok en del småveje, hvor der fx en 40 km/t hastighedsgrænse på
hele vejen og hvor der ikke er noget maxspeed tag i OSM. Der kunne vi
godt lave noget kvartautomatisk, så brugere kunne få ændringerne een ad
gangen ind i fx JOSM.

Så er der nogen veje, hvor hastighedsgrænserne varierer meget. Fx Nr 75,
Rømøvej, som har en masse små stykker, hvor hastighedsgrænsen er 70
km/t. Det ville rart at kunne se de steder, er endnu ikke er med i OSM.

Så vi skal for alt i verden undgå at få tusindvis af rettelser, der
splitter veje op for at flytte grænserne et par meter.

Men vi kan komme langt ved at vise, hvor vi mangler hastighedsgrænser i
OSM. Og måske kan vi lave noget, hvor brugere et tag ad gangen kan sætte
et maxspeedtag på et vejstykke, der ikke havde et maxspeed tag i forvejen.




> Bemærk at vi på internationalt plan har en del erfaringer med automatiske 
> redigeringer, som langt fra altid har været heldigt udført og at vi af netop 
> den grund har meget strikse regler med hensyn til den slags: https://
> wiki.openstreetmap.org/wiki/Automated_edits.
> 
> Med mit kendskab til OSM og IT kan jeg ikke forestille mig at et forsøg på 
> automatisk opdatering/"indlæsning" af hastighedsgrænser kan gå godt, så 
> desværre.
> 
> Regn med at forsøg af denne art uden forudgående grundig konsultation med 
> først og fremmest denne liste, næsten med sikkerhed vil blive rullet tilbage.
> 
> Mvh Hjart
> 
> On torsdag den 2. februar 2017 22.56.53 CET Morten Rüsz wrote:
>> Hej alle.
>>
>> Jeg arbejder på et trafiksikkerhedsprojekt, hvor vi benytter os af data fra
>> OSM. I den forbindelse forsøger vi at finde ud af, om det er muligt at
>> opdatere hastighedsgrænserne ved at indlæse dem, frem for at skulle
>> opdatere dem manuelt.
>>
>> Kan I hjælpe mig med dette? Helt konkret vil jeg gerne have hjælp til/viden
>> om følgende:
>>
>>
>>1. *Hvilke dataformater kan anvendes til at uploade hastighedsgrænser i
>>OSM? *Omkring 60 % af kommunerne anvender Vejdirektoratets platform
>>Vejman.dk og jeg er i dialog med med dem, for at blive klogere på, hvilke
>> dataformater de er i stand til at levere hastighedsdata i.
>>2. *Hvordan indlæser jeg større datamængder vedr. hastighedsgrænser?* Er
>>der nogen der erfaringer med dette?
>>
>> Vejdirektoratet har desværre ikke mulighed for at dele dataene med mig (ud
>> over statsvejnettet), da det er kommunerne der ejer dataene. Derfor er vi
>> nødt til at henvende os til dem enkeltvis. Det er jeg dog villig til at
>> gøre, hvis jeg kan finde en enkel løsning mht. at få indlæst disse i OSM.
>>
>> De øvrige kommuner anvender en eller flere andre platforme. Dette har jeg
>> endnu ikke undersøgt nærmere.
>>
>> Jeg er ikke selv specielt it-kyndig, hvorfor jeg vil sætte pris på, at
>> eventuelle svar tager hensyn til dette handicap :o)
>>
>> Håber at I er stand til at hjælpe mig og ser frem til at høre fra jer.
>>
>>
>> Med venlig hilsen
>> Morten Rüsz
>> (mobil: 30209039)
> 
> 
> 
> ___
> Talk-dk mailing list
> Talk-dk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-dk
> 

-- 
Niels Elgaard Larsen

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

Re: [osm-ve] Cuántos somos?

[Wladimir Szczerban]

Hola Sara,

Bienvenida a OSM, como ya han comentado en Venezuela no hay mucha gente
activa y estamos muy distribuidos por el territorio lo que és bueno y malo.
Bueno porque así cada quien mapea su zona y malo porque al estar muy
dispersos no podemos hacer quedadas.

Estaría bien que los que estamos un poco activos nos apuntemos en la página
de la wiki [1] para así poder saber mejor cuantos somos.

[1] http://wiki.openstreetmap.org/wiki/Category:Users_in_Venezuela


El 3 de febrero de 2017, 2:29, Rolando Algarin 
escribió:

> Hola Sara, la verdad no somos muchos, por telegram hay una canal de la
> comunidad Latinoaméricana en OSM, allí también hay varios venezolanos..
> Acá te dejo el canal de Telegram:
> t.me/OSMLatam
>
> También hay canales de otros países pero no de Venezuela por el momento,
> sería cuestión de crearlo.
>
> Saludos.
>
>
> El jue., 2 de feb. de 2017 7:55 PM, Sara Carvajal 
> escribió:
>
>> Hola mappers! Soy relativamente nueva en OSM y quería saber cuántos somos
>> en Venezuela y si existe algún grupo en las redes sociales.
>>
>> Saludos!
>> Sara
>> ___
>> Talk-ve mailing list
>> Talk-ve@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ve
>>
>
> ___
> Talk-ve mailing list
> Talk-ve@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ve
>
>


-- 
Saludos,

Bolo
www.geoinquiets.cat
___
Talk-ve mailing list
Talk-ve@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ve

Re: [Talk-dk] Vedr. indlæsning af data vedr. hastigshedsgrænser

[Ole Laursen]

2. februar 2017 kl. 23.45 skrev Jørgen Elgaard Larsen :
> Morten Rüsz skrev:
>> I den forbindelse forsøger vi at finde ud af, om det er muligt
>> at opdatere hastighedsgrænserne ved at indlæse dem, frem for at skulle
>> opdatere dem manuelt.

En mere realistisk tilgang er måske at få lavet et kortlag der viser
hastighedsgrænser så folk manuelt kunne opdatere ud fra det?

Hvis vi havde sådan et med hastigheder ifølge kommunen og et ifølge
OSM, kunne man sikkert nogenlunde hurtigt få rettet forskellene til.
Personligt rettede jeg gerne hastighedsgrænserne i mit nabolag, men
jeg mangler et datagrundlag at gøre det ud fra for jeg har ikke
mulighed for selv at køre rundt og kigge.

(Og ja, man skal være varsom når man tegner kort fra lænestolen og kun
rette i områder hvor det er åbenlyst at der ikke er nogen der har
været ude og kigge på det.)


Ole

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

Re: [OSM-talk-fr] Création suppression d'intercommunalité

[Christian Quest]

Pour moi c'est OUI, comme les fusions de communes car on a un paquet de
dataviz qui ont besoin de ces contours qui correspondent à des découpages
certes plus actifs mais suffisamment récents pour ne pas être complètement
oubliés et perdus.

disused:xxx et end_data sont nos amis !

Le 3 février 2017 à 09:13, Tony EMERY  a écrit :

> Bonjour à tous,
>
> Du coup, dans le cas d'une modification du contour des EPCI, garde-t-on
> l'historique en créant une nouvelle relation et en renommant l'ancienne ou
> pas ?
>
> Le 3 févr. 2017 09:00, "Christian Quest"  a
> écrit :
>
>> Le 3 février 2017 à 04:40, Jérôme Amagat  a
>> écrit :
>>
>>> Un point sur les EPCI.
>>>
>>> pour Bourgogne-Franche-Comté c'est à jour et ça correspond à cette
>>> source : http://www.ideobfc.fr/accueil/geoservices/catalogue_de_donne
>>> es?uuid=0a78e68d-738c-4284-ae64-e02e74859055=1
>>> Pareil pour Provence-Alpes-Côte d'Azur et cette source :
>>> http://opendata.regionpaca.fr/donnees/detail/etablissement-p
>>> ublic-de-cooperation-intercommunale-au-1er-janvier-2017.html
>>> Normalement c'est à jour aussi pour Auvergne-Rhône-Alpes et pour Pays de
>>> la Loire.
>>>
>>> Pour la Bretagne, ce n'est pas terminé mais si ça tente quelqu'un il y a
>>> cette source pour faire les modifications :
>>> http://www.data.gouv.fr/fr/datasets/epci-en-bretagne-au-01-01-2017/
>>> Pareil pour la Nouvelle-Aquitaine et cette source :
>>> http://www.data.gouv.fr/fr/datasets/nouvelle-aquitaine-perim
>>> etre-des-epci-a-fiscalite-propre-issus-des-sdci-sur-le-perim
>>> etre-regional-et-les-departements-limitrophes-surfacique/
>>> par contre ça parle du Schéma départemental de coopération
>>> intercommunale au 1er janvier 2017 il y a d'autre cas pour des régions ou
>>> des départements sur data.gouv.fr , normalement c'est les modifications
>>> qu'il était prévu de faire mais c'est pas sur quelles soient toutes faites
>>> donc il faut peut être trouver d'autres sources comme des articles de
>>> journaux pour vérifié que les modification ont été faite.
>>> J'ai pas l'impression qu'il y ai des modifications dans les DOM mais
>>> c'est à vérifier.
>>>
>>> Les arrondissements départementaux bougent aussi dans beaucoup de
>>> départements. J'ai fait les modifications pour Bourgogne-Franche-Comté et
>>> Auvergne-Rhône-Alpes que j'ai trouvé dans les arrêtés des préfectures de
>>> régions. je suis allé sur http://www.prefectures-regions.gouv.fr/ puis
>>> sur la région voulu puis sur les Recueil des actes administratifs et
>>> les modifications datent de fin décembre ou de janvier. les modifications
>>> n'ont pas l'air d'avoir été publié au JO il n'y a rien sur
>>> www.legifrance.gouv.fr ça sera peut être le cas dans quelque temps
>>> (pour les communes nouvelles j'ai l'impression que tout n'a pas été publié).
>>>
>>> A cause des communes nouvelles je sais qu'il y a au moins un cas de
>>> modification des limites de département, je sais pas si ça a été fait.
>>>
>>>
>> La limite du département et de la région, ainsi que les académies ont été
>> mises à jour (32 en tout de mémoire) mais une vérification de plus n'est
>> pas inutile.
>>
>>
>>
>>> Rien trouvé sur des modifications des circonscriptions législatives.
>>> J'ai lu quelque part mais je sais plus où que des modifications ne doivent
>>> pas avoir lieu à quelque mois d’élection, il y a des élections dans quelque
>>> mois mais si il n'y a pas de modifications il va y avoir des trucs bizarres
>>> à cause des communes nouvelles.
>>>
>>>
>> Il n'y a pas de changement globalement, mais les fusions de communes
>> peuvent provoquer localement un changement. Je suis en contact avec le
>> bureau des élections du Ministère de l'Intérieur, je vous informerai quand
>> j'aurai du nouveau.
>>
>>
>> Pour les communes nouvelles, il y a une source donnant toutes les commune
>>> nouvelle créés en au 1ert janvier 2017 : https://www.insee.fr/fr/inform
>>> ation/2549968
>>> Normalement Christian les a toutes créées (toutes?). Dans cette source
>>> il y a les communes nouvelles créés mais il y a aussi les communes 
>>> déléguées,
>>> le chef lieu (donc admin_centre pour osm) et le ref:INSEE. Si ça tente du
>>> monde de faire des vérifications sur les communes nouvelles (il y en a
>>> beaucoup avec des fixme qui demandent une vérification du numéro INSEE.
>>>
>>>
>> Ces fusions ont été intégrées. Il y a des "défusions " qui n'ont par
>> contre peut être pas été faites avec nouvelle fusion.
>> Au moins un cas avec Aurseulles, mais visiblement à jour dans OSM:
>> "La commune nouvelle
>> 
>>  regroupe les communes d'Anctoville
>> , de Longraye
>> , de Saint-Germain-d'Ectot
>>  et de
>> Torteval-Quesnay  qui
>> 

Re: [OSM-talk-fr] Nom des cours d’eau dans le cadastre

[Jérôme Seigneuret]

Bonjour,
il n'y a rien d'incohérent avec une extraction "dite du cadastre" car il
existe des outils pour les géomètres avec bases de données déjà enrichies
pour préparer des plans.
Sinon cela peut être extrait du Géoportail avec la surcouche parcelles
cadastrales et une autre source de données en fond de plan comme la carte
IGN en niveau de gris.

exemple


Sinon le géomètre à juste enrichi son fichier DWG...

Donc difficile de dire comment le plan a été réellement créé. Un lien pour
voir le plan serait mieux pour émettre des hypothèses. Le mieux serait de
savoir comment le géomètre a créé son plan (outils, données)

Pour moi les noms sont très rarement inscrit sur le plan cadastral.  En
plus de ça, le nom n'est pas forcément à coté de la parcelle cadastrale
concernée par par l'emprise géographique du plan en question (surtout si
les données d'affichage sont au format raster ou rasterisé pour faire le
fond de plan.

Jérôme

Le 3 février 2017 à 09:07, HELFER Denis (SNCF RESEAU / SIEGE SNCF RESEAU /
DT GE APPUI PERFORMANCE)  a écrit :

> Si si ça fonctionnait encore jusqu'à il y a peu. J'avais lancé une
> bouteille à mer (http://gis.19327.n8.nabble.com/plugin-cadastre-JOSM-
> td5877566.html) , mais elle s'est noyée.
>
> Denis
>
> -Message d'origine-
> De : Vincent de Château-Thierry [mailto:osm.v...@free.fr]
> Envoyé : jeudi 2 février 2017 22:29
> À : Discussions sur OSM en français
> Objet : Re: [OSM-talk-fr] Nom des cours d’eau dans le cadastre
>
>
> Le 02/02/2017 à 21:35, David Marchal a écrit :
> >
> > Après recherches, il semblerait que ce soit bien un plan de géomètre
> > extrait du cadastre raster, pas du cadastre vecteur ; on peut toujours
> > accéder aux cadastre raster par un WMS, une fois la commune
> > vectorisée, ou faut-il aller aux archives départementales ?
>
> Aucune idée. Je peux juste dire que via cadastre.gouv.fr je n'ai jamais
> vu d'accès au format raster une fois mise en production la version
> vectorisée d'une commune.
>
> vincent
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
> ---
> Ce message et toutes les pièces jointes sont établis à l'intention
> exclusive de ses destinataires et sont confidentiels. L'intégrité de ce
> message n'étant pas assurée sur Internet, la SNCF ne peut être tenue
> responsable des altérations qui pourraient se produire sur son contenu.
> Toute publication, utilisation, reproduction, ou diffusion, même partielle,
> non autorisée préalablement par la SNCF, est strictement interdite. Si vous
> n'êtes pas le destinataire de ce message, merci d'en avertir immédiatement
> l'expéditeur et de le détruire.
> ---
> This message and any attachments are intended solely for the addressees
> and are confidential. SNCF may not be held responsible for their contents
> whose accuracy and completeness cannot be guaranteed over the Internet.
> Unauthorized use, disclosure, distribution, copying, or any part thereof is
> strictly prohibited. If you are not the intended recipient of this message,
> please notify the sender immediately and delete it.
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>



-- 
Cordialement,
Jérôme Seigneuret
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-be] trees (in a row) vs. tree_row

[Marc Gemis]

On Fri, Feb 3, 2017 at 8:47 AM, joost schouppe  wrote:
> f you're looking for a wider range of opinions, do ask the same question in
> the tagging mailing list. I've come to kind of enjoy the merry-go-round
> discussions there, so I'm willing to ask for you and report here :)

Or ask it on help.openstreetmap.org

m

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

Re: [OSM-talk-fr] Création suppression d'intercommunalité

[Tony EMERY]

Bonjour à tous,

Du coup, dans le cas d'une modification du contour des EPCI, garde-t-on
l'historique en créant une nouvelle relation et en renommant l'ancienne ou
pas ?

Le 3 févr. 2017 09:00, "Christian Quest"  a écrit :

> Le 3 février 2017 à 04:40, Jérôme Amagat  a
> écrit :
>
>> Un point sur les EPCI.
>>
>> pour Bourgogne-Franche-Comté c'est à jour et ça correspond à cette source
>> : http://www.ideobfc.fr/accueil/geoservices/catalogue_de_donne
>> es?uuid=0a78e68d-738c-4284-ae64-e02e74859055=1
>> Pareil pour Provence-Alpes-Côte d'Azur et cette source :
>> http://opendata.regionpaca.fr/donnees/detail/etablissement-p
>> ublic-de-cooperation-intercommunale-au-1er-janvier-2017.html
>> Normalement c'est à jour aussi pour Auvergne-Rhône-Alpes et pour Pays de
>> la Loire.
>>
>> Pour la Bretagne, ce n'est pas terminé mais si ça tente quelqu'un il y a
>> cette source pour faire les modifications :
>> http://www.data.gouv.fr/fr/datasets/epci-en-bretagne-au-01-01-2017/
>> Pareil pour la Nouvelle-Aquitaine et cette source :
>> http://www.data.gouv.fr/fr/datasets/nouvelle-aquitaine-perim
>> etre-des-epci-a-fiscalite-propre-issus-des-sdci-sur-le-perim
>> etre-regional-et-les-departements-limitrophes-surfacique/
>> par contre ça parle du Schéma départemental de coopération intercommunale
>> au 1er janvier 2017 il y a d'autre cas pour des régions ou des départements
>> sur data.gouv.fr , normalement c'est les modifications qu'il était prévu
>> de faire mais c'est pas sur quelles soient toutes faites donc il faut peut
>> être trouver d'autres sources comme des articles de journaux pour vérifié
>> que les modification ont été faite.
>> J'ai pas l'impression qu'il y ai des modifications dans les DOM mais
>> c'est à vérifier.
>>
>> Les arrondissements départementaux bougent aussi dans beaucoup de
>> départements. J'ai fait les modifications pour Bourgogne-Franche-Comté et
>> Auvergne-Rhône-Alpes que j'ai trouvé dans les arrêtés des préfectures de
>> régions. je suis allé sur http://www.prefectures-regions.gouv.fr/ puis
>> sur la région voulu puis sur les Recueil des actes administratifs et les
>> modifications datent de fin décembre ou de janvier. les modifications n'ont
>> pas l'air d'avoir été publié au JO il n'y a rien sur
>> www.legifrance.gouv.fr ça sera peut être le cas dans quelque temps (pour
>> les communes nouvelles j'ai l'impression que tout n'a pas été publié).
>>
>> A cause des communes nouvelles je sais qu'il y a au moins un cas de
>> modification des limites de département, je sais pas si ça a été fait.
>>
>>
> La limite du département et de la région, ainsi que les académies ont été
> mises à jour (32 en tout de mémoire) mais une vérification de plus n'est
> pas inutile.
>
>
>
>> Rien trouvé sur des modifications des circonscriptions législatives. J'ai
>> lu quelque part mais je sais plus où que des modifications ne doivent pas
>> avoir lieu à quelque mois d’élection, il y a des élections dans quelque
>> mois mais si il n'y a pas de modifications il va y avoir des trucs bizarres
>> à cause des communes nouvelles.
>>
>>
> Il n'y a pas de changement globalement, mais les fusions de communes
> peuvent provoquer localement un changement. Je suis en contact avec le
> bureau des élections du Ministère de l'Intérieur, je vous informerai quand
> j'aurai du nouveau.
>
>
> Pour les communes nouvelles, il y a une source donnant toutes les commune
>> nouvelle créés en au 1ert janvier 2017 : https://www.insee.fr/fr/inform
>> ation/2549968
>> Normalement Christian les a toutes créées (toutes?). Dans cette source il
>> y a les communes nouvelles créés mais il y a aussi les communes déléguées,
>> le chef lieu (donc admin_centre pour osm) et le ref:INSEE. Si ça tente du
>> monde de faire des vérifications sur les communes nouvelles (il y en a
>> beaucoup avec des fixme qui demandent une vérification du numéro INSEE.
>>
>>
> Ces fusions ont été intégrées. Il y a des "défusions " qui n'ont par
> contre peut être pas été faites avec nouvelle fusion.
> Au moins un cas avec Aurseulles, mais visiblement à jour dans OSM:
> "La commune nouvelle
> 
>  regroupe les communes d'Anctoville
> , de Longraye
> , de Saint-Germain-d'Ectot
>  et de
> Torteval-Quesnay  qui
> deviennent des communes déléguées, le 1er janvier 20172
> . Les communes
> associées  d'
> Anctoville , issues de la
> fusion-association du 1er janvier 1973, Feuguerolles-sur-Seulles
> , Orbois
> , Sermentot
> 

Re: [OSM-talk-fr] Nom des cours d’eau dans le cadastre

[HELFER Denis (SNCF RESEAU / SIEGE SNCF RESEAU / DT GE APPUI PERFORMANCE)]

Si si ça fonctionnait encore jusqu'à il y a peu. J'avais lancé une bouteille à 
mer (http://gis.19327.n8.nabble.com/plugin-cadastre-JOSM-td5877566.html) , mais 
elle s'est noyée.

Denis

-Message d'origine-
De : Vincent de Château-Thierry [mailto:osm.v...@free.fr] 
Envoyé : jeudi 2 février 2017 22:29
À : Discussions sur OSM en français
Objet : Re: [OSM-talk-fr] Nom des cours d’eau dans le cadastre


Le 02/02/2017 à 21:35, David Marchal a écrit :
>
> Après recherches, il semblerait que ce soit bien un plan de géomètre 
> extrait du cadastre raster, pas du cadastre vecteur ; on peut toujours 
> accéder aux cadastre raster par un WMS, une fois la commune 
> vectorisée, ou faut-il aller aux archives départementales ?

Aucune idée. Je peux juste dire que via cadastre.gouv.fr je n'ai jamais vu 
d'accès au format raster une fois mise en production la version vectorisée 
d'une commune.

vincent

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr
---
Ce message et toutes les pièces jointes sont établis à l'intention exclusive de 
ses destinataires et sont confidentiels. L'intégrité de ce message n'étant pas 
assurée sur Internet, la SNCF ne peut être tenue responsable des altérations 
qui pourraient se produire sur son contenu. Toute publication, utilisation, 
reproduction, ou diffusion, même partielle, non autorisée préalablement par la 
SNCF, est strictement interdite. Si vous n'êtes pas le destinataire de ce 
message, merci d'en avertir immédiatement l'expéditeur et de le détruire.
---
This message and any attachments are intended solely for the addressees and are 
confidential. SNCF may not be held responsible for their contents whose 
accuracy and completeness cannot be guaranteed over the Internet. Unauthorized 
use, disclosure, distribution, copying, or any part thereof is strictly 
prohibited. If you are not the intended recipient of this message, please 
notify the sender immediately and delete it. 
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-it] R: Re: mappatura bar in Italia

[Lorenzo "Beba" Beltrami]

Il giorno 2 febbraio 2017 18:45, Martin Koppenhoefer  ha scritto:

>
> 2017-02-02 18:19 GMT+01:00 frali...@alice.it :
>
>> principalmente  i bar italiani sono
>> a) coffe-bar specializzato in colazioni
>> b) snack-bar , è più generico, puoi trovare secondo i luoghi anche degli
>> spuntini che possono sostituire il pranzo, ed è spesso unito anche alla
>> pasticceria e gelateria
>>
>>
>> poi esistono tante varianti e specializzazioni
>> guarda nel link
>>
>> http://www.salabar.it/node/303
>>
>
Questo link è molto interessante.
Potrebbe essere di ispirazione per una astrazione generale del tipo:
- amenity=bar per tutti (mi sembra di aver capito che alla fine quello che
accomuna tutti questi locali è il bancone)
- bar=* per specializzare[1]

In questo modo si può anche agire puntualmente, come suggerisce Simone,
indicando le principali differenziazioni: orari, quello che il locale
offre, ecc.

ci sono posti che ricadono in tutte le due categorie, ma ci sono tantissimi
> bar che non sono "cafe", anche se vendono coffee.
>
+1
Motivo per cui bisogna studiare un tagging più astratto e più completo di
quello attuale, che è piuttosto confusionario (per lo meno a livello
globale/non anglosassone).

Lorenzo

[1] http://taginfo.openstreetmap.org/keys/bar#overview
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [OSM-talk-fr] Création suppression d'intercommunalité

[Christian Quest]

Le 3 février 2017 à 04:40, Jérôme Amagat  a écrit :

> Un point sur les EPCI.
>
> pour Bourgogne-Franche-Comté c'est à jour et ça correspond à cette source
> : http://www.ideobfc.fr/accueil/geoservices/catalogue_de_donne
> es?uuid=0a78e68d-738c-4284-ae64-e02e74859055=1
> Pareil pour Provence-Alpes-Côte d'Azur et cette source :
> http://opendata.regionpaca.fr/donnees/detail/etablissement-p
> ublic-de-cooperation-intercommunale-au-1er-janvier-2017.html
> Normalement c'est à jour aussi pour Auvergne-Rhône-Alpes et pour Pays de
> la Loire.
>
> Pour la Bretagne, ce n'est pas terminé mais si ça tente quelqu'un il y a
> cette source pour faire les modifications : http://www.data.gouv.fr/fr/dat
> asets/epci-en-bretagne-au-01-01-2017/
> Pareil pour la Nouvelle-Aquitaine et cette source :
> http://www.data.gouv.fr/fr/datasets/nouvelle-aquitaine-perim
> etre-des-epci-a-fiscalite-propre-issus-des-sdci-sur-le-
> perimetre-regional-et-les-departements-limitrophes-surfacique/
> par contre ça parle du Schéma départemental de coopération intercommunale
> au 1er janvier 2017 il y a d'autre cas pour des régions ou des départements
> sur data.gouv.fr , normalement c'est les modifications qu'il était prévu
> de faire mais c'est pas sur quelles soient toutes faites donc il faut peut
> être trouver d'autres sources comme des articles de journaux pour vérifié
> que les modification ont été faite.
> J'ai pas l'impression qu'il y ai des modifications dans les DOM mais c'est
> à vérifier.
>
> Les arrondissements départementaux bougent aussi dans beaucoup de
> départements. J'ai fait les modifications pour Bourgogne-Franche-Comté et
> Auvergne-Rhône-Alpes que j'ai trouvé dans les arrêtés des préfectures de
> régions. je suis allé sur http://www.prefectures-regions.gouv.fr/ puis
> sur la région voulu puis sur les Recueil des actes administratifs et les
> modifications datent de fin décembre ou de janvier. les modifications n'ont
> pas l'air d'avoir été publié au JO il n'y a rien sur
> www.legifrance.gouv.fr ça sera peut être le cas dans quelque temps (pour
> les communes nouvelles j'ai l'impression que tout n'a pas été publié).
>
> A cause des communes nouvelles je sais qu'il y a au moins un cas de
> modification des limites de département, je sais pas si ça a été fait.
>
>
La limite du département et de la région, ainsi que les académies ont été
mises à jour (32 en tout de mémoire) mais une vérification de plus n'est
pas inutile.



> Rien trouvé sur des modifications des circonscriptions législatives. J'ai
> lu quelque part mais je sais plus où que des modifications ne doivent pas
> avoir lieu à quelque mois d’élection, il y a des élections dans quelque
> mois mais si il n'y a pas de modifications il va y avoir des trucs bizarres
> à cause des communes nouvelles.
>
>
Il n'y a pas de changement globalement, mais les fusions de communes
peuvent provoquer localement un changement. Je suis en contact avec le
bureau des élections du Ministère de l'Intérieur, je vous informerai quand
j'aurai du nouveau.


Pour les communes nouvelles, il y a une source donnant toutes les commune
> nouvelle créés en au 1ert janvier 2017 : https://www.insee.fr/fr/
> information/2549968
> Normalement Christian les a toutes créées (toutes?). Dans cette source il
> y a les communes nouvelles créés mais il y a aussi les communes déléguées,
> le chef lieu (donc admin_centre pour osm) et le ref:INSEE. Si ça tente du
> monde de faire des vérifications sur les communes nouvelles (il y en a
> beaucoup avec des fixme qui demandent une vérification du numéro INSEE.
>
>
Ces fusions ont été intégrées. Il y a des "défusions " qui n'ont par contre
peut être pas été faites avec nouvelle fusion.
Au moins un cas avec Aurseulles, mais visiblement à jour dans OSM:
"La commune nouvelle

 regroupe les communes d'Anctoville
, de Longraye
, de Saint-Germain-d'Ectot
 et de
Torteval-Quesnay  qui
deviennent des communes déléguées, le 1er janvier 20172
. Les communes
associées  d'Anctoville
, issues de la fusion-association
du 1er janvier 1973, Feuguerolles-sur-Seulles
, Orbois
, Sermentot
 sont maintenues au sein de la
commune nouvelle et deviennent aussi des communes déléguées3
. Son chef-lieu se
situe à Anctoville ." (wikipedia)

Est-ce le seul ?



> Je remets le lien vers un suivi des modifications des EPCI et des
>