date:20170217

河原さん、こんにちは。
私も千葉（松戸）在住で、マッピングを始めたころ河原さんのWiki記事やマッピング（たぶん）は参考にさせて頂きました。

東日本大震災の前後から日本のOSMをとりまく状況が
大きく変わってきているので、具体的な事象をベースに
議論させて頂いたほうが良さそうな気はしますが
インポートについてはどうしてもやりたい人は
ライセンスをクリアにしたり該当地域のコミュニティなどと
連絡を取りながら進めるのが原則となっているかと思います。
時々勝手にやってしまうケースも見受けられますが
そういったものには手順を踏んで頂くようお願いしたり
あくまでコンタクトを無視されるケースでは最終的に
リバートされて編集を取り消されることもあります。
（なお、私自身はインポートは好みません。下絵にしてトレース
する派です）

そういった中で2011年の東日本大震災の折には
たまたまYahoo/ALPSデータの利用を許諾頂いたところだったため
どこまで役に立つかは見えないながらも
災害復興の何らかの後方支援になればと
何名かで手分けして大挙、道路データをインポートしました。
結果として道路距離的には飛躍的に充実しましたが
Yahoo/ALPSデータはざっくりの感触では1/25000くらいの精度であり
今のスマホや衛星画像で見るとズレズレ感は否めません。
なのでYahoo/ALPSデータについては各地マッパーのみなさんが
より精度の高い衛星画像や地理院地図で都度描き直している
というのが実状ではないかと思います。
その際、別のデータをインポートするケースはごく少なく
大抵は画像を下絵にトレースし、POIは現地でマッピング
という形が多いのではないかと思います。

ご指摘のひどい編集状況は実際に見てみないとなんとも言えませんが
初心者の方がとりあえず編集してみました、で終わっている状況
だとすれば、地域のOSMコミュニティで連絡を取り合うような
ことができると良いですね。
また、品質改善ツールもいろいろあるのでそういったものにも
目を向ける人が増えてくることも期待したいです。

OSMFJという組織はありますが、少人数のボランティアが
最低限のことだけなんとかかんとか回している状況なので
中央集権的な機能や組織を強化するというより、分散的に
地方自治みたいな方向性がいちばん良いんじゃないかと思っています。
今でもOSM.orgにメモで不明点や誤りを指摘する機能もありますので
そういったものを地域でちゃんと運営していくといったことも
ひとつの方法かなと思ったりもします。
私見ですがとりあえず。
東



2017/02/18 insidekiwi...@yahoo.co.jp :
> ikiyaです。
>
> 河原さん、こんにちは。
>>他の利用可能とされたリソースからのデータインポートが行われるようになったからです。　多くのインポート元はデータが古く、・・・
>>インポート元となった航空写真の解像度が足りなかったのか、現地取材せずに写真を判図したのか・・・
>
> おっしゃる通り、がっかりします。
> 私も昔、Yahoo!アルプスの道路データがインポートされた時、自分でGPSログからライン取りをこだわって書いたあまたの県道が見事に置き換わりました。
> 当時、私のGPSトレースのほうが精度は上でした。（相変わらず、カリカリ直しています。）
> 最近は、ルール（既存データを無視したり）を外れたインポート、編集についてはリバートという方法も選べるようになりましたが、
> それでも、足しげくマッピングした地域が書き換わると気持ちが良いものではありません。
>
> OSMは誰でもが自由に書ける、使える地図データと言われます。
> 最近では「地図データの前に人ありきでしょ。」と聞きます。私は同感です。
>
>>誤りを指摘すると→プロのマッパー/編集チームがその指摘内容を検証し→資料に当たる・現地調査し→
>>地図の変更案を提示して意見を求め→異論が出なくなれば最終的にマスターファイルに反映する
>
> 正直、よい（あこがれる）フローだと思います。
> 市民レベルから誰でもが自由に書けるを掲げて歩んできたOSMですが、
> 制限のステップを設けることについてどう思われますか？
> このフローをボランタリなコミュニティーの中で構築するには知恵とコミュニティーの同意が必要と思っています。
> 私はまだ自由に書けるOSMを選びたいですが、ローカル重視で地図の誤り検証や意見調整する
> Regional Leader地域リーダーやRegionaｌ Ambassadorといった仕組みは不可欠と考えます。
> ボランタリーなメンバーでどう作るか考えるのも楽しいかもしれません。
>
> 以上、まとまりないですが雑感です。
>
>
>
>
> - Original Message -
>>From: 河原太郎 
>>To: OpenStreetMap Japanese talk 
>>Date: 2017/2/18, Sat 07:20
>>Subject: [OSM-ja] Missing points of OSM
>>
>>河原です。お久しぶりです。
>>
>>
>>私は、以前はOSMのマッパーだったこともありますが、今は興味を失っていまして、活動していません。
>>
>>ただ、現在のOSM組織の活動内容が偽善的だとは思っていません。
>> OSMを利用するのも編集するのも止めたのには、別の理由があります。それは、他の利用可能とされたリソースからのデータインポートが行われるようになったからです。
>> 　
>> 多くのインポート元はデータが古く、私が住んでいる地域のOSM地図は、まるで古地図をみているかのうような現状とは乖離した状態となっており、さすがに利用する気は起きません。ちょっといくつか追加編集すれば済むようなレベルではないのです。
>>
>>また、インポート元となった航空写真の解像度が足りなかったのか、現地取材せずに写真を判図したのか、神社の境内へ向かう通り抜けのできない階段が、反対側へ抜けられる道路として描かれていたり、実際にはフェンスがあって通行できない隣接した道路がフェンスなどなく通行できるかのように描かれていたり、自宅周辺半径1km以内だけでみても、両手で数え切れないぐらいの誤りがインポートされていて、それが全体に広がっているのかと思うとやる気を失いました。
>>
>>
>>現在のOSMで欠けている(他の地図サイトと異なっている)のは、レビューシステムの欠落ではないかと思います。どの地図サイトなのかは、書くと宣伝行為になりそうでこのMLの趣旨に反すると思うので、敢えて伏せますが、誤りを指摘すると→プロのマッパー/編集チームがその指摘内容を検証し→資料に当たる・現地調査し→地図の変更案を提示して意見を求め→異論が出なくなれば最終的にマスターファイルに反映する、というレビューシステムが構築されており、個々の誤り指摘に対して、その作業の進捗状況が分かるようになっています。OSMでは、誰もが勝手にマスターファイルを直接に更新しているため、それが誤りであっても即座に反映されてしまい、地図を信じた利用者が現地で通行止めを喰らってこん
> な地図使えねぇという事態になっています。
>>
>>
>>私がOSMを利用するのを止めていても、talk-ja
>> に継続して購読しているのは、こうしたシステムの改革がそのうち行われるだろうと期待しているからです。
>>
>>
>>千葉県千葉市在住
>>
>>河原太郎
>>
>>
>>
>>___
>>Talk-ja mailing list
>>Talk-ja@openstreetmap.org
>>https://lists.openstreetmap.org/listinfo/talk-ja
>>
>>
>>
___
Talk-ja mailing list
Talk-ja@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ja

Re: [OSM-ja] (無題)

2017/02/18 ribbon :
> On Sat, Feb 18, 2017 at 12:06:43PM +0900, Shu Higashi wrote:
>> こんにちは。日本語がおわかりのようなので日本語で。
>
> 分かっていない可能性もあるかと。
> 英文をそのままgoogle翻訳で処理してみましたが、投稿された日本語と
> 全く同じ訳文が出てきました。

自分が機械翻訳を使える人は日本語を自分の言語に翻訳するくらいは
できるでしょう。コミュニケーションをとる意志があれば。
そうしたことも含めて日本語がわかると書きました。

東

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

Re: [OSM-ja] (無題)

2017-02-17 Thread ribbon

On Sat, Feb 18, 2017 at 12:06:43PM +0900, Shu Higashi wrote:
> こんにちは。日本語がおわかりのようなので日本語で。

分かっていない可能性もあるかと。
英文をそのままgoogle翻訳で処理してみましたが、投稿された日本語と
全く同じ訳文が出てきました。

ribbon

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

Re: [OSM-ja] (無題)

先ほどのわたしの返信に対して下記配信エラーが返ってきました。
コミュニケーションを望んでおられないのでしょうか。。東

アドレスが見つからなかったため、メールは radcliff0...@yahoo.co.jp
に配信されませんでした。入力ミスや不要なスペースがないことを確認してから、もう一度送信してみてください。

2017/02/18 Shu Higashi :
> こんにちは。日本語がおわかりのようなので日本語で。
>
> ご自分が編集された内容が戻された(reverted)ということでしょうか。
> 私自身はrevertには関係しておりませんが
> 具体的にどの編集のことか示してもらえると
> 議論ができるのではないかと思います。
>
> 東
>
> 2017-02-17 22:38 GMT+09:00, radcliff0...@yahoo.co.jp
> :
>> あなたは良い貢献者の努力の結果を破壊します。 あなたはその成果を消して、あなたのように見せます。
>> あなたはグループ内のルールを緩和し、通常のコントリビュータに厳しく適用します。 あなたは偽善者です。 これは犯罪アリバイを作る場所です。
>> 私たちはあなたを日本の代表者として承認しません。 あなたは日本を管理する権利がありません。 あなたは何も言わずに編集内容を破棄します。
>> 誰も明確な意見を表明しません。 誰も責任を負いません。 あなたは利己的で不公平です。 あなたは独占権を守るために新しい貢献者に干渉します。
>> あなたの犯罪を忘れることはありません。
>> 善意の貢献者に。 日本から偽善者が消えるまで寄稿をやめてください。 私たちの努力は消滅します。 私たちの貢献は盗まれています。
>> 偽善者の嫌がらせのために、日本のOSM寄稿者の数は増えていない。 さらに、このメールを保存して他の場所に公開します。
>> 偽善者は事実を隠して犯罪を隠すでしょう。
>>
>> You destroy the results of the efforts of good contributors. You erase
>> their
>> achievements and make them look like yours. You relax the rules within
>> the
>> group and apply them to the ordinary contributors severely. You are
>> hypocrites. This is the place to make crime alibi. We will not approve
>> you
>> as representatives of Japan. You do not have the right to manage Japan.
>> You
>> destroy edits without arguing anything. No one expresses a clear opinion.
>> No
>> one takes responsibility. You are selfish and unfair. You interfere with
>> new
>> contributors to protect your monopoly. We will not forget your crime.
>>
>> To goodwill contributors. Stop contributing until the hypocrites
>> disappear
>> from Japan. Our efforts are extinguished. Our contributions are stolen.
>> Because of the harassment of the hypocrites, the number of Japanese OSM
>> contributors has not increased. In addition, save this mail and reveal it
>> to
>> other places. The hypocrites will hide the facts to conceal their crime.
>>
>> Sie zerstören die Ergebnisse der Bemühungen der guten Mitwirkenden. Sie
>> löschen ihre Leistungen und machen sie aussehen wie Ihre. Sie entspannen
>> die
>> Regeln innerhalb der Gruppe und wenden sie auf die gewöhnlichen
>> Mitwirkenden
>> streng an. Ihr seid Heuchler. Dies ist der Ort, um Verbrechen alibi. Wir
>> werden Sie nicht als Vertreter von Japan genehmigen. Sie haben nicht das
>> Recht, Japan zu verwalten. Sie zerstören Änderungen, ohne etwas zu
>> argumentieren. Niemand äußert eine klare Meinung. Niemand übernimmt
>> Verantwortung. Du bist egoistisch und ungerecht. Sie stören neue
>> Mitwirkende, um Ihr Monopol zu schützen. Wir werden Ihr Verbrechen nicht
>> vergessen.
>>
>> Für die Mitarbeiter des guten Willens. Hör auf damit zu helfen, bis die
>> Heuchler aus Japan verschwinden. Unsere Bemühungen sind ausgelöscht.
>> Unsere
>> Beiträge sind gestohlen. Wegen der Schikanierung der Heuchler ist die
>> Zahl
>> der japanischen OSM-Mitwirkenden nicht gestiegen. Darüber hinaus
>> speichern
>> Sie diese E-Mail und zeigen es an anderen Orten. Die Heuchler werden die
>> Tatsachen verbergen, um ihr Verbrechen zu verbergen.
>>
>> Вы разрушаете результаты усилий хороших авторов. Вы стереть свои
>> достижения
>> и сделать их похожими на твои. Вы расслабляетесь правила внутри группы и
>> применить их к обычным вкладчиков строго. Вы лицемеры. Это место, чтобы
>> сделать преступления алиби. Мы не будем утверждать вас, как представители
>> Японии. Вы не имеете права на управление Японии. Вы уничтожаете
>> изменения,
>> не споря ничего. Никто не выражает четкого мнения. Никто не берет на себя
>> ответственность. Вы эгоистичны и несправедливы. Вы мешать новых
>> вкладчиков,
>> чтобы
>>  защитить свою монополию. Мы не будем забывать о вашем преступлении.
>>
>> Деловой репутации участников. Прекратить вклад, пока лицемеры не исчезнут
>> из
>> Японии. Наши усилия гаснут. Наши вклады украдены. Из-за преследования
>> лицемерами, число японских OSM участников не увеличилось. Кроме того,
>> сохраните это письмо и раскрыть его в других местах. Лицемеры будут
>> скрывать
>> факты, чтобы скрыть свое преступление.
>>
>> ___
>> Talk-ja mailing list
>> Talk-ja@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ja
>>
>
___
Talk-ja mailing list
Talk-ja@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ja

