Re: [OSM-talk] Call to Take Action and Confront Systemic Offensive Behavior in the OSM Community

2020-12-10 Thread Midgard
This whole thread caused me great distress on account of some messages I saw 
that came across as
polarizing.

The reason I would be discouraged from joining OSM discussion right now would 
be hostility and
passive aggressive bickering. And this is among people who I suppose all mean 
the best for each
other.

So please, everyone, if you write a message, consider rereading it to make sure 
it doesn't sound
aggressive or polarising.

Peace.

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


Re: [OSM-talk] fake, edit, FAKE map.

2020-06-16 Thread Midgard
Quoting 80hnhtv4agou--- via talk (2020-06-16 18:09:44)
> Added a service road.
> Edited about  hours ago by 
> Version #1 · Changeset #86698283
>  
> https://imgur.com/gallery/k6Zjnqm

And what is your goal exactly in posting this two general mailing lists?

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


Re: [OSM-talk-be] privacy ed

2020-05-16 Thread Midgard
Quoting Nicolas Pettiaux (2020-05-16 14:59:41)
> > No! You need prior permission to take a photo of a person.
> 
> can you provide a legal text with that ?

No, I don't have the resources to search our law. The online lookup tools of 
the government are not
adequate for that.

The best I can get you is:
https://www.gegevensbeschermingsautoriteit.be/recht-op-afbeelding-principe
https://www.autoriteprotectiondonnees.be/droit-image/principe

> [...] het nemen van een afbeelding [is] onderworpen aan de toestemming van de 
> betrokken persoon.

> [...] la prise d'une image [...] de cette image [est soumise] au consentement 
> de la personne concernée.

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


Re: [OSM-talk-be] privacy ed

2020-05-16 Thread Midgard
Quoting Marc Gemis (2020-05-16 14:59:43)
> According to 
> https://www.gegevensbeschermingsautoriteit.be/recht-op-afbeelding-de-privacywet-algemeen,
> 
> "Toch geldt de Privacywet niet altijd. [...]

There are 2 panels:
* the privacy law and
* the picture rights, which are part of our copyright law (NL: recht op 
afbeelding,
  FR: droit à l'image).

Privacy law will indeed not give a problem for our purposes.

But if a person is prominent in the picture, picture rights may prevent you 
from taking it.

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


Re: [OSM-talk-be] privacy ed

2020-05-16 Thread Midgard
On Fri, May 15, 2020, 19:38 Marc Gemis  wrote:
> Taking pictures of people is not a problem, it's what you do with them
> afterwards that is important.
Op vr 15 mei 2020 22:51 schreef Sander Deryckere :
> Taking a picture is usually not illegal indeed.

No! You need prior permission to take a photo of a person.
Being in a public place can be interpreted as silent permission for appearing 
incidentally in
overview photos.

https://www.gegevensbeschermingsautoriteit.be/recht-op-afbeelding
https://www.autoriteprotectiondonnees.be/droit-image


Quoting Marc Gemis (2020-05-15 23:31:16)
> Afaik,  Belgium changed the law  one or two years ago and you can now
> publish pictures of art and buildings without problems.

With some restrictions:
https://nl.wikipedia.org/wiki/Panoramavrijheid#Belgi%C3%AB
https://fr.wikipedia.org/wiki/Libert%C3%A9_de_panorama#En_Belgique

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


Re: [OSM-talk-be] Telenav Mapping Project

2020-04-25 Thread Midgard
Quoting Adrian Budugan (2020-04-23 13:29:32)
> Hi Marc,
> 
> It's nice to hear from you. From our first analysis, Brussels looks quite 
> complete and correctly mapped. We are looking to  first correct any errors 
> that might come up by running the Keep Right tool.
> Where there will be any doubts, we will leave notes and/or ask the community 
> before making any edits.
> 
> Kind regards,
> Adrian

Keep right "errors" are not always real errors. I see a lot of almost-junction 
reports in my
neighbourhood, but they're all false positives.

Of course it highlights a lot of valid problems too. What I mean to say is, 
please don't map for
the validator.

Kind regards,
M!dgard

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


Re: [OSM-talk-be] IBPT antennas

2020-03-08 Thread Midgard
Replying inline to s8evq and Karel:

Quoting s8evq (2020-03-08 20:20:34)
> What is the point of adding longitude=* and latitude=* to the nodes?

I had overlooked them, but these tags definitely have to be dropped.

> How precise are the locations of the antennas in the BIPT dataset? Do we know 
> what the quality of this data is before importing?

The ten or so that I checked were pretty close, within 5 metres. One was either 
very recent, or
20 metres off. (BIPT has location 51.151194,3.235139 but there's no structure 
visible there on
the most recent imagery.)

In any case, we would get higher quality with a manual review instead of fully 
relying on the
source: we can correct errors when the structure is visible on imagery.

> Perhaps my questions sound a bit tough, but I appreciate the effort you put 
> into this.

Such is an import discussion. Original Poster has my appreciation too :)

