Re: [Talk-it] Posti auto per disabili.

2019-01-08 Per discussione Andrea Albani
Qui [0] la proposta di schema approvata a cui fa riferimento l'esempio di
Giovanni.
La regola vorrebbe che tutti gli elementi del parcheggio (es.
amenity=parking_space, amenity=parking, etc) siano messi in una relazione
type=site, site=parking. In fondo alla pagina trovi anche dei diagrammi che
spiega bene il concetto.
In [1] trovi la pagina del tag che presenta una piccola discrepanza con
quella di proposta perchè introduce un tag parking_space=disabled a mio
avviso superfluo rispetto al classico schema access:disabled=yes.

Ciao

[0] https://wiki.openstreetmap.org/wiki/Proposed_features/parking
[1] https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dparking_space

Il giorno mer 9 gen 2019 alle ore 08:17 Giuseppe  ha
scritto:

> Quando inserisco un parcheggio cerco sempre di compilare il tag
> capacity:disabled con il numero di stalli riservati ai disabili. Tuttavia,
> nei casi di parcheggi di grandi dimensioni, nel rendering non si riesce a
> capire la posizione dove sono ubicati questi stalli. Per ovviare al
> problema, qualche volta ho inserito, all’interno dell’area di parcheggio,
> un punto che individua la posizione degli stalli per disabili con i tag:
>
>
> amenity=parking
>
> capacity:disabled=*
>
>
> Non so se è la soluzione corretta, avete suggerimenti?
>
>
> Giuseppe
> ___
> 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-it] Posti auto per disabili.

2019-01-08 Per discussione Cascafico Giovanni
Coincidenza in qs giorni avevo mappato
https://www.openstreetmap.org/way/661163707

Il mer 9 gen 2019, 08:17 Giuseppe  ha scritto:

> Quando inserisco un parcheggio cerco sempre di compilare il tag
> capacity:disabled con il numero di stalli riservati ai disabili. Tuttavia,
> nei casi di parcheggi di grandi dimensioni, nel rendering non si riesce a
> capire la posizione dove sono ubicati questi stalli. Per ovviare al
> problema, qualche volta ho inserito, all’interno dell’area di parcheggio,
> un punto che individua la posizione degli stalli per disabili con i tag:
>
>
> amenity=parking
>
> capacity:disabled=*
>
>
> Non so se è la soluzione corretta, avete suggerimenti?
>
>
> Giuseppe
> ___
> 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


[Talk-it] Posti auto per disabili.

2019-01-08 Per discussione Giuseppe
Quando inserisco un parcheggio cerco sempre di compilare il tag
capacity:disabled con il numero di stalli riservati ai disabili. Tuttavia,
nei casi di parcheggi di grandi dimensioni, nel rendering non si riesce a
capire la posizione dove sono ubicati questi stalli. Per ovviare al
problema, qualche volta ho inserito, all’interno dell’area di parcheggio,
un punto che individua la posizione degli stalli per disabili con i tag:


amenity=parking

capacity:disabled=*


Non so se è la soluzione corretta, avete suggerimenti?


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


Re: [OSM-talk-fr] BANO

2019-01-08 Per discussione deuzeffe
Correctif : en avril 2018, Christian disait que les adresses BAN 
présentes dans BANO dataient de février 2017. Donc, elles ne sont pas 
déversées par flux, my bad.


D'autre part, attention, puisqu'il n'y a pas toutes les adresses dans le 
cadastres vectoriel, le jeu d'adresse qui en est extrait est... 
incomplet, la BAN étant alimentée par plusieurs sources (communes, la 
poste, ign, & so on ; pour plus d'info, demander au coordonnateur du 
projet ^^)


Le 09/01/2019 à 07:28, deuzeffe a écrit :

Christian me corrigera si je dis des bêtises.

Le 09/01/2019 à 01:37, Jérôme Amagat a écrit :
J'ai vu que les adresses du cadastre de octobre 2018 sont en open data 
sur data.gouv.fr  :

https://www.data.gouv.fr/fr/datasets/adresses-extraites-du-cadastre/

De quand date celles dans la BANO et son rendu?
Il me semble qu"elles commencent à dater, non?


Il me semble que BANO est alimentée en direct par toutes les bases 
adresses interrogées. Si c'est le cas et que les adresses extraites du 
cadastre (point bleu si rapproché, gris sinon cf 
https://wiki.openstreetmap.org/wiki/FR:WikiProject_France/WikiProject_Base_Adresses_Nationale_Ouverte_(BANO)#L.C3.A9gende 
) ne te semblent pas à jour, c'est dû à la DGFIP (ou du service d'état 
qui s'en occupe). Attention, dans certains coins, la géoloc. de 
certaines adresses présentes sur le cadastre vectoriel est parfois 
imprécise (euphémisme ; vérifié sur le terrain).


Pareil pour la base fantoir accessible par ici 
http://cadastre.openstreetmap.fr/


Fantoir (l'officiel d'octobre 2018) n'est de toute façon pas à jour de 
base. En revanche, il y a effectivement un souci avec "notre" Fantoir. 
Vincent (dct) est en train de remettre le chantier en ordre (si j'ai 
bien tout suivi).



d’ailler sur cette page http://cadastre.openstreetmap.fr/
ça serait peut être plus logique d'aller chercher le bâti là : 
https://www.data.gouv.fr/fr/datasets/cadastre/


Pour extraire le bâti (ou les adresses), la génération se fait à partir 
du cadastre en flux à jour. Donc, si ça ne te semble pas à jour, tu 
connais la réponse ;)




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


Re: [Talk-de] 2 Fragen zu Changesets

2019-01-08 Per discussione dktue

Hallo,

ich habe hierzu diesen RSS-Feed abboniert in Thunderbird -- sobald es 
ein Changeset in der Angegebenen Bounding-Box gibt das einen Rewiew 
Request wünscht, wird er im Feed angezeigt.


Gruß
dktue

[1] 
https://resultmaps.neis-one.org/osm-suspicious-feed-bbox?hours=96=-1=review_requested%3Dyes=t=8.901329,48.3829341,9.1687775,48.5920509


Am 17.12.2018 um 20:22 schrieb Andreas Frey:

Hallo,

zu Changeset Kommentaren und "Review requestet“ würde ich gerne zwei Fragen an 
die Erfahrenen stellen:

1) - wie kann ich am einfachsten alle Changesets auflisten (von anderen 
Mappern) bei denen ich einen Diskussionsbeitrag hinterlassen habe? (mit Osmcha 
habe ich es nicht geschafft und bei NeisOne auch kein passendes Tool gefunden)

2) - Dann und wann klicke ich "review requestet“ beim Hochladen an, 
insbesondere wenn ich im Kommentar eine Frage gestellt habe oder es sich um ein 
Mapping Gebiet handelt wo ich nicht so routiniert bin.
- > dann und wann werden diese Changesets auch angeschaut und erhalten dann z.B 
ein Daumen hoch in OSMCha - mehr Feedback gab es jedoch bis jetzt nicht.
-> was ich mir eigentlich wünschen würde wäre jedoch ein 
inhaltlich/schriftliches Feedback vor allem auf meine Fragen

Daher meine Idee/Frage würde sich evtl. jemand von den Erfahreneren 
bereiterklären meine zukünftigen Changesets mit „Review requestet“ anzuschauen 
und ggf. auch inhaltlich zu kommentieren? z.B. über einen osmCha-Feed? Also so 
eine Art „Patenschaft“ oder wie man das auch immer nennen möchte.

Grüße,

Andy
---
ajf3934221



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



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


Re: [OSM-talk-fr] BANO

2019-01-08 Per discussione deuzeffe

Christian me corrigera si je dis des bêtises.

Le 09/01/2019 à 01:37, Jérôme Amagat a écrit :
J'ai vu que les adresses du cadastre de octobre 2018 sont en open data 
sur data.gouv.fr  :

https://www.data.gouv.fr/fr/datasets/adresses-extraites-du-cadastre/

De quand date celles dans la BANO et son rendu?
Il me semble qu"elles commencent à dater, non?


Il me semble que BANO est alimentée en direct par toutes les bases 
adresses interrogées. Si c'est le cas et que les adresses extraites du 
cadastre (point bleu si rapproché, gris sinon cf 
https://wiki.openstreetmap.org/wiki/FR:WikiProject_France/WikiProject_Base_Adresses_Nationale_Ouverte_(BANO)#L.C3.A9gende 
) ne te semblent pas à jour, c'est dû à la DGFIP (ou du service d'état 
qui s'en occupe). Attention, dans certains coins, la géoloc. de 
certaines adresses présentes sur le cadastre vectoriel est parfois 
imprécise (euphémisme ; vérifié sur le terrain).


Pareil pour la base fantoir accessible par ici 
http://cadastre.openstreetmap.fr/


Fantoir (l'officiel d'octobre 2018) n'est de toute façon pas à jour de 
base. En revanche, il y a effectivement un souci avec "notre" Fantoir. 
Vincent (dct) est en train de remettre le chantier en ordre (si j'ai 
bien tout suivi).



d’ailler sur cette page http://cadastre.openstreetmap.fr/
ça serait peut être plus logique d'aller chercher le bâti là : 
https://www.data.gouv.fr/fr/datasets/cadastre/


Pour extraire le bâti (ou les adresses), la génération se fait à partir 
du cadastre en flux à jour. Donc, si ça ne te semble pas à jour, tu 
connais la réponse ;)


--
deuzeffe "si j'ai bien tout compris"

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


[OSM-talk-fr] BANO

2019-01-08 Per discussione Jérôme Amagat
J'ai vu que les adresses du cadastre de octobre 2018 sont en open data sur
data.gouv.fr :
https://www.data.gouv.fr/fr/datasets/adresses-extraites-du-cadastre/

De quand date celles dans la BANO et son rendu?
Il me semble qu"elles commencent à dater, non?