Re: [OSM-ja] (無題)

こんにちは。日本語がおわかりのようなので日本語で。

ご自分が編集された内容が戻された(reverted)ということでしょうか。
私自身はrevertには関係しておりませんが
具体的にどの編集のことか示してもらえると
議論ができるのではないかと思います。

東

2017-02-17 22:38 GMT+09:00, radcliff0...@yahoo.co.jp :
> あなたは良い貢献者の努力の結果を破壊します。 あなたはその成果を消して、あなたのように見せます。
> あなたはグループ内のルールを緩和し、通常のコントリビュータに厳しく適用します。 あなたは偽善者です。 これは犯罪アリバイを作る場所です。
> 私たちはあなたを日本の代表者として承認しません。 あなたは日本を管理する権利がありません。 あなたは何も言わずに編集内容を破棄します。
> 誰も明確な意見を表明しません。 誰も責任を負いません。 あなたは利己的で不公平です。 あなたは独占権を守るために新しい貢献者に干渉します。
> あなたの犯罪を忘れることはありません。
> 善意の貢献者に。 日本から偽善者が消えるまで寄稿をやめてください。 私たちの努力は消滅します。 私たちの貢献は盗まれています。
> 偽善者の嫌がらせのために、日本のOSM寄稿者の数は増えていない。 さらに、このメールを保存して他の場所に公開します。
> 偽善者は事実を隠して犯罪を隠すでしょう。
>
> You destroy the results of the efforts of good contributors. You erase their
> achievements and make them look like yours. You relax the rules within the
> group and apply them to the ordinary contributors severely. You are
> hypocrites. This is the place to make crime alibi. We will not approve you
> as representatives of Japan. You do not have the right to manage Japan. You
> destroy edits without arguing anything. No one expresses a clear opinion. No
> one takes responsibility. You are selfish and unfair. You interfere with new
> contributors to protect your monopoly. We will not forget your crime.
>
> To goodwill contributors. Stop contributing until the hypocrites disappear
> from Japan. Our efforts are extinguished. Our contributions are stolen.
> Because of the harassment of the hypocrites, the number of Japanese OSM
> contributors has not increased. In addition, save this mail and reveal it to
> other places. The hypocrites will hide the facts to conceal their crime.
>
> Sie zerstören die Ergebnisse der Bemühungen der guten Mitwirkenden. Sie
> löschen ihre Leistungen und machen sie aussehen wie Ihre. Sie entspannen die
> Regeln innerhalb der Gruppe und wenden sie auf die gewöhnlichen Mitwirkenden
> streng an. Ihr seid Heuchler. Dies ist der Ort, um Verbrechen alibi. Wir
> werden Sie nicht als Vertreter von Japan genehmigen. Sie haben nicht das
> Recht, Japan zu verwalten. Sie zerstören Änderungen, ohne etwas zu
> argumentieren. Niemand äußert eine klare Meinung. Niemand übernimmt
> Verantwortung. Du bist egoistisch und ungerecht. Sie stören neue
> Mitwirkende, um Ihr Monopol zu schützen. Wir werden Ihr Verbrechen nicht
> vergessen.
>
> Für die Mitarbeiter des guten Willens. Hör auf damit zu helfen, bis die
> Heuchler aus Japan verschwinden. Unsere Bemühungen sind ausgelöscht. Unsere
> Beiträge sind gestohlen. Wegen der Schikanierung der Heuchler ist die Zahl
> der japanischen OSM-Mitwirkenden nicht gestiegen. Darüber hinaus speichern
> Sie diese E-Mail und zeigen es an anderen Orten. Die Heuchler werden die
> Tatsachen verbergen, um ihr Verbrechen zu verbergen.
>
> Вы разрушаете результаты усилий хороших авторов. Вы стереть свои достижения
> и сделать их похожими на твои. Вы расслабляетесь правила внутри группы и
> применить их к обычным вкладчиков строго. Вы лицемеры. Это место, чтобы
> сделать преступления алиби. Мы не будем утверждать вас, как представители
> Японии. Вы не имеете права на управление Японии. Вы уничтожаете изменения,
> не споря ничего. Никто не выражает четкого мнения. Никто не берет на себя
> ответственность. Вы эгоистичны и несправедливы. Вы мешать новых вкладчиков,
> чтобы
>  защитить свою монополию. Мы не будем забывать о вашем преступлении.
>
> Деловой репутации участников. Прекратить вклад, пока лицемеры не исчезнут из
> Японии. Наши усилия гаснут. Наши вклады украдены. Из-за преследования
> лицемерами, число японских OSM участников не увеличилось. Кроме того,
> сохраните это письмо и раскрыть его в других местах. Лицемеры будут скрывать
> факты, чтобы скрыть свое преступление.
>
> ___
> Talk-ja mailing list
> Talk-ja@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ja
>
___
Talk-ja mailing list
Talk-ja@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ja

Re: [talk-au] A possible CAPAD 2016 import?

2017-02-17 Thread cleary

It's good to get access to that additional data and will improve the
map.

I would prefer incremental additions, that is one-by-one, after checking
what is already on the map.

My major concern with any mass import is the effect on existing data. In
particular where a new way is overlaid on an existing way, making
editing more difficult.  On parts of the NSW/VIC border, there are ten
relations (two of which are protected areas) attached to a single way.
It is manageable to alter relations if needed etc. but it is difficult
if we have ten separate ways overlaid one on top of the other.  For this
reason I would prefer to see new areas added where appropriate, but
adding new relations to existing ways where they exist. 

I have added some protected areas in NSW and SA using the approved
government data sources. If there were any discrepancies, I would be
inclined to prefer the state government sources although hopefully there
will not be any significant discrepancies.

While I can see that CAPAD has at least one NSW private area that is not
yet in OSM, I think there are shared boundaries with existing areas. 

CAPAD may also have errors or omissions. For example, I had mapped
Calperum Station in South Australia which is a non-government protected
area but I could not see it in CAPAD map (although it may well be in the
2016 edition when it becomes available).

Congrats on getting permission to sue this  additional data.

On Fri, Feb 17, 2017, at 09:04 PM, Andrew Davidson wrote:
> The good folks at DoEE have been more helpful and have given us 
> permission to use future releases of CAPAD under the same terms. Given 
> that the next release of CAPAD is due out in a number of weeks it raises 
> the question should we wait and then do an import?
> 
> Assuming that the community thinks this is a good idea the other big 
> question is what to do with the existing boundaries. Having a look at 
> the data it appears that the data we have permission to use is:
> 
> 1. NSW from NSW LPI (but these are only the areas managed by the NSW
> NPWS)
> 
> 2. Tas from CAPAD 2014
> 
> 3. SA from DEWNR
> 
> All of the other data is from unknown sources or sources we don't have 
> permission to use (or at least I can't find it on the wiki).
> 
> So do we:
> 
> 1. Scrub them off and start again,
> 2. Scrub off the other tags and leave them if they have a landcover tag,
> or
> 3. Try and reuse them with the replace geometry tool?
> 
> Other ideas?
> 
> ___
> 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: [OSM-ja] Missing points of OSM

2017-02-17 Thread insidekiwi555

ikiyaです。

河原さん、こんにちは。
>他の利用可能とされたリソースからのデータインポートが行われるようになったからです。　多くのインポート元はデータが古く、・・・
>インポート元となった航空写真の解像度が足りなかったのか、現地取材せずに写真を判図したのか・・・

おっしゃる通り、がっかりします。
私も昔、Yahoo!アルプスの道路データがインポートされた時、自分でGPSログからライン取りをこだわって書いたあまたの県道が見事に置き換わりました。
当時、私のGPSトレースのほうが精度は上でした。（相変わらず、カリカリ直しています。）
最近は、ルール（既存データを無視したり）を外れたインポート、編集についてはリバートという方法も選べるようになりましたが、
それでも、足しげくマッピングした地域が書き換わると気持ちが良いものではありません。

OSMは誰でもが自由に書ける、使える地図データと言われます。
最近では「地図データの前に人ありきでしょ。」と聞きます。私は同感です。

>誤りを指摘すると→プロのマッパー/編集チームがその指摘内容を検証し→資料に当たる・現地調査し→
>地図の変更案を提示して意見を求め→異論が出なくなれば最終的にマスターファイルに反映する

正直、よい（あこがれる）フローだと思います。
市民レベルから誰でもが自由に書けるを掲げて歩んできたOSMですが、
制限のステップを設けることについてどう思われますか？
このフローをボランタリなコミュニティーの中で構築するには知恵とコミュニティーの同意が必要と思っています。
私はまだ自由に書けるOSMを選びたいですが、ローカル重視で地図の誤り検証や意見調整する
Regional Leader地域リーダーやRegionaｌ Ambassadorといった仕組みは不可欠と考えます。
ボランタリーなメンバーでどう作るか考えるのも楽しいかもしれません。

以上、まとまりないですが雑感です。




- Original Message -
>From: 河原太郎 
>To: OpenStreetMap Japanese talk  
>Date: 2017/2/18, Sat 07:20
>Subject: [OSM-ja] Missing points of OSM
> 
>河原です。お久しぶりです。
>
>
>私は、以前はOSMのマッパーだったこともありますが、今は興味を失っていまして、活動していません。
>
>ただ、現在のOSM組織の活動内容が偽善的だとは思っていません。 
>OSMを利用するのも編集するのも止めたのには、別の理由があります。それは、他の利用可能とされたリソースからのデータインポートが行われるようになったからです。　
>多くのインポート元はデータが古く、私が住んでいる地域のOSM地図は、まるで古地図をみているかのうような現状とは乖離した状態となっており、さすがに利用する気は起きません。ちょっといくつか追加編集すれば済むようなレベルではないのです。
>
>また、インポート元となった航空写真の解像度が足りなかったのか、現地取材せずに写真を判図したのか、神社の境内へ向かう通り抜けのできない階段が、反対側へ抜けられる道路として描かれていたり、実際にはフェンスがあって通行できない隣接した道路がフェンスなどなく通行できるかのように描かれていたり、自宅周辺半径1km以内だけでみても、両手で数え切れないぐらいの誤りがインポートされていて、それが全体に広がっているのかと思うとやる気を失いました。
>
>
>現在のOSMで欠けている(他の地図サイトと異なっている)のは、レビューシステムの欠落ではないかと思います。どの地図サイトなのかは、書くと宣伝行為になりそうでこのMLの趣旨に反すると思うので、敢えて伏せますが、誤りを指摘すると→プロのマッパー/編集チームがその指摘内容を検証し→資料に当たる・現地調査し→地図の変更案を提示して意見を求め→異論が出なくなれば最終的にマスターファイルに反映する、というレビューシステムが構築されており、個々の誤り指摘に対して、その作業の進捗状況が分かるようになっています。OSMでは、誰もが勝手にマスターファイルを直接に更新しているため、それが誤りであっても即座に反映されてしまい、地図を信じた利用者が現地で通行止めを喰らってこん
な地図使えねぇという事態になっています。
>
>
>私がOSMを利用するのを止めていても、talk-ja に継続して購読しているのは、こうしたシステムの改革がそのうち行われるだろうと期待しているからです。
>
>
>千葉県千葉市在住
>
>河原太郎
>
>
>
>___
>Talk-ja mailing list
>Talk-ja@openstreetmap.org
>https://lists.openstreetmap.org/listinfo/talk-ja
>
>
>___
Talk-ja mailing list
Talk-ja@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ja

Re: [Talk-cz] nezobrazuje se mapka umístění rozcestníku

2017-02-17 Thread Marián Kyral


Dne 31.1.2017 v 15:10 Michal Grézl napsal(a):

je to strasne popularni:) tak spotrebujeme free limit.
Kdyby nekdo vedel o necem podobnem funkcnim bez limitu, predelam to.
.