> On Sun, 8 Mar 2020 17:46:38 +, Karel Adams  wrote:
> > didn't we
> > have a rule to map only those features visible in the scenery? The BIPT
> > antennae (sic!) are usually attached to existing structures, such as
> > church spires or GSM masts or so? Of course we map those highly visible
> > carrying structures, but to map the individual antennae seems to me like
> > overdoing things.

Looking at the source data, it's going to be one node for one mast, which 
typically has several
directional antennas mounted on it. A node per antenna is not something I'd 
like to see either.

Off-topic: when referring to the electrical part, "antennas" is actually the 
most common form. By the way,
could you maybe start trying to behave more constructive and socially 
acceptable? I believe you can
do it with some effort.

Kind regards,
Midgard

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


Re: [OSM-talk-be] IBPT antennas

2020-03-08 Thread Midgard
Cool news!

1) Instead of doing it once, wouldn't it be nicer to keep it updated? 
Generating a list of changes
   between two versions of the source file would be trivial.

2) Three meters is way, way, way too little. I opened the data and looked at 
literally the first
   antenna I saw in OSM, and it was 4.5 meters from BIPT's position. I would 
consider 25 meters the
   bare minimum.

3) And even then, just dumping elements in OSM without manual review is not 
considered best
   practice, but since it's only nodes, things are relatively simple and I 
won't object. I would
   just like to see that they're not placed too close to any other existing 
node, but that can be
   checked automatically.

Thanks for discussing before doing!

Kind regards,
Midgard