Pareil pour la base fantoir accessible par ici
http://cadastre.openstreetmap.fr/

d’ailler sur cette page http://cadastre.openstreetmap.fr/
ça serait peut être plus logique d'aller chercher le bâti là :
https://www.data.gouv.fr/fr/datasets/cadastre/
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [talk-au] Announcing: OpenStreetCam competition

2019-01-08 Per discussione Martijn van Exel
Hi all,

We have the results for the most prolific OpenStreetCam contributors for 
Australia for the period Dec 1 - Dec 24:


#1 ---> robbie-bloggs with 127971 points
#2 ---> steve91 with 65470 points


Congratulations to you both, you have just won yourselves an $25 Amazon gift 
card! Please get in touch with me so I can arrange (virtual) delivery.

It's not over yet though. This was just the holiday mid point of the 
competition. At the end of January there will be three more prizes ($100 / $25 
/ $25) for the overall top contributors for the months of December and January.

If you haven't started capturing yet, no worries. New, not yet covered roads 
get you 10x points. That adds up pretty quickly. For example, this 20km trip is 
worth more than 6000 points: 
https://openstreetcam.org/details/1318295/0/track-info 

Best,
--
 Martijn van Exel
 m...@rtijn.org



On Wed, Dec 12, 2018, at 12:33, Martijn van Exel wrote:
> Folks,
> 
> We added an additional holiday prize for the 2 mappers who collect the most 
> imagery before Christmas.
> Details added on the competition page! You need 25k points minimum to be 
> eligible for this prize, but since coverage is very low in Australia, you 
> collect points very quickly.
> 
> Let me know if you have any questions. Happy mapping / capturing,
> --
>  Martijn van Exel
>  m...@rtijn.org
> 
> 
> 
> On Fri, Dec 7, 2018, at 11:53, Martijn van Exel wrote:
>> Hi folks, 
>> 
>> We (Telenav map team) are holding an OpenStreetCam image capture 
>> competition. In case you're not familiar, OpenStreetCam is an open source / 
>> open data street level imagery collection platform for OSM. It is widely 
>> used to help improve OSM (through iD and JOSM) but there is not a lot of 
>> coverage in Australia yet. So with this competition we’re hoping to start to 
>> change that. 
>> 
>> More details here: 
>> https://github.com/openstreetcam/competitions/wiki/Australia-Competition-Dec-2018
>>  
>> 
>> The TL;DR is: collect as many OSC images as you can between now and Jan 31, 
>> the top 3 contributors get $100 / $25 Amazon gift cards!
>> 
>> Happy mapping / capturing!
>> Martijn
>> 
>> PS in case you’re in NZ, we have a separate competition staring there as 
>> well, 
>> https://github.com/openstreetcam/competitions/wiki/New-Zealand-Competition-Dec-2018
>>  
>> _
>> Talk-au mailing list
>> Talk-au@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-au
> 
> ___
> Talk-au mailing list
> Talk-au@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au
> 
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [Talk-de] Attribut für die Europachausee in Halle (Saale)

2019-01-08 Per discussione Martin Koppenhoefer


sent from a phone

> On 8. Jan 2019, at 19:46, Heinz-Jürgen Oertel  wrote:
> 
> Martin, aber: "Hauptverbindungsstraße unter zentraler Verwaltung..:"


wo das wohl herkommt, zentrale Verwaltung? Jedenfalls scheint es sich auf 
Deutschland zu beziehen, m.E. sollte man solche länderspezifischen 
Präzisierungen irgendwo am Ende in eine entsprechende Unterüberschrift packen, 
das deutsche Wiki ist in erster Linie das Wiki auf deutsch, nicht das Wiki für 
Deutschland.

Im englischen Wiki steht nichts von zentraler Verwaltung, und es steht auch ein 
bisschen gegen den Grundsatz des highway taggings, auf die Bedeutung im 
Netzwerk zu sehen und Verwaltungsfragen aussen vor zu lassen.
Jedenfalls steht da zusätzlich: 
„Außerdem können auch Straßen mit übergeordneter 
Verkehrsbedeutung(beispielsweise mindestens 10.000 Kfz/Tag) als highway=primary 
getaggt werden, selbst wenn sie amtlich niedriger klassifiziert sind“

Gruß, Martin 


> es ist eine städtische Straße.
> Danke Allen für Hinweise.
> Ich werde die gesamte Umgehung mal auf highway=trunk setzen.
> Falls noch eindeutige Argumente für oder wider kommen, ist ja schnell 
> geändert. Jedenfalls denke ich, sollte der gesamte Verlauf einheitlich sein.
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de


[Talk-es] Importación del Catastro de Benlloc

2019-01-08 Per discussione Jordi MF
Hola a todos,

Ya hemos creado el proyecto de importación del Catastro de Benlloc en el
Gestor de Tareas (gracias Javier por volver a generar los archivos de las
tareas). Se han incluido edificios y direcciones.

Creo que es el primer municipio valenciano en el que se trabaja una
importación del Catastro. Quedáis invitados a contribuir.

Saludos a todos y buen mapeo,

Jordi



--
Sent from: http://gis.19327.n8.nabble.com/Spain-f5409873.html

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


[Talk-at]  Mit, 16.01.  Maptime Stammtisch + OSM Mapping

2019-01-08 Per discussione Jakob Miksch

Hallo miteinander,

am Mittwoch den 16. Jänner ist in Salzburg der nächste Maptime 
Stammtisch. Es geht um Geo-Themen allgemein und natürlich auch um OSM. 
Ausführliche Einladung unten. Wir werden uns davor treffen und etwas 
mappen. Vermutlich mit der App StreetComplete.


Neue Teilnehmer sind herzlich willkommen.

Viele Grüße,
Jakob

-

Hallo liebe Geo-Begeisterte,

Unser letztes Treffen im Dezember war mit fast 30 Teilnehmern ein großer 
Erfolg.  Die Videos  und die Folien  sind auf unserer Website 
verfügbar: http://maptime.io/salzburg/event/2018/12/12/data-handling/


Nächste Woche ist wieder unser Stammtisch. Jeder ist herzlich 
eingeladen, sich über Geodaten, GIS, Fernerkundung, Programmieren und 
alle anderen Themen auszutauschen.


Datum: *Mittwoch, 16. Jänner*
Uhrzeit: *20:00 Uhr*
Ort: Academy Bar , 
Franz-Josef-Straße 4


All diejenigen, die sich für *OpenStreetMap* interessieren, treffen sich 
eine Stunde früher um 19:00 Uhr vor der Academy Bar. Mit der App 
StreetComplete  werden 
wir etwas mappen.


Bei Fragen könnt ihr uns per E-Mail erreichen: 
maptime.salzb...@gmail.com. Neue Teilnehmer sind immer herzlich willkommen.


Geographische Grüße,
Euer Maptime Team
___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [OSM-talk-be] Fwd: Open Belgium 2019: Call for Speakers + Early Bird Tickets!

2019-01-08 Per discussione Marc Gemis
I cannot make it to Open Belgium, but I have been thinking about a "walking
meetup" for some time now. So instead of sitting in a pub, doing a walk and
talk about OSM and survey techniques and apply them.

Taking that idea, on a community day, it could be a workshop about
surveying techniques, JOSM tips, micromapping, that kind of stuff. It would
be an hand-on workshop, where people have to go outside for 15 minutes or
so and collect data. Afterwards compare techniques, collected data and do a
bit of mapping. Perhaps discuss a bit about usefulness, special maps, ...

m.

On Tue, Jan 8, 2019 at 1:46 PM Ben Abelshausen 
wrote:

> Hi everyone!
>
> In a few months we have Open Belgium again (yay!) and as usual we will
> have talks about OSM (Belgium).  We invite everyone to submit a talk,
> **anything** related to open-(something) is fine, that means openstreetmap
> too! ;-) We will also organize a community day during the weekend this
> year, more news about that later, so even if you can't make it on the 4th
> of march we urge you to submit talks/workshops anyway. We can move them to
> the community day later.
>
> We will probably also have a booth with OSM Belgium and usually have a lot
> of fun so don't miss it! If you want to attend but find the entry tickets
> too expense get in touch with me, the community day will be free (to be
> announced later).
>
> All details here:
>
> -- Forwarded message -
> From: Astrid - Open Knowledge Belgium 
> Date: Tue, Jan 8, 2019 at 10:17 AM
> Subject: Open Belgium 2019: Call for Speakers + Early Bird Tickets!
> To: 
>
>
> A must-attend conference to discuss the state of and current trends around
> Open Knowledge and Open Data!
>
> Open Belgium 2019 - 4 March in Brussels
> Open Knowledge and Open Data in Belgium
> View this email in your browser
> 
>
> 
> Let's talk Open Knowledge and Open Data!
> Ready for Open Belgium 2019?
>
>
> The Belgian open knowledge and open data landscape is changing at a fast
> pace. In order to stay up-to-date and to share insights with *300+ fellow
> open enthusiasts,* we would like to invite you to join us at the annual 
> *community-driven
> Open Belgium 2019
> *
> conference on *4 March in Brussels*.
>
> Since you participated in previous editions of Open Belgium, you know
> exactly what to expect: inspirational high-level keynote speakers,
> engaging panel discussions, hands-on and minds-on workshops as well as an
> interactive exhibition space.
> Get your *Early Bird ticket* *now* and *save more than 30%!*
> GET YOUR TICKET
> 
>
> *When?*
> *Monday 4 March, 08:30-19:00*
> Full programme available soon
> *Where?*
> *Herman Teirlinck Building*
> Avenue du Port 88, 1000 Brussels
>
> 
> Link to Call for Speakers: http://2019.openbelgium.be/speakers
> 
>
> We are looking forward to seeing you at Open Belgium 2019!
>
> The Open Belgium team
>
>
> 
>
> 
>
> 
>
> 
> *Copyright © 2019 Open Knowledge Belgium, All rights reserved.*
> You are receiving this email because you attended Open Belgium in the past.
>
> *Our mailing address is:*
> Open Knowledge Belgium
> Kantersteen 12
> Brussels 1000
> Belgium
>
> Add us to your address book
> 
>
>
> Want to change how you receive these emails?
> You can update your preferences
> 
> or unsubscribe from this list
> 
> .
>
> [image: Email Marketing Powered by Mailchimp]
> 
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>