Nevím sice jak to mají wikimapy [1] s limity, ale narazil jsem na 
zajímavou vlastnost


It can provide static maps with a given size and scaling, e.g. 
https://maps.wikimedia.org/img/osm-intl,6,44.8247,4.9981,1000x600.png


A funguje to moc pěkně. Akorát tam nebudeš mít ten bod, ale to by 
teoreticky šlo dodělat přes javascript. Ale možná to to api umí. 
Podmínky pro použití jsou tady: [2]



[1] https://www.mediawiki.org/wiki/Maps
[2] https://wikimediafoundation.org/wiki/Maps_Terms_of_Use

Marián


2017-01-31 14:02 GMT+01:00 Marián Kyral :

Když si na té mapce kliknu pravým tlačítkem a vyberu "zobrazit obrázek", tak
se mi objeví následující text:

You have exceeded the number of monthly transactions included with your
current plan. If you need additional transactions, please consider upgrading
to a plan that offers additional transactions. If you would like to talk to
an Account Manager about Enterprise Edition licensing options, please
contact sa...@mapquest.com.

Takže se dá očekávat, že zítra to zase bude fungovat - začne nový měsíc :-D

Marián

-- Původní e-mail --
Od: Tom Ka 
Komu: OpenStreetMap Czech Republic 
Datum: 31. 1. 2017 8:23:20
Předmět: Re: [Talk-cz] nezobrazuje se mapka umístění rozcestníku

Ahoj, tohle neni OsmHiCheck ale API k PhotoDB a je to na walleyho...

Bye

Dne 30. ledna 2017 15:15 Zdeněk Pražák  napsal(a):

na OSMhicheck se nezobrazuje mapka s umístěním rozcestníku - viz např
http://api.openstreetmap.cz/table/id/3436

Pražák

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


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


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






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

Re: [Talk-it] Direzione relazioni route=*

2017-02-17 Thread mircozorzo

Ciao, tempo fa ho scritto allo sviluppatore riferendo un problema simile e mi
rispose che al momento la direzione del profilo altimetrico è "a caso".

Ciao, Mirco



--
View this message in context: 
http://gis.19327.n8.nabble.com/Direzione-relazioni-route-tp5891154p5891544.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-cz] chyba zabezpečeného spojení na api.openstreetmap.cz

2017-02-17 Thread Marián Kyral


Dne 17.2.2017 v 18:54 Zdeněk Pražák napsal(a):

chtel jsem se podívat na frontu rozcestníků označených k přesunu

objevuje se mi však hláška:

Chyba zabezpečeného spojení

Při spojení s api.openstreetmap.cz nastala chyba. Při komunikaci 
protokolem SSL byl obdržen záznam přesahující maximální povolenou 
délku. Kód chyby: SSL_ERROR_RX_RECORD_TOO_LONG


Požadovanou stránku nelze zobrazit, protože nelze ověřit 
autenticitu přijatých dat.
Kontaktujte prosím vlastníky webového serveru a informujte je o 
tomto problému.


Zjistit více…



Ahoj,
Michal něco instaloval a nechtěně to rozbil.

Marián


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

semanárioOSM Nº 343 07/02/2017-13/02/2017

Bom dia,

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

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

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º 343 07/02/2017-13/02/2017

Bom dia,

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

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

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

[talk-ph] Fwd: [OSM-talk] weeklyOSM #343 07/02/2017-13/02/2017

2017-02-17 Thread Eugene Alvin Villar

-- Forwarded message --
From: weeklyteam 
Date: Sat, Feb 18, 2017 at 2:08 AM
Subject: [OSM-talk] weeklyOSM #343 07/02/2017-13/02/2017
To: t...@openstreetmap.org

The weekly round-up of OSM news, issue # 343,
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/8745/

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
t...@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
___
talk-ph mailing list
talk-ph@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ph

semanarioOSM Nº 343 07/02/2017-13/02/2017

Hola, el semanario Nº 343, 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/8745/

¡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º 343 07/02/2017-13/02/2017

Hola, el semanario Nº 343, 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/8745/

¡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º 343 07/02/2017-13/02/2017

Hola, el semanario Nº 343, 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/8745/

¡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-latam mailing list
talk-latam@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-latam

semanarioOSM Nº 343 07/02/2017-13/02/2017

Hola, el semanario Nº 343, 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/8745/

¡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

[OSM-talk-ie] weeklyOSM #343 07/02/2017-13/02/2017

The weekly round-up of OSM news, issue # 343,
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/8745/

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-ie mailing list
Talk-ie@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ie

[Talk-ca] weeklyOSM #343 07/02/2017-13/02/2017

The weekly round-up of OSM news, issue # 343,
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/8745/

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

[Talk-in] weeklyOSM #343 07/02/2017-13/02/2017

The weekly round-up of OSM news, issue # 343,
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/8745/

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-GB] weeklyOSM #343 07/02/2017-13/02/2017

The weekly round-up of OSM news, issue # 343,
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/8745/

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

[OSM-talk] weeklyOSM #343 07/02/2017-13/02/2017

The weekly round-up of OSM news, issue # 343,
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/8745/

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 #343 07/02/2017-13/02/2017

The weekly round-up of OSM news, issue # 343,
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/8745/

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

Re: [OSM-talk-be] heiligenbeelden

2017-02-17 Thread Ruben

NB: In het Nederlands is 't "Jezus", met een Z.

Groetjes
Ruben

On vrijdag 17 februari 2017 19:03 Guy Vanvuchelen wrote:
> Bedankt Marc, In de toekomst zal ik ze zo mappen. 
> 
> Guy Vanvuchelen
> 
> -Oorspronkelijk bericht-
> Van: Marc Gemis [mailto:marc.ge...@gmail.com] 
> Verzonden: vrijdag 17 februari 2017 18:31
> Aan: OpenStreetMap Belgium
> Onderwerp: Re: [OSM-talk-be] heiligenbeelden
> 
> voor mij zijn die beelden sowieso
> 
> tourism=artwork
> artwork_type=statue
> name=Jesus Christus
> subject:wikidata=Q302  (voor bv. Jesus)
> 
> k weet niet zeker of dit wel plekken zijn waar men heen gaat om te bidden 
> (het geloof te belijden) zoals je verwacht bij een amenity=place_of_worship
> 
> m
> 
> 2017-02-17 16:38 GMT+01:00 Guy Vanvuchelen :
> > Kan iemand me zeggen hoe ik best een heiligenbeeld langs de weg map. 
> > Het is geen kapelletje, geen schrijn, maar toch iets in die aard. In 
> > mijn drang om zoveel mogelijk kapelletjes, kruisen, enz te mappen 
> > omdat die op veel toeristische kaarten voorkomen stoot ik op 
> > heiligenbeelden, soms op een altaar, soms gewoon op een sokkel.
> >
> > Ik heb al de gebruikelijke: amenity =  place_of _worship, denomination 
> > = roman_catholic, religion = Christian gebruikt samen met tourism : 
> > artwork maar is dat wel juist. In vele gevallen is het beeld immers 
> > geen kunst. We kunnen ook place_of_worshop = shrine kunnen gebruiken. 
> > Als je in Google afbeeldingen voor ‘shrine’ kiest zie je wel een heel 
> > andere selectie dan voor het Nederlandse ‘schrijn’. In het Nederlands 
> > gaat het eerder over een soort koffer terwijl de Engelse versie voor alle 
> > soorten heiligdom staat.
> >
> > Voor het beroemde beeld in Rio de Janeiro staat gewoon ‘name’ ingevuld.
> >
> > Guy Vanvuchelen

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

Re: [OSM-talk-ie] Typos in Townland names

2017-02-17 Thread Brian Hollinshead

Re Exclave
try Kiltiernan in County Dublin in townlands.ie

and Kinnitty as CP, both enclaves belong to eslewhere external CPs

On 17 February 2017 at 16:03, Rory McCann  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 17/02/17 16:38, Brian Tuffy wrote:
> > Just to be clear, if it is "X and Y" you should treat it as "X and
> > Y", as it says on the wiki page. If it is "X or Y" then it should
> > be treated as "X" or "Y" in OSM but It looks like Logainm treats "X
> > or Y" as "X or Y" and so two townland names have one ref tag. The
> > thing is your script will look for "Lisnakirka or Milebush" but in
> > OSM it is name=Milebush and alt_name= Lis...
> > https://www.logainm.ie/35706.aspx
>
> OK, that sounds a little more complicated. I think I'll leave it alone
> then. We can always just find townlands with an "and" and without a
> logainm:ref and manually add them. Sometimes manually adding it is
> quicker than programming complicated rules.
>
> > It confusses me why it is Lower or Northern (North is up right!! :)
> > ) but I think it might be lower in elevation possibly? I doubt it.
> > Upper Bavaria is the south because it rises to the alps.  More
> > interestingly, up might be to the south? you go up towards Rome in
> > Irish?? More More interestingly, I hear that Irish is one of those
> > languages that has an in-built sense of direction, you wouldn't say
> > move over to the left, you would say move east or something
> > like that. I am not sure about it. Anyway, back to the map.
>
> Usually "Upper" is upstream, and "lower" is downstream, near the mouth
> of the river. e.g. the Upper Rhine Plane is in south Germany, because
> that's near where the Rhine starts. So when you see "Upper X" that's
> usually more "upsteam" or something.
>
> > I agree with you that it should be mapped as an exclave. I have not
> > seen any like that so that's why I suggested to have two
> > townlands.
>
> I don't know if I've seen it with townlands. It's more common with
> Civil Parishes.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJYpx69AAoJEOrWdmeZivv2a/EIAKwvRsri1/hodVTDoy936q8w
> nrJzEdDGpfTHU/7MyyNRfcqrtAfp41x+qgr13jTmGC3yGMraM9waj9UZLdj9h7WG
> u0zLX1Lb6DX3FfSsKkXI47N3/bTCqQ5ZqdzBmAfJzjypd9fSPkTwJDBNdoiBBgCx
> UepxqQqAXgAJ+3F957dT5EcXzoP1p4pVrPTI6HI6knXNnw1F9XeICXIWQPZva7+D
> p6lDedvEQHA3Iwk7s2i1UqAXvf/TDd5ZCnJ+IO9Qm92VFmJ/N2k4umWsnQbLdKJy
> WG3R3QqiccE4IajpcJbGjgKafXuuSpLQn/7hHi6pP0j+KaE7FTp5aAh2na0FZEQ=
> =GEzN
> -END PGP SIGNATURE-
>
> ___
> Talk-ie mailing list
> Talk-ie@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ie
>
___
Talk-ie mailing list
Talk-ie@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ie

Re: [OSM-talk-be] heiligenbeelden

2017-02-17 Thread Guy Vanvuchelen

Bedankt Marc, In de toekomst zal ik ze zo mappen. 

Guy Vanvuchelen