Quoting Vucodil via Talk-be (2020-03-08 14:15:26)
> Hello everyone,
> 
> Recently, we got the permission from ibpt.be to use their data in 
> OpenStreetMap: 
> https://wiki.openstreetmap.org/wiki/Import/Catalogue/ibpt_belgium_antennas
> 
> This includes all the antennas (more than 9000) managed by the three 
> operators (Proximus, Mobistar and Telenet) with the info on who manages which 
> antennas and their localisation.
> 
> I wish to import them in a semi-automatic import. But before that, I wish to 
> have your feedback on the:
> 
> General workflow 
> 
> For the workflow, you can find it at the end of the import wiki page. The 
> main idea is that the antennas to close to existing antennas will be manually 
> reviewed.
> What do you think about that? Is it safe enough?
> 
> Tags to use
> 
> As there is around 300 antennas currently in Belgium 
> (https://overpass-turbo.eu/s/QPC) and considering that this import will bring 
> more than 9000 antennas, I think the tags of the import should be carefully 
> chosen. 
> 
> The tags for the objects related to telecoms are not well defined. Various 
> sources of information are available (see at the end of this email).
> If we choose to only map the antenna itself by excluding the support (mast, 
> tower, roof, ...), it seems to exist two tags:
> 
> - man_made=antenna 
> (https://taginfo.openstreetmap.org/tags/man_made=antenna#overview)
> 
> - telecoms=antenna 
> (https://taginfo.openstreetmap.org/tags/?key=telecom=antenna)
> 
> the first one being much more used. That's the one that I suggest. You can 
> see more details on the tagging here: 
> https://wiki.openstreetmap.org/wiki/Import/Catalogue/ibpt_belgium_antennas#Data_Preparation
> 
> With the data from IBPT, it make sense to only focus on the antenna itself 
> and not on the support as we don't have any information on it.
> In cities, it will usually be on roofs or underground like in tunnels but in 
> the countryside, it is often on communication towers.
> 
> Mapping only the antenna enable us to later map more complex things like in 
> this proposal 
> https://wiki.openstreetmap.org/wiki/File:Radio_antennas_mapping_proposal.png  
>  where I really like the separation between:
> 
> - antenna
> - support
> - station
> 
> Note that today, most antennas in Belgium are mapped via their support (mast 
> or tower).
> 
> What do you think about the tagging that I suggest? Does it make sense ?
> 
> Vucodil
> 
> PS: I sent two mails in a week about import. It is a coincidence, I'm not 
> doing only that!
> 
> Sources of information: 
> 
> - https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dantenna
> - https://wiki.openstreetmap.org/wiki/Telecoms
> - 
> https://wiki.openstreetmap.org/wiki/Proposed_features/Telecommunications_tower
> - https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dmast 
> - https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dcommunications_tower
> - 
> https://wiki.openstreetmap.org/wiki/FR:Proposed_features/Key:antenna#Les_antennes_t.C3.A9l.C3.A9com
> - https://lists.openstreetmap.org/pipermail/talk-be/2011-April/001970.html
> 
> - https://lists.openstreetmap.org/pipermail/talk-be/2011-April/001971.html

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


Re: [OSM-talk-be] RFC: removing OpenGeoDB and is_in tags (RFC by 29 Feb 2020)

2020-03-01 Thread Midgard
Quoting Midgard (2020-02-05 16:36:51)
> - tags with a "openGeoDB:" prefix and
> - "is_in" tags.
> 
> I hereby propose a mechanical edit to delete those from all features in 
> Belgium.

Done: https://www.openstreetmap.org/changeset/81642925

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


Re: [OSM-talk] Cease use of OpenStreetMap/Antifa logo

2020-02-13 Thread Midgard
Quoting Christoph Hormann (2020-02-13 15:06:21)
> On Monday 10 February 2020, Midgard wrote:
> >
> > I think it's a bad idea to create material that associates
> > OpenStreetMap with political groups. I suspect there are also
> > trademark issues with the mashup.
> 
> No, the trademark policy is pretty clear on that:
> 
> https://wiki.osmfoundation.org/wiki/Trademark_Policy
> 
> in section 3.5.

There's also section 2.1 that forbids using a mark that "confuses users by 
suggesting endorsement
by, or affiliation with, the OSMF". I think that is violated here.

Kind regards,
Midgard

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


Re: [OSM-talk] Cease use of OpenStreetMap/Antifa logo

2020-02-13 Thread Midgard
Hi,

Quoting Florian Lohoff (2020-02-13 12:59:23)
> Just nitpicking but "militant groups" is a little far fetched. Antifa is
> the abbreviation for "Anti fascist" and by no means has anything to do
> with militant activities.
> 
> Putting the Antifa into the militant left wing edge is polemic of a lot
> of right wing, facist or nationalist partys in the rise in a lot of
> European countries.

I have contacted the creator of the logo via PM with the same request, they did 
not react to my
description of antifa as violent, instead asking me to make a comparison to 
militaries.

The different language editions of Wikipedia use varying terminology to 
describe Antifa. The
English one describes it as militant anti-fascist groups that engage in 
property damage, physical
violence, and harassment.[1] The German one says that the violent antifa 
movements self-describe as
"militant antifascists". It does acknowledge that antifa is left to far-left.[2]

I conclude that it's possible to have differing impressions of antifa. (Think 
of the blind men and
the elephant.[3]) My impression is that there are violent antifa groups. Your 
antifa groups may be
more peaceful, but the logo is the same, and the overall impression will be 
"endorses violent
groups" for people who have that impression of antifa.

[1] https://en.wikipedia.org/wiki/Antifa_(United_States) and 
https://en.wikipedia.org/wiki/Antifa_(Germany)
[2] https://de.wikipedia.org/wiki/Antifa
[3] https://en.wikipedia.org/wiki/Blind_men_and_an_elephant

> I agree that OSM should not by itself get into the trouble of
> sympathising with any political views. OTOH the idea of Anti Facism should
> be within OSMs interest as we want to be a welcoming, divers and
> globally collaborating group of individuals.
> 
> Facism OTOH is the exact opposite of what the OSM Community wants to be
> so i sympathise with the idea of parts or the whole of the community
> opposing facism.
> 
> https://wiki.openstreetmap.org/wiki/Community_Code_of_Conduct_(Draft)

I'm definitely not fascist either. But in my experience, antifa stands for more 
than just being
opposed to fascism. It also includes hints of anarchy and use of violence.

> As already the URLs mention this is not an official OSM position but
> individuals making mashups.

These stickers were handed out at SotM 2019. If you see a sticker, you don't 
see that it's not
official.

> From my POV the mashup is to far from
> the original to be a serious and clear trademark issue. But - IANAL.

It is an adaptation from 
https://wiki.openstreetmap.org/wiki/File:Logo_simple.svg

IANAL either, but in my interpretation of the trademark policy it's a violation 
of
section 2.3 (Use of remixed logos) 
https://wiki.osmfoundation.org/wiki/Trademark_Policy#2.3._No_confusion.2C_endorsement.2C_or_affiliation
 and
section 3.5 (Use of remixed logos) 
https://wiki.osmfoundation.org/wiki/Trademark_Policy#3.5._Use_of_remixed_logos

Kind regards,
Midgard

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


[OSM-talk] Cease use of OpenStreetMap/Antifa logo

2020-02-10 Thread Midgard
Hi,

Someone created a mashup[1] between the logos of OpenStreetMap and Antifa, a 
collective of militant
groups which are known to use violence. This graphic is distributed on 
stickers.[2]

I'm asking to cease use of this logo.

I think it's a bad idea to create material that associates OpenStreetMap with 
political groups.
I suspect there are also trademark issues with the mashup.

[1] https://wiki.openstreetmap.org/wiki/File:2019_OSM_Anarchist_Antifa_logo.svg
[2] 
https://wiki.openstreetmap.org/wiki/OSM_Promotional_Material_Programme#Swag_from_Individual_OSMers

Kind regards,
Midgard

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


Re: [OSM-talk-be] Taggen van laadpalen in ondergrondse parkeergarages ?

2020-02-10 Thread Midgard
Als de parking betalend is, kun je ook niet echt de laadpaal gebruiken zonder 
te betalen, hé.

Zelf gebruik ik capacity:charging[1] op parkings met laadpalen. Het contacttype 
kun je dan wel niet
meegeven. Hm, socket:*=*[2] rechtstreeks op de parking gebruiken is dan 
mogelijk. Geen idee of
datagebruikers dat gaan verwachten, het zou misschien best in de wiki 
geschreven worden dan.

[1] https://wiki.openstreetmap.org/wiki/Key%3Acapacity%3Acharging
[2] https://wiki.openstreetmap.org/wiki/Key:socket

Groeten
Midgard

Quoting Pieter Vander Vennet (2020-02-09 16:58:30)
> Hallo Denis,
> 
> Persoonlijk zou ik wél een aparte node voor de laadpalen maken (ééntje
> die alle vier groupeert of zelfs ééntje per punt).
> Hoewel het een "integraal deel" van de parking is, is het toch een
> aparte amenity. Zo kan je ook de automaat, toiletten, ... in de parking
> als deel van de parking zien, maar dan wordt het parkingobject zelf
> overladen met nogal veel data en wordt het moeilijk om te zoeken ernaar.
> En wat als de laadpaal dan te betalen is maar de parking niet? Een
> combinatie 'amenity=parking; charging_station=yes; fee=yes; wordt dan
> voor interpretatie vatbaar.
> 
> Bovendien kan iemand zich door de aparte node dan al een beetje
> orienteren waar de laadpalen ongeveer zijn in de parking.
> 
> Om het ondergrondse aspect te vatten, kan je de tags 'indoor=yes;
> level=-1' toevoegen, eventueel met 'access=customers' als de laadpaal
> enkel bereikbaar is voor gebruikers van de parking.
> 
> Maar goed, just my two cents - wss hebben andere mensen andere inzichten.
> 
> Mvg, Pieter
> 
> On 09.02.20 14:27, Denis Verheyden wrote:
> > Hallo allen,
> >
> > Onlangs stuitte ik weer op een onderwerp waar er geen echte conventie
> > of goed voorbeeld is: hoe taggen we laadpalen voor elektrische
> > voertuigen in  ondergrondse parkeergarages ?
> >
> > Als voorbeeld wil ik de parkeergarage Tinel in Mechelen nemen, die ik
> > een paar maand geleden heb toegevoegd:
> > https://www.openstreetmap.org/node/7082405515
> >
> > De meeste basisgegevens heb ik ingevuld, maar hoe tag ik nu de laadpalen ?
> > In totaal zijn er 4 plaatsen voor elektrische wagens (op niveau -1), 
> > op mijn foto's heb ik weliswaar maar 1 laadpaal en 2 plaatsen afgebeeld:
> > https://photos.app.goo.gl/ARJ3YkYVTAs8M94XA
> >
> > Het lijkt me niet zinnig ze als aparte nodes met tag
> > amenity=charging_station te plaatsen, gezien ze integraal onderdeel
> > uitmaken van de parkeergarage en niet als losstaande laadpaal staan
> > (zoals op gelijkvloerse parkings buiten).
> >
> > Heeft iemand een bruikbare oplossing zodat het duidelijk is dat er
> > laadpalen aanwezig zijn, maar ze niet allemaal individueel op de kaart
> > moeten gezet worden ?
> > Mogelijk zal het dan iets met een relation worden vermoed ik ?
> >
> > Groeten,
> > Denis

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


[OSM-talk-be] RFC: removing OpenGeoDB and is_in tags (RFC by 29 Feb 2020)

2020-02-05 Thread Midgard
Dear mappers

If you ever touched a place node, chances are you saw it was cluttered with:
- tags with a "openGeoDB:" prefix and
- "is_in" tags.

I hereby propose a mechanical edit to delete those from all features in Belgium.
The Overpass query to fetch the data is https://overpass-turbo.eu/s/Qqa

- The openGeoDB tags date to 2008, when the plan was to keep populations 
updated from the openGeoDB
  database. This never happened and probably never will.
  Information about OpenGeoDB on the wiki: 
https://wiki.openstreetmap.org/wiki/OpenGeoDB
  For an example, see https://www.openstreetmap.org/node/79382706/history

- The is_in tags are largely obsolete. The administrative boundaries replace 
them.
  They're also not uniform in OSM to begin with. Some examples:
  - Beernem: is_in=Belgie, Vlaanderen, West-Vlaanderen
  - Sint-Andries:is_in=Brugge,West-Vlaanderen,Belgium,Europe
  - Hoekskensstraat: is_in=Lebbeke, Oost-Vlaanderen
  - Meise: is_in=Vlaams-Brabant,Belgium,Europe
   is_in:continent=Europe
   is_in:country=Belgium
   is_in:province=Flemish Brabant

Why remove them? For data users they create the impression that this is data 
they can use.
Mappers may be confused about them and waste time maintaining them. They are 
not useful to anyone.

I'd like to collectively make a decision ("go" or "no go") by the end of the 
month, 29 February.
Please send in your comments, even if it's just "not sure, maybe we shouldn't 
do this"!

Kind regards,
Midgard

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


Re: [OSM-talk-be] 17/02: Towards Equal Street Names with Open Data

2020-02-04 Thread Midgard
I'd strongly suggest including an easy default path for when people aren't sure.
If you use a completion metric, choosing "not sure" should imo also increase 
the completion
percentage, so that people are less psychologically pushed to add such data.

Additionally, if someone chose "not sure" and a second person chooses "not 
sure", I would avoid
showing it to any more people.

Why?

Adding name:etymology:wikidata is not that trivial. It requires some 
dedication. In the examples
below, I'm afraid that people who are given just the goal of completing gender 
will be inclined to
just pick one. That's harmful to the data quality.

Some examples from my experience Wikidatafying Blankenberge:
There's just a surname:
- Mametstraat: David, Zosia, Raymond, Clara, Magda, Julien...

or an initial letter and surname:
- J. De Meyerstraat: lots of people match that

or the street has first and last name, but there are multiple people called 
like that:
- Maurits Sabbepad: a writer, but also a theologian

or you can't find any information:
- Frans Feverystraat: The top search results for "Frans Fevery" are 
about the street. :p
  You could create a Wikidata item for them, see 
the last paragraph.

I was planning to bother my municipality to make them help me 
disambiguating those, based on
the records of the street name decision process.

Some other challenges:
Different spellings (should be added to "also known as" in Wikidata when 
found):
- Albert Ruzettelaan: in Wikidata as "Albéric Ruzette"
This could result in duplicate entries.

Often you have to take into account the context:
- Albertstraat and Elisabethstraat running in parallel: Albert I and 
his wife
- lots of surnames of painters in same neighbourhood

Streets named after non-persons. If you use completion metric, how will you 
deal with them? In
Blankenberge, I have been adding the thing they're named after.
- Vissersstraat: fisher

But sometimes, it's just not clear what they're named after:
- Duindistellaan: I can't find any indication that this is a real 
plant. Just a thistle
  that happens to grow in the dunes?
- Colombus (not Columbus)

If it's clear a person has no item yet, one should be created. It's nice if 
some research is done:
what made them famous enough to get a street name? Sometimes you find 
something, sometimes you
don't. In the latter case you can create a rather uninformative item with just 
"instance of: human"
and "sex or gender". But when there's information available on the web, imo it 
would be a shame not
to add it.

Kind regards,
Midgard

Quoting Santens Seppe (2020-02-04 12:52:57)
> True, but of course a nice thing to do.
> 
> Van: Pieter Vander Vennet [mailto:pieterv...@posteo.net]
> Verzonden: dinsdag 4 februari 2020 12:23
> Aan: winfi...@gmail.com; OpenStreetMap Belgium
> Onderwerp: Re: [OSM-talk-be] 17/02: Towards Equal Street Names with Open Data
> 
> Hey Jo,
> 
> Afaik there is no need to create an wikidata for the street.
> Met vriendelijke groeten,
> Pieter Vander Vennet
> On February 4, 2020 12:06:46 PM GMT+01:00, Jo  wrote:
> Hi,
> 
> I did this for one street in Evere: 
> https://www.openstreetmap.org/way/523050554/history
> 
> Took me more than half an hour for a single street (no automation). I created 
> a wikidata entry both for the person and for the street itself. Things are 
> complicated by the bilingual nature of the city and because this street also 
> had an old name.
> 
> Is that what we will be doing? Or did I somehow misunderstand?
> 
> Polyglot
> 
> On Mon, Feb 3, 2020 at 4:34 PM Santens Seppe  wrote:
> Hi community,
> 
> Open Knowledge Belgium, OpenStreetMap Belgium and Wikimedia Belgium want to 
> map all the streetnames by gender in Brussels, as a first step to change the 
> imbalance in reality. We need your help on 17/02 to get the OSM data linked 
> to wikidata.
> Register here to join the mapping effort: 
> https://eventbrite.co.uk/e/towards-equal-street-names-with-open-data-registration-92536026747.
>  And let us know if you can help with the framework.
> 
> 
> more info: 
> https://be.okfn.org/2020/02/03/towards-equal-street-names-with-open-data/
> 
> Please spread the word!
> -Twitter: https://twitter.com/OpenKnowledgeBE/status/1224291464496193538
> -Facebook: https://www.facebook.com/events/2852981998057886/
> -Eventbrite: http://equalstreetnamesbrussels.eventbrite.co.uk/
> 
> 
> Seppe

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


Re: [OSM-talk-be] Infrabel Open Data

2020-01-21 Thread Midgard
Hi Stijn

I think Infrabel Open Data would be useful for
* detecting unmapped tracks and removed tracks,
* the ref=* of railway lines,
* the ref=* and protection of level crossings,
* the milestones.


I fear more problems with the license than you do. I would avoid this data 
source unless we get an
official explicit agreement with Infrabel on this.

We can't fulfull requirement 5.1.3:
> [nl] dat het hergebruik van de Gegevens op geen enkel moment en op geen 
> enkele plaats de commerciële of andere belangen van Infrabel, noch het imago 
> of de reputatie van Infrabel schaadt;
> [fr] à ce qu'à tout moment et à tout endroit, la Réutilisation des Données ne 
> porte pas atteinte aux intérêts commerciaux ni à un quelconque autre intérêt 
> d'Infrabel, et ne nuira pas à l'image ni à la réputation d'Infrabel ;

5.1.5 would *require* something to keep updating it:
> [nl] de updates van de door de Licentienemer hergebruikte gegevens van 
> Infrabel die, indien van toepassing, door Infrabel op het Platform zullen 
> worden gepubliceerd (behalve in het geval van Hergebruik voor historische 
> doeleinden), te respecteren en onverwijld te integreren;
> [fr] à respecter et intégrer sans délai les mises à jour des Données 
> d'Infrabel réutilisées par le Preneur qui seront, le cas échéant, publiées 
> par Infrabel sur la Plateforme (sauf pour les cas de Réutilisation à des fins 
> historiques) ;

I'm not sure how we should interpret 5.1.7 in the context of OSM; it looks like 
mappers would be
required to report errors to Infrabel:
> [nl] Infrabel, zodra zulks [de Licentienemer] ter kennis komt, te informeren 
> over foutieve, ontbrekende of onvolledige Gegevens, zodat deze binnen een 
> redelijke termijn kunnen worden aangepast.
> [fr] à informer Infrabel, dès que [le Preneur de licence] en a connaissance, 
> de l'existence de Données erronées, manquantes ou incomplètes, afin qu’elles 
> puissent être adaptées dans un délai raisonnable ;

I think we cannot fulfill 5.1.4 since we don't know where our data ends up:
> [nl] na te gaan of het Hergebruik niet leidt tot een vertekening van de 
> betekenis, het informatieve karakter of het doel van de Gegevens;
> [fr] à vérifier que la Réutilisation n’entraîne pas une dénaturation du sens, 
> du caractère informationnel ou de l’objet des Donnees ;

Like you say, also 5.1.6 is a bit vague in the context of OSM.

Kind regards,
Midgard


Quoting Stijn Rombauts via Talk-be (2020-01-17 20:41:41)
> Hi,
> There is this page (1), which has a wealth of interesting information for 
> those who want to waste their time updating, improving and correcting the 
> railway related things in OSM. As far as I can see the licence is OK, except 
> for point 5.1.6 which requires us to mention the Open Data Infrabel-platform 
> as a source, with the date of the last update. But does it suffice to add 
> them to this page (2)? Perhaps with ... "These data are being updated 
> continuously." ;-)
> Regards,
> StijnRR

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