Re: [OSM-talk-fr] tag indiquant le paiement possible avec la monnaie locale

2019-01-08 Per discussione Axelos
Le 08/01/2019 à 12:03, Cyrille37 OSM a écrit :
> 
> Pour info, Le réseau des MLCC (Monnaies Locales Complémentaires
> Citoyennes) :
> 
> http://monnaie-locale-complementaire-citoyenne.net avec pour raccourci
> http://www.mlc.camp
> 
> par exemple la Gabare (en Touraine) : http://gabare.mlc.camp
> 
> C'est peut être le moyen de connaître une liste des monnaies locales
> (françaises).

J'ai étudié le sujet localement il y a plus d'un an et suis tombé sur
cette page
https://wiki.openstreetmap.org/wiki/User:FrViPofm/Key:local_currency/data

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


Re: [OSM-talk-fr] Attribution latitude-cartagene / CTRL

2019-01-08 Per discussione Erwan Salomon
Super
ils semblent réactif en plus
merci à toi Vincent

> Le 8 janv. 2019 à 16:42, Vincent de Château-Thierry  a 
> écrit :
> 
> Bonjour,
> 
>> De: "Vincent de Château-Thierry" 
>> 
>> Latitude-Cartagène utilise des fonds OSM et soutient OSM-France
>> depuis 2 ans en participant au State of the Map, cf.
>> http://sotm2018.openstreetmap.fr/sponsors.html
>> Il est donc bien possible que le(s) plan(s) que tu mentionnes
>> repose(nt) sur OSM.
>> 
>>> je n’ai pas pris contact, je ne me sent moyen de le faire (je suis
>>> timide, mais je me soigne)
>> 
>> Je vais leur glisser un mot et je vous tiens au courant.
> 
> Renseignements pris c'est bien un fond OSM qui est utilisé. L'attribution va 
> être rajoutée côté Latitude-Cartagène, et la version corrigée sera transmise 
> au client.
> 
> vincent
> 
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr


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


Re: [Talk-de] Attribut für die Europachausee in Halle (Saale)

2019-01-08 Per discussione Heinz-Jürgen Oertel
Am Dienstag, 8. Januar 2019, 19:13:43 CET schrieb Martin Koppenhoefer:
> Am Di., 8. Jan. 2019 um 16:00 Uhr schrieb Heinz-Jürgen Oertel <
> 
> hj.oer...@t-online.de>:
> > > Dass ein trunk am Anfang und Ende zur secondary wird, halte ich
> > > aber auch für komisch, vielleicht primary?
> > 
> > primary: "Hauptverbindungsstraße unter zentraler Verwaltung , meist mit
> > besonderer Kennzeichnung (D: Nummer oberhalb der Vorfahrtsschilder), die
> > meist
> > größere Städte verbindet und dem überregionalen Verkehr dient."
> > trifft es auch nicht.
> > 
> > Ein Punkt am südlichen Beginn:
> > https://www.openstreetmap.org/node/1231139671
> 
> doch, das könnte es schon treffen, das südliche Stück bis zur B91 könnte
> man primary setzen, und wahrscheinlich auch im Norden bis zur B100 hier:
> https://www.openstreetmap.org/way/275346451
> 
> Gruß,
> Martin

Martin, aber: "Hauptverbindungsstraße unter zentraler Verwaltung..:"
es ist eine städtische Straße.
Danke Allen für Hinweise.
Ich werde die gesamte Umgehung mal auf highway=trunk setzen.
Falls noch eindeutige Argumente für oder wider kommen, ist ja schnell 
geändert. Jedenfalls denke ich, sollte der gesamte Verlauf einheitlich sein.

-- 
mit freundlichen Grüßen aus Halle (Saale)
   Heinz



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


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-08 Per discussione Kevin Kenny
On Tue, Jan 8, 2019, 11:48 brad  I'm going to start close to home, extend that to the state of CO, & see
> how it goes.
> I've done quite a bit of recreating and boondock camping on BLM land and
> I've never come across any that are leased exclusively, altho I'm sure
> there are some.It's more of a rarity, than 'most of'.


Ok. I knew exclusive leases exist, not how usual they are. I've other
correspondents who've complained about what they see as a trend toward such
arrangements. I personally have the good fortune to live in New York, which
has very little Federal land, but a wealth of state-protected land whose
protection is enshrined in the state constitution.

Politically, your comment that the inhabitants resent BLM ownership is a
> gross generalization.   I'd say that the majority of western inhabitants
> do not resent it.
>

Careless editing! I even thought while typing that message that I needed to
go back and change 'the' to 'some' - but clearly didn't do it!  Sorry!
Still, one of our political parties has latched onto the issue. (Obviously,
not all members of any party share all its leaders' opinions.) In any case,
it's undeniable that a political controversy exists and has garnered media
attention.

In any case, in general we map land use, land cover and land access, not
land ownership. Of course, those attributes often follow property lines, so
cadastre has a way of coming along for the ride, but the focus should not
be on the ownership. There's no consensus about whether cadastre should be
in OSM at all, but boundaries for public-access facilities such as parks
are widely tolerated.  (Hardliners would exclude all cadastral data,
including boundary=administrative, but they appear to be a relatively small
minority.) Tagging with landuse=farmland/meadow/forest/..., with or without
natural=wood/grassland/heath/scrub/moor/... would be appropriate (assuming
that either the use or the cover is coterminous with the parcel), as would
leisure=nature_reserve if passive recreation in nature is the parcel's
purpose. Boundary=protected_area is appropriate if and only if the
protection status is known. For at least some BLM lands, there is not
significant protection; it's 'working land' that happens to be
government-owned. (alaskadave's comments notwithstanding, this last
sentence is not intended to be a comment, for well or ill, on BLM's
stewardship.)

Hey, whad'ya know... I even wikified something about that...
https://wiki.openstreetmap.org/wiki/Parcel#Parcel_data_as_a_secondary_source
. I don't remember writing that, but I still agree with it.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-de] Attribut für die Europachausee in Halle (Saale)

2019-01-08 Per discussione Martin Koppenhoefer
Am Di., 8. Jan. 2019 um 16:00 Uhr schrieb Heinz-Jürgen Oertel <
hj.oer...@t-online.de>:

>
> > Dass ein trunk am Anfang und Ende zur secondary wird, halte ich
> > aber auch für komisch, vielleicht primary?
> primary: "Hauptverbindungsstraße unter zentraler Verwaltung , meist mit
> besonderer Kennzeichnung (D: Nummer oberhalb der Vorfahrtsschilder), die
> meist
> größere Städte verbindet und dem überregionalen Verkehr dient."
> trifft es auch nicht.
>
> Ein Punkt am südlichen Beginn:
> https://www.openstreetmap.org/node/1231139671




doch, das könnte es schon treffen, das südliche Stück bis zur B91 könnte
man primary setzen, und wahrscheinlich auch im Norden bis zur B100 hier:
https://www.openstreetmap.org/way/275346451

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


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-08 Per discussione brad
I'm going to start close to home, extend that to the state of CO, & see 
how it goes.
I've done quite a bit of recreating and boondock camping on BLM land and 
I've never come across any that are leased exclusively, altho I'm sure 
there are some.    It's more of a rarity, than 'most of'.


Politically, your comment that the inhabitants resent BLM ownership is a 
gross generalization.   I'd say that the majority of western inhabitants 
do not resent it.


On 1/8/19 9:15 AM, Kevin Kenny wrote:

On Mon, Jan 7, 2019 at 10:05 PM Michael Patrick  wrote:

"Multiple uses under BLM management include renewable energy development (solar, 
wind, other); conventional energy development (oil and gas, coal); livestock grazing; 
hardrock mining (gold, silver, other), timber harvesting; and outdoor recreation (such as 
camping, hunting, rafting, and off-highway vehicle driving). ... 36 million-acre system 
of National Conservation Lands (including wilderness areas, wilderness study areas, 
national monuments, national conservation areas, historic trails, and wild and scenic 
rivers); protecting wild horse and burro rangeland; conserving wildlife, fish, and plant 
habitat"

Also agriculture. Burning Man's Black Rock City is leased from BLM under an Special 
Recreation Permit (SRP). ... " crop harvesting, residential occupancy, recreation 
facilities, construction equipment storage, assembly yards, well pumps, and other 
uses." So, even though it might be BLM, it could also be under a 50 year lease to a 
commercial entity, so for all intents and purposes be regarded as private property - like 
massive solar ( 19 million acres  ) and wind ( 20 million acres  ) energy farms. I seem 
to recall a Nevada brothel was at one time operating on BLM land with a lease and permit 
- pretty much, as long as you don't leave the land damaged and it doesn't interfere with 
other planned uses, you can get a lease.

Just saying, one class isn't going to do it. Mostly, 'exploited', not 
'protected'.

All that 'BLM land' says is 'this land is owned by the US Government'
- generally because it was Government-owned at the time that a state
was admitted to the Union and hasn't been sold since.

Some BLM land - about 145,000 km² - is 'conservation land' in some
way, and some small sliver is special recreation land.  But large
amounts are simply leased, to mining and drilling companies, cattle
ranchers and farmers, solar and wind energy companies, private
residences, basically, any land use that the Government agrees to.
Some, if not most of these leaseholds are exclusive, so that a ranch
can run barbed wire, put up posters, and treat it as private property
for as long as the lease runs and it pays the rent. (Some timber
leases explicitly require public access in areas that are not actively
being logged.)