-Oorspronkelijk bericht-
Van: Marc Gemis [mailto:marc.ge...@gmail.com] 
Verzonden: vrijdag 17 februari 2017 18:31
Aan: OpenStreetMap Belgium
Onderwerp: Re: [OSM-talk-be] heiligenbeelden

voor mij zijn die beelden sowieso

tourism=artwork
artwork_type=statue
name=Jesus Christus
subject:wikidata=Q302  (voor bv. Jesus)

k weet niet zeker of dit wel plekken zijn waar men heen gaat om te bidden (het 
geloof te belijden) zoals je verwacht bij een amenity=place_of_worship

m

2017-02-17 16:38 GMT+01:00 Guy Vanvuchelen :
> Kan iemand me zeggen hoe ik best een heiligenbeeld langs de weg map. 
> Het is geen kapelletje, geen schrijn, maar toch iets in die aard. In 
> mijn drang om zoveel mogelijk kapelletjes, kruisen, enz te mappen 
> omdat die op veel toeristische kaarten voorkomen stoot ik op 
> heiligenbeelden, soms op een altaar, soms gewoon op een sokkel.
>
> Ik heb al de gebruikelijke: amenity =  place_of _worship, denomination 
> = roman_catholic, religion = Christian gebruikt samen met tourism : 
> artwork maar is dat wel juist. In vele gevallen is het beeld immers 
> geen kunst. We kunnen ook place_of_worshop = shrine kunnen gebruiken. 
> Als je in Google afbeeldingen voor ‘shrine’ kiest zie je wel een heel 
> andere selectie dan voor het Nederlandse ‘schrijn’. In het Nederlands 
> gaat het eerder over een soort koffer terwijl de Engelse versie voor alle 
> soorten heiligdom staat.
>
> Voor het beroemde beeld in Rio de Janeiro staat gewoon ‘name’ ingevuld.
>
>
>
> Guy Vanvuchelen
>
>
>
>
> ___
> 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


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

[Talk-cz] chyba zabezpečeného spojení na api.openstreetmap.cz

2017-02-17 Thread Zdeněk Pražák

chtel jsem se podívat na frontu rozcestníků označených k přesunu

objevuje se mi však hláška:

Chyba zabezpečeného spojení

Při spojení s api.openstreetmap.cz nastala chyba. Při komunikaci protokolem 
SSL byl obdržen záznam přesahující maximální povolenou délku. Kód chyby: SSL
_ERROR_RX_RECORD_TOO_LONG

    Požadovanou stránku nelze zobrazit, protože nelze ověřit autenticitu 
přijatých dat.
    Kontaktujte prosím vlastníky webového serveru a informujte je o tomto 
problému.

Zjistit více…

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

Re: [OSM-talk-be] heiligenbeelden

2017-02-17 Thread Marc Gemis

voor mij zijn die beelden sowieso

tourism=artwork
artwork_type=statue
name=Jesus Christus
subject:wikidata=Q302  (voor bv. Jesus)

k weet niet zeker of dit wel plekken zijn waar men heen gaat om te
bidden (het geloof te belijden) zoals je verwacht bij een
amenity=place_of_worship

m

2017-02-17 16:38 GMT+01:00 Guy Vanvuchelen :
> Kan iemand me zeggen hoe ik best een heiligenbeeld langs de weg map. Het is
> geen kapelletje, geen schrijn, maar toch iets in die aard. In mijn drang om
> zoveel mogelijk kapelletjes, kruisen, enz te mappen omdat die op veel
> toeristische kaarten voorkomen stoot ik op heiligenbeelden, soms op een
> altaar, soms gewoon op een sokkel.
>
> Ik heb al de gebruikelijke: amenity =  place_of _worship, denomination =
> roman_catholic, religion = Christian gebruikt samen met tourism : artwork
> maar is dat wel juist. In vele gevallen is het beeld immers geen kunst. We
> kunnen ook place_of_worshop = shrine kunnen gebruiken. Als je in Google
> afbeeldingen voor ‘shrine’ kiest zie je wel een heel andere selectie dan
> voor het Nederlandse ‘schrijn’. In het Nederlands gaat het eerder over een
> soort koffer terwijl de Engelse versie voor alle soorten heiligdom staat.
>
> Voor het beroemde beeld in Rio de Janeiro staat gewoon ‘name’ ingevuld.
>
>
>
> Guy Vanvuchelen
>
>
>
>
> ___
> 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] KBO

2017-02-17 Thread joost schouppe

Apart from the license, there is also a quality issue. From what I have
seen iny own use of the data, it could be a help, but not much more than
that.
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-ie] Typos in Townland names

2017-02-17 Thread Brian Tuffy

On Fri, Feb 17, 2017 at 3:34 PM, Rory McCann  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Some great, detailed advice here! 
>
> Townlands.ie shows how many objects have logainm:refs:
> https://www.townlands.ie/progress/#logainm It's currentlya botu 73% of
> townlands.
>
>
> On 17/02/17 14:51, Brian Tuffy wrote:
> > Alternative names or 'typos that are not typos': (A) Many townlands
> > have two official names on the map source, "Ballindoo or
> > Doocastle". Both are valid, We should try to find out which one is
> > commonly-used/dominant and use that one in the name= tag and the
> > other in the alt_name= tag.
>
> The logainm match up will only look at the name:en tag (or failing
> that the name) tag. It doesn't look at the alt_name (etc) tags.
> Perhaps it should. likewise it should split "X and Y" into "X" and "Y"
> and look at them.
>


Just to be clear, if it is "X and Y" you should treat it as "X and Y", as
it says on the wiki page.
If it is "X or Y" then it should be treated as "X" or "Y" in OSM but It
looks like Logainm treats "X or Y" as "X or Y" and so two townland names
have one ref tag. The thing is your script will look for "Lisnakirka or
Milebush" but in OSM it is name=Milebush and alt_name= Lis...
https://www.logainm.ie/35706.aspx



>
> > (B) A name structure variation is valid, "East X" = "X East". We
> > don't have to add every variation but if you come across them, you
> > can add them. The idea is that if someone searches for a townland,
> > we want them to find it no matter what variation they use. The
> > example above is trivial for search but something like Inishmore
> > Vs. Inish More. Also consider, Upper/Lower, Island, More/Beg
> > Oughter/Eighter etc.
>
> The logainm script is aware of North/South/Upper/etc and will try to
> match based on that. It is able to tell that "X Upper" in Logainm is
> the same as "Upper X" in OSM (and vice versa etc).
>
> A few of these will be added to the logainm match up. I wasn't aware
> of them:


 My Irish is unfortunately terrible but
Oughter (butchered irish) = uachtar (Irish) = Upper or Southern (English)
Eighter = Íochtar = Lower or Northern

It confusses me why it is Lower or Northern (North is up right!! :) ) but I
think it might be lower in elevation possibly? I doubt it. Upper Bavaria is
the south because it rises to the alps.  More interestingly, up might be to
the south? you go up towards Rome in Irish?? More More interestingly, I
hear that Irish is one of those languages that has an in-built sense of
direction, you wouldn't say move over to the left, you would say move
east or something like that. I am not sure about it. Anyway, back to
the map.



>

> (C) Missing spaces can be valid names. e.g. Inishdeashmore =
> > Inishdeash-more = Inishdeash More
> >
> > (E) X Deme(ns)e and X Deme(sn)e. I suggest sticking to Deme(sn)e as
> > this is what is on the map source. (H) Apostrophes in names. I'm
> > getting a bit too in-depth here but I
> might
> > as well mention it. The old maps do not contain apostrophes in
> > names. "Georges Island", "Abbots Island". Some name tags are now
> > "George's
> Island"
> > etc. I suggest to keep "Georges Island" as an alt_name in this
> > case.
>
>
> > (G) Some townlands are named "Part of X" or "X (part of)". This
> > means it is a separate part of a nearby townland. Usually, you will
> > find an "X" townland nearby, that was split. I suggest we write the
> > name of these as "X (part of)".
>
> Are you sure about this? That would make 2 townlands, called "X" and
> "X (part of)". I thought if the map has a "X part of" displayed that
> it meant that little part was an exclave of the larger X townland, and
> I've been mapping them as such.
>

I agree with you that it should be mapped as an exclave. I have not seen
any like that so that's why I suggested to have two townlands.
If everyone is happy with it, I will also map the "part of" exclave with
the "X" townland. I will also amend my comments above when I put it up in a
wiki.

Thanks for the feedback!




> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJYpwntAAoJEOrWdmeZivv2FxoH/1GHOBmoLUMtsKQanmc9OhJC
> tYA1R/nLYXxenl7N3CXWxpFfpRrADb+G7SRZ6FC3YwABNOFudb3/4/QUh9T2zY00
> NICTF7gmp8k378zVr2RxreOxXb0Qz4kXCfg+4H8NzAuxgsfEihliegGmRYm+/A6e
> 2glvvD+8GAoQ9zZvJdqXkdtZvB5BtV213jiTDYRoXWVX9r8TlqI9OPULL1FQtii4
> LfP1s4oWKF5ma3Dip3VgyUvOCKWW/JaD5EGOZtT4uW8TnBKxEtWS/ahvoKInjyj6
> gSWGJOW1tVorHur8B/HXK/poAbPy91M2ttS5d2IhGQyr5nOe8l25Fhm+uaGvkJ8=
> =drU2
> -END PGP SIGNATURE-
>
> ___
> Talk-ie mailing list
> Talk-ie@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ie
>
___
Talk-ie mailing list
Talk-ie@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ie

[OSM-talk-be] heiligenbeelden

2017-02-17 Thread Guy Vanvuchelen

Kan iemand me zeggen hoe ik best een heiligenbeeld langs de weg map. Het is
geen kapelletje, geen schrijn, maar toch iets in die aard. In mijn drang om
zoveel mogelijk kapelletjes, kruisen, enz te mappen omdat die op veel
toeristische kaarten voorkomen stoot ik op heiligenbeelden, soms op een
altaar, soms gewoon op een sokkel.

Ik heb al de gebruikelijke: amenity =  place_of _worship, denomination =
roman_catholic, religion = Christian gebruikt samen met tourism : artwork
maar is dat wel juist. In vele gevallen is het beeld immers geen kunst. We
kunnen ook place_of_worshop = shrine kunnen gebruiken. Als je in Google
afbeeldingen voor 'shrine' kiest zie je wel een heel andere selectie dan
voor het Nederlandse 'schrijn'. In het Nederlands gaat het eerder over een
soort koffer terwijl de Engelse versie voor alle soorten heiligdom staat.

Voor het beroemde beeld in Rio de Janeiro staat gewoon 'name' ingevuld. 

 

Guy Vanvuchelen

 

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

Re: [OSM-talk-ie] Typos in Townland names

2017-02-17 Thread Rory McCann

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 16/02/17 20:38, Brian Tuffy wrote:
> I have a question about the logainm script, How can it handle a
> barony that crosses a county border? For example, Barony of Ross
> crosses the Galway-Mayo border as one relation. This relation has
> one logainm tag for Ross in Mayo (logainm:ref = 172) but there are
> separate loganim ref numbers for Ross in Galway (logainm:ref = 85)
> on the logainm website. Can we somehow add both ref numbers to the
> Barony relation? something like logainm:ref=172;85, or what do you
> suggest? It seems that the script assumes everything is nested
> inside counties but if baronies/civil parishes cross county
> borders, then they have two logainm ref numbers.
> 
> https://www.logainm.ie/en/85   Galway 
> https://www.logainm.ie/en/172 Mayo 
> https://www.openstreetmap.org/relation/4128697

I'll have to think about what exactly the code does in that case and
get back to you. As you can see it has only assigned on logainm code.

In my mind logainm:ref=172;85 is the right answer, since this one OSM
object represents 2 objects in Logainm. You can also have one object
in Logainm which corresponds to 2 (or more) OSM objects.

The logainm import code will never change a logainm:ref value that's
there already. In accordance with long standing OSM convention, human
mapping is viewed as better than what the script does. If the logainm
script has done something wrong (like this case), then you can, and
should, correct OSM manually.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJYpw04AAoJEOrWdmeZivv2dDgH/Rn9w2Nn70duVvOD5oOXvzWb
2e/leRdDgjjCa2iB8rQ4XoFV74n4KubaM2uyilp4Ywkdzjpfai/udzieaijhuOlj
JQ9rb7nPnspHKCVnNRFABbds+AGpvvUoGWPgt27YgMZss3MokWN31EI+HE9NxHmV
I2RBFn7FfJ/Ime5C/tZOKKS2bLgtJ34zCIMNgvI8drfDDl+YEUsIfZDVRw+vDAan
mIvuVmuNHj5oDmDsCrYff7cyA2dRcHhePOE8y5rasIkN6TfpEsUCN6NxKVDWE6TA
RqhzuourVuDiV9pwqCejy/qtsmrwHdg6MZYMc8RNEnAsSXT5MMy5efovVwbRQ/o=
=L2XJ
-END PGP SIGNATURE-

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

Re: [Talk-it] MAPPA IMMAGINE DI SFONDO

2017-02-16 23:19 GMT+01:00 Francesco Pelullo :

> 2. Usa fonti per le quali abbiamo licenza compatibile o autorizzazione (no
> GOOGLE MAPS, GOOGLE STREET VIEW, SFONDI o tracce prese "non dico come, non
> dico dove")



giusto, le url di Google non funzionano in iD e in JOSM, appositamente, per
evitare problemi.

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

Re: [OSM-talk-be] Talk-be Digest, Vol 110, Issue 25

2017-02-17 Thread Marc Gemis

On Fri, Feb 17, 2017 at 2:22 PM, Philippe Casteleyn <
philippecastel...@hotmail.com> wrote:

> Als Vlaming hebben wij altijd geleerd ons in het buitenland als
> ambassadeurs te gedragen.  Een toerist die in Brussel neerstrijkt en  het
> lokale voetvolk het werk moeilijk maakt, nee daarvoor schuw ik mijn woorden
> niet.
>
>
OSM is een open project, iedereen kan mappen waar ie dat wil. Anders kan je
ook zeggen dat een Mechelaar die in Rumst komt mappen een toerist is die
daar niks te zoeken heeft :-)

Verdraagzaamheid is een schone deugd, maar ik geef toe dat bij iedereen het
potje wel eens overkookt, ook bij mij. 't is dan een kwestie van toch te
proberen vriendelijk te blijven.

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

[Talk-TW] 台東荒野想找人分享開放街圖

2017-02-17 Thread pm5

Hi all,

3/19 或 3/26 我時間可以，我應該會去。不過先把訊息轉過來看看有沒有人也有興趣的。

Best,
pm5

-- Forwarded message -
From: Jenn Lin 
Date: Fri, Feb 17, 2017 at 12:50 AM
Subject: Re: 關於飲水地圖／開放街圖介紹一事 from 環境資訊協會瑞賓
To: being 
Cc: 吳柏旻 , 吳柏旻 


感謝秘書長瑞賓引介！

柏旻您好,

台東三月的兩天（3/19,3/26)綠活圖工作坊，其中的案例分享講座需求誠如瑞賓所提，
因此希望能有機會聽聽飲水地圖計畫的行動理念、使用OSM作為行動工具的想法與操作方式，以及你們希望這樣的地圖如何讓更多人參與進來。
因為我覺得在台東的荒野綠活圖推動往往在完成一張手繪地圖之後，便無後續的行動或開放參與，有點可惜。

分享時間約2小時內，1小時半或1小時也都可以，只要事先提出，方便我規劃課程即可。
再看您哪一天有時間方便來東分享，以及，若有住宿上的疑慮，仍可再溝通，感謝！
可加我臉書（https://www.facebook.com/jfr.lin）或電話（0919160786)，方便即時聯繫，感謝～

慧珍（臺東荒野綠活圖組長）


being  於 2017年2月17日 上午8:58 寫道：

慧珍

我昨天有徵詢Watergo的社群，有一位伙伴吳柏旻有意願前往。他之前是本會資訊組的組長，是有深度參與的一位。但，他也還在安排中，但，因為大家可能都各自在忙，為了加快速度，便於聯絡，我就先同時寄送你們兩位，方便你們後續連繫。

---底下是我所理解的需求和簡要的背景，如有不足，再煩請慧珍直接補充，或柏旻可直接跟慧珍再確認

台東荒野保護協會想邀人去跟他們分享如何使用開放街圖, 以及應用, 推廣. 荒野持續在推動"綠生活地圖", 他們看到了主婦聯盟,
以及大家在參與的watergo, 都採用OSM, 很好奇, 也很有興趣想多了解及參與。邀請飲水地圖計劃的伙伴, 出席他們工作坊講座分享計劃及執行經驗。

日期：3/19及3/26兩日中選一天,
地點：荒野台東分會
課程：綠生活地圖工作坊，
時間：約2個小時（但，可以協調，因為，他們也沒足夠經驗，就暫訂2小時)
費用：有車馬費及講師費補貼, (住宿可能是他們成員家中之類的 )

聯絡人為
台東荒野分會
0919-160-786 林慧珍小姐
lin.huei...@gmail.com

-- 
台灣環境資訊協會 陳瑞賓

我的理想是為團體或個人提供一個人人都能實現自身理想的生活方式和環境的機會

為了財務能夠獨立自主，台灣環境資訊協會希望爭取2000名定期的捐款者，
詳情請見http://teia.tw/donate

捐款帳號：臺灣中小企業銀行萬華分行 銀行代碼:050
戶名：社團法人台灣環境資訊協會 帳號:06012249169

辦公室地址：116台北市文山區萬隆街38號(捷運萬隆站1號出口)
電話：886-2-29332233；傳真：886-2-29332059
~~
台灣環境資訊協會網站> http://teia.tw
環境資訊中心及電子報> http://e-info.org.tw
~~




-- 
東台灣研究會
執行長 林慧珍
089-347660
0919160786
臺東市豐榮路259號
___
Talk-TW mailing list
Talk-TW@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-tw

Re: [OSM-talk-ie] Typos in Townland names

2017-02-17 Thread Brian Tuffy

Today I hope to upload my list of typo changes for Mayo to OSM.
When Rory runs his Logainm script tomorrow, I hope that it will add more
logainm tags because of this, let's see. Most of the typos are just
alternative spellings, The list here are just the ones that I plan to
overwrite. There could be a valid local spelling of a name that I have
missed. I challenge you guys to check my "Typos" column for a valid
townland name spelling.
https://docs.google.com/spreadsheets/d/1wobpofwXzLdkPyB8mjMT1sDMQuZiO
gebR4S94yvbzU4/edit?usp=sharing

I manually checked the names to make sure I am not overwriting valid names.
I learned a lot about the structure of the names, false positive (i.e. name
mismatches that are not typos but valid alternative spellings or
alternative name structure)... and so I wanted to share those with
everyone. I hope this will help others who attempt to correct typos, and
help those working on automating the process in the future.

My assumptions:
(1) I assume that the GSGS3906 1:25k War Office map sheets, are the
original source of townland names and the spellings are valid names.

(2) There can be multiple valid names for one townland. Valid name(s) can
be from: the map source, a structure variation (e.g. X East, East X, Upper
X Island West More, etc.), a local/commonly-used name (e.g. Bellavarry is
commonly written as Ballyvary, both are valid and so should not be
overwritten),

(3) With the correct spelling of townland names, the Logainm script should
be able to automatically add logainm tags. A lack of logainm tags is an
indication that something is up with the name. After the typos are fixed,
any remaining townlands without tags can be added manually. Islands are not
included, yet.


Guidelines:
(A) Make double sure that the typo is a mistake and not a valid alternative
name as I outline below.
(B) Try to keep the names where possible by adding alt_name, loc_name or
old_name tags.
(C) Try to keep consistent naming schemes. For example, If there is an "X
More Island", then also try to keep "X Beg Island" and not "Xbeg Island",
Its not always possible though, I would not create a new name just to be
consistent.
(D) Its sometimes ok to keep invalid names, if they are common spelling
errors and there is proof that it is in use. For example, "Srahcorick" gets
a few search hits. "Srahacorick" is the correct spelling but I recommend
not adding the alt_name in this example. An example where I would add an
alt_name is "Bohea", official correct spelling is "Boheh". Local names
often come from spelling mistakes that become popular.
(E) The name= tag is the one that is usually displayed/dominant. I suggest
that the order of "importance" for this is local name > other names. If
someone knows a local or commonly used name of a place, they should use
loc_name=, but often they just replace the name= tag. (This is all
debatable, which name tags to use? alt_name is for townlands that have 2
official names. I also use alt_name for valid spelling variations. name:en
may also be used etc.)


How to identify Typos:
(1) Compare the list of townlands to the openOSI and other sources. Logainm
(derived from OSI), local authorities, etc.
(2) Visually identify them in your area,
http://maps.openstreetmap.ie/os_opendata.html
(3) Missing Logainm tags indicate a name mismatch.
http://umap.openstreetmap.fr/en/map/townlands-missing-
logainm-data_83833#11/53.9650/-9.2107


How to check that the "typo" is a mistake:
(1) Check if it is an alternative spelling or alternative name. (see below)
(2) Check the map source.
(3) It may be obvious why the typo occurred. Is the mis-typed letter hard
to read?, blocked?, or a common mistake? (See common mistakes). This is
only an indication but it helps.
(4) If the name on the map source does not match any in the relation (even
as alt_name), this indicates that it was misspelled when first copied or
possibly overwritten.
(4) To check if it was overwritten, check the relation history on OSM, if
the name did not change at all, it is likely that it was misspelled when
first copied.
(5) Do a web search for the name (be sure it is the correct townland), if
there are lots (> 50 maybe) of webpage posts with that spelling, no matter
how wrong you think it is, it is likely a valid name spelling. Be aware
that some websites just use OSM data so there will always be a few hits.


Alternative names or 'typos that are not typos':
(A) Many townlands have two official names on the map source, "Ballindoo or
Doocastle". Both are valid, We should try to find out which one is
commonly-used/dominant and use that one in the name= tag and the other in
the alt_name= tag.

(B) A name structure variation is valid, "East X" = "X East". We don't have
to add every variation but if you come across them, you can add them. The
idea is that if someone searches for a townland, we want them to find it no
matter what variation they use. The example above is trivial for search but
something like Inishmore Vs. Inish

あなたは良い貢献者の努力の結果を破壊します。 あなたはその成果を消して、あなたのように見せます。
あなたはグループ内のルールを緩和し、通常のコントリビュータに厳しく適用します。 あなたは偽善者です。 これは犯罪アリバイを作る場所です。
私たちはあなたを日本の代表者として承認しません。 あなたは日本を管理する権利がありません。 あなたは何も言わずに編集内容を破棄します。
誰も明確な意見を表明しません。 誰も責任を負いません。 あなたは利己的で不公平です。 あなたは独占権を守るために新しい貢献者に干渉します。
あなたの犯罪を忘れることはありません。
善意の貢献者に。 日本から偽善者が消えるまで寄稿をやめてください。 私たちの努力は消滅します。 私たちの貢献は盗まれています。
偽善者の嫌がらせのために、日本のOSM寄稿者の数は増えていない。 さらに、このメールを保存して他の場所に公開します。 偽善者は事実を隠して犯罪を隠すでしょう。

You destroy the results of the efforts of good contributors. You erase their
achievements and make them look like yours. You relax the rules within the
group and apply them to the ordinary contributors severely. You are hypocrites.
This is the place to make crime alibi. We will not approve you as
representatives of Japan. You do not have the right to manage Japan. You
destroy edits without arguing anything. No one expresses a clear opinion. No
one takes responsibility. You are selfish and unfair. You interfere with new
contributors to protect your monopoly. We will not forget your crime.

To goodwill contributors. Stop contributing until the hypocrites disappear from
Japan. Our efforts are extinguished. Our contributions are stolen. Because of
the harassment of the hypocrites, the number of Japanese OSM contributors has
not increased. In addition, save this mail and reveal it to other places. The
hypocrites will hide the facts to conceal their crime.