Given the political controversy surrounding the BLM (in some Western
states, the BLM owns a majority of the land and the inhabitants resent
it), I'd tend to steer away from a wholesale import. I would think
that a pilot project could start with an import of land in one
specific, limited category of particular public interest (such as
wilderness areas or recreation areas) and use that to study issues of
integration and conflation. Restricting to wilderness or recreation
areas is also safer since these are relatively stable, rather than
other land uses that could change entirely with the next leaseholder.
Most other BLM land designations could be used only to inform
landuse=*. The land in many cases does not enjoy any form of legal
protection. It is simply owned by the government, and any protection
is simply by the policy of the agency that manages a particular parcel
and could change with the stroke of a pen.

Clearly, no land use is 100% guaranteed stable, and the fact that
something might change tomorrow is ordinarily not a reason to refrain
from mapping it today. Nevertheless, given that the justification for
an import is usually that the project lacks sufficient staff to map
the features being imported, importing features that are known to be
volatile seems imprudent.

I say this as someone who has done imports from databases of
government-owned land. In both the rework of New York State Department
of Environmental Conservation lands, and the import _de novo_ of the
New York City watershed lands, I restricted the import to particular
categories. I specifically excluded New York City lands that are
closed to the public (I could have mapped them as
boundary=protected_area protect_class=12 access=private, but decided
that they simply were neither sufficiently verifiable nor of
sufficient public interest to pursue.) Similarly, I excluded several
classes of New York State lands such as private conservation easements
and the bizarre category of "Forest Preserve land underwater".

It's much easier to go back later and import more than it is to
recover from a botched import.

___
Talk-us mailing list

Re: [Talk-de] Network Relationen

2019-01-08 Per discussione Christopher Lorenz
Hallo Martin,

du kannst alternativ (JOSM) auch, wenn du die IDs schon hast, die
Relationen direkt laden:

Datei>Objekt herunterladen (Ctrl+Shift+O)

Dann kannst du in der Relationsansicht deine Relation finden. Dort
kannst du auch angeben, dass auch Abhängige Elemente oder
Eltern-Relationen mit geladen werden, leider lädt er nur eine Ebene und
nicht alle. In deinem Fall lädt er dann für den Stadtverkehr Lübeck nur
alle Routen herunter, nicht aber die Wege und Haltestellen, das kann man
dann aber je nachdem wie man es braucht per Hand machen.

Christopher

On 08.01.19 08:22, Florian Lohoff wrote:
> On Mon, Jan 07, 2019 at 11:34:23PM +0100, Martin Scholtes wrote:
>> Nabend zusammen,
>>
>> bin derzeit wieder für den PT am arbeiten und musste feststellen das ich
>> einige Relationen zwar in der Datenbank finde, sie aber nicht über
>> ID/PL2 oder JOSM bearbeiten kann.
>>
>> ID 1991320 u. 1389631 als Beispiel.
>>
>> Weiß jemand wie ich dran ran komme?
> JOSM - Bus stop runterladen. Rechts klick auf die Relation und "Relation
> Selektieren" und dann ctrl-alt-d (Download parents).
>
> Dann fortpflanzen über die Relationen.
>
> Hat bei mir gerade geklappt.
>
> Gut das ich sowas nicht bearbeite ;) Gruselig.
>
> Flo



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


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-08 Per discussione Kevin Kenny
On Mon, Jan 7, 2019 at 10:05 PM Michael Patrick  wrote:
> "Multiple uses under BLM management include renewable energy development 
> (solar, wind, other); conventional energy development (oil and gas, coal); 
> livestock grazing; hardrock mining (gold, silver, other), timber harvesting; 
> and outdoor recreation (such as camping, hunting, rafting, and off-highway 
> vehicle driving). ... 36 million-acre system of National Conservation Lands 
> (including wilderness areas, wilderness study areas, national monuments, 
> national conservation areas, historic trails, and wild and scenic rivers); 
> protecting wild horse and burro rangeland; conserving wildlife, fish, and 
> plant habitat"
>
> Also agriculture. Burning Man's Black Rock City is leased from BLM under an 
> Special Recreation Permit (SRP). ... " crop harvesting, residential 
> occupancy, recreation facilities, construction equipment storage, assembly 
> yards, well pumps, and other uses." So, even though it might be BLM, it could 
> also be under a 50 year lease to a commercial entity, so for all intents and 
> purposes be regarded as private property - like massive solar ( 19 million 
> acres  ) and wind ( 20 million acres  ) energy farms. I seem to recall a 
> Nevada brothel was at one time operating on BLM land with a lease and permit 
> - pretty much, as long as you don't leave the land damaged and it doesn't 
> interfere with other planned uses, you can get a lease.
>
> Just saying, one class isn't going to do it. Mostly, 'exploited', not 
> 'protected'.

All that 'BLM land' says is 'this land is owned by the US Government'
- generally because it was Government-owned at the time that a state
was admitted to the Union and hasn't been sold since.

Some BLM land - about 145,000 km² - is 'conservation land' in some
way, and some small sliver is special recreation land.  But large
amounts are simply leased, to mining and drilling companies, cattle
ranchers and farmers, solar and wind energy companies, private
residences, basically, any land use that the Government agrees to.
Some, if not most of these leaseholds are exclusive, so that a ranch
can run barbed wire, put up posters, and treat it as private property
for as long as the lease runs and it pays the rent. (Some timber
leases explicitly require public access in areas that are not actively
being logged.)

Given the political controversy surrounding the BLM (in some Western
states, the BLM owns a majority of the land and the inhabitants resent
it), I'd tend to steer away from a wholesale import. I would think
that a pilot project could start with an import of land in one
specific, limited category of particular public interest (such as
wilderness areas or recreation areas) and use that to study issues of
integration and conflation. Restricting to wilderness or recreation
areas is also safer since these are relatively stable, rather than
other land uses that could change entirely with the next leaseholder.
Most other BLM land designations could be used only to inform
landuse=*. The land in many cases does not enjoy any form of legal
protection. It is simply owned by the government, and any protection
is simply by the policy of the agency that manages a particular parcel
and could change with the stroke of a pen.

Clearly, no land use is 100% guaranteed stable, and the fact that
something might change tomorrow is ordinarily not a reason to refrain
from mapping it today. Nevertheless, given that the justification for
an import is usually that the project lacks sufficient staff to map
the features being imported, importing features that are known to be
volatile seems imprudent.

I say this as someone who has done imports from databases of
government-owned land. In both the rework of New York State Department
of Environmental Conservation lands, and the import _de novo_ of the
New York City watershed lands, I restricted the import to particular
categories. I specifically excluded New York City lands that are
closed to the public (I could have mapped them as
boundary=protected_area protect_class=12 access=private, but decided
that they simply were neither sufficiently verifiable nor of
sufficient public interest to pursue.) Similarly, I excluded several
classes of New York State lands such as private conservation easements
and the bizarre category of "Forest Preserve land underwater".

It's much easier to go back later and import more than it is to
recover from a botched import.

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


Re: [OSRM-talk] Install OSRM on MacOs

2019-01-08 Per discussione Didier Doumerc
Thanks for your answer Daniel. It works fine !

I'm not sure to understand exactly the reason of "-p profiles/car.lua". Does 
the file car.lua contain speed limits ?

Then, if I change a speed, I must run another osrm-extract ?

In my exemple, the following request  :


10.168.221.144:5000/route/v1/driving/2.590291,44.360367;2.627096,44.980478?overview=false

returns :
1:45 and 100,6 km

The same request on 
https://www.openstreetmap.org/directions?engine=osrm_car=44.3604%2C2.5903%3B44.9805%2C2.6271#map=10/44.6713/2.4894

returns :
1:50 and 103 km

The second result is better than the first. Is it because of the car.lua file ?


Thanks+++

Didier

Le ven.04/01/19 à 18:52, Daniel Patterson a écrit :

> Check out the Wiki page at: 
> https://github.com/Project-OSRM/osrm-backend/wiki/Running-OSRM
> 
> With OSRM 5.x, the names of some of the tools changed.  You will now want to 
> run `osrm-extract -p profiles/car.lua yourmap.osm` then `osrm-contract 
> yourmap.osrm`
> 
> daniel
> 
> On Fri, Jan 4, 2019 at 9:33 AM Didier Doumerc  wrote:
> Hi,
> 
> Since I can't upgrade whith a new map (crash when running osrm-prepare), I 
> try to reinstall OSRM. 
> 
> Once I have reinstalled ORSM, I can extract the new map, but I don't find 
> osrm-prepare anymore. I don't know what to do before running osrm-routed.
> 
> Is someone can give me a link please to a clear and complete install method ?
> 
> Thanks and happy new year...
> 
> Didier
> 
> ___
> OSRM-talk mailing list
> OSRM-talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osrm-talk
> ___
> OSRM-talk mailing list
> OSRM-talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osrm-talk

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


Re: [OSM-talk-fr] Attribution latitude-cartagene / CTRL

2019-01-08 Per discussione Vincent de Château-Thierry
Bonjour,

> De: "Vincent de Château-Thierry" 
> 
> Latitude-Cartagène utilise des fonds OSM et soutient OSM-France
> depuis 2 ans en participant au State of the Map, cf.
> http://sotm2018.openstreetmap.fr/sponsors.html
> Il est donc bien possible que le(s) plan(s) que tu mentionnes
> repose(nt) sur OSM.
> 
> > je n’ai pas pris contact, je ne me sent moyen de le faire (je suis
> > timide, mais je me soigne)
> 
> Je vais leur glisser un mot et je vous tiens au courant.

Renseignements pris c'est bien un fond OSM qui est utilisé. L'attribution va 
être rajoutée côté Latitude-Cartagène, et la version corrigée sera transmise au 
client.

vincent

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


[Talk-de] Hackweekend Karlsruhe 23/24 Februar