Sie zerstören die Ergebnisse der Bemühungen der guten Mitwirkenden. Sie löschen
ihre Leistungen und machen sie aussehen wie Ihre. Sie entspannen die Regeln
innerhalb der Gruppe und wenden sie auf die gewöhnlichen Mitwirkenden streng
an. Ihr seid Heuchler. Dies ist der Ort, um Verbrechen alibi. Wir werden Sie
nicht als Vertreter von Japan genehmigen. Sie haben nicht das Recht, Japan zu
verwalten. Sie zerstören Änderungen, ohne etwas zu argumentieren. Niemand
äußert eine klare Meinung. Niemand übernimmt Verantwortung. Du bist egoistisch
und ungerecht. Sie stören neue Mitwirkende, um Ihr Monopol zu schützen. Wir
werden Ihr Verbrechen nicht vergessen.

Für die Mitarbeiter des guten Willens. Hör auf damit zu helfen, bis die
Heuchler aus Japan verschwinden. Unsere Bemühungen sind ausgelöscht. Unsere
Beiträge sind gestohlen. Wegen der Schikanierung der Heuchler ist die Zahl der
japanischen OSM-Mitwirkenden nicht gestiegen. Darüber hinaus speichern Sie
diese E-Mail und zeigen es an anderen Orten. Die Heuchler werden die Tatsachen
verbergen, um ihr Verbrechen zu verbergen.

Вы разрушаете результаты усилий хороших авторов. Вы стереть свои достижения и
сделать их похожими на твои. Вы расслабляетесь правила внутри группы и
применить их к обычным вкладчиков строго. Вы лицемеры. Это место, чтобы сделать
преступления алиби. Мы не будем утверждать вас, как представители Японии. Вы не
имеете права на управление Японии. Вы уничтожаете изменения, не споря ничего.
Никто не выражает четкого мнения. Никто не берет на себя ответственность. Вы
эгоистичны и несправедливы. Вы мешать новых вкладчиков, чтобы
защитить свою монополию. Мы не будем забывать о вашем преступлении.

Деловой репутации участников. Прекратить вклад, пока лицемеры не исчезнут из
Японии. Наши усилия гаснут. Наши вклады украдены. Из-за преследования
лицемерами, число японских OSM участников не увеличилось. Кроме того, сохраните
это письмо и раскрыть его в других местах. Лицемеры будут скрывать факты, чтобы
скрыть свое преступление.

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

Re: [OSM-talk-be] Talk-be Digest, Vol 110, Issue 25

2017-02-17 Thread Philippe Casteleyn

Als Vlaming hebben wij altijd geleerd ons in het buitenland als ambassadeurs te 
gedragen.  Een toerist die in Brussel neerstrijkt en  het lokale voetvolk het 
werk moeilijk maakt, nee daarvoor schuw ik mijn woorden niet.

Ph Casteleyn
Dahliastraat 16
2800 Mechelen
animals.slippers.loaders
gsm 0486 516261
Ctrl+v

Van: talk-be-requ...@openstreetmap.org 
Verzonden: vrijdag 17 februari 2017 13:00
Aan: talk-be@openstreetmap.org
Onderwerp: Talk-be Digest, Vol 110, Issue 25

Send Talk-be mailing list submissions to
talk-be@openstreetmap.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.openstreetmap.org/listinfo/talk-be
Talk-be Info Page - 
OpenStreetMap
lists.openstreetmap.org
To see the collection of prior postings to the list, visit the Talk-be 
Archives. Using Talk-be: To post a message to all the list members, send email 
...

or, via email, send a message with subject or body 'help' to
talk-be-requ...@openstreetmap.org

You can reach the person managing the list at
talk-be-ow...@openstreetmap.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Talk-be digest..."

Today's Topics:

   1. Re: KBO (Glenn Plas)
   2. Re: Notes pollutie in Brussel (Glenn Plas)

--

Message: 1
Date: Fri, 17 Feb 2017 12:45:31 +0100
From: Glenn Plas 
To: OpenStreetMap Belgium 
Subject: Re: [OSM-talk-be] KBO
Message-ID: <58a6e25b.9010...@byte-consult.be>
Content-Type: text/plain; charset=utf-8

Nope, we can't.  The license is incompatible with OSM.   It's too
restrictive.
http://economie.fgov.be/nl/modules/publications/kbo/licence_open_data.jsp
Gebruiksvoorwaarden Open data - - 
Home
economie.fgov.be
Licentie Open Data: gebruiksvoorwaarden. Link. Conditions d'utilisation Open 
Data (DOC, 70 Kb) Terug

I investigated this about a half year ago.  They call it open data but
they impose restriction on the usage.  I downloaded it back then and
gave as intended use : "creating a webapp".  It's a bit silly because
you can keep it very generic but it's too limiting to be a real opendata
license.

They used to sell this DB for a small fee of about 70K euro's in the
past, probably still a relic of clinging on reselling data that in
essence is 'ours' to begin with.

See also the cookbook:
http://economie.fgov.be/nl/binaries/Cookbook%20KBO%20Open%20Data%201.0.0_nl_2_tcm325-246659.pdf
Cookbook KBO Open Data Versie 1.0 - 
economie.fgov.be
economie.fgov.be
Cookbook KBO Open Data - versie 1.0.0 3/14 INLEIDING Dit document is een 
technische beschrijving van de bestanden die onder de licentie KBO Open Data

I've considered using this data to augment up the GRB data on import,
but decided against it.

Glenn

On 16-02-17 10:37, Killian De Volder wrote:
> Does anyone know if we are allowed to use
> http://kbopub.economie.fgov.be/kbopub/zoeknummerform.html ?
>
> I would read some of the policies on their site, but all the links are broken.
>
> If nobody knows, I could send an email to the department to ask.
>
> Regards,
> Killian
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
Talk-be Info Page - 
OpenStreetMap
lists.openstreetmap.org
To see the collection of prior postings to the list, visit the Talk-be 
Archives. Using Talk-be: To post a message to all the list members, send email 
...

>

--

Message: 2
Date: Fri, 17 Feb 2017 12:52:16 +0100
From: Glenn Plas 
To: OpenStreetMap Belgium 
Subject: Re: [OSM-talk-be] Notes pollutie in Brussel
Message-ID: <58a6e3f0.6010...@byte-consult.be>
Content-Type: text/plain; charset=utf-8

Mr Casteleyn,

Dit is de 2de maal dat u iemand persoonlijk aanvalt, en 2 maal dezelfde
persoon over een paar notes die u niet aanstaan.

U overdrijft gewoon.  Ik heb met de mantel der liefde al mensen
aangepakt die brokken data vernielden van mijn hand uit onwetendheid,
iedereen in OSM doet dubbel werk van tijd, live with it.  It's part of
the game.

Als de notes u werkelijk niet aanstaan, kijk er dan niet naar!  Dit is
een community, geen concurentie.  geen enkele 'dictator' verplicht u
toch om er rekening mee te houden ?

Ik vind dat Math nog heel proper reageerde op uw voorlaatste klaagzang,
ik stel voor om dezelfde diplomatische houding aan te nemen, uw
aanvallen storen mij meer dan de notes waar ik niet naar kijk.  Steek uw
energie in het editten van de kaart ipv in dit soort

Re: [OSM-talk-fr] Carte de bruit.

2017-02-17 Thread Philippe Verdy

Malgré tout, depuis cette démo initiale (signalée ici il y a quelques
mois), l'auteur a accepté quelques remarques de "feedback", mais son dépot
GitHub est mort, ce qui semble indiquer qu'il ne travaille plus dessus. Je
pense que c'était surtout une démo destinée à en discuter pour savoir qui
était intéressé pour la développer, et éventuellement compléter avec des
tags spécifiques pour le bruit (ou trouver des sources open data quand
elles existent, et voir comment les intégrer au delà de la seule
estimation).
Il n'y a eu aucune modification visible depuis cette démo initiale (donc
par exemple, les aéroports et zones de décollage ou vol en basse altitude
sont encore ignorés, et rien non plus concernant les aérodrome militaires
dont les chasseurs sont encore plus bruyants que les avions de ligne).
Concernant les aéroports, les tags indiquant le trafic ou les heures
d'ouverture pourraient être utiles et le niveau de bruit est hautement
variable selon les horaires de la journée. Autre source possible: les
mesures de trafic routier (en cas de ralentissement signalé, le trafic est
forcément plus chargé et plus bruyant), mais là aussi mettre ça sur une
carte dynamique peut être un problème.

Cependant la démo créait une couche SVG dynamique à la demande. On peut
envisager une démo montrant des niveaux de bruit heure par heure (on a des
sources open data sur le trafic, et si on ajoute les horaires d'ouverture,
cela peut rafiner le rendu et les estimations). Il peut aussi y avoir des
variations saisonnières significatives concernant les lieux touristiques:
affiner mois par mois), et le besoin d'avoir un rendu estimé sur une
moyenne annuelle pour chaque heure, ou une moyenne mensuelle ou annuelle
pour la journée complète. Je ne sais pas comment réglementairement le
niveaux de bruits moyens acceptables sont acceptés, je pense que la
législation locale joue pour beaucoup et qu'il est difficile d'établir une
règle générale commune.

On peut aussi tenir compte des restrictions d'accès des poids lourds et
bus. Sinon il y a la réglementation française ou européenne propre aux
véhicules (notamment les motos...) et engins ou activités bruyantes
(tondeuses/débroussailleuses en ville, scieries, démolition,
mines/carrières, travaux de voirie/marteaux-piqueurs, avec des contraintes
horaires fortes...) mais c'est difficile à estimer dans le temps (le bruit
peut être temporaire pendant au plus quelques jours ou semaines, voire
quelques mois pour les chantiers de construction) et ensuite se déplacer
plus loin, et on peut difficilement prévoir les situations exceptionnelles
(déviations suite à accident/inondation, ou restrictions imposées en cas de
pollution).

Il y a peut-être des données sur des sites d'évaluation/notation dans
l'immobilier, selon le bruit perçu, mais ça risque d'être très subjectif ou
assez vague dans les descriptions.

Autre source possible : les statistiques de plaintes pour tapage, si elles
sont disponibles et suffisamment géolocalisées (je pense qu'on n'aura rien
de mieux que commune par commune ou en fonction de la localisation des
zones de compétence des commissariats et gendarmeries, avec cependant des
plaintes rapportées hors zone, par exemple en France des plaintes au
procureur de la république du département).
Certaines installation réputées bruyantes font l'objet de réglementations
spécifiques bien établies pour leur autorisation (cas des aéroports civils
et militaires notamment, ou de certains gros chantiers).

De plus le bruit qui fait l'objet des plus nombreuses plaintes est celui
des troubles de voisinage par le comportement de quelques résidents, ou la
présence d'animaux d'élevage ou de compagnie, ou le manque de mesures
prises par les gérants d'établissements recevant du public ou diffusant de
la musique: il n'affecte qu'une zone très limitée, souvent un seul immeuble
ou le voisin le plus proche, et la perception du bruit varie largement
selon les voisins et les relations propres au partage de parties communes:
ce bruit est souvent une affaire privée, alors que le bruit sur la voirie
est une affaire publique rapportée aux mairies et assos de quartiers (qui
ont aussi à coeur de maintenir l'activité, les dessertes en transport en
commun et les sports et loisirs; tous les bruits ne sont pas égaux selon
leur nature : par endroit on accepte et promeut le brouhaha des piétons et
places publiques, ou celui des transports ou celui des stade les jours de
rencontres sportives ou la musique des manifestations et spectacles
extérieurs, mais il y a toujours des opposants locaux).

Le 17 février 2017 à 13:01, Philippe Verdy  a écrit :

> Oui je parlais de ça, j'ai oublié le lien, merci pour la précision
>
> Le 17 février 2017 à 11:25, Eric Brosselin - Osm 
> a écrit :
>
>> Le 17/02/2017 à 11:11, Philippe Verdy a écrit :
>>
>> *Il y a eu une démo suisse montrant comment on pouvait extrapoler des
>> données moyennes de bruit en fonction de la présence de certains

Re: [OSM-talk] Fixing broken multipolygons

2017-02-17 Thread Christoph Hormann

On Friday 17 February 2017, Jochen Topf wrote:
>
> Lets not get this thread hijacked by theoretical ideas about how to
> detect wooded areas. This thread is about broken multipolygons.

I did not mean to hijack this thread, i meant to provide context for the 
decision on if to keep the imported wood/forest polygons.

> I'd rather have more specific challenges addressing
> exactly one problem, for instance "Broken multipolygons of certain
> types of landcover data imported from Corinne in Sweden". That is
> something I can extract from OSM data and that I can explain to
> people how to fix after consulting with local mappers on how best to
> do this.

In principle that is a good idea, for the Scandinavian wood/forest 
polygons however the problem would be that likely for a large fraction 
of the mappers willing and able to work on this the best solution will 
often be to delete the polygon in question.  This should of course not 
happen against the desires of the local community.  This problem is the 
main reason why i brought up the subject here.

In terms of specific challenges that might be useful - waterbodies is an 
obvious candidate.  There does not appear to be any specific 
concentration of broken waterbody polygons related to an import, most 
of these are genuine manual mapping errors.  Although many of these are 
also substandard in terms of mapping quality very few are so bad it 
would be better to delete them than to keep them.

Of course this task would be technically non-trivial, many of these 
polygons are large, a lot of big river polygons that should be split 
into smaller ones etc.

-- 
Christoph Hormann
http://www.imagico.de/

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

Re: [Talk-cz] Otevřená data v Plzni

2017-02-17 Thread Pavel Cvrček

Ahoj,

tak jsem udělal první výstřel na oddělení GIS Správy informačních
technologií města, která má otevřená data na starosti. Zatím jsme si
vyměnili dva e-maily, kde jsme se domlouvali, co je potřeba s tím, že se to
"pošouplo" výše, aby žádost někdo posoudil. Nadhodil jsem to formou viz
níže. Tak uvidíme... výsledek pak napíšu.

Pavel

Dne 13. února 2017 4:03 Matej Lieskovský 
napsal(a):

> https://wiki.openstreetmap.org/wiki/Import/ODbL_Compatibility
>
> Zkušenost z Prahy:
> Změna licence je těžká. Raději miřte na explicitní souhlas. Pomáhá:
>  - zdůraznit, že to bude otevřený formát (a pouze odvozená data)
>  - slíbit jim uvedení zdroje (source tag)
>  - nabídnout zpracování statistik o využívanosti dat (pro ně je to možnost
> vykázat nějakou užitečnost, pro nás je to vyhledání všech changesetů a
> prvků s tím source tagem)
>
> Posílal jsem kompletní komunikaci s IPR Praha, můžete se inspirovat :)
>
> 2017-02-12 20:58 GMT+01:00 Jan Macura :
>
>> Ahoj,
>>
>> na začátek musím poznamenat, že ve srovnání s Krnem Plzeň těžce prohrává.
>> KMZ, výkresy z CADu, obrázky PNG... Naprosto tristní formáty, pro GIS de
>> facto nepoužitelné. Škoda slov. Co by teď člověk dal za GeoJSON...
>>
>> Ad tvoje otázka: No určitě to může být CC-0 ;-) Pokud by nikdo v listu
>> nevěděl líp, mohli bychom zkusit obrátit se s prosbou o konzultaci
>> kompatibility licencí na Creative Commons ČR
>> .
>>
>> H.
>>
>> 2017-02-12 20:46 GMT+01:00 Pavel Cvrček :
>>
>>> Ahoj,
>>>
>>> město Plzeň již nějaký čas zpřístupňuje některá svá data jako open data (
>>> https://opendata.plzen.eu/) a postupně nabídku dat rozšiřuje. Co jsem
>>> se namátkou díval, jsou poskytována pod licencí Creative Commons Uveďte
>>> autora-Zachovejte licenci.
>>>
>>> Předpokládám, že tato licence není OSM kompatibilní. Chtěl bych se ně
>>> proto obrátit, zda by data mohli zveřejňovat i pod licencí, která umožní
>>> jejich využití pro potřeby OSM. Rád bych se zeptal zkušenějších... musí
>>> být Open Data Commons Open Database License (ODbL)? Nebo co vše je
>>> akceptovatelné, aby šlo z dat čerpat pro potřeby OSM?
>>>
>>> Díky
>>>
>>> Pavel
>>>
>>> ___
>>> Talk-cz mailing list
>>> Talk-cz@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-cz
>>>
>>>
>>
>> ___
>> Talk-cz mailing list
>> Talk-cz@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-cz
>>
>>
>
> ___
> Talk-cz mailing list
> Talk-cz@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-cz
>
>
___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

Re: [OSM-talk-fr] Carte de bruit.

2017-02-17 Thread Philippe Verdy

Oui je parlais de ça, j'ai oublié le lien, merci pour la précision

Le 17 février 2017 à 11:25, Eric Brosselin - Osm  a
écrit :

> Le 17/02/2017 à 11:11, Philippe Verdy a écrit :
>
> *Il y a eu une démo suisse montrant comment on pouvait extrapoler des
> données moyennes de bruit en fonction de la présence de certains axes
> (types de highway, notemment rues piétonnes et routes majeures, présence de
> feux de circulation, limites de vitesse, voies de chemin de fer, proximité
> d'un aéroport), de certaines activités (restaurants/cafés, commerces, lieux
> de spectacle, usines).*
> *Ca donne une idée, mais pas une mesure réelle.*
>
>
> Il doit s'agir de celle-ci >>> http://lukasmartinelli.ch/gis/
> 2016/04/03/openstreetmap-noise-pollution-map.html
> Explications en bas de page.
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-it] Segnale stradale (a me) incomprensibile

2017-02-17 Thread Francesco Pelullo

Il 17 feb 2017 12:40, "Martin Koppenhoefer"  ha
scritto:




la vita del mappatore è più difficile di quella del guidatore, perché il
primo deve interpretare la situazione per tutti i tipi di veicolo, mentre
il secondo solo per se stesso.


Wow
Adoro questa lista.

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

Re: [OSM-talk-be] Notes pollutie in Brussel

2017-02-17 Thread Glenn Plas

Mr Casteleyn,

Dit is de 2de maal dat u iemand persoonlijk aanvalt, en 2 maal dezelfde
persoon over een paar notes die u niet aanstaan.

U overdrijft gewoon.  Ik heb met de mantel der liefde al mensen
aangepakt die brokken data vernielden van mijn hand uit onwetendheid,
iedereen in OSM doet dubbel werk van tijd, live with it.  It's part of
the game.

Als de notes u werkelijk niet aanstaan, kijk er dan niet naar!  Dit is
een community, geen concurentie.  geen enkele 'dictator' verplicht u
toch om er rekening mee te houden ?

Ik vind dat Math nog heel proper reageerde op uw voorlaatste klaagzang,
ik stel voor om dezelfde diplomatische houding aan te nemen, uw
aanvallen storen mij meer dan de notes waar ik niet naar kijk.  Steek uw
energie in het editten van de kaart ipv in dit soort thrash mails te
schrijven.

Er is geen deadline voor editeren van OSM, het is een constante golf van
veranderingen en aanpassingen aan de realiteit, we zullen de factor
altijd achterlopen op de werkelijkheid.

Don't fix the blame, fix the problem.

Glenn

On 16-02-17 09:38, Philippe Casteleyn wrote:
> http://www.openstreetmap.org/user/philippec
> 
> Het is beleefd op het OSM profiel te zeggen wat u waar doet.
> 
> 
> Ik heb er altijd een punt van eer van gemaakt de foto's voor
> fatsoenlijke notes de dag zelf te publiceren.  De laastste 5 maand zit
> ik naar de 50 notes van Math te staren en ik zie meer beweging in de
> winkels dan in de notes.  Bovendien zijn zijn notes geen notes.  Zelfs
> een Brusselaar kan op de OSM kaart zien welke panden en
> winkelgaanderijen niet getagd zijn.  Er is geen verdienste aan.   Het is
> gewoon hondjesgedrag.
> 
> 
> Ik ben niet van plan elke dag te kijken of er een éénenvijftigste
> fatsoenlijke note tussen zit.  Ik ben ook niet van plan naar de pijpen
> van een buitenlandse dictator te dansen.  Zijn er al precendenten ?  Hoe
> reageren andere beschavingen op zulke D.O.S. bombardementen ?  Ik heb
> ook niet de indruk dat de locals 100 procent achter mij staan.  De notes
> staan er nog.  Ik zal dan ook stoppen met de winkelgaanderijen te
> bolfotograferen.  Trop is te veel.
> 
> 
> 
> Ph Casteleyn
> Dahliastraat 16
> 2800 Mechelen
> animals.slippers.loaders
> gsm 0486 516261
> Ctrl+v
> 
> 
> ___
> 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] KBO

2017-02-17 Thread Glenn Plas

Nope, we can't.  The license is incompatible with OSM.   It's too
restrictive.
http://economie.fgov.be/nl/modules/publications/kbo/licence_open_data.jsp

I investigated this about a half year ago.  They call it open data but
they impose restriction on the usage.  I downloaded it back then and
gave as intended use : "creating a webapp".  It's a bit silly because
you can keep it very generic but it's too limiting to be a real opendata
license.

They used to sell this DB for a small fee of about 70K euro's in the
past, probably still a relic of clinging on reselling data that in
essence is 'ours' to begin with.

See also the cookbook:
http://economie.fgov.be/nl/binaries/Cookbook%20KBO%20Open%20Data%201.0.0_nl_2_tcm325-246659.pdf

I've considered using this data to augment up the GRB data on import,
but decided against it.

Glenn

On 16-02-17 10:37, Killian De Volder wrote:
> Does anyone know if we are allowed to use
> http://kbopub.economie.fgov.be/kbopub/zoeknummerform.html ?
> 
> I would read some of the policies on their site, but all the links are broken.
> 
> If nobody knows, I could send an email to the department to ask.
> 
> Regards,
> Killian
> 
> ___
> 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-it] Segnale stradale (a me) incomprensibile

2017-02-17 12:28 GMT+01:00 Volker Schmidt :

> Scrivo subito a Del Rio e propongo una nuova domanda per la prova scritta
> per la patente



la vita del mappatore è più difficile di quella del guidatore, perché il
primo deve interpretare la situazione per tutti i tipi di veicolo, mentre
il secondo solo per se stesso.

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

Re: [Talk-it] Segnale stradale (a me) incomprensibile

2017-02-17 Thread Volker Schmidt

Scrivo subito a Del Rio e propongo una nuova domanda per la prova scritta
per la patente

2017-02-17 12:21 GMT+01:00 Martin Koppenhoefer :

>
> 2017-02-17 12:03 GMT+01:00 Volker Schmidt :
>
>> La segnaletica non vieta solo la svolta a destra dei autocarri, ma di
>> tutto salvo autovetture [1]. Così motocicltette, cavalli, biciclette ecc
>> non possono girare a destra, probsabilmante nemmeno pedoni (ma non sono
>> certo)
>> :-)
>>
>
>
> pedoni possono girare (non so nel caso che devono stare per strada perché
> hanno baggaglio ingombrante (probabilmente non vale per loro), carriole o
> simili con se (probabilmente vale per loro: art. 48. 1a). Non so se i
> cavalli sono "veicoli", mentre per il resto sono d'accordo, la svolta è
> vietata per tutti i veicoli tranne le autovetture,
>
> quindi tutti i veicoli descritti in CdS,
> art. 47,1,a-n,2a-d;
> art. 48 1a+b,
> art. 49 1a-c, 2,
> art. 50 1+2,
> art 51 1+2,
> art. 52 1-4,
> art. 53 1a-h + 2-6,
> art. 54 1b-n, 2,
> art. 55, 56, 57, 58, 59, 60, ...
> tutto, tutto tutto, tranne (art. 54a.)
> (SCNR) Non le ho contate ma mi sembra circa una cinquantina di classi di
> veicoli.
>
> Ciao,
> Martin
>
> ___
> 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] Segnale stradale (a me) incomprensibile