2019-01-08 Per discussione Frederik Ramm
Hallo,

am 23./24. Februar gibt es wieder ein Hackweekend in Karlsruhe. Details
hier auf der Wikiseite:

https://wiki.openstreetmap.org/wiki/Karlsruhe_Hack_Weekend_February_2019

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"

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


Re: [Talk-de] Attribut für die Europachausee in Halle (Saale)

2019-01-08 Per discussione Heinz-Jürgen Oertel
Am Dienstag, 8. Januar 2019, 15:38:45 CET schrieb Martin Koppenhoefer:
> sent from a phone
> 
> > On 8. Jan 2019, at 11:03, Heinz-Jürgen Oertel 
> > wrote:
> > 
> > Grundsätzlich sollte diese Strecke auch als Umgehungsstraße von Navis
> > genutzt werden. Darauf weist auch der Wiki Eintrag hin, diese durch trunk
> > tagging zu bevorzugen.
> 
> trunk bedeutet AFAIK kreuzungsfrei ausgebaut
ist sie größtenteils

auch "meist mehrspurig ausgebaut" trifft zu, nicht immer aber meist.

auch das: getrennte Ein- und Ausfahrten. Wenn mindestens zwei solcher 
Anschlussstellen bestehen, kann eine Schnellstraße angenommen werden."
trifft zu, es gibt 5 kreuzungsfreie Anschlussstellen. 

> und Richtungsfahrbahnen getrennt.

> Dass ein trunk am Anfang und Ende zur secondary wird, halte ich
> aber auch für komisch, vielleicht primary?
primary: "Hauptverbindungsstraße unter zentraler Verwaltung , meist mit 
besonderer Kennzeichnung (D: Nummer oberhalb der Vorfahrtsschilder), die meist 
größere Städte verbindet und dem überregionalen Verkehr dient."
trifft es auch nicht.

Ein Punkt am südlichen Beginn:
https://www.openstreetmap.org/node/1231139671

 Heinz




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


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-08 Per discussione Dave Swarthout
Absolutely agree with your assessment of the management style of the BLM,
Michael. In Alaska, BLM land is literally crisscrossed with ATV trails.
It's a travesty but there's nobody around to enforce the rules and the
amount of land under BLM's "care" is truly humongous. Unmanageable, even
without a government shutdown.

On Tue, Jan 8, 2019 at 10:05 AM Michael Patrick  wrote:

>
> > Joseph,   I'm not stuck on class 27, but as you say, that fits the
>> definition on the wiki.   I should probably look for other specific
>> protection in the attributes and translate that somehow.   Mostly it's just
>> grazing and recreation land.   Anything such as wilderness or monument
>> would definitely be tagged as such.
>>
>
> "Multiple uses under BLM management include renewable energy development
> (solar, wind, other); conventional energy development (oil and gas, coal);
> livestock grazing; hardrock mining (gold, silver, other), timber
> harvesting; and outdoor recreation (such as camping, hunting, rafting, and
> off-highway vehicle driving). ... 36 million-acre system of National
> Conservation Lands (including wilderness areas, wilderness study areas,
> national monuments, national conservation areas, historic trails, and wild
> and scenic rivers); protecting wild horse and burro rangeland; conserving
> wildlife, fish, and plant habitat"
>
> Also agriculture. Burning Man's Black Rock City is leased from BLM under
> an Special Recreation Permit (SRP). ... " crop harvesting, residential
> occupancy, recreation facilities, construction equipment storage, assembly
> yards, well pumps, and other uses." So, even though it might be BLM, it
> could also be under a 50 year lease to a commercial entity, so for all
> intents and purposes be regarded as private property - like massive solar (
> 19 million acres  ) and wind ( 20 million acres  ) energy farms. I seem to
> recall a Nevada brothel was at one time operating on BLM land with a lease
> and permit - pretty much, as long as you don't leave the land damaged and
> it doesn't interfere with other planned uses, you can get a lease.
>
> Just saying, one class isn't going to do it. Mostly, 'exploited', not
> 'protected'.
>
> Michael Patrick
> Data Ferret
>
>
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>


-- 
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-de] Attribut für die Europachausee in Halle (Saale)

2019-01-08 Per discussione Martin Koppenhoefer


sent from a phone

> On 8. Jan 2019, at 11:03, Heinz-Jürgen Oertel  wrote:
> 
> Grundsätzlich sollte diese Strecke auch als Umgehungsstraße von Navis genutzt 
> werden. Darauf weist auch der Wiki Eintrag hin, diese durch trunk tagging zu 
> bevorzugen.


trunk bedeutet AFAIK kreuzungsfrei ausgebaut und Richtungsfahrbahnen getrennt. 
Dass ein trunk am Anfang und Ende zur secondary wird, halte ich aber auch für 
komisch, vielleicht primary?

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione mbranco2
Ciao Gianfranco,
nell'unirmi decisamente all'unanimità che non vuole vedere i landuse
attaccati alle strade ed agli edifici, faccio notare che duplicare la
strada (con il comando Modifica / Duplica, o meglio ancora dal pulsante
"Crea copie paralllele dei percorsi - Shift P") per fare il contorno di un
landuse è questione di un attimo.
Segnalo anche a chi non lo conoscesse il plugin di Josm ContourMerge [1]
che consente velocemente di unire landuse adiacenti.

[1] https://wiki.openstreetmap.org/wiki/JOSM/Plugins/ContourMerge

Il giorno mar 8 gen 2019 alle ore 12:54 Simone Saviolo <
simone.savi...@gmail.com> ha scritto:

> Il giorno mar 8 gen 2019 alle ore 09:47 Graizzaro Gianfranco <
> gianfranco.graizz...@gmail.com> ha scritto:
>
>> Però secondo me bisogna anche distinguere le situazioni, per esempio se
>> metto una zona residenziale e la strada ci passa in mezzo, anche la strada
>> ed il marciapiede sono in zona residenziale, non vedo perchè bisogna
>> tenere
>> staccata il landuse dalla strada,
>
>
> Io non dormo né mangio in mezzo alla strada :)
>
> Se mi parli di una zona come questa [1] e mi dici che il vicolo e
> parcheggino dietro a "La Convenienza" non li escluderesti dall'isolato
> residenziale, posso essere d'accordo. Ma le strade che vedi (via Paggi, via
> Alfieri, via Ariosto, via Guicciardini, etc.) non sono un landuse
> residenziale. La gente le usa per andare da una parte all'altra della città
> (via Paggi). o ci parcheggia anche quando non abita lì. La strada non è una
> pertinenza della zona residenziale.
>
> [1] https://www.google.com/maps/@45.3215192,8.4140972,163m/data=!3m1!1e3
>
>
>> la stessa cosa se ho da una parte
>> residenziale e dall'altra industriale o bosco, fuori dal nastro di asfalto
>> che viene renderizzato con la striscia bianca, la cui larghezza cambia a
>> seconda della scala è una o l'altra cosa, non è che è niente.
>>
>
> Giusto: *fuori* dal nastro di asfalto. Ma la larghezza del nastro di
> asfalto non cambia con la scala del rendering: è fissa e fisicamente
> misurabile. Se disegni i landuse fino alla strada, *nel rendering* sembrano
> separati da una striscia la cui larghezza non ha correlazione con la
> realtà, invece sono (su OSM) attaccati e "sotto" la strada.
>
>
>> Considerato che i landuse hanno un livello di rendering più basso di tutti
>> gli altri oggetti, e che non mappiamo per il rendering,
>
>
> Vedi sopra. In questo caso, attaccare i landuse alla strada sarebbe
> tollerabile solo per un comportamento (neppure sbagliato) del rendering.
>
> (Più che tollerabile, non salterebbe all'occhio).
>
>
>> io pensavo di
>> utilizzare anche le strade come bordo perchè in caso di spostamento delle
>> strade si spostano anche loro,
>
>
> Non è vero: se riprendi il mio esempio di prima (
> https://www.openstreetmap.org/#map=19/45.18441/8.40137) quel parcheggio
> vicino alla chiesa fra un anno potrebbe essere rimosso, potrebbero far
> passare la strada di fianco alla chiesa e il resto dello spazio a ovest
> usarlo come area verde. Voilà: strade spostate, parcheggio spostato, un
> nuovo landuse (l'area verde), ma il residential (case e loro pertinenze)
> rimangono dove sono.
>
> Io da anni dico che bisognerebbe usare il landuse=road.
>
>
>> ed a tutte le scale non vedi residui grigi.
>> esempio:
>> https://www.openstreetmap.org/#map=18/45.60637/11.25387
>
>
> I residui grigi non sono il male :)
>
>
>> Però capisco la difficoltà di molti utenti e la facilità di errore per chi
>> non usa JOSM
>>
>
> Anche per chi usa JOSM, credimi. Sbrogliare matasse di landuse è un
> lavoraccio.
>
> Ciao,
>
> Simone
> ___
> 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-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Martin Koppenhoefer


sent from a phone

> On 8. Jan 2019, at 09:46, Graizzaro Gianfranco 
>  wrote:
> 
> Però secondo me bisogna anche distinguere le situazioni, per esempio se
> metto una zona residenziale e la strada ci passa in mezzo, anche la strada
> ed il marciapiede sono in zona residenziale


per me questo è sbagliato, la strada non fa parte del landuse. Un tag 
landuse=residential per me indica un’area dove si vive (una proprietà del suolo 
che viene utilizzato per vivere), non è la stessa cosa di una “zona 
residenziale”, quest’ultima è un place in osm (una parte di un centro abitato, 
con nome).

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Martin Koppenhoefer


sent from a phone

> On 8. Jan 2019, at 09:13, Lorenzo Beltrami  wrote:
> 
> Penso anch'io che gli svantaggi siano superiori ai vantaggi.


concordo pienamente. Posso anche capire che non è necessariamente sbagliato 
(topologicamente la linea della strada rappresenta tutta la strada, ecc.), ed è 
un cincinno più veloce inizialmente, ma poi diventa un incubo per successive 
modifiche, mappatori meno esperti rischiano di connettere altre strade al 
landuse invece della strada, la superficie dell’area diventa troppo grande ecc.

Immagina un’area delimitata da una recinzione, cosa fai? Estendi l’area oltre 
la recinzione oppure metti la recinzione in mezzo alla strada?


Ciao, Martin 



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


Re: [OSM-talk] Help with way forward with Grab

2019-01-08 Per discussione Martin Koppenhoefer


sent from a phone

> On 7. Jan 2019, at 18:53, Volker Schmidt  wrote:
> 
> Essentially the amount of work needed to obtain a good map for bicycles is 
> considerably higher than for a map that will only be used for car routing. 
> Mapping for bicycles requires more details, like minor roads that can onluy 
> be used by pedestrians or bicycles with accurate width plus mapping of all 
> obstacles, including the maxwidth of all barriers.


+1, I would also expect cyclists to be more demanding, a 5km detour because of 
a missing connection will maybe not even be noticed by a car driver, but a 
cyclist will be very upset when she sees it ;-)

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


[OSM-talk-fr] Offre de stage "Accessibilité dans OSM" à Clermont-Ferrand

2019-01-08 Per discussione Vincent de Château-Thierry
Bonjour,

C'est par ici : https://georezo.net/forum/viewtopic.php?id=113843

vincent

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


Re: [talk-ph] Music Venues

2019-01-08 Per discussione Eugene Alvin Villar
I personally just tag the type of establishment and not really bother with
whether the place often has live bands or musicians. Usually it is
amenity=bar but could also be amenity=pub or amenity=nightclub.

On Tue, Jan 8, 2019 at 9:46 AM Jim Morgan  wrote:

> I've often thought it would be useful to be able to tag music venues, bars
> which have bands on, etc. I see there is a tag in the proposal stage. How
> are people in the OSM-PH community handling this, if at all?
>
> Jim
>
___
talk-ph mailing list
talk-ph@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ph


[Talk-it] Wikimedia Italia cerca una/un responsabile per la sezione OpenStreetMap

2019-01-08 Per discussione Maurizio Napolitano
ciao a tutt*
vi giro l'offerta di lavoro di Wikimedia Italia per una persona da
allocare, all'interno dell' associazione, sul tema OpenStreetMap.
--

Wikimedia Italia, Associazione per la diffusione della conoscenza libera,
cerca un responsabile per OpenStreetMap
Dal 2016, Wikimedia Italia è *chapter* ufficiale della OpenStreetMap
Foundation.

Per questo ruolo, la nostra associazione sta cercando una persona che aiuti
a far crescere il progetto in Italia e, per farlo, è necessario essere in
costante contatto con la comunità, seguirla, capirla, espanderla,
rispettarla, potenziarla nelle sue richieste e creare progetti per i quali
cercare finanziamenti.

*Perché crediamo che questo lavoro ti piacerà*

   - avrai modo di contribuire ad un progetto che crea un bene comune
   - potrai rivestire un punto di unione fra gli attori del progetto e
   tutti gli interessati (in particolare istituzioni)
   - conoscerai appassionati del mondo della cartografia
   - creerai sinergie con la comunità italiana di OpenStreetMap
   - sarai in grado di coordinare un gruppo di volontari

*Requisiti*

   - dimostri di avere avuto occasione di interagire con comunità che
   creano beni comuni
   - hai molto chiaro cosa è OpenStreetMap ed hai contributo
   - hai ottime capacità relazionali e sai trasformare il linguaggio
   tecnico in colloquiale e viceversa dialogando così fra comunità online ed
   istituzioni
   - sai definire “tecnologie GIS”, ti esalta usarle
   - sei in grado di contribuire a OpenStreetMap
   - sai automotivarti ed organizzarti con attenzione ai dettagli
   - ti stimola l’idea di riuscire a trovare i finanziamenti per vedere i
   progetti prendere forma
   - sei in grado di coordinare volontari e non in attività di divulgazione
   e/o di sviluppo tecnico
   - non hai grosse difficoltà ad esprimerti in inglese scritto e parlato

*Se tutto ciò ti affascina allora abbiamo bisogno di*

   - un tuo curriculum dove è scritto il tuo percorso fra studio, lavoro ed
   esperienze per cui dovremmo scegliere te
   - una nota dove ci spieghi cosa ti appassiona di questo lavoro
   - esempi di progetti di gestione della comunità in cui hai lavorato o
   partecipato in passato.
   - come ti troviamo sui social network
   - con quale nickname partecipi a OpenStreetMap e/o Wikipedia

Tutto questo va inviato a lav...@wikimedia.it con oggetto "Candidatura
responsabile OpenStreetMap" entro il 23 gennaio 2019.

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


[OSM-talk-be] Fwd: Open Belgium 2019: Call for Speakers + Early Bird Tickets!

2019-01-08 Per discussione Ben Abelshausen
Hi everyone!

In a few months we have Open Belgium again (yay!) and as usual we will have
talks about OSM (Belgium).  We invite everyone to submit a talk,
**anything** related to open-(something) is fine, that means openstreetmap
too! ;-) We will also organize a community day during the weekend this
year, more news about that later, so even if you can't make it on the 4th
of march we urge you to submit talks/workshops anyway. We can move them to
the community day later.

We will probably also have a booth with OSM Belgium and usually have a lot
of fun so don't miss it! If you want to attend but find the entry tickets
too expense get in touch with me, the community day will be free (to be
announced later).

All details here:

-- Forwarded message -
From: Astrid - Open Knowledge Belgium 
Date: Tue, Jan 8, 2019 at 10:17 AM
Subject: Open Belgium 2019: Call for Speakers + Early Bird Tickets!
To: 


A must-attend conference to discuss the state of and current trends around
Open Knowledge and Open Data!

Open Belgium 2019 - 4 March in Brussels
Open Knowledge and Open Data in Belgium
View this email in your browser


Let's talk Open Knowledge and Open Data!
Ready for Open Belgium 2019?


The Belgian open knowledge and open data landscape is changing at a fast
pace. In order to stay up-to-date and to share insights with *300+ fellow
open enthusiasts,* we would like to invite you to join us at the
annual *community-driven
Open Belgium 2019
*
conference on *4 March in Brussels*.

Since you participated in previous editions of Open Belgium, you know
exactly what to expect: inspirational high-level keynote speakers, engaging
panel discussions, hands-on and minds-on workshops as well as an
interactive exhibition space.
Get your *Early Bird ticket* *now* and *save more than 30%!*
GET YOUR TICKET


*When?*
*Monday 4 March, 08:30-19:00*
Full programme available soon
*Where?*
*Herman Teirlinck Building*
Avenue du Port 88, 1000 Brussels

Link to Call for Speakers: http://2019.openbelgium.be/speakers


We are looking forward to seeing you at Open Belgium 2019!

The Open Belgium team





*Copyright © 2019 Open Knowledge Belgium, All rights reserved.*
You are receiving this email because you attended Open Belgium in the past.

*Our mailing address is:*
Open Knowledge Belgium
Kantersteen 12
Brussels 1000
Belgium

Add us to your address book



Want to change how you receive these emails?
You can update your preferences

or unsubscribe from this list

.

[image: Email Marketing Powered by Mailchimp]

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


[Talk-de] Stipendium zu vergeben

2019-01-08 Per discussione Sebastian Kürten
Hallo allerseits,

meine Mitgründerin und ich sind noch auf der Suche nach einer dritten
Person, die mit uns, finanziert durch ein Stipendium, für mindestens
ein Jahr an einem gemeinsamen Projekt arbeiten möchte. Da OSM in diesem
Projekt eine zentrale Rolle spielen wird, schreibe ich an diese Liste,
um jemand zu finden, der die OSM bereits kennt und sich für OSM, aber
auch für offene Daten insgesamt und freie Software, interessiert.

Unser Ziel ist es, spannende, innovative Anwendungen im Geo-Kontext auf
Grundlage von OSM und anderen Datenquellen zu entwickeln. Mittelfristig
wollen wir es schaffen, durch diese Tätigkeit unsere Existenz zu
sichern und gleichzeitig an der OSM mitzuwirken, also Beruf und das
Mitwirken an offenen Daten und freier Software unter einen Hut zu
bekommen. Das Stipendium macht es uns möglich, nicht vom ersten Tag an
Geld verdienen zu müssen, sondern ein Jahr lang in geschützem Rahmen an
unserem Konzept weiter zu arbeiten und Prototypen zu entwickeln. Falls
das für dich interessant klingt, würde ich mich freuen, wenn wir ins
Gespräch kommen könnten.

Pilotregion für unser Projekt ist Berlin, d.h. wir werden Anwendungen
entwickeln, die einen besonderen Fokus auf Berlin haben und lokale
Gegebenheiten berücksichtigen. Wir haben ein Büro bei der
Gründungsförderung der Freien Universität Berlin in Dahlem. Dass du in
Berlin wohnst ist jedoch keine zwingende Vorraussetzung für eine
Zusammenarbeit, da wir uns auch vorstellen können, das ganze remote zu
organisieren. Vorraussetzung ist allerdings ein abgeschlossenes Studium
oder eine abgeschlossene technische Ausbildung. Weitere allgemeine
Informationen zum Stipendium erhaltet ihr auf dieser Website:
https://www.exist.de/DE/Programm/Exist-Gruenderstipendium/inhalt.html

Viele Grüße
Sebastian

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Simone Saviolo
Il giorno mar 8 gen 2019 alle ore 09:47 Graizzaro Gianfranco <
gianfranco.graizz...@gmail.com> ha scritto:

> Però secondo me bisogna anche distinguere le situazioni, per esempio se
> metto una zona residenziale e la strada ci passa in mezzo, anche la strada
> ed il marciapiede sono in zona residenziale, non vedo perchè bisogna tenere
> staccata il landuse dalla strada,


Io non dormo né mangio in mezzo alla strada :)

Se mi parli di una zona come questa [1] e mi dici che il vicolo e
parcheggino dietro a "La Convenienza" non li escluderesti dall'isolato
residenziale, posso essere d'accordo. Ma le strade che vedi (via Paggi, via
Alfieri, via Ariosto, via Guicciardini, etc.) non sono un landuse
residenziale. La gente le usa per andare da una parte all'altra della città
(via Paggi). o ci parcheggia anche quando non abita lì. La strada non è una
pertinenza della zona residenziale.

[1] https://www.google.com/maps/@45.3215192,8.4140972,163m/data=!3m1!1e3


> la stessa cosa se ho da una parte
> residenziale e dall'altra industriale o bosco, fuori dal nastro di asfalto
> che viene renderizzato con la striscia bianca, la cui larghezza cambia a
> seconda della scala è una o l'altra cosa, non è che è niente.
>

Giusto: *fuori* dal nastro di asfalto. Ma la larghezza del nastro di
asfalto non cambia con la scala del rendering: è fissa e fisicamente
misurabile. Se disegni i landuse fino alla strada, *nel rendering* sembrano
separati da una striscia la cui larghezza non ha correlazione con la
realtà, invece sono (su OSM) attaccati e "sotto" la strada.


> Considerato che i landuse hanno un livello di rendering più basso di tutti
> gli altri oggetti, e che non mappiamo per il rendering,


Vedi sopra. In questo caso, attaccare i landuse alla strada sarebbe
tollerabile solo per un comportamento (neppure sbagliato) del rendering.

(Più che tollerabile, non salterebbe all'occhio).


> io pensavo di
> utilizzare anche le strade come bordo perchè in caso di spostamento delle
> strade si spostano anche loro,


Non è vero: se riprendi il mio esempio di prima (
https://www.openstreetmap.org/#map=19/45.18441/8.40137) quel parcheggio
vicino alla chiesa fra un anno potrebbe essere rimosso, potrebbero far
passare la strada di fianco alla chiesa e il resto dello spazio a ovest
usarlo come area verde. Voilà: strade spostate, parcheggio spostato, un
nuovo landuse (l'area verde), ma il residential (case e loro pertinenze)
rimangono dove sono.

Io da anni dico che bisognerebbe usare il landuse=road.


> ed a tutte le scale non vedi residui grigi.
> esempio:
> https://www.openstreetmap.org/#map=18/45.60637/11.25387


I residui grigi non sono il male :)


> Però capisco la difficoltà di molti utenti e la facilità di errore per chi
> non usa JOSM
>

Anche per chi usa JOSM, credimi. Sbrogliare matasse di landuse è un
lavoraccio.

Ciao,

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


Re: [Talk-is] Data improvements in Iceland

2019-01-08 Per discussione Jóhannes Birgir Jensson
This sounds very useful Matt.

I have previously approached ja.is about the 360 imagery on behalf of 
OpenStreetMap á Íslandi and a permission to use it as a data source. The reply 
in 2018 was "not for now - maybe later" so if this is later then it would be 
great.

The GPS traces would be very nice too.

Regarding using LUKR as a source then be advised it is not 100% correct - it 
contains a number of ghost buildings for example (where a zone has been 
approved for a building but it hasn't been built yet). For example in my 
previous residence I had a license to build a garage (with other residents) and 
on LUKR the garage was already built while it still has not moved off the 
drawing board for 20 years.

--JBJ

8. janúar 2019 kl. 11:30, skrifaði "Matt Riggott" :

>> On 5 Jan 2019, at 11:14, Morten Lange  wrote:
>> 
>> It would be great if paths found on ja.is maps could be freely used on 
>> OpenStreetMap, and the other
>> way around. I guess that depends on licensing clauses.
> 
> Hi Morten,
> 
> I agree, it'd be really nice to have that, but you're right to think the 
> licence is too
> prohibitive. The map tiles are produced by Samsýn and they're quite strict on 
> what we can do with
> them. Besides that, the tiles are projected using ISN 93, so using them as an 
> OpenStreetMap layer
> would cause alignment problems.
> 
> But I can think of some ways Já could help OpenStreetMap. First, I could ask 
> for Já to give
> OpenStreetMap explicit permission to use the Já 360 street view photos as a 
> data source. Second, we
> have GPS coordinates from the car that drove around the country taking the Já 
> 360 photos; I could
> ask to be able to publish the GPS data under a permissive licence.
> 
> If any of that sounds useful, let me know.
> 
> M.
> 
> --
> Matt Riggott
> Programmer / Forritari
> 
> https://ja.is
> ___
> Talk-is mailing list
> Talk-is@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-is

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


Re: [Talk-is] Data improvements in Iceland

2019-01-08 Per discussione Matt Riggott
> On 5 Jan 2019, at 11:14, Morten Lange  wrote:
> 
> It would be great if paths found on ja.is maps could be freely used on 
> OpenStreetMap, and the other way around. I guess that depends on licensing 
> clauses. 

Hi Morten,

I agree, it'd be really nice to have that, but you're right to think the 
licence is too prohibitive. The map tiles are produced by Samsýn and they're 
quite strict on what we can do with them. Besides that, the tiles are projected 
using ISN 93, so using them as an OpenStreetMap layer would cause alignment 
problems.

But I can think of some ways Já could help OpenStreetMap. First, I could ask 
for Já to give OpenStreetMap explicit permission to use the Já 360 street view 
photos as a data source. Second, we have GPS coordinates from the car that 
drove around the country taking the Já 360 photos; I could ask to be able to 
publish the GPS data under a permissive licence.

If any of that sounds useful, let me know.

M.

-- 
Matt Riggott
Programmer / Forritari

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


Re: [OSM-talk-fr] tag indiquant le paiement possible avec la monnaie locale

2019-01-08 Per discussione Cyrille37 OSM

Salut

Pour info, Le réseau des MLCC (Monnaies Locales Complémentaires 
Citoyennes) :


http://monnaie-locale-complementaire-citoyenne.net avec pour raccourci 
http://www.mlc.camp


par exemple la Gabare (en Touraine) : http://gabare.mlc.camp

C'est peut être le moyen de connaître une liste des monnaies locales 
(françaises).


Cyrille37

Le 08/01/2019 à 11:52, marc marc a écrit :

Le 08.01.19 à 10:00, Francescu GAROBY a écrit :

Mais peut-être faudrait-il plutôt un tag du genre
"payment:local:rollon=yes", pour regrouper toutes les monnaies locales
existantes sous une même sous-clé ?

c'est une idée séduisante mais qui ne semble quasi pas avoir été
utilisée pour le moment
https://taginfo.openstreetmap.org/search?q=payment%3Aloca

je ne connais pas assez de nom de monnaie alternative
pour repérer dans la liste si beaucoup d'entre elle sont deja
renseignée dans osm
https://taginfo.openstreetmap.org/search?q=payment%3A
les noms que je connais sont absent ou ultra marginal <5 occurrences
(eusko en france, wir/léman en suisse, talent en belgique,
Chiemgauer en allemagne)

ceci dit, c'est pas nécessaire de mettre la valeur dans la clef
payment:local=rollon fait tout aussi bien l'affaire non ?
le jour ou un commerce accepte 2 monnaies locales (exemple en suisse
avec wir et léman) payment:local=léman;wir le gère sans soucis.
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


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


Re: [OSM-talk-fr] tag indiquant le paiement possible avec la monnaie locale

2019-01-08 Per discussione marc marc
Le 08.01.19 à 10:00, Francescu GAROBY a écrit :
> Mais peut-être faudrait-il plutôt un tag du genre 
> "payment:local:rollon=yes", pour regrouper toutes les monnaies locales 
> existantes sous une même sous-clé ?

c'est une idée séduisante mais qui ne semble quasi pas avoir été 
utilisée pour le moment
https://taginfo.openstreetmap.org/search?q=payment%3Aloca

je ne connais pas assez de nom de monnaie alternative
pour repérer dans la liste si beaucoup d'entre elle sont deja
renseignée dans osm
https://taginfo.openstreetmap.org/search?q=payment%3A
les noms que je connais sont absent ou ultra marginal <5 occurrences 
(eusko en france, wir/léman en suisse, talent en belgique,
Chiemgauer en allemagne)

ceci dit, c'est pas nécessaire de mettre la valeur dans la clef
payment:local=rollon fait tout aussi bien l'affaire non ?
le jour ou un commerce accepte 2 monnaies locales (exemple en suisse 
avec wir et léman) payment:local=léman;wir le gère sans soucis.
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-it-trentino] [Talk-it-cai] Sedi SAT

2019-01-08 Per discussione michele zanolli
Ciao Luca,
concordo anche io, mi suona meglio il primo

la SAT è una sede/sezione CAI, le sezioni SAT invece sarebbero delle
"sottosezioni" CAI, ma rispondono direttamente alla SAT

michele

On Tue, Jan 8, 2019 at 3:32 AM Luca Delucchi  wrote:
>
> Ciao a tutti,
>
> visto l'altro thread sulle sedi CAI, per quelle SAT come operator cosa usiamo?
> Società degli Alpinisti Tridentini o Club Alpino Italiano ?
>
> Io propenderei più per il primo
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
> ___
> Talk-it-cai mailing list
> talk-it-...@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it-cai

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


Re: [Talk-de] Attribut für die Europachausee in Halle (Saale)

2019-01-08 Per discussione Heinz-Jürgen Oertel
Martin,

Am Montag, 7. Januar 2019, 23:57:58 CET schrieb Martin Scholtes:
> Hallo,
> 
> also ich sehe da kein hw=secondary? 

da hast Du wohl gerade das Mittelstück erwischt, ja das ist als trunk getaggt.
Aber der Anfang, Beginn an der Merseburger Straße im Süden, und das neue Ende 
im Norden an der B100 als secondary.

> Grundsätzlich stimme ich dir aber
> für die Umgehung zu, das es ein hw=trunk sein sollte, auch wenn es keine
> Kraftfahrstraße sein sollte.

Grundsätzlich sollte diese Strecke auch als Umgehungsstraße von Navis genutzt 
werden. Darauf weist auch der Wiki Eintrag hin, diese durch trunk tagging zu 
bevorzugen.

Heinz


> 
> Am 07.01.2019 um 23:53 schrieb Heinz-Jürgen Oertel:
> > Hallo,
> > 
> > endlich ist die östliche Umgehungsstraße in Halle fertiggestellt und
> > befahrbar. Das Mittelteil ist als highway=trunk getaggt. Anfang und Ende
> > jedoch highway=secondary.
> > Nach meiner Meinung macht dies keinen Sinn, da die Straße wie in
> > https://wiki.openstreetmap.org/wiki/DE:Tag:highway=trunk?uselang=de
> > "eine autobahnähnliche Schnellstraße mit hoher Verkehrsbedeutung"
> > bezeichnet.
> > 
> > Sie wird offiziell Umgehungsstraße zur Entlastung, oder auch Osttangente
> > genannt.





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


[talk-cz] Strava heatmapa CZ

2019-01-08 Per discussione Tom Ka
Ahoj,

doplnil jsem krome informace o nejstarsi dlazdici i histogram poctu
dlazdic dle stari (primarne pro sebe at je videt, kdy ma smysl poustet
aktualizaci):

http://osm.fit.vutbr.cz/strava/

Mimo jine, ted par ni poustim mensi aktualizace at se zase posuneme na
novejsi podklady :-)

Bye

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Max1234Ita
Graizzaro Gianfranco wrote
> Si infatti, sono d'accordo anch'io con voi, stavo solo cercando di
> chiarirmi
> le idee.
> Però secondo me bisogna anche distinguere le situazioni, per esempio se
> metto una zona residenziale e la strada ci passa in mezzo, anche la strada
> ed il marciapiede sono in zona residenziale, non vedo perchè bisogna
> tenere
> staccata il landuse dalla strada, la stessa cosa se ho da una parte
> residenziale e dall'altra industriale o bosco, fuori dal nastro di asfalto
> che viene renderizzato con la striscia bianca, la cui larghezza cambia a
> seconda della scala è una o l'altra cosa, non è che è niente.
> Considerato che i landuse hanno un livello di rendering più basso di tutti
> gli altri oggetti, e che non mappiamo per il rendering, per una maggiore
> manutenzione è meglio che siano indipendenti e secondo me anche chiusi,
> cioè
> senza buchi vuoti, anche in corrispondenza delle strade, io pensavo di
> utilizzare anche le strade come bordo perchè in caso di spostamento delle
> strade si spostano anche loro, ed a tutte le scale non vedi residui grigi.
> esempio:
> https://www.openstreetmap.org/#map=18/45.60637/11.25387
> 
> Però capisco la difficoltà di molti utenti e la facilità di errore per chi
> non usa JOSM
> 
> Gianfranco


Scusate ma il browser mi ha caricato solo ora la parte restante della
pagina.

IMHO, non è un problema se restano dei "buchi vuoti", anche se devo prendere
atto che da sempre i mappatori soffrono di questa sorta di "horror vacui"
che li porta a riempire ogni spazio con qualche informazione, quale che sia,
pur di non lasciare aree in bianco sulla carta.

Credo invece che dovremmo essere più pragmatici, specialmente oggi che di
informazioni da mappare ce ne sono fin troppe: un po' di spazio vuoto è
sempre utile per poterne aggiungere altre, se necessario, senza troppa
difficoltà. :-)