2017-02-17 12:03 GMT+01:00 Volker Schmidt :

> La segnaletica non vieta solo la svolta a destra dei autocarri, ma di
> tutto salvo autovetture [1]. Così motocicltette, cavalli, biciclette ecc
> non possono girare a destra, probsabilmante nemmeno pedoni (ma non sono
> certo)
> :-)
>


pedoni possono girare (non so nel caso che devono stare per strada perché
hanno baggaglio ingombrante (probabilmente non vale per loro), carriole o
simili con se (probabilmente vale per loro: art. 48. 1a). Non so se i
cavalli sono "veicoli", mentre per il resto sono d'accordo, la svolta è
vietata per tutti i veicoli tranne le autovetture,

quindi tutti i veicoli descritti in CdS,
art. 47,1,a-n,2a-d;
art. 48 1a+b,
art. 49 1a-c, 2,
art. 50 1+2,
art 51 1+2,
art. 52 1-4,
art. 53 1a-h + 2-6,
art. 54 1b-n, 2,
art. 55, 56, 57, 58, 59, 60, ...
tutto, tutto tutto, tranne (art. 54a.)
(SCNR) Non le ho contate ma mi sembra circa una cinquantina di classi di
veicoli.

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

Re: [Talk-it] Segnale stradale (a me) incomprensibile

scusate, non èra l'ultimo commento, un'altro ancora.
Ho letto il codice della strada:
https://it.wikisource.org/wiki/D.Lgs._30_aprile_1992,_n._285_-_Nuovo_codice_della_strada/Titolo_III
Art. 54 tratta dei Autoveicoli.

"autoveicolo" non vuol dire motorcar (come avevo scritto prima), invece è
una sottoclasse di motor_vehicle (non abbiamo questa classe in OSM).

Nel caso della segnaletica esposta penso che quel divieto vale ancora per
tanti altri veicoli, per esempio caravan (54m), goods (54c), ambulanze e
disabili (credo sia quella la classe di 54f/g, ma non sono sicuro). Divieto
vale anche per le ape (53c), e tutte le motoveicoli (art. 53), tutti i
veicoli a trazione animale (49), le slitte (51), i ciclomotori (52), ...

Generalmente, leggendo il CdS, credo che ci mancano ancora access classes.

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

Re: [Talk-it] Segnale stradale (a me) incomprensibile

2017-02-17 Thread Volker Schmidt

La segnaletica non vieta solo la svolta a destra dei autocarri, ma di tutto
salvo autovetture [1]. Così motocicltette, cavalli, biciclette ecc non
possono girare a destra, probsabilmante nemmeno pedoni (ma non sono certo)
:-)

[1] Wikipedia: L'*autovettura* (spesso definita automobile
, comunemente chiamata con la
forma contratta *auto* o popolarmente *macchina*) è un autoveicolo
 progettato e costruito per il
trasporto privato di un numero limitato di persone che trovano spazio in
appositi sedili situati all'interno di un abitacolo.

2017-02-17 6:18 GMT+01:00 Francesco Pelullo :

> Non sarebbe stato più corretto un "divieto di svolta a destra per
> autocarri"?
>
> Ciao
> /niubii/
>
>
> Il 17 feb 2017 00:03, "Giuseppe Profiti" 
> ha scritto:
>
> Il 16 febbraio 2017 23:43, Francesco Pelullo  ha
> scritto:
> > Ciao a tutti,
> >
> > Oggi mi sono imbattuto in questo segnale stradale:
> >
> > https://wiki.openstreetmap.org/w/images/3/37/Tmp_28292-IMG_
> 20170216_2333291422665715.jpg
> >
> > Sarà che sono rincoglionito, ma non ho capito che cosa significa.
> >
> > Ciao
> > /niubii/
>
> Ciao,
> quello è una direzione obbligatoria per tutti i veicoli, tranne le
> autovetture, che possono invece svoltare anche a destra.
> Il pannello integrativo di solito specifica o le tipologie di veicoli
> che devono seguire la prescrizione del cartello, o quali categorie di
> veicoli sono escluse.
>
> Giuseppe
> --
> Giuseppe Profiti
> Coordinatore regionale per l'Emilia-Romagna
> Wikimedia Italia – Associazione per la diffusione della conoscenza libera
> http://www.wikimedia.it | giuseppe.prof...@wikimedia.it
>
> ___
> 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 mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [OSM-talk] Fixing broken multipolygons

2017-02-17 Thread Jochen Topf

On Fri, Feb 17, 2017 at 11:11:12AM +0100, Christoph Hormann wrote:
> On Friday 17 February 2017, Andreas Vilén wrote:
> >
> > We are aware of the Corine import problems and have discussed them
> > locally at least in Sweden. Our community is very loose with not much
> > activity in mailing lists or other media, but so far consensus has
> > been not to remove Corine if it's not replaced by improved data.
> >
> > I have done some cleanup myself mostly around Kalmar, but in the huge
> > Northern parts of the country it seems unmanagable. Some users have
> > made good progress in the Bergslagen area though.
> 
> Well - the question you should probably ask yourselves is if this data 
> is of any help when you map in these areas.  I find it doubtful that it 
> is and areas like here:
> 
> http://www.openstreetmap.org/#map=13/56.7935/16.0168
> 
> support this impression.  IMO it would be a good idea to concentrate on 
> what you gain and not too much look at what you loose.
> 
> If there are worries in the local community about how to efficiently map 
> large wooded areas there are other methods that would be much better 
> suited.  Forests can be positively detected on multispectral imagery 
> with good reliability - in contrast to land cover classification data 
> sets like Corine which essentially only specify the least unlikely of a 
> fixed set of classes.  Producing a conservative data set this way (i.e. 
> one that only includes area which are clearly wooded), splitting this 
> into reasonably small chunks and providing this to mappers to avoid the 
> need for a lot of large scale tracing work seems a much more productive 
> way and much more compatible with normal manual mapping in OSM.

Lets not get this thread hijacked by theoretical ideas about how to
detect wooded areas. This thread is about broken multipolygons.

The issue at hand here is that there are a lot of broken multipolygons
out there. Some are probably from Corinne data. Now there are these
options:

a) Do nothing. Broken MPs will disappear once osm2pgsql switches.
b) Remove existing MPs and start from scratch.
c) Repair existing MPs.

From some of the posts in this thread, c) doesn't seem to be a good
option. Both a) and b) will result in those MPs disappearing from the
map first, before things get better. In the case of a) they will all
disappear one day, but the broken data is still there. In the case of b)
we can go through them and replace them by better data piece by piece.

I am willing to talk with the Swedish community (or any other) about
how best to approach this. I can generate special Maproulette challenges
for specific areas, in fact I think this is a better way then having
generic challenges for the whole world. If you work on such a challenge,
you might be thrown from an error in Borneo to one in Sweden to one in
Antarctica. And the problems are different everywhere. I'd rather have
more specific challenges addressing exactly one problem, for instance
"Broken multipolygons of certain types of landcover data imported from
Corinne in Sweden". That is something I can extract from OSM data and
that I can explain to people how to fix after consulting with local
mappers on how best to do this.

Jochen
-- 
Jochen Topf  joc...@remote.org  https://www.jochentopf.com/  +49-351-31778688

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

Re: [talk-au] A possible CAPAD 2016 import?

2017-02-17 Thread Warin

On 17-Feb-17 09:04 PM, Andrew Davidson wrote:
The good folks at DoEE have been more helpful and have given us
permission to use future releases of CAPAD under the same terms. Given
that the next release of CAPAD is due out in a number of weeks it
raises the question should we wait and then do an import?

Wait.

For those like me lost with the acronyms

DoEE, Commonwealth Department of Environment and Energy
CAPAD, Collaborative Australian Protected Areas Database

Assuming that the community thinks this is a good idea the other big
question is what to do with the existing boundaries. Having a look at
the data it appears that the data we have permission to use is:

1. NSW from NSW LPI (but these are only the areas managed by the NSW
NPWS)

2. Tas from CAPAD 2014

3. SA from DEWNR

All of the other data is from unknown sources or sources we don't have
permission to use (or at least I can't find it on the wiki).

So do we:

1. Scrub them off and start again,
2. Scrub off the other tags and leave them if they have a landcover
tag, or

3. Try and reuse them with the replace geometry tool?

Other ideas?

My thoughts ... initial .. subject to improvements?

A)
Data should not be removed from OSM base on a suspicion.
If you believe something comes from a copyright source then take it up
with the contributor on an individual basis. If you don't want to do
this .. then don't remove the data either.

B)
The NSW LPI data I would leave alone for now.
Work on those states that are not well defined or poorly represented in
OSM.
I would compare the present data in OSM with the CAPAD data .. if it is
the same then add the tag checked=CAPAD ? (where = numerical year)
If it is different then use the replace geometry tool and then alter the
source tag..

If new .. then just add it as usual.

C)
Has the appropriate OSM permission for this import been obtained? It has
been for past CAPAD .. but may need to be verified for 2016? Should be a
simple thing?
Possibly the permission needs to be open ended like the DoEE permission
to use it?

I note that the DoEE are using OSM mapping ... through mapbox.
see map on
https://data.gov.au/dataset/collaborative-australian-protected-areas-database-capad-2010-external12

Some OSM links
2014 import of CAPAD
http://wiki.openstreetmap.org/wiki/Import/Catalogue/Collaborative_Australian_Protected_Areas_Database_(CAPAD)
Permission to use CAPAD (starts sequentially from the top earliest and
to the bottom latest)

http://wiki.openstreetmap.org/wiki/Attribution/Department_of_the_Environment_and_Energy_CAPAD

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

Re: [Talk-it] Segnale stradale (a me) incomprensibile

2017-02-17 11:24 GMT+01:00 Martin Koppenhoefer :

> Adirittura gli autoveicoli destinati al trasporto merci (furgoni) non
> possono svoltare (perché non sono autovetture).




un'ultimo commento: credo che non abbiamo una classe per "autovettura" in
OSM, abbiamo solo "autoveicolo" (motorcar), però abbiamo "goods" che
dovrebbe relazionarsi così:

autovettura = motorcar - goods

autoveicolo = motorcar

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

Re: [OSM-talk-fr] Carte de bruit.

2017-02-17 Thread Eric Brosselin - Osm


Le 17/02/2017 à 11:11, Philippe Verdy a écrit :
/Il y a eu une démo suisse montrant comment on pouvait extrapoler des 
données moyennes de bruit en fonction de la présence de certains axes 
(types de highway, notemment rues piétonnes et routes majeures, 
présence de feux de circulation, limites de vitesse, voies de chemin 
de fer, proximité d'un aéroport), de certaines activités 
(restaurants/cafés, commerces, lieux de spectacle, usines)./

/Ca donne une idée, mais pas une mesure réelle./


Il doit s'agir de celle-ci >>> 
http://lukasmartinelli.ch/gis/2016/04/03/openstreetmap-noise-pollution-map.html

Explications en bas de page.
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-it] Segnale stradale (a me) incomprensibile

2017-02-17 8:26 GMT+01:00 Lorenzo "Beba" Beltrami :

> Non è per nulla scontato che quel cartello indichi quello che avevano in
> mente



+1, perché trattare furgoni, moto, motorini e bici come camion, ma
autovetture no?

Adirittura gli autoveicoli destinati al trasporto merci (furgoni) non
possono svoltare (perché non sono autovetture).

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

Re: [OSM-talk] Fixing broken multipolygons

2017-02-17 Thread Paul Norman


On 2/16/2017 2:51 AM, Yves wrote:
Is there an example where the community has cleaned up the Corine 
multi polygons instead of starting from scratch? 


I've done some Corine cleanup, mainly consisting of deleting obviously 
wrong data. Where I've remapped it's been faster to delete it and start 
from scratch.


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

Re: [Talk-it] Segnale stradale (a me) incomprensibile