Max


PS. Per chi fosse interessato alla storia della Cartografia e/o cercasse un
"regalo della Befana un po' in ritardo", segnalo 2 interessanti titoli:
  - /Sulle mappe. Il mondo come lo disegniamo/ - di Simon Garfield (ed.
Ponte alle Grazie)
  - /I signori delle mappe. La storia avventurosa dell'invenzione della
cartografia/, di John Noble Wilford (ed. Garzanti)



--
Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Graizzaro Gianfranco
Perfetto, allora teniamo le landuse separate dalle higway.

Gianfranco



--
Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html

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


[OSM-talk-fr] tag indiquant le paiement possible avec la monnaie locale

2019-01-08 Per discussione Francescu GAROBY
Bonjour (et bonne année),
En consultant la page du Wiki sur les modes de paiement
, je ne vois pas de cas
pour les monnaies locales.
Voulant déclarer les commerces (en Normandie) qui acceptent le Rollon
, je suis tenté de créer le tag
"payment:rollon=yes", mais je voulais être sûr que c'était la bonne façon
de faire.
Mais peut-être faudrait-il plutôt un tag du genre
"payment:local:rollon=yes", pour regrouper toutes les monnaies locales
existantes sous une même sous-clé ?

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Graizzaro Gianfranco
Si infatti, sono d'accordo anch'io con voi, stavo solo cercando di chiarirmi
le idee.
Però secondo me bisogna anche distinguere le situazioni, per esempio se
metto una zona residenziale e la strada ci passa in mezzo, anche la strada
ed il marciapiede sono in zona residenziale, non vedo perchè bisogna tenere
staccata il landuse dalla strada, la stessa cosa se ho da una parte
residenziale e dall'altra industriale o bosco, fuori dal nastro di asfalto
che viene renderizzato con la striscia bianca, la cui larghezza cambia a
seconda della scala è una o l'altra cosa, non è che è niente.
Considerato che i landuse hanno un livello di rendering più basso di tutti
gli altri oggetti, e che non mappiamo per il rendering, per una maggiore
manutenzione è meglio che siano indipendenti e secondo me anche chiusi, cioè
senza buchi vuoti, anche in corrispondenza delle strade, io pensavo di
utilizzare anche le strade come bordo perchè in caso di spostamento delle
strade si spostano anche loro, ed a tutte le scale non vedi residui grigi.
esempio:
https://www.openstreetmap.org/#map=18/45.60637/11.25387

Però capisco la difficoltà di molti utenti e la facilità di errore per chi
non usa JOSM

Gianfranco



--
Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Max1234Ita
Ciao Gianfranco,
come diceva Volker, la convenzione è di lasciare strade e multipoligoni
/landuse/ (e /natural/) come entità a sè, per ridurre il rischio che
cambiando le proprietà di una strada (ad esempio cancellando un nodo)
qualche utente inesperto o poco accorto possa andare a distruggere più o
meno involontariamente qualche relazione connessa.


Graizzaro Gianfranco wrote
>  però in questo caso le strade extraurbane verrebbero spezzettate ad
> ogni cambio di landuse.

...e questo è un altro dei "buoni motivi" già citati.
Solo per farti un esempio, pensa che cosa succederebbe se, "banalmente",
cambiasse o venisse mappato ex-novo il limite di velocità su un tratto di
strada che comprende una dozzina di relazioni di questo tipo...


Ciao e buona mappatura!
Max



--
Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html

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


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Lorenzo Beltrami
Penso anch'io che gli svantaggi siano superiori ai vantaggi.

Per esempio c'è un utente dalle mie parti che tende a riempire tutto
(horror vacui?) con i landuse appiccicandoli a tutto quello che trova.
Percorsi, strade, edifici, altri landuse...
Ecco uno screenshot: https://i.imgur.com/nE0cL4K.png [1]
È il classico caso in cui la manutenzione è un incubo, come hanno detto
Andrea e Alessandro.
Tempo fa per creare la relazione di una route per autobus (che richiede una
relazione utilizzando le strade) ci ho messo ore...

Per quanto riguarda le strade in particolare ha ragione Daniele. Al momento
su OSM la strada è rappresentata con un percorso posto sulla mezzeria, ma
nella realtà ha una dimensione; informazione che verrebbe persa se usassimo
quel percorso come bordo di un landuse.
Inoltre spesso tra la strada e il landuse, come dice Volker, ci stanno
marciapiedi, lampioni, fossi e tanto altro che finirebbero dentro il
landuse (o a sua volta come bordo per esso, ritornando daccapo).

Saluti
Lorenzo

[1] https://www.openstreetmap.org/#map=18/44.71731/10.62453
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [Talk-it] Relazioni Multypoligon per landuse

2019-01-08 Per discussione Simone Saviolo
Il giorno lun 7 gen 2019 alle ore 19:26 Gianfranco Graizzaro <
gianfranco.graizz...@gmail.com> ha scritto:

> Stavo pensando per i landuse di usare i Multipolygon e includere le strade
> in essi, però in questo caso le strade extraurbane verrebbero spezzettate
> ad ogni cambio di landuse.
>

N!! (con enfasi cinematografica :) )

Usare i nodi delle strade per mappare i landuse è
- brutto: la mappa diventa un pastone e si salva solo grazie ad un effetto
collaterale (le way delle strade vengono renderizzate con una larghezza che
"copre" l'errore);
- scomodo: rifinire o modificare il landuse o la strada comporta una
modifica anche dell'altro elemento - e non sempre questo è quello che si
vuole;
- semplicemente sbagliato: il landuse non finisce in mezzo alla strada; due
landuse che stanno dalle due parti opposte della strada non si toccano e
non confinano.

E questo vale sia per le way chiuse sia per i multipoligoni. Per i
multipoligoni ci sono ulteriori difficoltà che ti hanno già illustrato gli
altri.

Quindi, mappa la realtà: le residential, i campi e le foreste finiscono
qualche metro più in là della strada.
Un esempio in un paese:
https://www.openstreetmap.org/#map=19/45.18438/8.40170
Un esempio appena fuori città:
https://www.openstreetmap.org/#map=18/45.32414/8.38724

Ciao,

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