Re: [OSM-talk-be] error for revert a changeset

[Jo]

Hi, have a look at the relations referencing the way in the relation
editor. One of the members will seem 'translucent'. Remove it from the
relation, as it's pointing to the way that doesn't exist anymore.


Polyglot

On Thu, Oct 15, 2020 at 11:53 PM DJ_frombelgium 
wrote:

> Hi
>
> DJ_frombelgium, a mapper in wallonia (big building contributor)
>
> I write because i need some help for a changeset that a could revert on
> josm
>
> I explain.
> In Namur a roundabout (Boulevard Cauchy) have change and now it's not a
> roundabout, way have change a lot (with traffic signals, revert of road
> direction and other)
> The community has change the map very quickly, but now i see a a part of
> the changeset  91713233  has erase everything and redraw the map wit the
> sat image...
>
> https://www.openstreetmap.org/changeset/91713233#map=19/50.46860/4.86838
>
> Before the changeset  (image of my backup of 01/04/2020)
> https://www.zupimages.net/viewer.php?id=20/42/fqfm.png
>
> After the changeset
> https://www.zupimages.net/viewer.php?id=20/42/7e3l.png
>
> It's too much work for redraw for me (because i never use "member"
> relation, and i dont want do a mistake)
>
> So i've try a revert in Josm with the plugin.
>
> i download the map, select way that i would revert, -> "revert selection
> and restore deleted object"
> That ok, but when i try to upload the changeset i've somes conflict that
> i couldn't resolve...
>
> (i have the error in french but i "translate")
>   "error for delete way 852742595, there a reference for relation
> 114261. 2314735 . 11686987
>
> and i cant find this way, and josm conflict said nothing...
>
> Thats probably very basic but not for me.
>
> Help are appreciated
>
>
> Thanks
>
> ___
> 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] Request to change the cycle highway network tag

[Jo]

Hi Wannes and Frank,

I think that is about the numbered node network. That's a different network
from the cycle_highway network. We tag that one at the rcn level. Of course
it's odd if the node numbers differ between 2 renderings.

Jo

On Wed, Oct 7, 2020 at 12:43 PM Frank Vdm  wrote:

> I see difference in node numbers, view arrond st Vith.
> https://cycling.waymarkedtrails.org/#?map=14!50.2864!6.1335
> https://www.ostbelgien.eu/nl/fiets/fietsrouteplaner
>
> Op wo 7 okt. 2020 om 11:29 schreef Wannes Soenen :
>
>>
>>
>> Op 7 okt. 2020, om 10:40 heeft Jo  het volgende
>> geschreven:
>>
>> In Wallonia they don't have cycle highways yet, but they have had RaVeL
>> for longer than we do in Flanders. OK, it's not a network yet, but that can
>> change.
>>
>>
>> https://www.ostbelgien.eu/nl/fiets/fietsrouteplaner
>>
>> Eastbelgium (German speaking part of Wallonia) has a cycle network with
>> numbers and signposts. It contains the Vennbahn (which is part of the RaVel)
>> (Also a walking network at
>> https://www.ostbelgien.eu/nl/wandelen/wandelrouteplaner )
>>
>> ___
>> 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

Re: [OSM-talk-be] Request to change the cycle highway network tag

[Jo]

I don't have big issues with prepending a prefix. Having said that, if the
issue is that they are signposted differently in each country, here in
Belgium they are likely to become signposted differently depending on the
region.

The way I understood it, in Flanders it's Fxyz. In Brussels it would be
Cxyz, where xyz would be the same number as in Flanders, for example, F3
would continue as C3, F203 as C203. Anyway, that was the plan about a year
ago, not sure if it's still the case. Actually F203 already continues to
Diamant, but according to that logic it should become C203 west of Tollaan.
It runs parallel to the E40 highway for the last stretch. Last time I went
there, nothing was signposted, but ofc, I went a little too early. It was
not quite finished.

In Wallonia they don't have cycle highways yet, but they have had RaVeL for
longer than we do in Flanders. OK, it's not a network yet, but that can
change.

Will cycle_network=BE:cycle_highway be sufficient, or do we need to
subdivide it further for the regions? Even though the signposting might be
different between Flanders and Brussels, the plan is still to have 2
networks that interconnect seamlessly.

Jo



On Wed, Oct 7, 2020 at 9:53 AM s8evq  wrote:

>  I think the arguments of Minh Nguyễn are valid.  It wouldn't be a big
> deal to change cycle_network=cycle_highway to
> cycle_network=BE:cycle_highway for example (or to
> cycle_network=BE:fietssnelweg). I would additionally also add
> cycle_highway=yes.
>
> On Tue, 6 Oct 2020 20:53:06 +0200, Pieter Vander Vennet <
> pieterv...@posteo.net> wrote:
>
> > Hello everyone,
> >
> > Minh NGuyen had the following remark on the wiki
> > <
> https://wiki.openstreetmap.org/wiki/Talk:Tag:cycle_network%3Dcycle_highway
> >
> > about the current tagging scheme of the cycle highways.
> >
> > Anyone any thought on it?
> >
> >
> > Incompatible with cycle_network
> >
> > This tag is incompatible with the predominant usage of cycle_network
> > <https://wiki.openstreetmap.org/wiki/Key:cycle_network>=*. This key was
> > originally intended to identify a specific network with uniform
> > signage – a renderer was supposed to be able to choose a shield based on
> > a combination of cycle_network
> > <https://wiki.openstreetmap.org/wiki/Key:cycle_network>=* and ref
> > <https://wiki.openstreetmap.org/wiki/Key:ref>=*. But it appears that
> > cycle highways are signposted and numbered differently in each country,
> > so there's no such cycle network as "cycle highway":
> >
> >   *
> > <
> https://wiki.openstreetmap.org/wiki/File:F7_teller_-_Gent_-_Kortrijk_-_ter_hoogte_van_station_Deinze.jpg
> >
> >
> > Belgium
> >
> >   *
> > <https://wiki.openstreetmap.org/wiki/File:2019Radschnellweg.jpg>
> >
> > Germany
> >
> >   *
> > <
> https://wiki.openstreetmap.org/wiki/File:Fietssnelweg_F35_at_Go_Planet.jpg
> >
> >
> > Netherlands
> >
> > A renderer would have to perform a spatial query to reliably display the
> > correct shield for each of these routes, somewhat undermining the push
> > to have renderers use route relations instead of ref
> > <https://wiki.openstreetmap.org/wiki/Key:ref>=* tags on ways.
> >
> > We already made this mistake once by repurposing the network
> > <https://wiki.openstreetmap.org/wiki/Key:network>=lcn/rcn/ncn tags for
> > routes outside the United Kingdom, leading to the otherwise redundant
> > key cycle_network
> > <https://wiki.openstreetmap.org/wiki/Key:cycle_network>=* as a
> > workaround. Let's avoid making this mistake again by deprecating
> > cycle_network
> > <https://wiki.openstreetmap.org/wiki/Key:cycle_network>=cycle_highway
> > <https://wiki.openstreetmap.org/wiki/Tag:cycle_network%3Dcycle_highway>
> > in favor of country-prefixed values like cycle_network
> > <https://wiki.openstreetmap.org/wiki/Key:cycle_network>=NL:cycle_highway
> > <
> https://wiki.openstreetmap.org/w/index.php?title=Tag:cycle_network%3DNL:cycle_highway&action=edit&redlink=1
> >,
> > or by choosing a different key altogether like cycle_highway
> > <
> https://wiki.openstreetmap.org/w/index.php?title=Key:cycle_highway&action=edit&redlink=1
> >=yes.
> >
> >
> > – Minh Nguyễn <https://wiki.openstreetmap.org/wiki/User:Minh_Nguyen> ^💬
> > <https://wiki.openstreetmap.org/wiki/User_talk:Minh_Nguyen> 00:51, 5
> > October 2020 (UTC)
> >
> > --
> > Met vriendelijke groeten,
> > Pieter Vander Vennet
> > ___
> > 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

[OSM-talk-be] Hoppin / Mobipunt

[Jo]

Hi,

I wanted to map our shiny new Hoppin points meant to group sharing
facilities for bicycles and cars + public transport.

https://www.openstreetmap.org/relation/11683352/history#map=16/50.8633/4.7005
https://www.openstreetmap.org/relation/11683353#map=18/50.86545/4.69504

are my first attempts.

I used a site relation, because we already have tags for the amenities that
form part of the group. They are supposed to be concentrated in a 'point',
but sometimes the bus or train stops are a bit further away.

There should also be a sign, possibly with a map on them, but I didn't map
those yet.

For those I thought of

tourism=information
information=board
maybe
board_type


Any comments?

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

Re: [OSM-talk-be] regional cycle routes in Brussels

[Jo]

Yes, I'll look at those as well.

Jo

On Thu, Sep 3, 2020 at 1:00 PM Yves bxl-forever 
wrote:

> Hello,
>
> Thanks for this.
>
> @Polyglot, I saw you updated numbered cycle routes (1 to 12).
> The Brussels cycle route network also has 7 routes with letters.  I
> suppose we should apply the same change.
> A small circle: https://www.openstreetmap.org/relation/237027
> B middle circle: https://www.openstreetmap.org/relation/116569
> C large circle: https://www.openstreetmap.org/relation/7418111
> CC: Canal/Kanaal: https://www.openstreetmap.org/relation/1119347
> SZ Senne/Zenne valley: https://www.openstreetmap.org/relation/116611
> MM Maalbeek valley: https://www.openstreetmap.org/relation/114235
> PP (King’s Palace): https://www.openstreetmap.org/relation/2133184
>
> Cheers.
> Yves
>
>
> On Thu, 3 Sep 2020 10:40:29 +0200
> Jo  wrote:
>
> > I had a look at them after downloading them using Overpass API and
> started
> > making them continuous where they were 'broken'. So I went ahead and also
> > converted them all to rcn.
> >
> > Jo
> >
> > On Thu, Sep 3, 2020 at 9:41 AM Jo  wrote:
> >
> > > Hi Joost,
> > >
> > > In Flanders it depended more on topology than anything else. We used:
> > >
> > > lcn: for loops
> > > rcn: for the numbered node networks, this logic was taken to rwn and
> rhn
> > > later on
> > > ncn: for long routes going from A to B (LFx) and then later for the
> Fxxx
> > > cycle highways
> > > icn: for European routes going from A to B
> > >
> > > In Brussels rcn doesn't seem to be used and those routes are
> topologically
> > > more similar to the numbered routes system used in Flanders and
> Wallonia.
> > >
> > > I agree with you that it makes more sense to tag them as rcn.
> > >
> > > Jo
> > >
> > > On Thu, Sep 3, 2020 at 9:14 AM joost schouppe <
> joost.schou...@gmail.com>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> I was always a little confused that the regional cycle network is
> mapped
> > >> as lcn in Brussels. Since this network is organized by
> Brussels-the-region,
> > >> not Brussels-the-city, it seems logical that it should have the rcn
> tag. In
> > >> fact, more so than the Flemish cycle node network, which is composed
> of
> > >> several networks and almost by coincidence covers the region.
> > >>
> > >> This is also what we say in the wiki:
> > >>
> > >>
> https://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Cycle_Routes#Itin.C3.A9raires_Cyclables_R.C3.A9gionaux_-_Gewestelijke_Fietsroute
> > >>
> > >> But the example given there (
> https://www.openstreetmap.org/relation/9623
> > >> I believe), is now mapped as an lcn.
> > >>
> > >> Looking at the edit history, it looks like there was a minor edit war
> > >> about this, where user RoRay repeatedly changed it from rcn to lcn
> > >> https://www.openstreetmap.org/changeset/8141976
> > >> https://www.openstreetmap.org/changeset/12902663
> > >> (RoRay is still mapping, still using the not-very helpful default
> > >> changeset description "update")
> > >>
> > >> User BenoitL tried to change it back to rcn (with much better
> changeset
> > >> comments :) - https://www.openstreetmap.org/changeset/12849599), but
> I
> > >> guess he gave up. Polyglot later seems to have mapped most of the
> other
> > >> routes; my guess is he just went with lcn because that's how the
> others
> > >> were mapped.
> > >>
> > >> Apart from the network not showing up when it should on some maps, it
> > >> doesn't really matter much. However, bxl-forever is now mapping
> -actual-
> > >> lcn routes in the Brussels region, operated by Anderlecht
> municipality.
> > >> Example: https://www.openstreetmap.org/relation/11544325
> > >> Putting both types of routes in the same level is just wrong IMHO.
> > >>
> > >> Can anyone provide some more context? Based on my own research, I'd
> > >> suggest we simply retag all the regional operated routes from lcn to
> rcn.
> > >>
> > >> Best,
> > >> Joost Schouppe
> > >> ___
> > >> 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

Re: [OSM-talk-be] regional cycle routes in Brussels

[Jo]

I had a look at them after downloading them using Overpass API and started
making them continuous where they were 'broken'. So I went ahead and also
converted them all to rcn.

Jo

On Thu, Sep 3, 2020 at 9:41 AM Jo  wrote:

> Hi Joost,
>
> In Flanders it depended more on topology than anything else. We used:
>
> lcn: for loops
> rcn: for the numbered node networks, this logic was taken to rwn and rhn
> later on
> ncn: for long routes going from A to B (LFx) and then later for the Fxxx
> cycle highways
> icn: for European routes going from A to B
>
> In Brussels rcn doesn't seem to be used and those routes are topologically
> more similar to the numbered routes system used in Flanders and Wallonia.
>
> I agree with you that it makes more sense to tag them as rcn.
>
> Jo
>
> On Thu, Sep 3, 2020 at 9:14 AM joost schouppe 
> wrote:
>
>> Hi,
>>
>> I was always a little confused that the regional cycle network is mapped
>> as lcn in Brussels. Since this network is organized by Brussels-the-region,
>> not Brussels-the-city, it seems logical that it should have the rcn tag. In
>> fact, more so than the Flemish cycle node network, which is composed of
>> several networks and almost by coincidence covers the region.
>>
>> This is also what we say in the wiki:
>>
>> https://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Cycle_Routes#Itin.C3.A9raires_Cyclables_R.C3.A9gionaux_-_Gewestelijke_Fietsroute
>>
>> But the example given there (https://www.openstreetmap.org/relation/9623
>> I believe), is now mapped as an lcn.
>>
>> Looking at the edit history, it looks like there was a minor edit war
>> about this, where user RoRay repeatedly changed it from rcn to lcn
>> https://www.openstreetmap.org/changeset/8141976
>> https://www.openstreetmap.org/changeset/12902663
>> (RoRay is still mapping, still using the not-very helpful default
>> changeset description "update")
>>
>> User BenoitL tried to change it back to rcn (with much better changeset
>> comments :) - https://www.openstreetmap.org/changeset/12849599), but I
>> guess he gave up. Polyglot later seems to have mapped most of the other
>> routes; my guess is he just went with lcn because that's how the others
>> were mapped.
>>
>> Apart from the network not showing up when it should on some maps, it
>> doesn't really matter much. However, bxl-forever is now mapping -actual-
>> lcn routes in the Brussels region, operated by Anderlecht municipality.
>> Example: https://www.openstreetmap.org/relation/11544325
>> Putting both types of routes in the same level is just wrong IMHO.
>>
>> Can anyone provide some more context? Based on my own research, I'd
>> suggest we simply retag all the regional operated routes from lcn to rcn.
>>
>> Best,
>> Joost Schouppe
>> ___
>> 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] regional cycle routes in Brussels

[Jo]

Hi Joost,

In Flanders it depended more on topology than anything else. We used:

lcn: for loops
rcn: for the numbered node networks, this logic was taken to rwn and rhn
later on
ncn: for long routes going from A to B (LFx) and then later for the Fxxx
cycle highways
icn: for European routes going from A to B

In Brussels rcn doesn't seem to be used and those routes are topologically
more similar to the numbered routes system used in Flanders and Wallonia.

I agree with you that it makes more sense to tag them as rcn.

Jo

On Thu, Sep 3, 2020 at 9:14 AM joost schouppe 
wrote:

> Hi,
>
> I was always a little confused that the regional cycle network is mapped
> as lcn in Brussels. Since this network is organized by Brussels-the-region,
> not Brussels-the-city, it seems logical that it should have the rcn tag. In
> fact, more so than the Flemish cycle node network, which is composed of
> several networks and almost by coincidence covers the region.
>
> This is also what we say in the wiki:
>
> https://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Conventions/Cycle_Routes#Itin.C3.A9raires_Cyclables_R.C3.A9gionaux_-_Gewestelijke_Fietsroute
>
> But the example given there (https://www.openstreetmap.org/relation/9623
> I believe), is now mapped as an lcn.
>
> Looking at the edit history, it looks like there was a minor edit war
> about this, where user RoRay repeatedly changed it from rcn to lcn
> https://www.openstreetmap.org/changeset/8141976
> https://www.openstreetmap.org/changeset/12902663
> (RoRay is still mapping, still using the not-very helpful default
> changeset description "update")
>
> User BenoitL tried to change it back to rcn (with much better changeset
> comments :) - https://www.openstreetmap.org/changeset/12849599), but I
> guess he gave up. Polyglot later seems to have mapped most of the other
> routes; my guess is he just went with lcn because that's how the others
> were mapped.
>
> Apart from the network not showing up when it should on some maps, it
> doesn't really matter much. However, bxl-forever is now mapping -actual-
> lcn routes in the Brussels region, operated by Anderlecht municipality.
> Example: https://www.openstreetmap.org/relation/11544325
> Putting both types of routes in the same level is just wrong IMHO.
>
> Can anyone provide some more context? Based on my own research, I'd
> suggest we simply retag all the regional operated routes from lcn to rcn.
>
> Best,
> Joost Schouppe
> ___
> 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] Fietsstraatzones in Leuven and a question about zones inside zones

[Jo]

I added some A23 here and there around Leuven. It made me realise I don't
have recent Mapillary images for many streets in Leuven to determine where
exactly those school zone30 start and end... Time to go out and cycle to
make more pictures, I guess.

Jo

On Mon, Aug 31, 2020 at 9:52 AM Tim Couwelier 
wrote:

> F4a should remain yes, despite both implying the same speed limit, UNLESS
> the local gov removed the F4a signs due to the 'fietszone' completely
> overlapping with the 'zone 30'.
> Ideally, for the 'zone 30', differentiate between 'normal' with F4a only
> and 'school- zone 30'  (F4a + A23)
>
> If there's living streets within, I'd say the restrictions 'stack': no
> overtaking, 20 km/h.
> There may actually be a slight nuance here - generally in case of possible
> contradiction, the rule applies 'traffic sign takes priority over traffic
> rules'. The speed limits in both fietszone and living_street are traffic
> rules, but this might leave a loophole where 'zone 30' as a sign takes
> priority.
>
> There used to be a loophole where a C43 70km/h would trump the 50km/h
> speed limit in a built up area until the first intersection (extent of the
> validity for the C43) but afaik that's been 'patched' in legislation now.
> This might just be an unforeseen edge case opening another such loophole,
> although I'm not 100% sure on this.
>
>
> Sidenote: I think I agree with not making a seperate sign for this, but
> just giving it a 'zonal' extent. If anything, F4a/b signs existing as such
> is confusing. But then again, so were the original streetsigns as they were
> semi-assumed to be zonal, but the law wasn't overly specific (and didn't
> mention it being zonal). Readability, in database or map format, is far
> better if you speak of 'zonal C43' and 'zonal F111' without having to know
> another number for the same type of thing.
>
> Op zo 30 aug. 2020 om 14:50 schreef Jo :
>
>> Hi,
>>
>> I added the new fietsstraatzones in Leuven to the map. They will be in
>> vigor on September 1st. The legislator didn't create a separate sign, they
>> just decided that it's allowed use F111 on a ZONE sign...
>>
>> I do like to distinguish between the 'real' cycle streets and the
>> 'pretenders', so the ones inside zones and the ones connecting the zones, I
>> guess. I used BE:F111zone as the traffic_sign. I may have done something
>> silly though, as I removed the F4a from the traffic sign tag.
>>
>> If you search for F111 you get all.
>> If you search for F111zone you get all the ones inside the zones.
>> If you search for "F111 -F111zone" in JOSM, you get only the cyclestreets
>> with an actual cycle street sign.
>>
>> If you search for F4a you get all the streets inside the zone30, but the
>> cycle streets are not included in that. How do we want to work with zones
>> within zones? There are also parking zones...
>>
>> Should I have put traffic_sign=BE:F111;BE:F4a;BE:F1a ?
>>
>> Initially I didn't because both are limited to 30km/h, but now I'm
>> thinking I should have.
>>
>> What about the living_street ways? They are also inside the zone30 (and
>> in built-up area), but the traffic rules that apply are BE:F12a. Do we add
>> BE:F12a;BE:F4a;BE:F1a ?
>>
>> Jo
>> ___
>> 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

[OSM-talk-be] Fietsstraatzones in Leuven and a question about zones inside zones

[Jo]

Hi,

I added the new fietsstraatzones in Leuven to the map. They will be in
vigor on September 1st. The legislator didn't create a separate sign, they
just decided that it's allowed use F111 on a ZONE sign...

I do like to distinguish between the 'real' cycle streets and the
'pretenders', so the ones inside zones and the ones connecting the zones, I
guess. I used BE:F111zone as the traffic_sign. I may have done something
silly though, as I removed the F4a from the traffic sign tag.

If you search for F111 you get all.
If you search for F111zone you get all the ones inside the zones.
If you search for "F111 -F111zone" in JOSM, you get only the cyclestreets
with an actual cycle street sign.

If you search for F4a you get all the streets inside the zone30, but the
cycle streets are not included in that. How do we want to work with zones
within zones? There are also parking zones...

Should I have put traffic_sign=BE:F111;BE:F4a;BE:F1a ?

Initially I didn't because both are limited to 30km/h, but now I'm thinking
I should have.

What about the living_street ways? They are also inside the zone30 (and in
built-up area), but the traffic rules that apply are BE:F12a. Do we add
BE:F12a;BE:F4a;BE:F1a ?

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

Re: [OSM-talk-be] Import of GPX files for marked trails in OSM / Import de traces GPX pour promenades balisées dans OSM

[Jo]

Please have a look at JOSM's PT_Assistant plugin for helping with this. For
foot/walking/hiking and bicycle relations, there is an additional button,
"routing helper". Originally it only worked for public transport, but now
it works for all route relations that describe itineraries.

The GPX tracks can be shown with various options (thicker line, colouring)
in the background. That's standard JOSM.

Polyglot

On Thu, Aug 20, 2020 at 7:53 AM Matthieu Gaillet 
wrote:

>
> Génial ! Count me in. J’ai l’expérience de ce genre de relation et suis
> donc opérationnel.
>
> Matthieu G.  (en mode mobile)
>
> Le 20 août 2020 à 07:46, Julien Minet  a écrit :
>
> 
> Hello / Bonjour,
>
> Thanks to an active lobbying of Jacques Fondaire, contributor in Aubange,
> we had the explicit right (well, an email) to use some GPX files from the
> local tourism offices from the province of Luxembourg for completing the
> marked trails in South-Luxembourg in OSM. We did not receive all the tracks
> yet but in total there are about 120 walking marked trails in the Parc
> Naturel Haute-Sure Forêt d'Anlier.
>
> This is not an automatic import since, to the best of my knowledge, there
> is no automatic tool to convert some GPX into OSM relations. So we have to
> manually add these relations based on the GPX information. From my
> experience, it takes about 15 min. per relation to do so (in JOSM). I plan
> to write a few lines about this import somewhere on the OSM wiki such as
> here
> .
>
>
> If anyone wants to help to enter this information in OSM, just let me
> know! If you want to know how to add some marked trails in OSM, have a look
> at this page  and that
> one
> 
> for Belgian specificities. A nice app rendering all these routes is
> https://hiking.waymarkedtrails.org/.
>
> // en français //
>
> Grâce à un lobbying actif de Jacques Fondaire, collaborateur à Aubange,
> nous avons eu le droit explicite (enfin, un email) d'utiliser certains
> fichiers GPX des offices de tourisme locaux de la province de Luxembourg
> pour compléter les sentiers balisés du Sud-Luxembourg dans OSM. Nous
> n'avons pas encore reçu tous les fichiers, mais il s'agit d'environ 120
> pistes balisées dans le Parc Naturel Haute-Sure Forêt d'Anlier.
>
> Il ne s'agit pas d'une importation automatique car, à ma connaissance, il
> n'existe pas d'outil automatique permettant de convertir des GPX en
> relations OSM. Nous devons donc ajouter manuellement ces relations sur la
> base des GPX. D'après mon expérience, il faut environ 15 minutes par
> relation pour le faire (dans JOSM). J'ai l'intention d'écrire quelques
> lignes sur cette importation quelque part, par exemple ici
> .
>
>
> Si quelqu'un veut aider à saisir ces informations dans OSM, faites-le moi
> savoir ! Si vous voulez savoir comment ajouter quelques pistes balisées
> dans OSM, jetez un coup d'oeil à cette page
>  et à celle-ci
> 
> (spécificités belges). Une belle application rendant tous ces parcours est
> https://hiking.waymarkedtrails.org/.
>
> Happy mapping,
>
> juminet
>
> ___
> 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

Re: [OSM-talk-be] Mapping disapPeared vicinal paths

[Jo]

Meerdaalwoud is mapped quite well. I think we are at least 3 experienced
mappers doing so. Not always easy with aerial imagery alone and GPX gets
distorted, although that has improved a lot over the past 10 years.

I'm afraid there is not much chance to still find this person alive now,
after more than 2 weeks of intensive searching.


Jo

On Sun, Aug 9, 2020, 14:27 Philippe Casteleyn 
wrote:

> Recently I was searching for a disappeared  person in the woods.
>
> Looking at OSMAnd I advised the group leader that we could split a search
> parcel in two because the small  path went to the next wider path.
>
> I was happy that I was luckily correct.
>
> In my region (Mechelen) I have seen that not all ditches are mapped.  I
> find them difficult to map.
>
> Neither are fences.
>
>
>
> The person is still missing.
>
>
> ___
> 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] Help to young active men in kivu

[Jo]

If you need someone to teach JOSM online, I can help with that. I can't do
much about prices for internet access.

Polyglot

On Wed, Aug 5, 2020, 13:02 CHAVEZ CIKURU  wrote:

> Hello Prof. Nicolas, Hello Georges, Hello everyone.
>
> Hope you are well.
>
> Here in Kivu, we already use Telegram a lot, we had difficulties being
> able to create accounts on Riot.
>
> In KIVU as in the whole of the national territory, these are the foreign
> communication companies (VODACOM, ORANGE, AIRTEL and AFRICEL in Kinshasa)
> which provide us with the connection, and this is what causes it to have
> the prices high levels of Internet access due to much higher taxes and the
> weak control of the Congolese authorities on the sale of Internet packages,
> weak control of consumption, etc.
>
> I also don't know what the cost of opening a regional service
> communication with Riot can be; maybe it can be done independently without
> accepting the terms of VODACOM, ORANGE or AIRTEL. On this issue, I want to
> try to contact these different companies for clarification.
>
> I wish you a good day and good work.
>
> Yours truly.
>
> Alain
>
> Le ven. 31 juil. 2020 à 14:02, Georges Khaznadar <
> georges.khazna...@free.fr> a écrit :
>
>> Hello Nicolas, hello everybody,
>>
>> using Riot rather than Telegram does not change much when one cannot
>> master the web servers which are providing the service.
>>
>> As far as I undestood, the high prices of Internet access in Kivu are
>> due to foreign companies trusting the scarse hardware network.
>>
>> If I live in Kivu, and if I want to create a small communication
>> company, what would be the cost of opening a regional communication
>> service, eventually featuring Riot? Can I do it independently, or must I
>> accept the conditions of Orange, Airtel or Vodacom?
>>
>> Best regards,   Georges.
>>
>> Nicolas Pettiaux a écrit :
>> > Hello,
>> >
>> > A team of active young men in kivu with very limited internet access
>> are looking for help to map better their city of Bukavu and surroundings.
>> >
>> > They have smatphones and expensive connections with low bandwidth.
>> >
>> > They use telegram and email, but I don't know for riot.
>> >
>> > Some are in cc and more are on the mailing list k...@educode.ne
>> >
>> > Much thanks to everyone who van guide and help thème better than I can
>> or do.
>> >
>> > Regards,
>> >
>> > Nicolas
>> >
>> > --
>> > Nicolas Pettiaux
>> > --
>> > Nicolas Pettiaux, PhD - tel +32.496.24.55.01
>> > Collaborer pour mieux enseigner - https://wiki.educode.be
>> > Educode accompagne les écoles face aux défis du numérique
>> > Envoyé de mon fairphone - veuillez excuser la brièveté
>> >
>>
>> --
>> Georges KHAZNADAR et Jocelyne FOURNIER
>> 22 rue des mouettes, 59240 Dunkerque France.
>> Téléphone +33 (0)3 28 29 17 70
>>
>>
>
> --
>
> *CIKURU KAMERA Alain Chavez*
>
> Technicien en Développement Rural et consultant en matière de développement
>
> *Adresse* : *55, Av. Cibera/A, Q. Nkafu, C. Kadutu, Ville de Bukavu RD.
> Congo*
>
> *Tél* : +243 97 57 57 359, +243 85 23 36 465
>
> *Skype* : Alain Chavez Cikuru Kamera
>
> *Linkedln* : Chavez Alain Cikuru Kamera
>
> *Facebook* : Alain Kamera Cikuru Chavez
> ___
> 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

[OSM-talk-be] Mappen van fietssnelwegen, mapping of cycling highways

[Jo]

English below

Hallo,

Het mappen van fietssnelwegen op OSM is een beetje een uitdaging.
Persoonlijk heb ik graag routerelaties die een continue reeks van ways
zijn, maar de fietssnelwegen liggen er nagenoeg nergens over hun volle
lengte. Ik vind het interessant om de geplande fietssnelwegen nu al op de
kaart te kunnen zetten, maar anderzijds wil ik ook aangeven wat de
alternatieve omleidingen zijn, aangenaam fietsbaar zonder al teveel omweg.

Ik meen dat ik nu een goede oplossing gevonden heb: superroute-relaties.

Hiermee kunnen we de deeltrajecten in route-relaties stoppen, al dan niet
met proposed (zodat ze in stippellijn op de cyclemap getoond worden).

Deze route-relaties kunnen dan in superroutes worden opgenomen. Hier en
daar is het ook zo dat fietssnelwegen elkaar overlappen. F2 en F44, F3 en
F8. Ook voor deze gemeenschappelijke stukken zijn afgesplitste
route-relaties een goede oplossing.

josm-latest laat sinds een dikke maand toe om te zien dat
superroute-relaties continu zijn. (als de laatste way in de vorige route
zijn laatste node gemeenschappelijk heeft met de eerste way zijn eerste
node).

Ik ben gaandeweg alles aan het omzetten. F3, F8, F24, F25, F26 en nog een
paar zijn al klaar. Gisteren F2 gedaan, nu ben ik bezig met F44.

Dit is een goede query om ze te downloaden in JOSM:

[out:xml][timeout:190][bbox:{{bbox}}];
(
  nwr["cycle_network"="cycle_highway"];
);
(._;>;);
out meta;

(expert mode activeren en dan 2e tab, download from Overpass)

Hi,

Mapping cycling highways on OSM is a bit of a challenge. Personally I like
for route relations to have continuous sequences of ways, but there are
very few cycle highways that are already realised over their full length. I
think it's interesting to already include the planned cycling highways, but
their practical use for routing is negligent. So it seems important to me
to also include how to get from A to B today, following ways that are nice
to ride along with overly big detours.

I think I found a good solution to have my cookie and eat it too:
superroute relations.

This allows us to put the different parts in separate route relations.
Those composed of highway=proposed/proposed=cycleway tagged with
state=proposed, so they are shown in a dashed line on the cyclemap
rendering.

Then those route relations can be used to compose superroute relations. It
also happens that cycle highways overlap, f.e.  F2 en F44 in Gent, F3 en F8
in Leuven. Also for these parts it's interesting to split them off in
separate route relations.

For about a month, maybe 2 now, josm-latest also shows continuity for
superroute relations.

This is a good query to download them in JOSM:

[out:xml][timeout:190][bbox:{{bbox}}];
(
  nwr["cycle_network"="cycle_highway"];
);
(._;>;);
out meta;

(activate expert mode and then 2nd tab, download from Overpass)

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

Re: [OSM-talk-be] privacy ed

[Jo]

Not only their faces, also license plates. And if you're doing it manually
maybe also stickers with recognisable information.

Jo

On Fri, May 15, 2020, 19:38 Marc Gemis  wrote:

> Hello,
>
> I see no difference between contributing to OpenStreetMap via JOSM and
> iD or StreetComplete.
> Mapping a house, street, waste bin, etc. will not break any privacy.
> We do not map the names of the inhabitants of a house. Mapping items
> from someone's garden based on aerial imagery might be on the
> borderline of what is allowed. However, I do map sheds, ponds and
> swimming pools.
>
> Taking pictures of people is not a problem, it's what you do with them
> afterwards that is important. If you use the image yourself and map
> the things you see on them from your PC, it doesn't matter that there
> are people.
> If you post the image on a public website (as you do via
> StreetComplete), you have to make sure that there are no people or
> that their faces are blurred (e.g. uploading to Mapillary is OK I
> think).
>
> Of course, you cannot enter private grounds.
>
> On Thu, May 14, 2020 at 3:49 PM wbrt  wrote:
> >
> > Hello,
> >
> > a question about privacy of people in general (not the mapper) (in
> Belgium)
> >
> > when contributing using for example streetcomplete:
> https://github.com/westnordost/StreetComplete
> > answering the questions, i suppose this is ok juridical?
> >
> > when taking pictures to make it clear for the mappers,
> > i guess this also ok, as long as people are not recognizable in it?
> >
> > or am i wrong?
> > and can you get in trouble for contributing to openstreetmap?
> >
> > The info i found:
> >
> https://wiki.openstreetmap.org/wiki/Limitations_on_mapping_private_information
> >
> > kr
> > ___
> > 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

Re: [OSM-talk-be] Weggetje verdwenen, hoe terug ?

[Jo]

Er is nog een 'truuk' om verwijderde ways terug te halen. (werkt enkel voor
ways).

Start editeersessie met Potlatch2.

Je wilt eigenlijk de vorige versie van Potlatch gebruiken, haal daarom de 2
weg uit de url in de adresbalk...

De originele versie van Potlatch maakt gebruik van een niet gedocumenteerde
'feature' in de API.

Er is een knop om deleted ways te zien.

Jo

On Tue, May 12, 2020 at 1:07 PM Tim Couwelier 
wrote:

> Bijlage bleeft hangen wegens groter dan 80kb, maar hierbij even ter
> illustratie hoe je ze kan traceren met de 'skyview' laag.  Is een soort
> hoogtemodelweergave op grondniveau, de bomen zie je dus niet.. en het pad
> wordt zichtbaar.
>
> https://framapic.org/r01ExtbzPorU/Z1Zri8oU24QM.jpg
>
> (ik had al even afzonderlijk gemaild naar de betrokken persoon, maar
> mogelijks zijn er nog mensen waarvoor dit een meerwaarde kan betekenen.)
>
>
> Op di 12 mei 2020 om 10:57 schreef Wannes Soenen :
>
>> Ok, dan lijkt me het het “handigste” dat ik een GPX neem en het pad terug
>> teken (want het zit onder de bomen)
>> Die relaties, en GR enz toevoegen/verleggen, zal ik eerst eens moeten
>> bestuderen, want dat heb ik nog nooit gedaan.
>>
>> Op 12 mei 2020, om 10:53 heeft Sander Deryckere 
>> het volgende geschreven:
>>
>> Hallo,
>>
>> Het hangt er van af hoe lang de wijziging geleden is.
>> Als het vrij recent is (enkele dagen), kan je de geschiedenis van een
>> gebied opvragen (de geschiedenis knop op de hoofdpagina).
>> Maar deze wijziging lijkt langer geleden te zijn, dus valt dit moeilijk
>> te bespeuren.
>>
>> Wat je wel kan is bekijken welke objecten waarschijnlijk ook gewijzigd
>> zijn bij die aanpassing (zoals het fietspad dat nu gebruikt wordt).
>>
>> 
>>
>> Als je dat fietspad selecteert, en de geschiedenis opvraagt, dan kom je
>> hier terecht: https://www.openstreetmap.org/way/24520913/history
>>
>> Er is dus in de laatste maanden tamelijk wat aangepast aan het pad.  In
>> het bijzonder zie ik een wijziging van 4 maand geleden met het commentaar 
>> "cycleroute
>> 03-04 update: broken (again), now due to missing segments". Wat er op
>> wijst dat iemand er voor die regio heeft aangepast, zonder rekening te
>> houden met de relaties.
>>
>> Het is dus waarschijnlijk niet 1 iemand die de relatie verlegd heeft,
>> maar iemand heeft dat pad verwijderd, en iemand anders heeft de relatie
>> opnieuw verbonden met de bestaande paden...
>>
>> Mvg,
>> Sander
>>
>> Op di 12 mei 2020 om 10:18 schreef Wannes Soenen :
>>
>>> Hoi,
>>>
>>> Ik zie dat er zeer lokaal, een wegje verdwenen is op de kaart.
>>> Ik kan dat er zelf terug op gaan zetten, maar dan is de kans groot dat
>>> diegene die de edit gedaan heeft het weer wist.
>>>
>>> Hoe kan ik 1) zien wie de edit deed, of er een comment bij was? 2)
>>> rollback doen
>>>
>>> Het betreft een pad net ten zuiden van het Ringfietspad op
>>> https://www.openstreetmap.org/edit#map=18/51.20462/4.44275
>>> De plaatselijke merkkringen van het GR-pad (en van op de GR site) loopt
>>> wel degelijk over dat pad, niet over het fietspad.
>>> Dus, de huidige gemaakte situatie is fout, want 1) pad is niet meer
>>> gemapt 2) GR loopt over het fietspad.
>>> ___
>>> 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-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] archives - streams and rivers

[Jo]

In Dutch it's very likely that the spelling 'progressed' in the meantime.

How does one search for a specific map of a river in the region of interest?

Jo

On Sat, Apr 25, 2020 at 11:19 AM Pierre Parmentier <
pierrecparment...@gmail.com> wrote:

> Hello,
>
> The Belgian State Archives have put the following archives online:
> 'Ministère de l'Intérieur. Plans généraux des cours d'eau non navigables ni
> flottables' (1877-1890).
>
> You can find them via Cartesius.be. They can be useful for
> finding/veryfying the correct names of small streams and rivers. But be
> careful: it appears that in some cases the actual current names (hydronyms)
> are slightly different from what they were at the end of the nineteenth
> century! These maps cover the entire Belgian territory they said but I did
> not check it really ;-)
>
> Two samples:
>
>-
>
> https://search.arch.be/imageserver/topview.php?FIF=510/510_0156_000/510_0156_000_00159_000/510_0156_000_00159_000_0_0003.jp2
>-
>
> https://search.arch.be/imageserver/topview.php?FIF=510/510_0156_000/510_0156_000_00132_000/510_0156_000_00132_000_0_0095.jp2
>
> Pierre P.
> aka foxanddpotatoes
>
> ___
> 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] cycling allong the R4 in Gent

[Jo]

Since both the highway and the cycleway are separate (mostly parallel)
'entities' in OSM, I think it does make sense to use bicycle=use_sidepath.
For routing purposes, it's probably not needed, while editing in JOSM and
for highlighting using MapCSS it is handy to have the tags directly on the
objects they apply to.

Jo

On Thu, Apr 9, 2020 at 12:00 PM Wouter Hamelinck 
wrote:

> Hi,
>
> All three are correct in my opinion. Tbh, I've never really understood the
> use of use_sidepath. The only case where it contains really helpful
> information for me is when that alternative is not mapped. But then there
> is a more efficient solution...
> But I don't really have anything for or against any of the options.
>
> The third option is correct, but is a little uninformative, especially
>> since you actually ARE allowed to cycle on some parts of this same R4
>>
>
> Isn't the first question here if they should be trunk if you are allowed
> to cycle?
>
> wouter
> --
> "Den som ikke tror på seg selv kommer ingen vei."
>- Thor Heyerdahl
> ___
> 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] Fietssnelwegen in Brussel

[Jo]

All I know is that they use a C instead of an F. But for example F3 should
continue as C3. Do you know any that are already realised? I think they are
still in the planning stage.

On Mon, Mar 2, 2020, 3:41 PM Pieter Vander Vennet 
wrote:

> Hi everyone,
>
> Today I discovered that the 'Fietssnelwegen' in the Brussels region are
> missing: https://overpass-turbo.eu/s/Rdy
>
> Is there someone who know why this is? I also suspect that they should
> be tagged there slightly differently.
>
>
> --
> Met vriendelijke groeten,
> Pieter Vander Vennet
>
> ___
> 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] 17/02: Towards Equal Street Names with Open Data

[Jo]

I think the hardest part is figuring out what the name stands for if it is
a former maire of the city or commune. Especially if we only have an
initial for the first name. Sometimes it is possible to find this
information on the internet, often it isn't.

Do we have a way to look into the city's archives?

Jo



On Tue, Feb 11, 2020 at 11:07 AM Jonathan Beliën  wrote:

> Given this workflow, I wonder whether we can drop the focus on Wikipedia
> (to save work/time): 1) If there is an existing Wikipedia page, it will
> probably already be linked to the corresponding Wikidata item. 2) If we put
> a Wikidata tag on a street in OSM, I personally see no reason to add a
> Wikipedia tag as well, as the Wikipedia page can be found through the
> Wikidata item (I now not all data consumers will work like that, but I feel
> they should be educated to do so J )
>
>
> Yes, I thought about adding the `wikipedia` tag if there is a Wikipedia
> page but no wikidata "page" but we could indeed add the `wikipedia` tag
> even if we have the `wikidata` tag !
>
> I guess the link between OSM street and Wikidata item for that street will
> be done beforehand (automagically)? In that case, we could really focus on
> the people behind the street names and only fill in the
> name:etymology:wikidata tag in OSM and/or the ‘named after’ statement in
> Wikidata.
>
>
> Indeed, automagically but (very) carefully !
> Exact process is not defined yet, I'll consult all of you to find the best
> way to do that properly !
> Addition of the tags in OSM will be done no matter what AFTER the event
> but the participant will have access to that information to help them in
> their research of course.
>
> I suppose the participants of the workshop will also have an option to
> indicate 1) is this street named after a person (y/n) 2) which gender does
> the person have (m/f/don’t know)
>
>
> You suppose correctly !
> We'll get all those information during the event !
> But the final process will get the gender from the wikidata "page" (if
> there is a wikidata "page" for every person that have a street with their
> name).
>
> Thanks for the feedback !
>
> Jonathan Beliën
>
>
> Mar 11 févr 2020, à 10:56, Santens Seppe a écrit :
>
> Hi Jonathan,
>
>
>
> Workflow sounds good!
>
> If I may, a few remarks:
>
> ·   Given this workflow, I wonder whether we can drop the focus on
> Wikipedia (to save work/time): 1) If there is an existing Wikipedia page,
> it will probably already be linked to the corresponding Wikidata item. 2)
> If we put a Wikidata tag on a street in OSM, I personally see no reason to
> add a Wikipedia tag as well, as the Wikipedia page can be found through the
> Wikidata item (I now not all data consumers will work like that, but I feel
> they should be educated to do so J )
>
> ·   I guess the link between OSM street and Wikidata item for that
> street will be done beforehand (automagically)? In that case, we could
> really focus on the people behind the street names and only fill in the
> name:etymology:wikidata tag in OSM and/or the ‘named after’ statement in
> Wikidata.
>
> ·   I suppose the participants of the workshop will also have an
> option to indicate 1) is this street named after a person (y/n) 2) which
> gender does the person have (m/f/don’t know)
>
>
>
> Cheers,
>
>
>
> Seppe
>
>
>
>
>
> *Van:* Jonathan Beliën [mailto:l...@jbelien.be]
> *Verzonden:* dinsdag 11 februari 2020 10:16
> *Aan:* talk-be@openstreetmap.org
> *Onderwerp:* Re: [OSM-talk-be] 17/02: Towards Equal Street Names with
> Open Data
>
>
>
> Hello everyone,
>
>
>
> I just find out about this discussion and realize we are currently doing
> the work twice !
>
>
>
> The initial (and main) goal of the project is indeed to link streets in
> Brussels from OpenStreetMap with the wikidata "page" of the person present
> in the streetname !
>
>
>
> BUT we got in contact with Romain (Wikimedia Belgium) and he told us that
> he is working on creating a wikidata "page" for all the streets in Brussels
> and that his works is almost complete !
> So we added that part in our Equal Street Names project !
>
>
>
> For every street in Brussels, we'll add the `wikidata` tag and the
> `name:etymology:wikidata` !
>
>
>
> My workflow is the following :
>
>- Make the list of streets in Brussels ;
>- Since almost all the streets have an `associatedStreet` relation in
>   Brussels, I'll start with that and add the streets missing ;
>   - Take the already existing `wikidata` and
>   `name:etymology:wikidata`

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

[Jo]

OK, in that case, we'll have to go back to the original source, Urbis if we
want to add coordinates for the streets to Wikidata.

I always thought that if I'm the one who adds features to OSM myself, or if
I'm the one who places them at their correct spot, using aerial imagery
that the data was mine and I could contribute it to Wikidata, if that
pleases me. But maybe I shouldn't link back to OSM in that case in the
reference url.

Seppe, Joost and Jonathan's project is about linking through
name:etymology:wikidata to persons, and add those persons to Wikidata if
they don't exist there yet. No addition of geodata involved in that  case.

I know that Romaine has the wish for several years now, to add the streets
of Brussels themselves to Wikidata.

 Cheers,

Jo

On Tue, Feb 11, 2020 at 7:56 AM Marc Gemis  wrote:

> > About the geocoding. If I look at the street in my JOSM, then create a
> node somewhere in the center of it and then add the coordinates of that
> node to Wikidata, did I violate any rights? If it does, we could use Urbis
> data to source coordinates for the whereabouts of the street. I'm not using
> any nodes of the street itself. I do try to link back to openstreetmap (one
> of the ways or associatedStreet relation) in the reference url field.
> >
>
> IMHO, that is a derivative database. You look at OSM data, apply some
> algorithm and create new data.
> AFAIK, the project that Seppe, Joost and Jonathan have will not add
> such data, but if you want to do it, you might contact the LWG to be
> sure it's OK. I doubt it is.
>
> regards
>
> m.
>
___
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

[Jo]

Hi,

I used Overpass API to generate a list of unique street names in the
Brussels Region:

https://docs.google.com/spreadsheets/d/1MsII28mSORExmGhxAFPCON4GK3Zpg-BUbvy8eauy63I/edit?usp=sharing

It is easy to find streets that are not mapped entirely bilingually. I
should have included the id and then created an easy way to link back to
JOSM. Not sure why I didn't think of that before. I might still do it, but
then using the associatedStreet relations, which most of the streets in
Brussels still seem to have. (I'm glad for this, I know it's not a popular
one)

I think we should create wikidata items for the streets themselves as well.

About the geocoding. If I look at the street in my JOSM, then create a node
somewhere in the center of it and then add the coordinates of that node to
Wikidata, did I violate any rights? If it does, we could use Urbis data to
source coordinates for the whereabouts of the street. I'm not using any
nodes of the street itself. I do try to link back to openstreetmap (one of
the ways or associatedStreet relation) in the reference url field.

I agree that if we were to add full polylines based on all the nodes of the
street, there would be an issue, but I don't think anyone wants to do that.

Jo

On Wed, Feb 5, 2020 at 11:25 AM Marc Gemis  wrote:

> As I wrote on Riot, I do hope this event will not copy geocoded data
> from OSM into Wikidata, I think this violates
> https://wiki.openstreetmap.org/wiki/Open_Data_License/Geocoding_-_Guideline
> Please let me know if I'm wrong.
>
> regards
>
> m.
>
> On Tue, Feb 4, 2020 at 12:08 PM 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
> >
> > ___
> > 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] 17/02: Towards Equal Street Names with Open Data

[Jo]

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
>
___
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

[Jo]

A few years ago I created this script to interlink schools in Uganda to
wikidata. No idea if it would be useful:

https://github.com/PolyglotOpenstreetmap/Python-scripts-to-automate-JOSM/blob/master/UseWDTKtoCreateWDitems.py


To run it in JOSM, you'd need the scripting plugin, jython.jar and the
Wikidata Toolkit jar.

I'm proposing to make this simpler for this year's Google Summer of Code,
so all comments are welcome.

Jo

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

Re: [OSM-talk-be] Mappen van paalcampings

[Jo]

Looks good. Usually there is a first come, first served rule. There is no
way to reserve a spot from 'remote'. When you arrive, you write your name
in a register.

If the person responsible for the site passes by later that night and finds
5 tents and 4 registrations, the tent that wasn't registered and the last
tent that was registered will have to leave and find another spot to camp.
(officially, at least, it may depend on the discretion of the warden)

Or alternatively, the warden may find that the first one that arrived are
already there for more than the allowed number of nights.

I think in practice the ones that are too many would simply be asked to
leave the next morning. Possibly also depending on their mode of transport
and how far away from home they are. In the case of the ones in
Meerdaalwoud, you might be told to go to De Kluis and camp there for a
small fee.

Jo

On Fri, Jan 10, 2020 at 1:52 PM Pieter Vander Vennet 
wrote:

> Hey everyone,
>
> This is a very funny coincidence... Hack Your Future will do a project on
> paalcampings as well!
> I will send out a general mail with more information about that project
> later today. We are in touch with bivakzones.be and will be discussing
> how they can be added to OSM, with what tags and if we can use their site
> as a source. More details about that will be following later on.
>
> However, to prepare that project, I would like to have a better tagging
> scheme for this as well (in order to be able to get them all at once using
> overpass).
>
> After consulting the wiki, I do think that having the tags 
> *'toursim=camp_site',
> 'camp_site=basic' and 'backcountry=yes'* would be the correct tagging.
> The first indicates "an area without facilities where it is legal to camp
> with tents". The second one is even closer to the the concept of these
> bivouacs. At last, an additional 'motor_vehicles=no' makes it very explicit
> that cars and jeeps are not welcome - even though the 'backcountry=yes'
> already implies this.
>
> IMHO is the key 'impromtu=yes' antithetical to the concept of a
> 'paalkamping' - they indicate an *informal* place where people could
> rest, e.g. when travelling through the country *with their jeep... *This
> implies both motorized vehicles and 'camping in the wild', which is AFAIK
> illegal in Belgium.
>
> And of course, there is a lot of additional tagging possible as well.
>
> I've written a wiki page with an explanation, links and a proposal for
> tagging. Please read them carefully. If you have extra information and
> tagging that is still missing, feel free to add this directly to the wiki
> page: https://wiki.openstreetmap.org/wiki/WikiProject_Belgium/Bivakzones
>
>
>
>
>
> On 29.12.19 17:47, Guy Vanvuchelen wrote:
>
> De bivakzone  Het Vinne in Zoutleeuw heb ik aangepast volgens de info van
> Jo
>
>
>
> Guy Vanvuchelen
>
>
>
> *Van:* Jo [mailto:winfi...@gmail.com ]
> *Verzonden:* zondag 29 december 2019 15:53
> *Aan:* OpenStreetMap Belgium
> *Onderwerp:* Re: [OSM-talk-be] Mappen van paalcampings
>
>
>
> Hallo Karel,
>
>
>
> Ik heb een paar jaar geleden deze toegevoegd:
>
>
>
> https://www.openstreetmap.org/way/222137187/history
>
>
>
> Die is onbereikbaar met de wagen. Ik denk niet dat het feit dat hij op
> OpenStreetMap staat ervoor zorgt dat hij overrompelt wordt.
>
>
>
> In Tielt-Winge is er vorig jaar ook één bijgekomen. Ik heb die wel op
> Mapillary, maar blijkbaar heb ik 'm nog niet toegevoegd aan OSM.
>
>
>
> Jo
>
>
>
> On Sun, Dec 29, 2019 at 3:38 PM Karel Adams  wrote:
>
> Na enige aarzeling heb ik, proberenderwijs, de paalcamping Arkadia in
> Muizen toegevoegd. Zie
> https://www.openstreetmap.org/node/7093111580#map=19/51.00354/4.54221
>
> Het zou me helemaal niet verbazen als de initiaftiefnemers daarmee
> allesbehalve gelukikig waren, ik heb dan ook geschreven om een en ander
> toe te lichten, en om goedkeuring te vragen. Want dit soort initiatieven
> houdt graag een laag profiel, het allerlaatste dat men daar wil is dat
> er iemand met een 4x4-superdeluxekampeerbus komt binnengetuft. En dat
> houd ik best voor mogelijk, allicht zal er wel iemand campinggidsen
> opmaken op basis van overpassqueries.
>
> Misschien toch beter maar terug verwijderen? Of welke tags zouden er
> kunnen toegevoegd worden om het eigen karakter van zo'n paalcamping
> duidelijk over te brengen? Iets van "access=???" of "regulations=strict"?
>
> Over het concept van paalcampings kan men meer lezen op o.a.
> http://www.bivakzone.be/
>
> Karel
>
>
> ___

Re: [OSM-talk-be] Tagging proposal for cycling highways (Fietssnelwegen)

[Jo]

On Mon, Jan 6, 2020, 23:07 Pieter Vander Vennet 
wrote:

> Hey everyone,
>
> After some silence in this thread, I would like to close it with a small
> wrap-up.
>
> As the consensus is clear, I've created a wiki page describing the tag in
> detail
> <https://wiki.openstreetmap.org/wiki/Tag:cycle_network%3Dcycle_highway>.
> Feel free to update, add or correct on this page. Additionally, I've added
> links and updated tagging on a few wiki pages where I encountered the old
> tagging.
>
>
> Secondly, I would wish to thank Polyglot for his extensive work on the
> mapping of these cycle networks and to already execute the changes
> described here!
>

I may have made a mistake though. I only saw it when I reread the thread;
BE: is missing.

> Thirdly, I would like to thank everyone involved for all the ideas and the
> constructive way everything was discussed!
>
> Kind regards & best wishes for 2020,
> Pietervdvn
>
>
>
> On 26.12.19 11:16, EeBie wrote:
>
> I am checking  some cycling highways with status proposed and keep the
> parts that are released as usable (Befietsbaar) in the relation and delete
> the status proposed to make them visible and usable in routeplanners.
> I experienced that the information on the website Fietssnelwegen.be is not
> 100% correct. There are parts released where no bike access is allowed. I
> leave these parts out and also the parts over unpaved paths that are
> difficult for usual bikes.
>
> Eebie
>
> Op 25/12/19 om 13:14 schreef joost schouppe:
>
> Hi Jo,
>
> I think that's the right thing to do, thank you.
>
> What I'm still a bit unclear about: if the route itself is unfinished, but
> large sections of them are, then I would think the finished parts do
> deserve a "ready for use state". We talked about this briefly before, maybe
> someone here has an idea how to split up the route (say F3) in three types
> of subrelations :
>
> - usable, ready and waymarked (so similar to any "normal" cycle route)
> - usable but not ready or waymarked (here the route is proposed, I'd say)
> - unusable (here the ways themselves are proposed)
>
> As stated by Stijn and Eebie, the connections "invented" by Jo don't
> belong in OSM. However some of these detours are in fact waymarked. For
> example, in the cycle highway Brussel-Halle there is an official detour
> that will be in place for two years. I'm not sure if this kind of situation
> needs to ge in a fourth type...
>
> Joost
>
> Op di 24 dec. 2019 10:57 schreef Jo :
>
>> All the figments of my imagination have been removed. I reviewed the
>> remaining ones, and fixed them here and there. Where it's not possible to
>> use them today to get from the start till the end, they are marked as
>> state=proposed.
>>
>> Jo
>> ___
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
>>
>
> ___
> Talk-be mailing 
> listTalk-be@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-be
>
>
>
> ___
> Talk-be mailing 
> listTalk-be@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-be
>
> --
> Met vriendelijke groeten,
> Pieter Vander Vennet
>
> ___
> 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] Mappen van paalcampings

[Jo]

Hallo Karel,

Ik heb een paar jaar geleden deze toegevoegd:

https://www.openstreetmap.org/way/222137187/history

Die is onbereikbaar met de wagen. Ik denk niet dat het feit dat hij op
OpenStreetMap staat ervoor zorgt dat hij overrompelt wordt.

In Tielt-Winge is er vorig jaar ook één bijgekomen. Ik heb die wel op
Mapillary, maar blijkbaar heb ik 'm nog niet toegevoegd aan OSM.

Jo

On Sun, Dec 29, 2019 at 3:38 PM Karel Adams  wrote:

> Na enige aarzeling heb ik, proberenderwijs, de paalcamping Arkadia in
> Muizen toegevoegd. Zie
> https://www.openstreetmap.org/node/7093111580#map=19/51.00354/4.54221
>
> Het zou me helemaal niet verbazen als de initiaftiefnemers daarmee
> allesbehalve gelukikig waren, ik heb dan ook geschreven om een en ander
> toe te lichten, en om goedkeuring te vragen. Want dit soort initiatieven
> houdt graag een laag profiel, het allerlaatste dat men daar wil is dat
> er iemand met een 4x4-superdeluxekampeerbus komt binnengetuft. En dat
> houd ik best voor mogelijk, allicht zal er wel iemand campinggidsen
> opmaken op basis van overpassqueries.
>
> Misschien toch beter maar terug verwijderen? Of welke tags zouden er
> kunnen toegevoegd worden om het eigen karakter van zo'n paalcamping
> duidelijk over te brengen? Iets van "access=???" of "regulations=strict"?
>
> Over het concept van paalcampings kan men meer lezen op o.a.
> http://www.bivakzone.be/
>
> Karel
>
>
> ___
> 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] Tagging proposal for cycling highways (Fietssnelwegen)

[Jo]

All the figments of my imagination have been removed. I reviewed the
remaining ones, and fixed them here and there. Where it's not possible to
use them today to get from the start till the end, they are marked as
state=proposed.

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

Re: [OSM-talk-be] Tagging proposal for cycling highways (Fietssnelwegen)

[Jo]

Go ahead, they are not important to me. I was trying to create itineraries
that get you from one place to another today, instead of in 5 or 10 years.

I like to see bicycle routes that are continuous. That is usually not
possible today on any of the fietsnelwegen.

Jo

On Mon, Dec 23, 2019, 23:40 EeBie  wrote:

> I agree with the remarks of Stijn. Only the parts of the "Fietssnelwegen"
> that are realized and “Befietsbaar” on the website of Fietssnelwegen and/or
> marked in the field as such, should be on OSM as cycle route.
> During the past 2 years I suffered several times from the unreliable
> information on OSM as a user of OSM based bike route planners. Planned
> cycle highways were put on the map as realized and existing. A bike
> routeplanner makes a route with preference to cycle routes that are on OSM.
> I supposed to follow a cycle highway but landed on a single track path of
> 30 cm wide with surface of soft sand that I had to walk. On another spot I
> was following a paved footway and had to squeeze my brakes at once because
> the paved footway went over in a stairs downwards where a bridge will be
> build in the future. Luckily it was in daylight and feasible; users of
> cycle highways are supposed to take these routes before and after work when
> it is dark.The proposed routes on OSM are dangerous.
>
> I have given that cycle highway relation the state proposed=yes that makes
> that they are not taken in account on bike routeplanners and on
> https://cycling.waymarkedtrails.org (those proposed relations are visible
> on the Bike Map layer on OSM cycle map layer
> <https://www.openstreetmap.org/relation/1244996#map=15/50.7919/5.4333&layers=C>
> ). There was a fixme or incomplete remark on those relations of planned
> cycle highways but those doesn’t make that they are neglected by
> routeplanners.
>
> I have put the proposed state on other cycle highways that were mapped as
> going through fences over private industrial premises and others where
> biking was not permitted or where even was no path at all.
>
> I have deleted parts of cycle highways in the route relation where bike
> riding wasn’t possible as for example on railway bridge
> <https://www.openstreetmap.org/way/242291877#map=17/51.07556/5.21979&layers=C>
> where the bridge wasn’t ready a few months back (maybe it is meanwhile, but
> I wasn’t there recently).
>
> A few years back I have mapped *parts* of cycle highways that where ready
> and marked and put on the website as “Befietsbaar” in a route relation but
> I had to notice that parts that weren’t ready were added to those relations.
>
> I also don’t like the “alternative cycle highways” because they only exist
> in the head of one person and their quality is (in a lot of cases) very
> poor and dangerous. Example: https://www.openstreetmap.org/way/17298358
> If you take this path riding on modal electric bike style downwards from
> the embankment of the canal over a small unpaved path to a narrow bridge
> over a ditch, you are death. And that should be highway for bikes.
>
> I propose to *delete all what is “**alternatief Fietssnelweg” *because
> they are non existing and they make OSM unreliable because those routes are
> put as preferred by routeplanners.
>
> For the F Fietswegen I propose to *delete the parts that are not ready*
> from the route relations and leave the parts that are ready and
> “Befietsbaar” as on the on Fietssnelwegen website (putting the “proposed”
> status to a complete F relation isn’t a solution any more because parts of
> them are released as “Befietsbaar”).
>
> Regards,
>
> Eebie
>
>
>
>
> Op 23/12/19 om 21:10 schreef Stijn Rombauts via Talk-be:
>
> Hi,
>
> I don't understand why nobody else objects to the 'alternatives'. They're
> just somebody's personal inventions, but they do not exist. If we allow
> Jo's alternatives, then we have to allow anybody's alternatives,
> suggestions , etc. for cycle highways or any other kind of hiking, cycle,
> ... routes. E.g. the cycle highway between Diest and Hasselt has been
> deleted: can I add to OSM a good alternative that I use daily? I hope the
> aswer is no. I don't mind that somebody suggests on some website alternatives
> for the cycle highways which do not yet exist. It's even a very good idea,
> but please keep them out of the OSM database.
> In my opinion, only those parts which are already waymarked should be in
> OSM as cycle highways (and shown on e.g.
> https://cycling.waymarkedtrails.org). The fact that there is a road or a
> cycle path which might be turned into a cycle highway, doesn't mean that
> there is a cycle highway. So, all the rest: state=proposed. [As it is
> alr

Re: [OSM-talk-be] Mapillary

[Jo]

Zou het kunnen dat blauw de foto's zijn die je nog niet hebt doorgestuurd
naar Mapillary?

Jo

On Thu, Dec 19, 2019 at 1:15 PM Guy Vanvuchelen 
wrote:

> Kan iemand me vertellen hoe het komt dat ik bepaalde stukken uit een
>  fotoserie niet zie op Mapillary en wel in JOSM. (zie bijlage)
>
> Wat is het verschil tussen blauw en groen?
>
>
>
> 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] Tagging proposal for cycling highways (Fietssnelwegen)

[Jo]

It is true that the cycle highways form some sort of a network. macro view
at least. When I was trying to map them in OSM, it was often tricky to find
a single spot that could be considered a node where they connect.

Around Gent, mapping F40 as a single continuous cycle highway is a
challenge. There is also quite often some overlap.

In Bilzen there is an actual gap on F76.

Jo

On Tue, Dec 10, 2019 at 8:43 PM s8evq  wrote:

> Actually, after reading the wiki pages, `cycle_network=BE:cycle_highway`
> seems indeed the best choice here.
>
> On Tue, 10 Dec 2019 19:45:39 +0100 (CET), "s8evq" 
> wrote:
>
> > On Tue, 10 Dec 2019 18:35:51 +0100, Pieter Vander Vennet <
> pieterv...@posteo.net> wrote:
> >
> > > *Tagging scheme*
> > >
> > > I'd actually go for `cycle_network=BE:cycle_highway`, as cycle_network
> > > normally has a country prefix. Because most (all?) of them are already
> > > tagged, we could simply update the tagging all at once.  I'll do that
> > > next week, unless a better proposal or good reason not to is raised.
> >
> >
> > Concerning the tagging, would perhaps the new tag "network:type" be of
> any help? https://wiki.openstreetmap.org/wiki/Key:network:type It was
> invented for the use with value node_network, but could perhaps take other
> values?
> >
> > If we can be critical? What makes a "Fietssnelweg" different from
> another long distance route like LF5
> https://www.openstreetmap.org/relation/5285 Only the operator key?
> >
> > ___
> > 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

Re: [OSM-talk-be] Tagging proposal for cycling highways (Fietssnelwegen)

[Jo]

Brussels too is planning to extend the Fxxx toward the center. Of course,
they'll use a C instead of an F, but as far as I understood, they are
planning to use the same numbers, so F3 becomes C3 at the border of the
Brussels region.

On Wed, Dec 11, 2019 at 10:33 AM Lionel Giard 
wrote:

> To answer Joost question about relevance in other regions : yes it is
> relevant. Wallonia recently started to plan and implement these "cycle
> highway" to reach Brussels from multiple different locations (with
> protected cycleway along motorway, national road or railway). They want to
> connect and continue some of the existing cycle highway in Flanders (like
> the F20 near Halle and go further to Tubize...).
> That would definitely be a belgian thing, and not only flanders. ^_^
>
> Le mer. 11 déc. 2019 à 10:12, Marc Gemis  a écrit :
>
>> > Tagging scheme
>> >
>> > I'd actually go for `cycle_network=BE:cycle_highway`, as cycle_network
>> normally has a country prefix. Because most (all?) of them are already
>> tagged, we could simply update the tagging all at once.  I'll do that next
>> week, unless a better proposal or good reason not to is raised.
>>
>> to be honest I find "network" strange in the context of a single
>> cycle_highway. All cycle_highways together form a network, but a
>> single one not.
>> We do not map the E 19 motorway as car_network:BE:motorway, but we do
>> have a relation for all parts of the E 19 in a route-relation (I
>> think, OSM website was soo slow yesterday when I tried to access the
>> page on E-motorways).
>>
>> Is this cycle_network value OK with the inventors of that tag ? Wasn't
>> it invented recently to distinguish cycle networks from local cycle
>> routes ?
>>
>> In conclusion: I would prefer another way to tag cycle highways
>>
>> regards
>>
>> m
>>
>> ___
>> 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

Re: [OSM-talk-be] Tagging proposal for cycling highways (Fietssnelwegen)

[Jo]

On Tue, Dec 10, 2019 at 6:35 PM Pieter Vander Vennet 
wrote:

> Hello Jo,
>
> Thanks for the informative answer which offers a very informed view and
> for your many contributions.
>
> I'll break it up onto multiple subtitles, as there are some sub-topics
> emerging.
>
> *Tagging scheme*
>
> I'd actually go for `cycle_network=BE:cycle_highway`, as cycle_network
> normally has a country prefix. Because most (all?) of them are already
> tagged, we could simply update the tagging all at once.  I'll do that next
> week, unless a better proposal or good reason not to is raised.
>

Sounds good to me

>
> *state=proposed and ground truth *
>
> This is a very good semantic question. Officially, we could only lift the
> state=proposed when all the signposts are present. Alternatively, we could
> have the relation only containing the parts that are already cyclable, and
> having another relation containing the unfinished parts, but I feel that
> this is a lot of work for little to no gain. If a segment has
> 'highway=proposed' on it, well, the meaning of that is quite clear. So,
> practically speaking, how it is done now is quite good.
>

highway=proposed, proposed=cycleway works well for ways that don't exist
yet. state=proposed somewhat less well.
One of my goals is to create route relations that don't have gaps in them.
To reach that in the official ones, we need those highway=proposed ways, no
problem there.

My other goal is to show cyclists what itinerary they can already use today
to bridge the missing parts to get from the start of the intended Fxx to
the end. In that relation I also want to have no gaps, hence the
duplication of ways for those parts that are already realised.

My solution would be to have many subrouterelations, but that would become
somewhat more complex.

> *Alternative routes*
>
> The alternatives pose a different problem. I think that the best solution
> would be to have a single extra relation for each alternative leg - but
> only containing the differing parts, which would avoid having cycleways
> which are part of both the official and alternative ways.
>
> For tagging, I find it however hard to add a
> `cycle_network=BE:cycle_highway` to it. Maybe we could opt for
> `cycle_network=BE:cycle_highway:unofficial` or
> `cycle_network=BE:cycle_highway:alternative`? It should be noted however
> that these will never be verifiable on the ground and thus a bit against
> the OSM-spirit! Their disappearing nature thus is a bonus.
>
> Practically speaking, our routeplanner should be able to figure out a
> decent route over missing links.
>

I think in general, until most of them are signposted, they all (or most of
them) are hard to verify on the ground.

> *The website fietssnelwegen.be <http://fietssnelwegen.be>*
>
> First of all, the earlier link lacked one S. For the record, the correct,
> working website is https://fietssnelwegen.be/
>
> I've always considered that website as being informative for the public -
> and as how they were planned years ago with quite a bit of guesswork. It
> looks to me that they took a map and drew some approximate lines on them,
> open to change.
>
> In the Veltem case could be an example of that where the plans were
> amended. This view also answers the question on what to map: in my opinion,
> the signposted cycle network *is* the official network, even if this
> website happens says otherwise. Even more, it simply indicates that
> fietssnelwegen.be should be updated, not that OSM should copy incorrect
> data.
>
I had access to the official data, and I agree that fietssnelwegen is only
indicative, but as far as I understood, the official itinerary will pass
through the center of Veltem. So I have no idea why it is now signposted
south of the railroad in the field. I expect that this will change at some
point.

> About your alternative for F203 passing Kraainem via Molenstraat instead:
> maybe, because the signs aren't placed yet, we should try contact the
> official instances and try to change the F203 there? It clearly isn't to
> late for that and would make for a better, safer route. It seems to have
> happened that way in the Veltem case as well.
>
Yes, I hope they will come to their senses with that one. Lobbying is on
its way, but it won't hurt if we all write them a little email...

> At last: why aren't they just using an overpass-based map? It could show
> the status, surface, lit=yes/no for each segment and calculate all of that
> live!
>

No idea, but I don't think they actually make use of OSM data.

> *The master relation*
>
> At last, I've also created a master relation containing all the F*:
> https://www.openstreetmap.org/relation/66

Re: [OSM-talk-be] Tagging proposal for cycling highways (Fietssnelwegen)

[Jo]

Hi Pieter,

You are right, that is an odd way of tagging them. cycle_highway seems
better indeed. I don't know who started doing it that way, I simply
continued the practice, without giving it enough thought.

Most of these cycle highways can't be cycled from beginning to end, they
continue over large distances (for bicycles). This means they are all
tagged with state=proposed. Some of them are mostly done though, like F1 or
F3, but the parts that are missing from them will take several years to
complete. Do we want to keep them with state=proposed?

What I started doing is to also map alternatives that can be cycled from
start to end today. I recently learned this is not really appreciated by
some official instances. They don't control what we do, so it's not
extremely important, but still maybe something to keep in mind.

One thing I was considering to do, is to divide them in subrelations. Such
that the parts that are finished would go into both the 'official' relation
and into the alternative one. If you would like, I'll do this for F3, to
show what I mean.

Then there is also sometimes  a difference between what is shown on
fietsnelwegen.be and what is actually visible in the field. I'm thinking
about the situation in Veltem, where F3 has a leg on the southern side
marked in the field, but it is actually meant to go through the center of
Veltem, north of the railway it generally follows.

Most cycle highways are not yet visible in the field. The signs aren't
placed yet. For example F203 from Sterrebeek to Sint-Stevens-Woluwe. It
passes through Kraainem over 2 cycleways of 50cm, with no separation to
motorized traffic that is allowed to go at 70km/h there. Then it goes
through the center with lots of crossings. This is a bit odd, as there is
the possibility to pass through Molenstraat, wich is a lot safer and has a
far better experience for the cyclist.

The alternative route relations I was creating, are meant to disappear
after a few years, but that point, I might be tempted to keep it, even when
the official instances decide to keep the less suitable itinerary.

One general problem with the cycle highways, today, is that it's next to
impossible to apply 'ground truth'  to them, except if we would only map
the parts that are actually already finished and marked in the field.

Those are my thoughts on the subject. If I find some more time, I might
continue mapping the official ones, with the projected parts, like I did it
here: https://www.openstreetmap.org/way/691027464/history

But for longer stretches. I have no idea if they are planning to add those
dedicated cycleways in the next 2 years, or in the next 15 years though.

For the ones that I audited over the past year, there are many pictures on
Mapillary.

Polyglot

On Mon, Dec 9, 2019 at 10:53 PM Pieter Vander Vennet 
wrote:

> Hello everyone,
>
> As we (Anyways BVBA) are making a route planner which takes
> 'Fietssnelwegen' into account, we would like to have some uniform
> tagging into place for this.
>
> Some of them are already tagged with `cycle_network=Fietssnelweg`, which
> sounds very Flemish.
>
> I'm going ahead with adding them to other existing fietssnelwegen, but
> would like to document them on the wiki and to have some more thought
> put into them. First of all, the dutch term is something very
> inconsistent with the rest of OSM - perhaps "cycle_highway" is a better
> fit. Secondly, maybe we should prefix them with "BE:". Thirdly, OSM tags
> are mainly written in lowercase, which this tag is not.
>
> Any more thoughts on tagging? I'm especially looking looking forward to
> input from polyglot who is very familiar with them.
>
> --
> Met vriendelijke groeten,
> Pieter Vander Vennet
>
> ___
> 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] Mapillary tip bij regen

[Jo]

Why would you press against the camera? I used a gimbal for a little less
than a week. It was possible to put in in balance for the horizontal axis,
but not for the 'inclination' axis, which meant that motor had to work hard
in order to keep the camera looking forward horizontally -> battery drain
and hot motor. My conclusion was that it wasn't suitable for a heavier cell
phone like mine. It was also yet another fragile device that was eating up
battery power. It was nice that the pictures were all perfectly horizontal,
but in the end it doesn't matter that much.

So I made use of Coolblue's return policy.

As far as making photographs when it's raining, I usually consider it 'game
over' when it starts to drizzle or rain.

Oops, nu heb ik dat helemaal in het Engels geschreven:

Antwoord op Philippe: wat mij betreft is het gedaan met foto's maken van
zodra het zelfs maar miezert.

Jo

On Thu, Nov 7, 2019 at 5:06 AM Marc Gemis  wrote:

> Ik vrees een beetje voor mijn gimbal als ik dat doe.
> Voorlopig zie ik het maar als een test voor de object herkenning van
> Mapillary :-)
>
> Iemand ervaring met gimbals als je telkens weer opnieuw tegen de camera
> duwt ?
> (Anyone experience with gimbals when you keep pressing against the
> camera over and over again
> ?)
>
> m.
>
> On Tue, Nov 5, 2019 at 1:10 PM Philippe Casteleyn
>  wrote:
> >
> >
> https://www.mapillary.com/app/?focus=photo&pKey=tyzRIji1MXSDUcxAxoxFoQ&lat=51.04352509997222&lng=4.263778&z=17
> >
> > Wanneer het regent droog ik mijn cameralens bij elke straathoek.
> >
> >
> >
> > ___
> > 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

Re: [OSM-talk-be] Vhello - New Cycle Nodes Network /Nouveau réseau Points-Noeuds Vélo / Niew Fietsknooppunten

[Jo]

I'm doing another teleconference: anyone is welcome:
https://streamyard.com/dcnmSwhuiF

On Thu, Aug 15, 2019 at 10:36 AM Jo  wrote:

> The chat url is: https://hangouts.google.com/call/0DSbdqltI_JXc0aivzB2AEEM
>
> On Thu, Aug 15, 2019 at 10:27 AM Jo  wrote:
>
>> Hi François,
>>
>> In about 10 minutes I'm going to do a hangout with the student developing
>> PT_Assistant.
>>
>> Let me know if you want to join.
>>
>> Jo
>>
>> On Sun, Aug 11, 2019 at 8:50 PM François ROLAND 
>> wrote:
>>
>>> Hi Corentin, hi Polyglot,
>>>
>>> I've encoded a few routes between Vhello junctions, starting with
>>> Braine-le-Comte area.
>>>
>>> I'll go on in the coming days based on the paper map and fietsnet
>>> website.
>>>
>>> Polyglot, if you also encode some routes, maybe a good plan is that you
>>> start with the West part of the network so that we meet somewhere in the
>>> middle. What are your thoughts about this?
>>>
>>> @Corentin: le monde est petit ;-)
>>>
>>> Best regards,
>>>
>>> François
>>>
>>>
>>> ___
>>> 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] Vhello - New Cycle Nodes Network /Nouveau réseau Points-Noeuds Vélo / Niew Fietsknooppunten

[Jo]

The chat url is: https://hangouts.google.com/call/0DSbdqltI_JXc0aivzB2AEEM

On Thu, Aug 15, 2019 at 10:27 AM Jo  wrote:

> Hi François,
>
> In about 10 minutes I'm going to do a hangout with the student developing
> PT_Assistant.
>
> Let me know if you want to join.
>
> Jo
>
> On Sun, Aug 11, 2019 at 8:50 PM François ROLAND 
> wrote:
>
>> Hi Corentin, hi Polyglot,
>>
>> I've encoded a few routes between Vhello junctions, starting with
>> Braine-le-Comte area.
>>
>> I'll go on in the coming days based on the paper map and fietsnet website.
>>
>> Polyglot, if you also encode some routes, maybe a good plan is that you
>> start with the West part of the network so that we meet somewhere in the
>> middle. What are your thoughts about this?
>>
>> @Corentin: le monde est petit ;-)
>>
>> Best regards,
>>
>> François
>>
>>
>> ___
>> 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] Vhello - New Cycle Nodes Network /Nouveau réseau Points-Noeuds Vélo / Niew Fietsknooppunten

[Jo]

Hi François,

In about 10 minutes I'm going to do a hangout with the student developing
PT_Assistant.

Let me know if you want to join.

Jo

On Sun, Aug 11, 2019 at 8:50 PM François ROLAND  wrote:

> Hi Corentin, hi Polyglot,
>
> I've encoded a few routes between Vhello junctions, starting with
> Braine-le-Comte area.
>
> I'll go on in the coming days based on the paper map and fietsnet website.
>
> Polyglot, if you also encode some routes, maybe a good plan is that you
> start with the West part of the network so that we meet somewhere in the
> middle. What are your thoughts about this?
>
> @Corentin: le monde est petit ;-)
>
> Best regards,
>
> François
>
>
> ___
> 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] Vhello - New Cycle Nodes Network /Nouveau réseau Points-Noeuds Vélo / Niew Fietsknooppunten

[Jo]

oh, by the way, I'm not sure what to do about the routes that connect to
the French border. On the border, they were apparently not assigned node
numbers, which is somewhat unfortunate. I also don't know how they are
signposted in the field.

Polyglot

On Sun, Aug 11, 2019 at 9:00 PM Jo  wrote:

> Purely by coincidence I did start in the southwest. I loaded the shape
> files in JOSM though and converted them to GPX format.
>
> On Sun, Aug 11, 2019, 20:50 François ROLAND  wrote:
>
>> Hi Corentin, hi Polyglot,
>>
>> I've encoded a few routes between Vhello junctions, starting with
>> Braine-le-Comte area.
>>
>> I'll go on in the coming days based on the paper map and fietsnet website.
>>
>> Polyglot, if you also encode some routes, maybe a good plan is that you
>> start with the West part of the network so that we meet somewhere in the
>> middle. What are your thoughts about this?
>>
>> @Corentin: le monde est petit ;-)
>>
>> Best regards,
>>
>> François
>>
>>
>> ___
>> 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] Vhello - New Cycle Nodes Network /Nouveau réseau Points-Noeuds Vélo / Niew Fietsknooppunten

[Jo]

Purely by coincidence I did start in the southwest. I loaded the shape
files in JOSM though and converted them to GPX format.

On Sun, Aug 11, 2019, 20:50 François ROLAND  wrote:

> Hi Corentin, hi Polyglot,
>
> I've encoded a few routes between Vhello junctions, starting with
> Braine-le-Comte area.
>
> I'll go on in the coming days based on the paper map and fietsnet website.
>
> Polyglot, if you also encode some routes, maybe a good plan is that you
> start with the West part of the network so that we meet somewhere in the
> middle. What are your thoughts about this?
>
> @Corentin: le monde est petit ;-)
>
> Best regards,
>
> François
>
>
> ___
> 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] Tr : Vhello - New Cycle Nodes Network / Nouveau réseau Points-Noeuds Vélo / Niew Fietsknooppunten

[Jo]

Hi Corentin,

I started by adding all the nodes and integrating them with our data.

For the itineraries, it will take a bit longer. If you like, it might be a
good idea to do a Hangout, so I can show you how to do it using JOSM and a
plugin of which I'm  I'm overseeing the development. I would probably
invite some folks I met at SotM-FR who also had an interest in mapping
bicycle itineraries.

I wouldn't mind adding all the itineraries between the points. That will
take me a few days, would it be possible for the province of Hainaut to
provide me with a few nights accommodation in the region? Then I'd come
over and actually cycle (part of) the network (and make pictures for
Mapillary of it). Sort of a vacation for me, but very useful for OSM and, I
suppose, for the province as well.

Polyglot

On Thu, Aug 8, 2019 at 2:20 PM marc marc  wrote:

> Hello,
>
> Le 08.08.19 à 14:05, corentin.marec...@hainaut.be a écrit :
> > we translated in french the following page:
> > https://wiki.openstreetmap.org/wiki/Cycle_Node_Network_Tagging
> > How can I add it for the community ?
>
> clic on "Toutes les langues", and "Français",
> save your translation there, including wikicode,
> use preview before saving
>
> Regards,
> Marc
>
> ___
> 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] join us at State of the Map

[Jo]

I'm interested in this. Aber verdammt noch mal! :-) AirBNBs are expensive
in Heidelberg, near the venue. I might also try my chances on Couchsurfing.

Jo

On Mon, May 20, 2019 at 11:25 AM joost schouppe 
wrote:

> Hi,
>
> Every year, the global OpenStreetMap convenes for a long weekend of
> presentations and workshops about the state of the map. More than just a
> chance to learn new things, it is a place where you get to meet all those
> people you only know by their username or e-mail.
>
> Last year, for State of the Map Milan, a small group of us Belgians rented
> an AirBnB together. It was fun and cost-effective.
> This year, it's even closer to home, in Heidelberg, Germany.
>
> Please send me a message if you would like to join this years' group!
> The sooner we know how many people will join us, the easier it will be to
> find a nice place. I aim for mid June to start organizing, so let me know
> by then.
>
> For more details about the event, check out
> https://2019.stateofthemap.org/
>
> --
> Joost Schouppe
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
> ___
> 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] landuse & highways

[Jo]

I'm under the impression (from reading international mailing lists) most
dislike it when landuse gets glued to the highways nowadays.

Polyglot

On Tue, Mar 19, 2019 at 7:34 PM Stijn Rombauts via Talk-be <
talk-be@openstreetmap.org> wrote:

> Hi,
>
> What are the opinions these days about landuse mapping: connect landuses
> to highways or let space between landuse polygons and adjacent highways?
> Is there a consensus or can everyone do whatever he/she likes?
> My opinion: I *hate* landuse connected to highways.
>
> Regards,
>
> StijnRR
> ___
> 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] how to create a 'ready-to-print' city map from OSM

[Jo]

I tried to get started on something like that:

https://www.openstreetmap.org/user/Polyglot/diary/47876

QGIS 3 allows to move very quickly for the inital steps, but of course
defining a style that you are happy with is going to take a while.

In OpenStreetMap we expand all abbreviations on purpose. The idea is that
it is easier to shorten, than to expand in a reliable way, but that doesn'
t mean it' s entirely trvial, of course.

You can define a new column in the features table and calculate its value
based on what you find in name:nl and name:fr.

So all Rue, become R., Place, Pl. Where the end of French and the start of
Dutch are the same as in

Place Fontainas - Fontainasplein

You could try to turn it into

Place Fontainasplein.

That looks odd though.

On the street signs they did it like this:

Place
Fontainas
 plein

According to Dutch spelling rules, that's not correct though.

Bd Adolphe Max-ln
R. Vander Elst-st.
Pl. Sainctelette-pl.
R. Masui-st.


also looks weird and the dash is only a compromise that looks odd to both
French and Dutch speakers, alike. Glueing the straat/plein/laan to the word
would probably be even stranger to French speakers.

I guess the labeling will be your biggest challenge.

Polyglot

On Wed, Mar 6, 2019 at 9:53 AM PONCELET Nadia (Firebru)
 wrote:

> Hello everyone,
>
>
>
> I would like to create some map from OSM that could be printed on paper at
> the approximate scale of 1:5000 and where all street names would appear on
> the map and be easy to read.
>
>
>
> This is quite tricky I think, especially for Brussels where street names
> usually have a french and a dutch version. I have already done this
> exercise previously using UrbIS and I had to use some tricks such as
> shortening the names by combining the french and dutch versions when
> possible (e.g. "Rue de l'Ommegangstr." or "Quai F. Demetskaai") and widen
> the streets. I don't care that the streets are no more "at scale", the
> important is that all (or most) street names are legible. The rendering is
> similar to De Rouck map guides or 'Bruxelles en poche' for those who know
> these books. In long streets, the name can also be repeated several times.
>
>
>
> My final result from UrbIS was more or less satisfactory (even if it still
> required some workforce to displace manually a few toponyms at the end) but
> I would like to be able to create the same kind of map from OSM for a
> larger area than the Brussels Region and also be able to update it
> periodically.
>
>
>
> Before I start working on this, would you have some advice or know any
> people/projects/tools/libraries/ideas that could be a source of inspiration
> (maybe from ‘OSM on paper’ wiki page)?
>
>
>
> Thank you very much for your answers.
>
>
>
> Nadia
> ___
> 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] Status GRB-import tool ?

[Jo]

Als er zo'n Meetup georganiseerd wordt, zal ik alleszins wel proberen om
erbij te zijn.

Jo

On Thu, Jan 24, 2019 at 8:13 PM Marc Gemis  wrote:

> Hallo Denis,
>
> Ik had gehoopt dat iemand die dichter betrokken is bij de ontwikkeling
> tijd zou hebben om je te beantwoorden, maar ze hebben het misschien te
> druk momenteel.
> Ik zal dan maar proberen te de situatie te schetsen:
>
> - de import mailing list had niet echt bezwaren, dus die hindernis is
> genomen
> - de documentatie is volgens mij zo goed als af. De laatste beetjes
> zouden tijdens een soort van kick-off meeting kunnen aangevuld worden
> - de tool heeft nog 2 problem (voor zover ik weet)
> * er komen nog extra tags mee die je niet mag uploaden. Daar bestaat
> wel een eenvoudige workaround voor.
> * niet alle adressen zijn correct. Vooral bij appartementsgebouwen met
> meerdere huisnummers, zou het beter kunnen. Stel je hebt een gebouw
> met 3 ingangen en huisnummers 15, 16 en 17.
> Nu zal je 3 gebouwen met nummer 15-17 krijgen. Er is een mogelijkheid
> om dit te verbeteren door een extra databank te laden in de tool. Dit
> vraagt natuurlijk ontwikkelingstijd.
>
> Ik begrijp Glenn wel dat die wijziging echt noodzakelijk is voordat de
> tool beschikbaar kan gemaakt worden. Als iemand die altijd klaagt over
> foutieve data van externe bronnen, juich ik dat alleen maar toe.
>
> Ik weet echter niet of het enkel aan ons is om daarover te beslissen.
>
> Momenteel werkt ook Lodde1949 rustig verder aan het intekenen van
> gebouwen adhv de GRB achtergrond en met de oude adres import tool. Dus
> in een groot deel van de provincie Antwerpen is de tool al niet meer
> zo relevant.
>
> Misschien moet er gewoon iemand een datum prikken, een zaal met
> internet verbinding voorzien, iemand uitnodigen die de nodige
> toelichtingen kan geven en de "import" officieel starten.
> Het is duidelijk dat iemand de "projectleiderrol" op zich zal moeten
> nemen om alles naast de ontwikkeling van de tool te organiseren en
> daar dan ook voldoende tijd in stoppen.
>
> mvg
>
> m.
>
> p.s. Ik wil hier niemand met de vinger wijzen, we zijn allemaal
> vrijwillers met beperkte tijd. Ikzelf heb ook geen tijd noch interesse
> om deze rol op te nemen.
>
> On Sun, Jan 20, 2019 at 6:02 PM Denis Verheyden 
> wrote:
> >
> > Dag iedereen,
> >
> > Graag wou ik nog eens polsen wat de status is van de GRB-import tool.
> Ergens in 2017 is de publieke versie uitgezet omdat veel mensen hiermee
> onbedoelde of verkeerde wijzigingen hebben gedaan.
> >
> > Voor mij is deze tool echter het middel waarop ik wacht om nieuwe of
> aangepaste gebouwen toe te voegen/wijzigen in OSM. Het heeft geen zin nu
> gebouwen te tracen als we ze later opnieuw moeten vervangen door de
> "officiële" geometrie van A(G)IV. Tot dan beperk ik mij enkel tot toevoegen
> van nodes of features niet gerelateerd aan gebouwen.
> >
> > Groeten,
> > Denis
> > ___
> > 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

Re: [OSM-talk-be] Status GRB-import tool ?

[Jo]

Ik voel me ook niet geroepen om die rol op me te nemen, maar ik heb wel een
suggestie voor tags die niet mogen worden doorgestuurd.

JOSM heeft daar ondersteuning voor.

Wat ik gewoonlijk doe is zulke tags created_by of odbl noemen, aangezien
die al in de lijst staan.

De andere mogelijkheid is een key (tags.discardable) in de instellingen
aanpassen en dan worden ze vanzelf weggegooid voordat er data naar de
server gaat.

mvg,

Jo


On Thu, Jan 24, 2019 at 8:13 PM Marc Gemis  wrote:

> Hallo Denis,
>
> Ik had gehoopt dat iemand die dichter betrokken is bij de ontwikkeling
> tijd zou hebben om je te beantwoorden, maar ze hebben het misschien te
> druk momenteel.
> Ik zal dan maar proberen te de situatie te schetsen:
>
> - de import mailing list had niet echt bezwaren, dus die hindernis is
> genomen
> - de documentatie is volgens mij zo goed als af. De laatste beetjes
> zouden tijdens een soort van kick-off meeting kunnen aangevuld worden
> - de tool heeft nog 2 problem (voor zover ik weet)
> * er komen nog extra tags mee die je niet mag uploaden. Daar bestaat
> wel een eenvoudige workaround voor.
> * niet alle adressen zijn correct. Vooral bij appartementsgebouwen met
> meerdere huisnummers, zou het beter kunnen. Stel je hebt een gebouw
> met 3 ingangen en huisnummers 15, 16 en 17.
> Nu zal je 3 gebouwen met nummer 15-17 krijgen. Er is een mogelijkheid
> om dit te verbeteren door een extra databank te laden in de tool. Dit
> vraagt natuurlijk ontwikkelingstijd.
>
> Ik begrijp Glenn wel dat die wijziging echt noodzakelijk is voordat de
> tool beschikbaar kan gemaakt worden. Als iemand die altijd klaagt over
> foutieve data van externe bronnen, juich ik dat alleen maar toe.
>
> Ik weet echter niet of het enkel aan ons is om daarover te beslissen.
>
> Momenteel werkt ook Lodde1949 rustig verder aan het intekenen van
> gebouwen adhv de GRB achtergrond en met de oude adres import tool. Dus
> in een groot deel van de provincie Antwerpen is de tool al niet meer
> zo relevant.
>
> Misschien moet er gewoon iemand een datum prikken, een zaal met
> internet verbinding voorzien, iemand uitnodigen die de nodige
> toelichtingen kan geven en de "import" officieel starten.
> Het is duidelijk dat iemand de "projectleiderrol" op zich zal moeten
> nemen om alles naast de ontwikkeling van de tool te organiseren en
> daar dan ook voldoende tijd in stoppen.
>
> mvg
>
> m.
>
> p.s. Ik wil hier niemand met de vinger wijzen, we zijn allemaal
> vrijwillers met beperkte tijd. Ikzelf heb ook geen tijd noch interesse
> om deze rol op te nemen.
>
> On Sun, Jan 20, 2019 at 6:02 PM Denis Verheyden 
> wrote:
> >
> > Dag iedereen,
> >
> > Graag wou ik nog eens polsen wat de status is van de GRB-import tool.
> Ergens in 2017 is de publieke versie uitgezet omdat veel mensen hiermee
> onbedoelde of verkeerde wijzigingen hebben gedaan.
> >
> > Voor mij is deze tool echter het middel waarop ik wacht om nieuwe of
> aangepaste gebouwen toe te voegen/wijzigen in OSM. Het heeft geen zin nu
> gebouwen te tracen als we ze later opnieuw moeten vervangen door de
> "officiële" geometrie van A(G)IV. Tot dan beperk ik mij enkel tot toevoegen
> van nodes of features niet gerelateerd aan gebouwen.
> >
> > Groeten,
> > Denis
> > ___
> > 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

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

[Jo]

I could probably explain a thing or 2 about Wikidata in OSM and vice versa.

Jo

On Wed, Jan 9, 2019 at 9:04 PM Marc Gemis  wrote:

> I'm a bit confused about
>
> - Open Belgium (on March 4)
> and
> - We will also organize a community day during the weekend this year
>
> which weekend is that ? Which community (OpenBelgium or OSM or both) ?
>
> I was also thinking (for a OSM public) -- at least I would be interested
> to participate in such a workshop/presentation to learn more.
>
> - Improve your armchair mapping with Mapillary and OpenStreetCam
>   Explain the 2 project, techniques to use them in iD or JOSM, filter
> images on "topic", ...
> - Wikidata (and Wikipedia and Commons) for mappers.
> What is Wikidata, how can you edit, how can you put data in OSM, potential
> ideas for using a joined DB.
>
>
> m.
>
>
> On Wed, Jan 9, 2019 at 5:18 PM Jonathan Beliën  wrote:
>
>> That’s a really awesome idea indeed !
>> Thanks Marc !
>>
>>
>>
>> I’ll see if we can make that happen during OpenBelgium Community Day ! \o/
>>
>>
>>
>> Jonathan Beliën
>> SPRL GEO-6 <https://geo6.be/>
>>
>>
>>
>> *De :* Santens Seppe 
>> *Envoyé :* mercredi 9 janvier 2019 09:27
>> *À :* OpenStreetMap Belgium 
>> *Objet :* Re: [OSM-talk-be] Fwd: Open Belgium 2019: Call for Speakers +
>> Early Bird Tickets!
>>
>>
>>
>> Cool idea, Marc!
>>
>>
>>
>> *Van:* Marc Gemis [mailto:marc.ge...@gmail.com]
>> *Verzonden:* dinsdag 8 januari 2019 20:32
>> *Aan:* OpenStreetMap Belgium
>> *Onderwerp:* Re: [OSM-talk-be] Fwd: Open Belgium 2019: Call for Speakers
>> + Early Bird Tickets!
>>
>>
>>
>> I cannot make it to Open Belgium, but I have been thinking about a
>> "walking meetup" for some time now. So instead of sitting in a pub, doing a
>> walk and talk about OSM and survey techniques and apply them.
>>
>> Taking that idea, on a community day, it could be a workshop about
>> surveying techniques, JOSM tips, micromapping, that kind of stuff. It would
>> be an hand-on workshop, where people have to go outside for 15 minutes or
>> so and collect data. Afterwards compare techniques, collected data and do a
>> bit of mapping. Perhaps discuss a bit about usefulness, special maps, ...
>>
>>
>>
>> m.
>>
>>
>>
>> On Tue, Jan 8, 2019 at 1:46 PM Ben Abelshausen 
>> wrote:
>>
>> Hi everyone!
>>
>>
>>
>> In a few months we have Open Belgium again (yay!) and as usual we will
>> have talks about OSM (Belgium).  We invite everyone to submit a talk,
>> **anything** related to open-(something) is fine, that means openstreetmap
>> too! ;-) We will also organize a community day during the weekend this
>> year, more news about that later, so even if you can't make it on the 4th
>> of march we urge you to submit talks/workshops anyway. We can move them to
>> the community day later.
>>
>>
>>
>> We will probably also have a booth with OSM Belgium and usually have a
>> lot of fun so don't miss it! If you want to attend but find the entry
>> tickets too expense get in touch with me, the community day will be free
>> (to be announced later).
>>
>>
>>
>> All details here:
>>
>>
>>
>> -- Forwarded message -
>> From: *Astrid - Open Knowledge Belgium* 
>> Date: Tue, Jan 8, 2019 at 10:17 AM
>> Subject: Open Belgium 2019: Call for Speakers + Early Bird Tickets!
>> To: 
>>
>>
>>
>> A must-attend conference to discuss the state of and current trends
>> around Open Knowledge and Open Data!
>>
>> Open Belgium 2019 - 4 March in Brussels
>> Open Knowledge and Open Data in Belgium
>>
>>
>>
>> View this email in your browser
>> <https://mailchi.mp/d884372f2d2a/open-belgium-2019-call-for-speakers-early-bird-tickets?e=17370c2173>
>>
>> [image: Image supprimée par l'expéditeur.]
>> <https://openbelgium.us8.list-manage.com/track/click?u=16c22b5f724fd6ef8c78c79fc&id=a9315be566&e=17370c2173>
>>
>>
>> Let's talk Open Knowledge and Open Data!
>> Ready for Open Belgium 2019?
>>
>>
>> The Belgian open knowledge and open data landscape is changing at a fast
>> pace. In order to stay up-to-date and to share insights with *300+
>> fellow open enthusiasts,* we would like to invite you to join us at
>> the annual *community-driven Open Belgium 2019
>> <https://openbelgium.us8.list-mana

Re: [OSM-talk-be] identifier in ref:xOperatorx=y0yyyy to url=http://mijnlijn.be/y0yyyy

[Jo]

Frank,

url wasn't used yet on the bus stops, so no conflict there.

Pieter, good to hear De Lijn plans such deep links. I think it will be good
to have them on our route_master relations. The route relations are for the
longest variations in itinerary, not sure if they fit there.

For the stops, I tend to like the mijnlijn.be/ form, as that is the
information printed on each of the paper schedules on the stops. So if De
Lijn is not planning to abolish those in the medium term, I'd prefer to use
them. I'll hold off with preparing the data and launching the Project of
the Month though.

Pieter, is De Lijn planning to introduce uic identifiers we could put in
uic_ref?

We don't have anything that corresponds to the zones in OSM. I'm curious to
find out what will be behind those urls. I painstakinglly added the zone
information on the stops, but now that a ticket has a time limitation
instead of a zone dependent one, they became less relevant.

Marc, we can leave the ref:De_Lijn tags. I'm not strongly against keeping
them, but I doubt anyone uses them (except me in my integraton scripts). If
anyone wants to use them, it's trivial to extract the identifiers from the
url tag values.

There is another tag I'd like to introduce. While reviewing the import of
bus stops around Finland, they added a direction tag.

My first reflex was to remove it after reviewing the stop, but now I start
to see value in knowing in which direction the bus will leave. I plan to
add functionality to PT_Assistant to calculate it automatically based on
the segment of the way the stop is adjacent to. And in a second stage a
validator rule that checks whether the stop is (still) on the correct side
of the road (right or left, depending on the side of the road vehicles
drive on)

Polyglot





El dom., 18 nov. 2018 a las 11:19, Pieter Colpaert ()
escribió:

> Hi Polyglot,
>
> We are in a Linked Data project with De Lijn and we’re going to have
> official persistent identifiers (HTTP URIs) soon for stops (but also for
> things like the routes and zones). It might be interesting to integrate
> these in OSM rather than the mijnlijn.be one?
>
>  From the moment we have an official URI strategy, I will get back to
> this list in each case.
>
> Kind regards,
>
> Pieter
>
> On 18/11/18 11:10, Jakka wrote:
> > Using key as "url=" not comming in conflict with already other keys
> > that use short key url ?
> >
> > Op 18/11/2018 om 10:51 schreef Jo:
> >> Our bus stops in Flanders have unique identifiers visible to the public
> >> on the flags of the stop poles.
> >>
> >> I started by entering those in the ref tag, then later decided to use
> >> ref:De_Lijn=y0, as some of those stops are served by other operators
> >> as well.
> >>
> >> For several years now itt's possible to obtain real-time information
> >> about the buses on a url+identifier, so I want to add that to those
> >> stops. As i don't like to duplicate information I'd prefer to drop the
> >> ref:De_Lijn though.
> >>
> >> So all of those stops would have:
> >> url=http://mijnlijn.be/303079(<- you can test this, the url is
> >> expanded/translated to a url on www.delijn.be <http://www.delijn.be>)
> >>
> >> For the conversion, I'd like to launch a Belgian "Project of the month",
> >> so the position of the stops can be verified once more by locals, but
> >> also shelters and bus_bays can be added and if cycle ways split off to
> >> go around those bus bays, that detail can be added as well.
> >>
> >> I know that that is what we have been doing for the past 5+ years, but
> >> now it would get some more dedicated focus.
> >>
> >> For several years I thought having the identifier n a dedicated ref:X
> >> tag and then telling everyone about how to turn it into such a url was
> >> the way to go,. That doesn't actually work though. Nobody knows how to
> >> get from the identifer to the url. Giving potential passengers a url
> >> they can simply click through on, seems to be the better way of doing
> >> this for this use case.
> >>
> >> Polyglot
> >>
> >>
> >> ___
> >> 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
>
> --
> +32486747122
>
>
> ___
> 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

[OSM-talk-be] identifier in ref:xOperatorx=y0yyyy to url=http://mijnlijn.be/y0yyyy

[Jo]

Our bus stops in Flanders have unique identifiers visible to the public on
the flags of the stop poles.

I started by entering those in the ref tag, then later decided to use
ref:De_Lijn=y0, as some of those stops are served by other operators as
well.

For several years now itt's possible to obtain real-time information about
the buses on a url+identifier, so I want to add that to those stops. As i
don't like to duplicate information I'd prefer to drop the ref:De_Lijn
though.

So all of those stops would have:
url=http://mijnlijn.be/303079(<- you can test this, the url is
expanded/translated to a url on www.delijn.be)

For the conversion, I'd like to launch a Belgian "Project of the month", so
the position of the stops can be verified once more by locals, but also
shelters and bus_bays can be added and if cycle ways split off to go around
those bus bays, that detail can be added as well.

I know that that is what we have been doing for the past 5+ years, but now
it would get some more dedicated focus.

For several years I thought having the identifier n a dedicated ref:X tag
and then telling everyone about how to turn it into such a url was the way
to go,. That doesn't actually work though. Nobody knows how to get from the
identifer to the url. Giving potential passengers a url they can simply
click through on, seems to be the better way of doing this for this use
case.

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

Re: [OSM-talk-be] Note tells OSM fails

[Jo]

That sounds like a good solution Lionel. Most of those 'French' names are
simply archaic spellings of the original Flemish names anyway.

Polyglot

Op wo 5 sep. 2018 om 09:40 schreef Lionel Giard :

> The official french name is "Kraainem" too, while Crainhem is an alternate
> spelling for french (but i had never seen it before). Maybe we should
> change the tag and put it like that "name:fr=Kraainem" and "alt_name:fr=
> Crainhem" ?
>
> Le mar. 4 sept. 2018 à 20:43, Marc Gemis  a écrit :
>
>> I replied with the same names as person used in the original note.
>> Kraainem is named Kraainem in the name and name:nl fields.
>>
>> It is possible that Nominatim returns the name:fr field in case you
>> have your browser configured to prefer French above Dutch.
>>
>> m.
>> On Tue, Sep 4, 2018 at 7:21 PM Karel Adams  wrote:
>> >
>> > In the margin and without wishing to enter politics, allow me to insist
>> > we should name the village by its primary and original name "Kraainem".
>> >
>> >
>> > On 04/09/18 09:39, Marc Gemis wrote:
>> > > Here is the answer I gave on the note:
>> > >
>> > > As you can see on the map, the boundary between Woluwe-Saint-Pierre
>> > > and Crainhem runs slighty left of the Rue Longue.
>> > >
>> > > Since the current implementation of Nominatim (the software that looks
>> > > up the addresses), always looks at the street and never at the POIs,
>> > > there is no way to solve this with data.
>> > >
>> > > AFAIK, they are working on a solution for this, but there is no
>> > > timeframe for a solution
>> > >
>> > > m.
>> > > On Tue, Sep 4, 2018 at 9:38 AM Jakka  wrote:
>> > >> Hi,
>> > >>
>> > >> Who can answer and close this note.
>> > >> Building is located in Woluwe-Saint-Pierre but access highway is in
>> > >> Crainhem I think...
>> > >> https://www.openstreetmap.org/note/1477650#map=19/50.84217/4.46717
>> > >> https://nominatim.openstreetmap.org/details.php?place_id=84536059
>> > >>
>> > >>
>> > >> ___
>> > >> 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-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

Re: [OSM-talk-be] National Road relation: does order matter?

[Jo]

The "problem" with N roads is that they are not linear features, they
split, recombine, have dangling dead ends, roundabouts and so on.

Yes, you can group some of the elements, but the next time you sort, other
groups may be formed, so it's arbitrary.

Jo

Op ma 3 sep. 2018 om 20:03 schreef André Pirard :

> On 2018-09-03 00:24, Jo wrote:
>
> for route=road relations order doesn't matter much. It's impossible to
> sort them according to any meaningful criterion.
>
> A meaningful criterion to sort a route is so that two adjacent ways of it
> share one same end node.
> In other words, that the route is ordered the way you travel it without
> interruptions.
> That's what the "sort" buttons of JOSM do.
> And, beside finding a segment more easily, the schema of the route made by
> JOSM shows the gaps (missing pieces).
> And in particular it will show if the road is circular.
> For example, if you sort the N30, you will see a gap between Boulevard de
> Fraipont and Avenue de la Libération.
> And 16 other gaps in total.
>
> Last time I spoke of routes with a Potlatch user, he told me he couldn't
> sort routes.
> I don't know about ID and that's quite a time ago.
>
> The N30 should be sorted and corrected.
> I will let Nathan do it if he's busy with it.
>
> Amitiés,
>
> André.
>
> Polyglot
>
> Op zo 2 sep. 2018 om 22:54 schreef Nathan Monfils  >:
>
>> Hello!
>>
>> I was doing some editing on the N30 near Liège, when I noticed that its
>> relation was completely unordered, with ways near the city center being
>> next
>> to ways much further south (see relation `124374`).
>>
>> The wiki defines a relation as an *ordered list*, yet only mentions order
>> for
>> bus lines. Is there a need for the road relations to be ordered correctly?
>>
>> Regards,
>>
>> Nathan Monfils
>>
>
> ___
> 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] National Road relation: does order matter?

[Jo]

for route=road relations order doesn't matter much. It's impossible to sort
them according to any meaningful criterion.

Polyglot

Op zo 2 sep. 2018 om 22:54 schreef Nathan Monfils :

> Hello!
>
> I was doing some editing on the N30 near Liège, when I noticed that its
> relation was completely unordered, with ways near the city center being
> next
> to ways much further south (see relation `124374`).
>
> The wiki defines a relation as an *ordered list*, yet only mentions order
> for
> bus lines. Is there a need for the road relations to be ordered correctly?
>
> Regards,
>
> Nathan Monfils
>
>
>
> ___
> 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] Opportuniteit voor OV mapper.

[Jo]

Oh, ik had die buslijnen al eens gemapt. Ja, fameuze verandering, geen 2,
2A en 2B meer. 2B ging naar België...

Komt er in LEFFRINCKOUCKE FORT DES DUNES een groter busstation?

Hmm, eens gaan kijken. Ik had alles mooi gemapt met nodes langs de weg.
sind februari 2018 heeft iemand dat compleet aangepast met nodes op de ways
en platform ways, ook al zijn er daar niet overal perrons langs die
kustweg, die voorstellen met een way is eigenlijk absurd.
Dus ik ga me daar niet mee bezig houden. Wat mij betreft een stap achteruit
om van 1 object per halte naar 2 te gaan.

Jo

Op wo 29 aug. 2018 om 22:47 schreef Marc Coevoet :

> Besten,
>
> Vanaf 1 sept verandert het OV van Duinkerke.  Er zal niet alleen een bus
> zijn om de 10' in het centrum, het schema van de stadsbedekking
> verandert totaal.
> En bovendien, de bus zal IEDERE dag GRATIS zijn. (al sinds een drietal
> jaar gratis in het weekend).
>
> Een kans dus voor een mapper, om de ganse dkbus.com te herschrijven in
> dkbus2018.com
>
>
> Marc
> PS: en wat heeft dat nu met Belgie te maken?  Wel de bus start oa in
> Adinkerke, aan het station.  Ipv ieder uur nu zowat om de 15' tot aan
> een groot knooppunt in Leffrinckoucke.
> --
> The "Penguin" has arrived - and he's not going away - ever.
> For former Apple users: Xubuntu.org (menu's up left)
> For former Windows users: Lubuntu.org (menu's down left)
>
> ___
> 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] Fwd: Oplijsting fietssnelwegen - hulp gezocht

[Jo]

If somebody were to pay me  €1 for each kilometer that I inventorise this
way, I'd jump on the train tomorrow and come back with 1 Mapillary
pictures of the actual state of the network. I'd prefer to do map it on
umap though. That way I could use some smart Overpass Queries to fetch data
from OSM directly, and draw lines for the missing 'wishful thinking' parts.

I already worked on F3 (more intersting bits missing) and F24 (almost non
existent where it's supposed to be) a bit.

Polyglot

Op wo 15 aug. 2018 om 14:08 schreef joost schouppe :

>
> Hi,
>
> The Fietsersbond would like to know how much of the Fietsostrades are
> already realized. They are looking for some volunteers to help them do
> that. Problem is that nobody really knows, and Fietsersbond needs to know
> this to be able to give an estimate of their cost to inventarize the
> network in detail. The data that will be created will be open data
> afterwards.
> it will probably be something like "look at the desired network data,
> match it to the underlying road network, and if there is a path or cycleway
> or road below it, consider it as needs-inventory". I think. Anyway, if you
> think it's interesting, read the mail below and contact Thierry by mail or
> phone (see below).
>
> -- Forwarded message -
> From: Meetfiets Fietsersbond 
> Date: di 14 aug. 2018 om 20:26
> Subject: Oplijsting fietssnelwegen - hulp gezocht
> [...]
> Het departement Mobiliteit en Openbare Werken van de Vlaamse overheid
> heeft op 24 juli een bestek uitgeschreven om alle fietssnelwegen
>  in Vlaanderen
> te auditen (met een meetfiets). *De offerte hiervoor moet ingediend
> worden op 24 augustus!*
>
> Het departement noch de de Vlaamse provincies, die mee trekker zijn van de
> fietssnelwegen, weten hoeveel kilometer fietssnelweg er effectief al ligt
> op het
> terrein. Dit komt omdat heel wat fietssnelwegen "wenslijnen" zijn, en dus
> voor een deel gewoonweg nog niet bestaan.
> Anderzijds komt dit ook doordat er verschillende wegbeheerders zijn
> (Administratie Wegen en Verkeer voor de gewestwegen, gemeenten voor de
> gemeentewegen
> en de Vlaamse Waterweg voor de jaagpaden).
>
> Wat we nu voor de offerte moeten doen is een zo *nauwkeurig mogelijke
> inschatting* maken van het effectief te auditen kilometers fietssnelweg.
> In de praktijk komt het erop neer dat we op basis van terreinkennis, OSM,
> google streetview, mapillary  en eventuele andere bronnen,
> op een Google Maps kaart (die al aangemaakt is) segmenten gaan aanmaken
> (m.a.w. lijntjes trekken) waarmee automatisch het aantal km berekend wordt.
>
> Ondertussen hebben we met 4 vrijwilligers een flink deel opgelijst (zie
> bijlage), maar er zijn er 3 die binnenkort weeral op verlof vertrekken. Ik
> ben dus nog op zoek naar 1 of 2 personen die tussen nu en maandag nog
> kunnen helpen met oplijsten.
> Ter info nog: Prov. Antwerpen valt al af omdat wij dat al gedaan hebben.
> En verder ook alle fietssnelwegen die op gewestwegen liggen, omdat de
> wegbeheerder AWV
> dit al doet.
> Limburg en een groot deel van West-Vlaanderen en VL-Brabant is al gedaan.
> Vooral voor Oost-Vlaanderen is nog hulp nodig.
>
> [...]
>
> *Thierry Jiménez & Werner Lievens | Fietsersbond vzw*
>
> *Team Meetfiets & Advies fietsinfrastructuur*
>
> 02 502 68 51 | 0498 57 47 49 | 0472 49 78 53
> Oude Graanmarkt 63, 1000 Brussel
> Facebook Fietsersbond Brussels Gewest
>  | Twitter
>  | Fietsersbond
> 
>
>
>
>
>
> ___
> 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] int_ref, ref spelling, no space between letter and number....

[Jo]

Karel, you are probably right, but the key to create such a blank is
commonly known as the space bar.

I would also remove the 'empty character' (Leerzeichen) here in Belgium.

In France it's consistently with a space, I guess they find it like that on
their signage.

Jo

Op za 11 aug. 2018 om 15:11 schreef Karel Adams :

> Excuse me for being pecky on language - for this once I feel free
> because language is (more or less) the subject matter anyway.
>
> Where @jakka writes "space", and @ruben neatly follows suit, I think the
> actual meaning is "blank".
>
> nl "spatie" => en "blank"
>
> en "space" => nl "ruimte"
>
> Not wanting to "score" any personal hits, just for the common good:
> allow me to recommend that English should only be used by those who
> master that subtle language really well. There is no reason for not
> posting in one's native language, on a list of regional importance such
> as this.
>
> Groeten :)
>
> Karel
>
>
> On 11/08/18 12:38, Ruben wrote:
> > Hi Frank,
> >
> > On Fri, 10 Aug 2018 21:06:54 +0200, Jakka  wrote:
> >> Where can I see and read what is the correct spelling of the E and
> other road network like A? Is there a space between the letter and number?
> >> The wiki pages
> https://wiki.openstreetmap.org/wiki/WikiProject_Europe/E-road_network and
> https://en.wikipedia.org/wiki/International_E-road_network are not clear
> about that...
> >> See the mapillary
> https://www.mapillary.com/map/im/vEtPrDgYQ9nVD2kfehABQg example: there
> are no spaces so should we adapt all those tags?
> > I believe our local refs are without space (so "A17", "R0", "N540"). Our
> signposting for international refs doesn't use a space either (E40), or
> sometimes a 'thin space' (E 40). I've never seen a full space (E 40).
> > On their site[1], the Flemish Agency for Roads and Traffic (AWV)
> consistently uses no space for both local and E refs. So I'd be inclined to
> say it's without space.
> >
> >> I see that most of int_ref is with space and ref and nat_ref without?
> But not always...
> > A few years ago, a French mapper came along and mechanically edited
> int_refs in Belgium. I asked them to stop but their changes were never
> fully reverted, so there are still int_refs with a space in Belgium.
> > I think it would be safe to remove the spaces mechanically, as it would
> actually be reverting an earlier unauthorized mechanical edit. What do you
> think?
> >
> > [1] https://wegenenverkeer.be/
> >
> > Cheers,
> > Ruben
> >
> > ___
> > 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

Re: [OSM-talk-be] How to request arbitration?

[Jo]

Karel, you are going to have to fly over to that airstrip and put up a
large sign next to it . Photograph it and hope it catches on among the
local population... (That's how I read Frederik Ramms comment)

I didn't look at the changeset. We have a description tag, if it's a
description and not a name. Of course if it's only in English, maybe
description:en?

Anyway, you made it into WeeklyOSM.

Jo

2018-04-02 7:57 GMT+02:00 Marc Gemis :

> Did you contact the owner of the airfield to find out how they name it
> ? Did you find a sign along the street pointing to the airfield with a
> name ? Is there a name sign at the entrance ? Is there an official
> document  from a government which mentions a name ?
>
> If all of those questions return false, i.e. no name, then the
> airfield has no name. Maybe there are a few other places where we can
> look for the item of items, but making them up from ones armchair is
> certainly not one of them.
>
> No everybody gives their house, private tennis court, driveway or
> airfield a name. So noname=yes might be the only thing we can do. We
> should not make up names as "Airfield of Family Anderson", "Airfield
> near road N111" or whatever.
>
> Regards
>
> m.
>
>
> p.s. @Pieter, SomeoneElse, who participates in the changeset
> discussion is member of the DWG.
>
> On Sun, Apr 1, 2018 at 11:08 PM, Karel Adams  wrote:
> > I am in a bitter dispute with a couple of mappers who absolutely refuse
> to
> > accept a "name=*" tag on an aerodrome because officially it has no name -
> > indeed it figures in no official document.
> >
> > My point of view is that an "invented" name - which can be discussed, of
> > course - is better than no name at all but they are quite adamant. How to
> > address this?
> >
> > For the details: see https://www.openstreetmap.org/changeset/57717417
> and
> > https://www.openstreetmap.org/way/573934869
> >
> > https://wiki.openstreetmap.org/wiki/Names has been called in but I found
> > nothing there to indicate only official names should be mentioned.
> >
> > This seems really a case for arbitration, but how to request it?
> >
> > Karel
> >
> >
> > ___
> > 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

Re: [OSM-talk-be] OSM Belgium Local Chapter application, community feedback wanted

[Jo]

Yes, life will never be the same anymore :-)

Jo

2018-03-30 15:04 GMT+02:00 Steven Clays :

> Looking forward to participate in an official local chapter! 🎩
>
> 2018-03-30 9:42 GMT+02:00 Marc Gemis :
>
>> I have confidence that the people behind the application know what
>> they do and I hope that a local chapter will be beneficial for
>> OpenStreetMap in Belgium.
>>
>> regards
>>
>> m.
>>
>> On Fri, Mar 30, 2018 at 8:41 AM, joost schouppe
>>  wrote:
>> > Martijn from the OpenStreetMap Foundation had some trouble reaching
>> talk-be,
>> > so I'm sending this message on his behalf. Please keep his mail in the
>> > conversation!
>> > ---
>> >
>> > French / Dutch below.
>> >
>> > Hi all,
>> >
>> > You may be aware that OSMbe has applied to become an official Local
>> Chapter
>> > of the OpenStreetMap Foundation. As part of the application process, I
>> am
>> > asking you, the community, to share any questions, comments or concerns
>> that
>> > you have, so we can address them.
>> >
>> > You can find all the information about this Local Chapter application
>> on the
>> > wiki:
>> > https://wiki.osmfoundation.org/wiki/Local_Chapters/Applications/Belgium
>> >
>> > We will close this round of discussion two weeks from now (April 11th).
>> > I am looking forward to hearing your responses.
>> >
>> > Best regards,
>> > 8<8<8<8<8<8<8<
>> > Beste allemaal,
>> >
>> > Jullie hebben wellicht vernomen dat OSMbe zich kandidaat heeft gesteld
>> om
>> > een officieel 'Local Chapter' van de OpenStreetMap Foundation te
>> worden. Als
>> > onderdeel van het proces nodig ik de Belgische community namens de
>> > Foundation uit om vragen of eventuele bezwaren kenbaar te maken.
>> >
>> > Alle informatie over de kandidatuur is te vinden op de OSMF wiki:
>> > https://wiki.osmfoundation.org/wiki/Local_Chapters/Applications/Belgium
>> >
>> > Deze consultatieronde duurt twee weken en sluit op 11 april. Ik kijk uit
>> > naar jullie reacties.
>> >
>> > Beste groeten,
>> > 8<8<8<8<8<8<8<
>> > Vous êtes peut-être déjà au courant mais OSMbe a soumis une demande pour
>> > devenir un Chapitre Local de la Fondation OpenStreetMap.
>> > Dans le cadre du processus de demande, je vous demande, à vous la
>> > communauté, de poser vos questions, vos commentaires ou vos
>> préoccupations
>> > afin que nous puissions y répondre.
>> >
>> > Vous pouvez trouver toutes les informations nécessaires au sujet de
>> cette
>> > demande sur le wiki :
>> > https://wiki.osmfoundation.org/wiki/Local_Chapters/Applications/Belgium
>> >
>> > Nous clôturerons cette discussion dans 2 semaines.
>> > J'ai hâte de lire vos réponses.
>> >
>> > Bonne journée.
>> > --
>> > Martijn van Exel
>> > Secretary, OpenStreetMap Foundation
>> >
>> > ___
>> > 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-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] temporary cycle routes

[Jo]

Around Leuven there are a few that are (partially) signposted. But if you
want to take them to get all the way to Brussels for example, you'd either
need a helicopter to get across R0 or make a serious detour. I mapped some,
including the detours.

I tried mapping the one that goes to Tienen, but had to give up. All
detours at present.

2018-02-02 7:56 GMT+01:00 Marc Gemis :

> I would only map them if they are signposted. So if there are signs
> indicating how you get from one dedicated fiets-o-strade section to
> another via "regular" roads, no problem. If there are no signs, let
> the router decide the route based on other tags.
>
> As for the concrete that has to be placed on the ground. I'm not in
> favour of mapping things that one day might be there (or were there
> for that matter). There are already enough objects one have to
> maintain that are actually there.
>
> regards
>
> m
>
> On Thu, Feb 1, 2018 at 4:29 PM, Ben Abelshausen
>  wrote:
> > In London some of the routes are mapped as proposed, it's a bit annoying
> if
> > you don't know that they are just proposed and not actually there:
> >
> > https://www.openstreetmap.org/relation/6691788
> >
> > Rendering is a dotted version of the normal line on the cycle layer:
> >
> > https://www.openstreetmap.org/#map=18/51.54524/-0.01871&layers=C
> >
> > So, not sure if we should be mapping this if they don't exist yet... but
> if
> > it's an 'official' detour why not? Some of these routes are only virtual
> > anyway and not signed at all.
> >
> > Cheers,
> > Ben
> >
> > On Thu, Feb 1, 2018 at 2:55 PM, joost schouppe  >
> > wrote:
> >>
> >> Hi,
> >>
> >> I got an interesting question today. As the Flemish "fietsostrades"
> >> (fietssnelwegen, or cycle highways) are taking shape, so they are being
> >> mapped in OSM. People are already using the data, even though in
> reality,
> >> this is till very much a project.
> >>
> >> In more and more places, parts are completely ready, but then just stop.
> >> And in some cases, there is an "official detour" of the fietsostrade. So
> >> while the infrastructure is not there yet, in a sense the route is
> already
> >> there.
> >>
> >> How do you think this should be mapped, if at all?
> >>
> >> --
> >> Joost Schouppe
> >> OpenStreetMap | Twitter | LinkedIn | Meetup
> >>
> >> ___
> >> Talk-be mailing list
> >> Talk-be@openstreetmap.org
> >> https://lists.openstreetmap.org/listinfo/talk-be
> >>
> >
> >
> > ___
> > Talk-be mailing list
> > Talk-be@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-be
> >
>
> ___
> 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] low emission zones

[Jo]

The one in Antwerpen is now in OpenStreetMap, completely based on the KML
file they provided. I don't see any correlation with boundaries we already
had in OSM.

Jo

2018-02-01 10:13 GMT+01:00 wannes :

> Geen ervaring met importeren: kan (en MAG!) deze geimporteerd worden van
> http://opendata.antwerpen.be/datasets/lage-emissiezone-afbakening
> http://opendata.antwerpen.be/gratis-open-data-licentie
>
> On Thu, Feb 1, 2018 at 9:52 AM, joost schouppe 
> wrote:
>
>> Hi,
>>
>> There are now two low emission zones in Belgium, neither of which is
>> mapped. You will find all the needed info to map them on this wiki page:
>>
>> https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dlow_emiss
>> ion_zone#Belgium
>>
>> Anyone up to the challenge?
>>
>> --
>> Joost Schouppe
>> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
>> Twitter <https://twitter.com/joostjakob> | LinkedIn
>> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
>> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>>
>> ___
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
>>
>>
>
>
> --
> wannes
>
> ___
> 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] low emission zones

[Jo]

I mappped the one around Brussels:
https://www.openstreetmap.org/relation/7966939

Started with the boundary of the Brussels Region, then added all the
exceptions for R0 and 3 parking lots.

Jo

2018-02-01 15:36 GMT+01:00 joost schouppe :

> They have explicitly asked to map this sometime back, so license-wise it's
> not a problem IMHO.
> The license was also meant to be as close as possible to the Flemish Open
> Data License, which is deemed OK.
>
> Should we go to imports for a single multipolygon? I don't know, but it
> sounds a little strange to me.
>
> 2018-02-01 10:13 GMT+01:00 wannes :
>
>> Geen ervaring met importeren: kan (en MAG!) deze geimporteerd worden van
>> http://opendata.antwerpen.be/datasets/lage-emissiezone-afbakening
>> http://opendata.antwerpen.be/gratis-open-data-licentie
>>
>> On Thu, Feb 1, 2018 at 9:52 AM, joost schouppe 
>> wrote:
>>
>>> Hi,
>>>
>>> There are now two low emission zones in Belgium, neither of which is
>>> mapped. You will find all the needed info to map them on this wiki page:
>>>
>>> https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dlow_emiss
>>> ion_zone#Belgium
>>>
>>> Anyone up to the challenge?
>>>
>>> --
>>> Joost Schouppe
>>> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
>>> Twitter <https://twitter.com/joostjakob> | LinkedIn
>>> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
>>> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>>>
>>> ___
>>> Talk-be mailing list
>>> Talk-be@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-be
>>>
>>>
>>
>>
>> --
>> wannes
>>
>> ___
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
>>
>>
>
>
> --
> Joost Schouppe
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
> ___
> 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] OSM and SIAMU

[Jo]

If I  understood correctly every single street name of the Netherlands is
already in Wikidata.

2017-11-23 14:31 GMT+01:00 joost schouppe :

> Jo,
> Does Urbis hold the same authority about the correct street name as CRAB
> does in Flanders? I've understood there might not be a single authoritaive
> list for Brussels, but I'm not sure.
> Do you have an idea on how it would actually work on this scale with
> Wikidata? Do you know of some projects that use Wikidata on that scale? I'm
> asking because I think Agentschap Informatie Vlaanderen might be really
> interested in linking their data to Wikidata, and from there to OSM. It
> helps that it allows for a single datamodel for any country that uses
> street names. And thus for one single QA tool to keep street names valid
> anywhere that model is used.
>
> 2017-11-22 22:11 GMT+01:00 Jo :
>
>> Urbis released all the data for the Brussels region several years ago, so
>> it should be possible to use that data like we use CRAB in Flanders.
>>
>> My personal preference would be to work with wikidata identifiers for
>> every street in and around Brussels.
>>
>> Polyglot
>>
>> 2017-11-22 21:09 GMT+01:00 joost schouppe :
>>
>>> Hi Nadia,
>>>
>>> Nice to see you here!
>>>
>>> I've played with the idea of unique identifiers for OSM objects myself
>>> before. But it remains controversial in the international community (not so
>>> much in Belgium). Here's an article I wrote long long time ago about it.
>>> It's especially useful for the comments, which outline some of the problems
>>> with my idea [1].
>>> Also relevant to get a feel for the issues is when this proposition for
>>> a global reviews database was discussed. Possibilities for linking were
>>> investigated, and adding external IDs got quite a bit of headwind.
>>>
>>> There has been a discussion about wikidata recently that turned so big
>>> that I couldn't follow at all. But at least until recently, there seemed to
>>> be an openness towards adding wikidata unique IDs. I don't know enough
>>> about it to have a real opinion, but to me it sounds elegant to translate
>>> an official source of streetnames into wikidata objects, then adding that
>>> identifier to OSM. Maybe those more versed in Wikidata can explain.
>>>
>>> That said, I'm not sure your proposed solution is the most simple
>>> solution to the problem. Given that streetnames are given by the
>>> government, in theory there is one and only possible way of writing the
>>> name. In Flanders, that would be the CRAB name. In the very few cases where
>>> CRAB is still wrong (or more to the point: the sign in the street says
>>> something slightly different than what CRAB says), you could have
>>> name="Name on the Street Sign" and something like name_official="Name in
>>> CRAB". In that situation, the problem is different: how do make sure all
>>> the street names are and stay correct in OSM. By coincidence, we are
>>> actually working towards doing something like that. In the scope of the
>>> Road Completion project [1] we want to start "attribute/tag comparison"
>>> real soon. Glenn as well has built something that is even further along the
>>> line of being in production, where we look for "close to this official
>>> road, there is no OSM road with the same exact name".
>>> Similar bit different, we developed a website last Open Summer of Code,
>>> where official cycling network data is compared to OSM data all the time.
>>> That way we can make sure our Brussel cycling network is always at least as
>>> correct as the official data.
>>> It's only a few more steps (not easy ones, I know) until we can work
>>> this out further. Any difference in street names should then be fixed quite
>>> quickly. I'd rather see you guys helping out in this effort, than starting
>>> a cumbersome import.
>>>
>>> As far as I know, those codes are only open data in Flanders
>>> (accidentally through CRAB open data). One of the few rules about "what to
>>> map" is that it should be verifiable (preferable by anyone, in the field).
>>> There are a few exceptions, but they are rather rare. As long as the
>>> National Registry codes are not open data, that sounds lie a real problem
>>> to me. In fact, there is no way you can import data into OSM that is not
>>> open. Because then we would have to re-license OSM with the license of

Re: [OSM-talk-be] OSM and SIAMU

[Jo]

Urbis released all the data for the Brussels region several years ago, so
it should be possible to use that data like we use CRAB in Flanders.

My personal preference would be to work with wikidata identifiers for every
street in and around Brussels.

Polyglot

2017-11-22 21:09 GMT+01:00 joost schouppe :

> Hi Nadia,
>
> Nice to see you here!
>
> I've played with the idea of unique identifiers for OSM objects myself
> before. But it remains controversial in the international community (not so
> much in Belgium). Here's an article I wrote long long time ago about it.
> It's especially useful for the comments, which outline some of the problems
> with my idea [1].
> Also relevant to get a feel for the issues is when this proposition for a
> global reviews database was discussed. Possibilities for linking were
> investigated, and adding external IDs got quite a bit of headwind.
>
> There has been a discussion about wikidata recently that turned so big
> that I couldn't follow at all. But at least until recently, there seemed to
> be an openness towards adding wikidata unique IDs. I don't know enough
> about it to have a real opinion, but to me it sounds elegant to translate
> an official source of streetnames into wikidata objects, then adding that
> identifier to OSM. Maybe those more versed in Wikidata can explain.
>
> That said, I'm not sure your proposed solution is the most simple solution
> to the problem. Given that streetnames are given by the government, in
> theory there is one and only possible way of writing the name. In Flanders,
> that would be the CRAB name. In the very few cases where CRAB is still
> wrong (or more to the point: the sign in the street says something slightly
> different than what CRAB says), you could have name="Name on the Street
> Sign" and something like name_official="Name in CRAB". In that situation,
> the problem is different: how do make sure all the street names are and
> stay correct in OSM. By coincidence, we are actually working towards doing
> something like that. In the scope of the Road Completion project [1] we
> want to start "attribute/tag comparison" real soon. Glenn as well has built
> something that is even further along the line of being in production, where
> we look for "close to this official road, there is no OSM road with the
> same exact name".
> Similar bit different, we developed a website last Open Summer of Code,
> where official cycling network data is compared to OSM data all the time.
> That way we can make sure our Brussel cycling network is always at least as
> correct as the official data.
> It's only a few more steps (not easy ones, I know) until we can work this
> out further. Any difference in street names should then be fixed quite
> quickly. I'd rather see you guys helping out in this effort, than starting
> a cumbersome import.
>
> As far as I know, those codes are only open data in Flanders (accidentally
> through CRAB open data). One of the few rules about "what to map" is that
> it should be verifiable (preferable by anyone, in the field). There are a
> few exceptions, but they are rather rare. As long as the National Registry
> codes are not open data, that sounds lie a real problem to me. In fact,
> there is no way you can import data into OSM that is not open. Because then
> we would have to re-license OSM with the license of the National Registry :)
>
> One more thing is that using this ID will give you false certainty. You
> will get your results, most of the time. But someone might have corrected a
> segment (it used to have the name A, but it really is street B), and they
> will not know what to do with this strange ref number. So even after a
> succesful import, you would still need something like the constant
> comparison described above to check if the streetname is still what the
> unique identifier assumes it should be.
>
> Ben and I have also spent a lot of time thinking about this problem in
> general terms: "how do you keep external data synchronized to OSM". In the
> case of roads it shouldn't actually be that hard. Say you start of with a
> table joining the two datasets together based on the object IDs. You then
> need to monitor how both datasets evolve. On the OSM side, you only have to
> keep analysing segments that have changed a lot (say, the average
> coordinate is too far away; the total length changed too much) or have
> disappeared. Then you can have a process that finds if an object that is
> similar enough is still mapped in the same place. Only when a certain
> threshold is reached, there's a need for manual intervention to check what
> is going on.
> While this sounds complicated, I do think someone experienced in the
> field, could build a model in a couple of days. I think the end result
> would actually be more dependable than your idea, and probably less work to
> implement. I've built something solving a similar problem in FME in not too
> much time (a professional FME worker then re-built it in 

Re: [OSM-talk-be] Afbraak hoogspanningslijn: hoe aanpakken in OSM ?

[Jo]

zou het dan niet beter zijn om disused: o.i.d. voor de tags te zetten? Dan
wordt ze niet meer gerenderd, maar de kans is 0 dat iemand ze opnieuw zou
tekenen.

Jo

Op 13 november 2017 om 05:16 schreef Marc Gemis :

> Aangezien we enkel mappen wat nu zichtbaar is, zou ik opteren om alles te
> verwijderen.
> Er is dan wel een hele kleine kans dat iemand ze terug gaat intekenen aan
> de hand van oude luchtfoto's.
>
> m.
>
> 2017-11-12 17:52 GMT+01:00 Denis Verheyden :
>
>> Dag iedereen,
>>
>>
>> Een tijd geleden is Elia begonnen met de afbraak van de 70kV
>> hoogspanningslijn Schelle-Mechelen, die niet zo ver van mijn deur loopt:
>>
>> http://www.openstreetmap.org/way/23157086
>> <http://www.openstreetmap.org/way/23157086>
>> OpenStreetMap | Way: 23157086 <http://www.openstreetmap.org/way/23157086>
>> www.openstreetmap.org
>> OpenStreetMap is a map of the world, created by people like you and free
>> to use under an open license.
>>
>> Voor zover ik weet zijn er deze eeuw nog niet zo veel lijnen verdwenen,
>> er zijn er eerder bijgekomen of sommige hebben nieuwe
>> draadstellen/isolatoren gekregen voor een hoger voltage.
>>
>>
>> De vraag is nu: hoe pak ik dit aan in OSM ? Gewoon alle palen en de
>> hoogspanningslijn verwijderen ?
>>
>> Of alles omzetten met een tag 'former:' of 'historic:' voor ? In dat
>> geval kunnen kaarten die voormalige hoogspanningslijnen weergeven nog
>> altijd deze lijn weergeven, terwijl in de OSM default view de lijn niet
>> meer getoond wordt (zoals er nu ook geen kabels meer hangen)
>>
>>
>> Groeten,
>>
>> Denis
>>
>>
>>
>> ___
>> 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

Re: [OSM-talk-be] landuse mapping

[Jo]

I also found Julien Radoux' talk very interesting. We should definitely
seize this opportunity to improve our data. Unfortunately I missed Julien
Minet's talk.

I'm interested in participating online in such a meeting.

Jo

2017-11-08 17:10 GMT+01:00 joost schouppe :

> Hi,
>
> We would have loved to have a landuse-mapping debate during Foss4G, it
> didn't really happen though. There were two very cool presentations about
> landuse mapping though, by Julien Minet and Julien Radoux.
>
> You can see Julien's presentation here [1]. It does a nice job of
> summarizing the state of the landuse map, and shows some of the current
> mapping dilemmas.
>
> Julien Radoux explained how OSM is useful - and sometimes fails - for his
> project to map the landcover in Wallonia for the Lifewatch project [2].
> This data is available for download and could possibly be interesting for
> us - not for a simple import, but at least as food for a mapping challenge
> to map Wallonia landuse in detail.
>
> The agenda of the meeting would be:
> - work on a Belgian proposal to deal with current dilemmas, so "Belgian
> mapping standards". These would hopefully be followed internationally, but
> we have to start somewhere. This would build especially on the thoughts of
> Marc and Julien on the subject and would ideally result in a Belgian
> mapping standards on the wiki.
> - define usecases for the dataset Julien Radoux is providing, and make
> sure that everything is OK to make that happen
> - what you bring to the table
>
> To move forward, I would like to propose having a (virtual) meeting about
> the subject. Who would be interested in participating? We could have a real
> meeting (probably in Brussels or Namur) with some people participating
> online.
>
> 1: https://cdn.rawgit.com/nobohan/OSMLanduseAnalyzer/
> 9a8b0290/presentation/2017_10_26_FOSS4G.be_OSMLanduse/index.html#/
> 2: http://www.lifewatch.be/en/lifewatch-wb-ecotope-database
>
> --
> Joost Schouppe
>
> ___
> 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] Meetup about rendering of maps

[Jo]

Yes, we can look into github on Wednesday evening. Joost, please set up a
repo for it.

OK, so with a bit of luck we have Clem to show Maperitive and Pieter to
show QGIS for rendering.

Yesterday I started watching this series:
https://www.youtube.com/playlist?list=PL7HotvlLKHCs9nD1fFUjSOsZrsnctyV2R

This explains it quite succinctly, but putting it into practice is still a
challenge with QGIS. Mine crashes a lot. Now I'm thinking it would be
better if I would involve PostGIS, instead of working with files, for a
larger region.

Somehow Maperitive was able to cope with it, but there my problem is
automating the workflow to get consistent results.

Jo

2017-10-05 11:06 GMT+02:00 Pieter Brusselman <
pieter.brussel...@tragewegen.be>:

> @Joost,
>
> OK, you can do that.  But I need a short intro in Github.  Maybe wendsday
> evening?
>
>
> Pieter Brusselman
> *Cartografie ~ Projectmedewerker*
>
> [image: (logo boompja)] <http://www.tragewegen.be>
>
> *A* Kasteellaan 349 A, 9000 Gent
> *T* 09 / 331 59 27
> *W *www.tragewegen.be
>
> [image: logo facebook] <http://www.facebook.com/tragewegen>
>
> ter info: ik werk niet op vrijdag
> Op 5/10/2017 om 10:48 schreef joost schouppe:
>
> Pieter,
>
> I could make a repository on our github page https://github.com/osmbe/
> for a QGIS project if you're interested.
>
> 2017-10-05 10:22 GMT+02:00 Jo :
>
>> Hey, that is great news! I will also come to FOSS4G the day after our
>> Meetup. Somebody who uses Maperitive to render maps for the GR guides will
>> probably also join us on Wednesday evening.
>>
>> Jo
>>
>> 2017-10-05 9:33 GMT+02:00 Pieter Brusselman <
>> pieter.brussel...@tragewegen.be>:
>>
>>> Hi,
>>>
>>> The last year we (trage wegen vzw) made a lot of maps based on OSM-data
>>> using QGIS.  On octobre 26th we give a talk about this on FOSS4G.  But I
>>> like to come to the meeting to talk about this and sharing experience (and
>>> stylsheets :-))
>>>
>>> Grtz,
>>> Pieter
>>>
>>> Pieter Brusselman
>>> *Cartografie ~ Projectmedewerker*
>>>
>>> [image: (logo boompja)] <http://www.tragewegen.be>
>>>
>>> *A* Kasteellaan 349
>>> <https://maps.google.com/?q=Kasteellaan+349&entry=gmail&source=g> A,
>>> 9000 Gent
>>> *T* 09 / 331 59 27
>>> *W *www.tragewegen.be
>>>
>>> [image: logo facebook] <http://www.facebook.com/tragewegen>
>>>
>>> ter info: ik werk niet op vrijdag
>>> Op 5/10/2017 om 9:11 schreef joost schouppe:
>>>
>>> I like to use QGIS for basic stuff. E.g. use an open layers background
>>> map, and some data on top of that to highlight certain details. E.g. the
>>> maps in this diary were made with OSM data queried from overpass and some
>>> open layers map: http://www.openstreetmap.org/user/joost%20schouppe/diar
>>> y/38103
>>>
>>> It's also relativly easy to use QGIS for rendering OSM data using a
>>> sqlite database (and that's easy to make within the package, based on a
>>> .pbf file). I don't have experience making a pretty map that way, but it
>>> can be quite useful to make maps highlighting specific kinds of data. E.g.
>>> maps like these are easy to make in QGIS: http://www.openstreetmap
>>> .org/user/joost%20schouppe/diary/40267
>>> (though here the data comes from the osm-history toolchain, not just
>>> from a pbf file)
>>>
>>> I think theoretically you could use QGIS and a stylesheet to make a
>>> pretty map from scratch, but haven't seen an example yet. And someone has
>>> been working for years on doing something similar in ArcGIS, and I don't
>>> think he released it yet.
>>>
>>> 2017-10-05 8:17 GMT+02:00 Jo :
>>>
>>>> Hi,
>>>>
>>>> During the next Leuven Monthly OSM Meetup I would like to discuss
>>>> rendering. I was using Maperitive in the past to create this:
>>>>
>>>> https://upload.wikimedia.org/wikipedia/commons/a/a2/Pad_van_
>>>> Ad_op_OSM.png
>>>>
>>>> I know. I should update that map more regularly...
>>>>
>>>> Would it make sense to try and use QGIS for rendering? Are there other
>>>> solutions in the mean time?
>>>>
>>>> Maybe somebody with more expertise in this would like to come and give
>>>> a demo?
>>>>
>>>> Jo
>>>>
>>>> ___

Re: [OSM-talk-be] Meetup about rendering of maps

[Jo]

Hey, that is great news! I will also come to FOSS4G the day after our
Meetup. Somebody who uses Maperitive to render maps for the GR guides will
probably also join us on Wednesday evening.

Jo

2017-10-05 9:33 GMT+02:00 Pieter Brusselman :

> Hi,
>
> The last year we (trage wegen vzw) made a lot of maps based on OSM-data
> using QGIS.  On octobre 26th we give a talk about this on FOSS4G.  But I
> like to come to the meeting to talk about this and sharing experience (and
> stylsheets :-))
>
> Grtz,
> Pieter
>
> Pieter Brusselman
> *Cartografie ~ Projectmedewerker*
>
> [image: (logo boompja)] <http://www.tragewegen.be>
>
> *A* Kasteellaan 349
> <https://maps.google.com/?q=Kasteellaan+349&entry=gmail&source=g> A, 9000
> Gent
> *T* 09 / 331 59 27
> *W *www.tragewegen.be
>
> [image: logo facebook] <http://www.facebook.com/tragewegen>
>
> ter info: ik werk niet op vrijdag
> Op 5/10/2017 om 9:11 schreef joost schouppe:
>
> I like to use QGIS for basic stuff. E.g. use an open layers background
> map, and some data on top of that to highlight certain details. E.g. the
> maps in this diary were made with OSM data queried from overpass and some
> open layers map: http://www.openstreetmap.org/user/joost%20schouppe/
> diary/38103
>
> It's also relativly easy to use QGIS for rendering OSM data using a sqlite
> database (and that's easy to make within the package, based on a .pbf
> file). I don't have experience making a pretty map that way, but it can be
> quite useful to make maps highlighting specific kinds of data. E.g. maps
> like these are easy to make in QGIS: http://www.
> openstreetmap.org/user/joost%20schouppe/diary/40267
> (though here the data comes from the osm-history toolchain, not just from
> a pbf file)
>
> I think theoretically you could use QGIS and a stylesheet to make a pretty
> map from scratch, but haven't seen an example yet. And someone has been
> working for years on doing something similar in ArcGIS, and I don't think
> he released it yet.
>
> 2017-10-05 8:17 GMT+02:00 Jo :
>
>> Hi,
>>
>> During the next Leuven Monthly OSM Meetup I would like to discuss
>> rendering. I was using Maperitive in the past to create this:
>>
>> https://upload.wikimedia.org/wikipedia/commons/a/a2/Pad_van_Ad_op_OSM.png
>>
>> I know. I should update that map more regularly...
>>
>> Would it make sense to try and use QGIS for rendering? Are there other
>> solutions in the mean time?
>>
>> Maybe somebody with more expertise in this would like to come and give a
>> demo?
>>
>> Jo
>>
>> ___
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
>>
>>
>
>
> --
> Joost Schouppe
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
>
> ___
> Talk-be mailing 
> listTalk-be@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-be
>
>
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

[OSM-talk-be] Meetup about rendering of maps

[Jo]

Hi,

During the next Leuven Monthly OSM Meetup I would like to discuss
rendering. I was using Maperitive in the past to create this:

https://upload.wikimedia.org/wikipedia/commons/a/a2/Pad_van_Ad_op_OSM.png

I know. I should update that map more regularly...

Would it make sense to try and use QGIS for rendering? Are there other
solutions in the mean time?

Maybe somebody with more expertise in this would like to come and give a
demo?

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

Re: [OSM-talk-be] Visit to Tourism Pajottenland

[Jo]

Ik was deze namiddag op een bijeenkomst van Bos en Natuur, maar er waren
ook andere mensen aanwezig. Onder andere iemand van Toerisme Vlaanderen,
die zeer geïnteresseerd was voor de wandelnetwerken.

Miisschien moet ik de volgende meetup in Leuven eens kaderen in het mappen
van wandelroutes? En de mensen van GR ook nog eens uitnodigen.

Jo

2017-10-04 15:50 GMT+02:00 Marc Gemis :

> Today I visited Tourism Pajottenland to explain OSM to them.
>
> Here's a brief summary of their plans. If you have contact with
> similar origanisations in your area, let me know. They will all have
> to make the same inventory.
>
> They have to make an inventory of all non-protected heritage items, be
> it buildings, pillories, trees or hedges.
> just like any other region in Flanders. Nobody has a system for this yet.
> So they are thinking of doing part of it in OSM (the data we can use).
> This would also be used as some kind of base for the volunteers they
> will train to make the full inventory of the items. I was thinking
> about MapContrib. Isn't there a way to have private fields that are
> not uploaded to OSM ?
> They will make a publication of Pajot-Zenne for Spring 2018 in which
> they will present OSM, but also waarneming.be and may some other
> projects. There will be an announcement for workshops around those
> projects. I already volunteered for the OSM part, but of course others
> are welcome to join me. Furthermore I will get an updated list of
> heritage, so I can start adding it to OSM.
> I will also recontact Rivierenland to tell them about this project, as
> they were thinking of similar projects.
>
> Another topic are the walking networks. They will be reorganized, new
> maps will have to be published. Alwin was already dreaming of having
> them published in the magazine by the time the official brochures will
> be published.
> Also part of the network will be completely digital. No more print
> outs or poles, just the wandelknooppunt.be app.
>
> regards
>
> m
>
> ___
> 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] Do you Tag those as cycleway?

[Jo]

It definitely is not always permitted to ride a bicycle against the flow of
traffic on oneway streets.

The law was changed at some point to allow administrations to create oneway
streets where bicycles are allowed in both directions, but it's not for all
oneway strees.

Jo

2017-09-30 11:56 GMT+02:00 Marc Gemis :

> I thought was always allowed to drive in the opposite direction under
> Belgian law. What does not mean that a sign to remind car drivers  is
> welcome.
>
> m.
>
> On Sat, Sep 30, 2017 at 9:19 AM, marc marc 
> wrote:
> > Hello,
> >
> > Le 29. 09. 17 à 22:42, eMerzh a écrit :
> >> https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,
> 141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!
> 2e0!7i13312!8i6656
> >
> > imho the bike painted in the opposite direction to what appears to be a
> > one-way street is intended to warn that bike is allowed in the reverse
> > direction (a traffic sign should exist under the one-way traffic sign
> > but no traffic sign exist at the other end of the street)
> >
> > Regards,
> > Marc
> > ___
> > 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

Re: [OSM-talk-be] Do you Tag those as cycleway?

[Jo]

True, we could use shared_lane, but then we either have to do that on all
highways where bicycles aren't banned, or we go on with that as the de
facto standard.

The fact that a bicycle is drawn, doesn't make it 'more' of a shared lane
than it would be without the wasted paint.

All it does is make motorists aware that there might be bicycles sharing
their lane. Something they should have been aware of anyway.

2017-09-30 8:07 GMT+02:00 Marc Gemis :

> cycleway=shared_lane
> https://wiki.openstreetmap.org/wiki/Key:cycleway#Shared_cycle_lanes
>
> note that https://wiki.openstreetmap.org/wiki/Proposed_features/
> shared_lane
> says nothing about any required legal status.
>
> m.
>
>
> On Fri, Sep 29, 2017 at 10:42 PM, eMerzh  wrote:
> > hi,
> >
> > i stumble upon some streets that have small cycles drawn on the street
> now
> > and then, and often there are small dashed line at the start or the end
> of
> > the street,
> > but tagging those as cycleway seems a bit weird as there are no clear
> > delimitations...
> >
> >
> > How to you tag thoses?
> >
> >
> > An example :
> > https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,
> 141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!
> 2e0!7i13312!8i6656
> >
> >
> > Thanks
> >
> > ___
> > 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

Re: [OSM-talk-be] Do you Tag those as cycleway?

[Jo]

It's not only in Brussels that they had leftover paint. Maybe it would have
been better if they had drawn some flowers...

They are indeed meaningless as far as traffic rules go. I guess they only
mean something to the politicians who decided to draw them.

Polyglot

2017-09-29 22:56 GMT+02:00 Wouter Hamelinck :

> Ah, Brussels where they think that painting cycles randomly in streets and
> on sidewalks results in cycling infrastructure.
> It is very simply. The meaning of those painted cycles is the same as when
> they would have painted flowers or hearts or something; none whatsoever. It
> doesn't mean anything. Maybe that they had some remnants of paint that they
> wanted to get rid of.
> The practical answer is that you don't tag them.
>
> wouter
>
> On Fri, Sep 29, 2017 at 10:42 PM, eMerzh  wrote:
>
>> hi,
>>
>> i stumble upon some streets that have small cycles drawn on the street
>> now and then, and often there are small dashed line at the start or the end
>> of the street,
>> but tagging those as cycleway seems a bit weird as there are no clear
>> delimitations...
>>
>>
>> How to you tag thoses?
>>
>>
>> An example :
>> https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,141.
>> 06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!2e0!7i13312!8i6656
>>
>>
>> Thanks
>>
>> ___
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
>>
>>
>
>
> --
> "Den som ikke tror på seg selv kommer ingen vei."
>- Thor Heyerdahl
>
> ___
> 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] OSM track at Foss4G be

[Jo]

Normally Giacomo, my GSoC student already sent in a proposal about
PT_Assistant.

If there is interest, I can do a workshop with it, working on public
transport,bicycle and hiking route relations

Jo

2017-08-25 17:22 GMT+02:00 joost schouppe :

> Just a reminder that the deadline is approaching, and we'd like to see
> more talks about OSM! It does NOT have to be a presentation, you can also
> propose mapping sessions, tagging discussions, etc.
> I'd love to see a talk about the GRB import, tools for public transport or
> biking route validation, OSM apps, JOSM presets and other cool stuff this
> community has been working on.
>
> (there are already a few really cool proposals in, so SAVE THE DATE even
> if you're not presenting)
>
>
> 2017-07-03 18:16 GMT+02:00 joost schouppe :
>
>> Hi,
>>
>> All OpenStreetMap contributors and data users are invited to submit a
>> proposal for the next Foss4G be event. There will be a special
>> OpenStreetMap track that OSM Belgium will help organize.
>>
>> Did you work with OpenStreetMap data? Did you work with the OpenStreetMap
>> community? Did you make new tools for mappers or map users?
>>
>> All of this is welcome, and more! OpenStreetMap is a creating community,
>> so you are invited to submit workshop ideas too. Want to work on tagging
>> discussions? Improve documentation? Teach people about mapping special
>> interest stuff? Want to go outside and collect real life data? Go ahead!
>>
>> The call for papers is out:
>> https://wiki.osgeo.org/wiki/FOSS4G-BE_2017_Call_for_Papers
>>
>> Event: October 26th 2017, Brussels
>> Deadline for proposals: September 4th, but selection will already start
>> early August!
>>
>> If you would like to help out with selecting proposals, or with general
>> organisation of the event, send a mail to commun...@osm.be!
>>
>>
>> --
>> Joost Schouppe
>> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
>> Twitter <https://twitter.com/joostjakob> | LinkedIn
>> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
>> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>>
>
>
>
> --
> Joost Schouppe
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
> ___
> 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] open summer of code: cycling event

[Jo]

I'm always prepared to give a presentation on how to use JOSM for mapping
route relations.

Jo

2017-06-23 23:03 GMT+02:00 joost schouppe :

> Hi,
>
> This Open Summer of Code, we'll be supporting two projects about cycling
> data in OpenStreetMap. We'll be working with the Brussels region to check
> and complete their cycle route data in OSM. Then that data, mapped in OSM,
> will be used to build an app to guide cyclists along those cycle networks.
> Several advanced students will do this over a month in July.
>
> There will be some mapping work to do! So we're organizing an event on
> July 21st where you are welcome to help out on these projects. With the
> support of Open Belgium, this event became a bit larger. Several
> organisations (Fietsersbond, Antwerpen aan 't Woord, Horizontal Cities)
> will join, and talk about how they use or create open cycling data. In the
> afternoon, it's up to us to give workshops on how to contribute to OSM data
> for cyclists and about the tools that are available to help organisations
> like these with data collection and making maps for their networks.
>
> This is an invitiation to participate, and especially to join and give a
> workshop. We could work on things like tagging best practices, use of
> Mapcontrib for easy data collection, Umap and overpass for easy webmaps and
> more technical solutions.
>
> Send a mail to commun...@osm.be if you're willing to help out.
>
> Registration and more information on the event:
> https://openbikedatamapping.eventbrite.com
>
> --
> Joost Schouppe, Ben Abelshausen & Jonathan Belien
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
> ___
> 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] Belang van photo's.

[Jo]

je kan de sleutel van de foto ook in de Mapillary tag opnemen. Niet de hele
url, enkel het laatste gedeelte dat voor elke foto verschillend is... maar
ik weet dat je dat ook niet ziet zitten.

In ieder geval zijn die foto's alleszins zeer nuttig, maar wat OSM betreft
is iets pas gemapt, als het als object met al zijn attributen is opgenomen
in de database. Dan pas kunnen we er iets mee. Weergeven op een kaart,
opzoeken, statistieken mee berekenen, enz...

Jo



Op 11 juni 2017 om 20:11 schreef Marc Gemis :

> Nu ik begrijp wel waar je naar toe wil, bedankt.
>
> Zelf gebruik ik daarvoor de source_ref tag op de changeset met een
> verwijzing naar de foto's. Ik ga daarvoor de database niet groter maken met
> een foto van ieder objectje. Als je dat extreem doortrekt, moet je een foto
> plaatsen bij een gebouw met het huisnummer en een waarop het aantal
> verdiepingen te zien zijn, eentje voor de locatie van de ingang, enz. En je
> hebt maar 1 image tag.
>
> Ik ga ook altijd verder op wat ik gezien heb, en niet op een foto van een
> ander die bv. enkele maanden of zelfs dagen oud is. Zo'n foto kan al lang
> achterhaald zijn tegen dat ik er passeer. Denk maar aan je Mapillary reeks
> in Rumst die achterhaald was van zodra de rotonde was afgewerkt.
>
> Ik gebruik de image tag enkel maar bij historische objecten en omdat die
> op historic.places getoond worden. Feitelijk is dat ook geen goede reden om
> die tag erbij te plaatsen. Ze kunnen de foto net zo goed via Wikidata
> ophalen. Ergens hoort de image tag niet echt thuis in OSM. Maar ik ga mijn
> gewoonte toch niet wijzigen :-)
>
> mvg
>
> m
>
> 2017-06-11 17:51 GMT+02:00 Philippe Casteleyn <
> philippecastel...@hotmail.com>:
>
>> Als ik bij een punt zie dat escada het gemapt heeft dat weet ik dat het
>> op de juiste plaats staat.
>>
>>
>> Voor de reddingsboei aan de Plaisancebrug te Mechelen had ik drie
>> bezoeken nodig om hem te vinden.  Iemand die mijn werk controleert kan
>> natuurlijk niet weten dat ik ook precies map.  De boei staat tussen het
>> riet en het is best mogelijk hem niet op te merken.  Hoe makkelijk  lopen
>> we niet iets voorbij.
>>
>> http://www.openstreetmap.org/node/4502129016#map=19/51.02098
>> /4.47243&layers=D
>>
>> <http://www.openstreetmap.org/node/4502129016#map=19/51.02098/4.47243&layers=D>
>> OpenStreetMap | Node: 4502129016
>> <http://www.openstreetmap.org/node/4502129016#map=19/51.02098/4.47243&layers=D>
>> www.openstreetmap.org
>> OpenStreetMap is a map of the world, created by people like you and free
>> to use under an open license.
>>
>>
>>
>>
>> De Oude Graanmarkt in Brussel heeft drie fonteinen.  Probeer daar maar
>> eens wijs uit te geraken als er eentje verdwijnt en de punten maar met de
>> losse hand op de markt gezet zijn.
>> http://www.openstreetmap.org/#map=17/50.85016/4.34787
>> <http://www.openstreetmap.org/#map=17/50.85016/4.34787>
>> OpenStreetMap <http://www.openstreetmap.org/#map=17/50.85016/4.34787>
>> www.openstreetmap.org
>> OpenStreetMap is the free wiki world map. ... OpenStreetMap is a map of
>> the world, created by people like you and free to use under an open license.
>> Vooral voor het deleten is een photo van groot belang.  Hoe kan je anders
>> ooit zeker zijn van iemands werk ?  En heb ik niet goed of volledig gemapt
>> ? Met een photo kan een ander het verbeteren.
>>
>> Als ik ergens naartoe ga kijk ik eerst op Google Streetview.  Als er een
>> discussie is over het mappen, dan kunnen we eerst kijken of we over
>> hetzelfde spreken.
>> Het navigeren in Mapillary is lastig, een photo tag maakt het zoveel
>> gemakkelijker.
>> Mijn opvolgers in Brussel  zullen in een fractie van de tijd die ik nodig
>> had de fietsinfrastructuur kunnen controleren als ze eerst naar mijn
>> photo's kijken.
>>
>> Leer de mensen eerst met Mapillary werken.  Dat is gemakkelijker dan
>> mappen en is een goede instap.
>>
>> Er is een verschil tussen een school en levensreddende uitrustingen.
>> Voor het laatste zou ik bewijs eisen.
>> 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
>
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

[OSM-talk-be] nouvelle liste transport public et screencast en français

[Jo]

Sorry this is only in French. It's to announce a new French mailing list
concerning public transport and to let people know I made a screencast for
all I forgot to tell at SOTM-FR :-)

Salut,

Je suis désolé que c'est fort amateuriste, mais j'ai enregistré un
'screencast' Google Hangout on Air, où je fais une petite démo du plugin
PT_Assistant et comment s'y prendre pour convertir des lignes vers
public_transport:version=2.

Je me rends compte tout d'un coup que j'ai oublié de créer le route_master.
Mais le travail n'est pas encore achevé et je n'ai pas encore envoyé mes
modifications vers le serveur. Vous êtes donc priés de ne pas encore trop
changer... sinon je vais avoir un tas de conflits.

https://www.youtube.com/watch?v=farfCqj1NmE

J'ai essayé d'ajouter un tas de petites astuces qui font que travailler
avec JOSM est un plaisir, même si au début je peux m'imaginer que tout ne
vas pas toujours aisément.

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

Re: [OSM-talk-be] hoe peuktegel mappen?

[Jo]

Looking at the 'tag' as an English word, it seems to fit, but indeed the
OpenStreetMap definition for the tag refers to dump container.

So amenity waste_basket, but I might go and ask on tagging as well.

Can somebody make a Mapillary or OpenStreetCam picture?

Jo

2017-05-04 8:51 GMT+02:00 Marc Gemis :

> An underground fire hydrant  does not look like the pillar shaped
> (above the ground) one, still we tag both as fire hydrant.
> So why wouldn't we map underground waste_baskets the same as the above
> the ground ones ?
>
> I'll admit that Guy's proposal is also possible, but "Waste disposal
> is used for medium sized waste bins, typically for bagged up household
> or industrial waste. They may be in the street, but they are not
> primarily for use by passing pedestrians." from the wikipage
> https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dwaste_disposal does
> not match very well.
>
> m.
>
> On Thu, May 4, 2017 at 7:11 AM, Jo  wrote:
> > http://www.nieuwsblad.be/cnt/dmf20170503_02865128
> >
> > it doesn't look like a waste_basket. not exactly recycling either.
> >
> > The first one was installed in Vilvoorde.
> >
> > Polyglot
> >
> > ___
> > 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

[OSM-talk-be] hoe peuktegel mappen?

[Jo]

http://www.nieuwsblad.be/cnt/dmf20170503_02865128

it doesn't look like a waste_basket. not exactly recycling either.

The first one was installed in Vilvoorde.

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

[OSM-talk-be] Monthly Meetups in Leuven

[Jo]

(Geef een seintje als je deze boodschap in het Nederlands wenst)
(Faites-moi signe si vous voulez lire ce message en français)

I'd like to start Meetups in Leuven again, every last Wednesday of the
month.
For the first one we'll follow up on the National Mapathon we had about a
month ago. But the intent is to touch all topics related to OpenStreetMap.
* Cycle and hiking routes
* Photo mapping using Mapillary or OpenStreetCam
* Use of apps like OsmAnd and Maps.ME on smartphones
* Rendering thematic maps using Maperitive of Mapbox
* Overpass API
* Harder topics like mapping public transport
* Or all the buildins and addresses in Flanders
* Later on we can also invite somebody to explain how to work with
OpenStreetMap data using QGIS
* We can use a computer room with projection and wifi on the university
campus Celestijnenlaan 200C in Heverlee.
My preference is to use JOSM. We'll start off with an introduction, do some
mapping for HOT and maybe some of you want to learn how to validate tasks
for a HOT project.

Please register here: https://www.meetup.com/OpenStreetMap-Be … 239007607/

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

Re: [OSM-talk-be] Multilingual names

[Jo]

Wow, for the faciliteitengemeenten I don't agree either! For Brussels I
don't really care that name has "fr - nl" order in a consistent way.

For faciliteitengemeenten it should be official language only in name and
name:fr, name:nl as fits.

Polyglot

2017-04-07 12:34 GMT+02:00 Gerard Vanderveken :

> Ik lees ook :
> *These municipalities should have the official translated names under
> name:nl =*, name:fr
> =* and name:de
> =* (depending on which
> language facilities are offered), the name
> =* tag should contain only
> the official name in the primary language. For the moment, the
> municipalities bordering Brussels also follow the naming schema used in
> Brussels (with both languages in the name tag), while the other
> municipalities have a tendency to only include a single language in the
> name tag. Do not delete translated data by following this rule. If a good
> translation exists in a dutch municipality in french, do not remove it. We
> only care for correct data, as much as possible without being intrusive in
> any way. *
> Ook de dubbele standaard voor de taalfacileitgemeenten rond Brussel lijkt
> mij niet aangewezen.
> Ofwel doe je voor iedere faciliteitsgemeente in de name tag alleen de
> officiele taal, ofwel beiden in volgorde van officiele - faciliteit.
>
> Met vriendelijke groeten,
> Gerard.
>
>
> Ben Laenen wrote:
>
> On Friday, 7 April 2017 11:28:32 CEST Marc Gemis wrote:
>
>
> I just stumbled upon the wiki 
> pagehttps://wiki.openstreetmap.org/wiki/Multilingual_names#Brussels
> I was surprised to read e.g. "Note that the "first mapper rule" is
> deprecated now." and "In OSM, we have a consensus to use a fixed
> order" (both changes made by Gplv2 on Oct 19, 2016)
>
> Not that I care about the order of French and Dutch on those
> streetnames, but it would be nice to inform the community about such
> an important change via the mailing list, not ? If this is indeed the
> consensus I would have violated it since I did not know deprecation of
> the first mapper rule.
>
> I asked Gplv2 to point me to the discussion leading to the consensus.
>
> So I have no problems with this being the consensus, I do have a
> problem that such an important change is made without informing the
> mailing list.
>
>
> There was a small talk about it around that time in the thread "Some
> information about Nominatim for addresses in Brussels" on this mailing list.
>
> But there was no real discussion to change it, and certainly no consensus.
>
> Ben
>
>
> ___
> Talk-be mailing 
> listTalk-be@openstreetmap.orghttps://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

Re: [OSM-talk-be] overpass query

[Jo]

En andersom, je kan voor een node op opvragen tot welke ways en relaties
hij behoort, of van ways to welke relaties met _<;

Beschouw het als steno.

_ betekent vorige resultaatset
< alles waar deze objecten deel van uitmaken
> alle nodes voor een way of alle nodes en ways van een relatie
; is gewoon om de lijn af te sluiten (geen knipoogje)

Het duurt wat eer je aan de notatie gewend bent, maar als je eenmaal zover
bent, leest het veel vlotter dan al die 

mvg,

Jo



Op 20 maart 2017 om 13:12 schreef joost schouppe :

> Op Overpass-turbo kan je (met dit soort query) gewoon zoomen, de huidige
> extent wordt dan bevraagd. je kan ook een gebied op de kaart aanduiden, met
> één van de knopjes op de kaart.
> En als je bijvoorbeeld een query laat maken voor "Luchthaven in België",
> dan zal je zien hoe het ding omgaat met andere manieren om een gebied af te
> bakenen.
>
> Die emotische regel 8 gaat over "recursing". Ik snap dat zelf ook nog niet
> helemaal, maar het heeft iets te maken met dat als je een way terugkrijgt,
> je ook nog zijn onderliggende nodes moet binnentrekken.
>
>
>
> Op 19 maart 2017 om 10:04 schreef Karel Adams :
>
> Jo, sorry hoor, maar hier snap ik den hond zijn ... niet van. Dat ligt
>> natuurlijk aan mij en niet aan u :) Ik had dan ook nog nooit van Overpass
>> Turbo gehoord, hoogstens de term al eens tegengekomen in deze maillijst
>> Herinner u misschien dat ik nogal van de ambachtelijke aanpak houd?
>>
>> Bovenal zie ik met uw query niet de minste aero-info, maar ik krijg dan
>> ook een prentje van het Zuiden van Mechelen te zien, "den Arsenaal" en
>> omgeving zeg maar; en daar is nu eenmaaal niets aeronautisch in de buurt,
>> enkel treinen. Maar ik zie nergens waar uw bbox is vastgelegd zodat ik hem
>> ook niet kan wijzigen.
>> Ook de syntax van uw query ziet er voor mij kabbalistisch uit; vooral
>> regel 8 lijkt me eerder een emoticon dan uitvoerbare code ;)
>>
>> Excuus voor mijn onwetendheid!
>> Karel
>>
>> 1[out:xml][timeout:25];
>> 2(
>> 3      node["aeroway"]({{bbox}});
>> 4  way["aeroway"]({{bbox}});
>> 5  relation["aeroway"]({{bbox}});
>> 6);
>> 7out meta;
>> 8._>;
>> 9out meta;
>>
>>
>> On 19/03/17 07:59, Jo wrote:
>>
>> Hallo Karel,
>>
>> Voor het ontwikkelen van query's is Overpass Turbo van onschatbare
>> waarde. Probeer hier eens mee en laat  weten of dat in de juiste richting
>> gaat:
>>
>> http://overpass-turbo.eu/s/nCn
>>
>> Ik heb de verkorte QL-taal gebruikt, omdat ik die gemakkelijker vind om
>> te lezen dan de XML-notatie.
>>
>> Je kan converteren op deze pagina:
>>
>> http://overpass-api.de/convert_form.html
>>
>> En dan zie je dat jouw  query een recurse-from nodig had:
>>
>> 
>>   
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>>   
>>   > order="id" s="" w=""/>
>>   
>>   > order="id" s="" w=""/>
>> 
>>
>> In die verkorte notatie wordt dat weergegeven als ">;", <; zou betekent 
>> hebben alle 'parents'.
>>
>> mvg,
>>
>> Jo
>>
>>
>> Op 19 maart 2017 om 08:22 schreef Karel Adams :
>>
>>> Nog steeds knutsel ik met het query'en van overpass om
>>> vliegveldinformatie te pakken te krijgen.
>>>
>>> Huidige opgave: renderen van 1 luchtvaartterrein met alles erop en eraan.
>>>
>>> De eerste stap is eenvoudig, en geeft reeds heel wat nuttigs. Dingen die
>>> als node zijn gemapt krijg ik zondermeer in mijn xml en kunnen dus
>>> gerenderd worden. Maar dingen die als "way" zijn gemapt, en dat zijn de
>>> voornaamste (runway, taxiway, apron, ...) geven me enkel een lijst van
>>> nodes, zonder coordinaten. Nu zou ik al moeten een tweede query lanceren om
>>> van al die nodes de coordinaten op te vragen? Of is er een manier om reeds
>>> van de eerste query niet alleen voor elke way de nodes te bekomen maar ook
>>> de coordinaten derzelve?
>>>
>>> Hier de query voor vliegveld Kiewit:
>>>
>>> 
>>>  
>>>  
>>>  >> w="5.36448355547"/>
>>>  
>>>  
>>>  
>>>  
>>>  >> w="5.36448355547"/>
>>>  
>>>  
>>> 
>>>
>>>
>>> _

Re: [OSM-talk-be] many mappy meetings this March

[Jo]

It seems like I'll be the only one helping participants in Leuven, which is
probably not a problem, but it wouldn't hurt to have some backup.

Jo

2017-03-20 8:45 GMT+01:00 joost schouppe :

> Hi,
>
> This will be a busy week:
>
> On Friday, we'll have a regular OpenStreetMap meetup in Louvain La Neuve
> [1]. C'est le premier OSM meetup en Wallonie depuis tres tres longtemps!
>
> On Saturday and Sunday, Dewey is doing a Cartopartie about their
> maps.dewey.org [2]. It is more an open source dev hackaton than something
> OSM. But they are investigating the relation between their geodata and OSM.
> As Philippe noted somewhere, their data isn't always better - but there are
> surely some mutual benefits to be found.
>
> On Saturday, we are having the National Mapathon. It looks like we will
> surpass last year's participation, with 177 people already registered [3].
> We are still looking for volunteers to help new mappers, especially in
> Louvain-la-Neuve and Namur.
> In the evening, you're welcome to the Validation Party, which we will do
> at the Dewey Cartopartie in Brussels.
> Even though only 1% of participants go on to become heavy Belgium mappers,
> this is a great opportunity to present OSM to a completely new public.
>
> On Sunday, we will join the Cartopartie crew for our second OSM Belgium
> Hackday [4]. All your projects are welcome, though we have several in the
> works: improving the new website, GRB import, Roadmapping project, etc.
>
>
> 1: https://www.meetup.com/OpenStreetMap-Belgium/events/238062854/
> 2: http://www.dewey.be/cartopartie/cartopartie-
> bruxelloise-au-pianofabriek/
> 3: http://nationalmapathon.eventbrite.com
> 4: https://www.meetup.com/OpenStreetMap-Belgium/events/238459488/
>
> --
> Joost Schouppe
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
> ___
> 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] overpass query

[Jo]

Hallo Karel,

Voor het ontwikkelen van query's is Overpass Turbo van onschatbare waarde.
Probeer hier eens mee en laat  weten of dat in de juiste richting gaat:

http://overpass-turbo.eu/s/nCn

Ik heb de verkorte QL-taal gebruikt, omdat ik die gemakkelijker vind om te
lezen dan de XML-notatie.

Je kan converteren op deze pagina:

http://overpass-api.de/convert_form.html

En dan zie je dat jouw  query een recurse-from nodig had:


  

  


  


  

  
  
  
  



In die verkorte notatie wordt dat weergegeven als ">;", <; zou
betekent hebben alle 'parents'.


mvg,


Jo


Op 19 maart 2017 om 08:22 schreef Karel Adams :

> Nog steeds knutsel ik met het query'en van overpass om vliegveldinformatie
> te pakken te krijgen.
>
> Huidige opgave: renderen van 1 luchtvaartterrein met alles erop en eraan.
>
> De eerste stap is eenvoudig, en geeft reeds heel wat nuttigs. Dingen die
> als node zijn gemapt krijg ik zondermeer in mijn xml en kunnen dus
> gerenderd worden. Maar dingen die als "way" zijn gemapt, en dat zijn de
> voornaamste (runway, taxiway, apron, ...) geven me enkel een lijst van
> nodes, zonder coordinaten. Nu zou ik al moeten een tweede query lanceren om
> van al die nodes de coordinaten op te vragen? Of is er een manier om reeds
> van de eerste query niet alleen voor elke way de nodes te bekomen maar ook
> de coordinaten derzelve?
>
> Hier de query voor vliegveld Kiewit:
>
> 
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
> 
>
>
> ___
> 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] Fwd: [iRail] Job positions in open data not being filled in

[Jo]

Java is also not my cup of tea

On Mar 4, 2017 5:31 PM, "Karel Adams"  wrote:

> Ik heb recentelijks bij IMEC gesolliciteerd (weliswaar niet in een
> opendata-context) en - beleefd blijvend - was de ontvangst daar niet van
> zo'n aard dat ik in dat bedrijf verder nog interesse heb.
>
> MIVB heeft mij bedankt, droogweg maar wel correct.
>
> Meer algemeen: het lijkt me dat kandidaat-werkgevers de lat erg hoog
> leggen, dezer dagen. Dan moeten ze niet klagen hé, dat ze geen geschikte
> kandidaten vinden.
>
> Karel
>
> On 04/03/17 11:03, Ben Abelshausen wrote:
>
> Hi,
>
> Anyone here who can help Pieter?
>
> Cheers,
>
> Ben
>
> -- Forwarded message --
> From: Pieter Colpaert 
> Date: Sat, Mar 4, 2017 at 12:00 PM
> Subject: [iRail] Job positions in open data not being filled in
> To: iRail list 
>
>
> Hi all,
>
> I have 2 open positions at imec to work on open data:
>  * https://www.iminds.be/en/about-us/jobs/jobs-overview/open-da
> ta-researcher-smart-flanders
>  * https://www.iminds.be/en/about-us/jobs/jobs-overview/vacancy
> -for-big-andtransport-data-projects
>
> I also see that MIVB-STIB has an open position to work on the Open Data
> Platform:
>  * https://www.linkedin.com/jobs/view/257410408/
>
> It’s currently very hard to find people willing to work on Open Data
> publishing for a living. Any ideas how to find the right people? Is there
> anyone in your network that might be trained to work on Open Data?
>
> Kind regards,
>
> Pieter
> ___
> iRail mailing list
> ir...@list.irail.be
> https://lists.okfn.org/mailman/listinfo/irail
>
>
>
> ___
> Talk-be mailing 
> listTalk-be@openstreetmap.orghttps://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

Re: [OSM-talk-be] trage wegen trefdag

[Jo]

Dat is wel bijzonder ongelukkig, aangezien ik er anders zeer waarschijnlijk
voor naar Kortrijk was getrokken.

Jo

Op 1 maart 2017 om 11:39 schreef joost schouppe :

> Hoi,
>
> Dezelfde dag als onze Nationale Mapathon is het ook de trefdag van Trage
> Wegen VZW.
>
> Je kan je hier inschrijven [1]
>
> Trage Wegen werkt nogal intensief met OSM [2], en ze doen die dag ook een
> workshop over OSM. Dus het zou wel fijn zijn als er iemand zou kunnen gaan.
>
>
> 1: http://www.tragewegen.be/trefdag#inschrijven
> 2: https://www.youtube.com/watch?v=KClcJhGktoE
>
> --
> Joost Schouppe
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
> ___
> 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] wijzigingen n.a.v. Circulatieplan Gent

[Jo]

Hallo Seppe,

Dat is waar we de mailing list voor hebben, dus vraag maar! Eventueel wil
ik ook wel eens een Google Hangoutsessie doen om wat mee te helpen. Ik heb
de data voor Leuven omgezet, maar op zich stelt het niet zoveel voor. Veel
wegen splitsen, een aantal omdraaien. oneway=-1 vind ik geen goede
oplossing. Als ik die tegen kom, zet ik ze om naar oneway=yes (dmv van
reverse, natuurlijk).

Dat ze dat in Gent van de ene dag op de andere willen doen, lijkt me een
logistieke nachtmerrie, maar dat is niet echt ons probleem.

mvg,

Jo

Op 28 februari 2017 om 10:55 schreef Santens Seppe 
:

> De data:
>
> ·OSM-bestanden: https://we.tl/3jpyFMuf0t (let wel: enkel road
> network, hier en daar quick and dirty oplossingen, want enkel met het oog
> op routering)
>
> ·GIS-materiaal: https://we.tl/ExJZGWLJ8L (mag hergebruikt worden
> onder Open Data Licentie Gent <https://data.stad.gent/open-data-licentie>,
> equivalent met Gratis Open Data Licentie Vlaanderen)
>
> (let op: wetransfer links met beperkte houdbaarheidsdatum)
>
>
>
> Ik wil wel de zeer gemotiveerde persoon proberen zijn J Ik zal de
> mailinglijst dan wellicht nog enkele keren moeten lastigvallen met enkele
> bijkomende vraagjes (bedankt voor de tips/antwoorden tot nu toe).
>
>
>
> Groeten,
>
>
>
> Seppe
>
>
>
>
>
> *Van:* joost schouppe [mailto:joost.schou...@gmail.com]
> *Verzonden:* maandag 27 februari 2017 15:09
> *Aan:* OpenStreetMap Belgium
> *Onderwerp:* Re: [OSM-talk-be] wijzigingen n.a.v. Circulatieplan Gent
>
>
>
> Mij lijkt het alleszins interessant om zowel de OSM-data als de GIS-data
> hier te delen.
>
>
>
> Doorgaans worden dit soort dingen door één zeer gemotiveerde persoon
> gedaan. Ik weet niet of er nu zo iemand in de zaal is :)
>
>
>
> Indien niet, dan kunnen we hier eventueel een task in de Belgische tasking
> manager aanmaken; eigenlijk alleen maar om te kunnen volgen wat al gedaan
> is en wat er nog moet gebeuren.
>
>
>
> Voor relaties: het enige dat ik zie waar je specifiek op zou moeten
> letten, is dat de role "forward" en "backward" moet omgedraaid worden als
> je de weg omdraait. Kan je eventueel vermijden door van oneway=yes naar
> oneway=-1 te gaan. Als je bij het knippen van wegen relaties onmogelijk
> maakt (vb een bus die een barriere passeert), dan is dit wel eenvoudig op
> te pikken door de QA tools denk ik.
>
>
>
>
>
> --
>
> Joost Schouppe
>
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
> ___
> 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] wijzigingen n.a.v. Circulatieplan Gent

[Jo]

Gaan ze dat van de ene dag op de andere van kracht laten worden?

Ik heb me daar hier in Leuven wat aan mispakt. Ik had het allemaal mooi
aangepast op een vrijdagochtend om dan (net te laat) tot de conclusie te
komen, dat ze dat gingen spreiden over 4 maanden. OSM heeft dus een paar
maanden 'voorgelopen' op de eigenlijke situatie.

Jo

Op 27 februari 2017 om 11:40 schreef Santens Seppe 
:

> // in Dutch as this concerns the local situation in Ghent
>
>
>
> Hallo allemaal,
>
>
>
> Op 3 april 2017 wordt in Gent het circulatieplan ingevoerd (
> https://stad.gent/mobiliteitsplan/het-circulatieplan). Heel wat straten
> worden “geknipt” (voor autoverkeer zonder vergunning), heel wat
> rijrichtingen veranderen. Mijn vraag naar jullie is hoe we ons kunnen
> organiseren om de nieuwe situatie tijdig en zo goed mogelijk te mappen.
>
>
>
> Enkele opmerkingen, mogelijkheden:
>
> ·Ik heb de situatie na 3 april al eens gemapt voor onze
> “routesimulator”, een tool die de huidige en toekomstige situatie met
> elkaar vergelijkt (de software is van de hand van Ben Abelshausen, jullie
> natuurlijk niet onbekend): http://stad.gent/vananaarb. Ik kan de
> OSM-bestanden die we daarvoor gebruiken ter beschikking stellen, alleen
> dateert de “huidige situatie” al van enkele maanden geleden en bevatten de
> bestanden enkel de zaken die we nodig hadden voor routering. (Ik zou
> trouwens graag nog een “dagboekbericht” schrijven over onze ervaringen
> tijdens dit project, maar voorlopig heb ik daar de tijd nog niet voor
> gevonden).
>
> ·Ik kan de mapping nog eens zelf doen, maar voor zo’n grote
> aanpassingen lijkt het me goed dat er een quality check gebeurt door meer
> ervaren mappers. Ik kan bijv. wel wat hulp gebruiken om relaties netjes te
> behouden / aan te passen (voor de routesimulator hebben we hier geen
> rekening mee gehouden) en om het  “toegangsbeleid” zo correct mogelijk te
> taggen (uitzonderingen, venstertijden,…)
>
> ·Mijn collega Pieter organiseert op dinsdag 7 maart een sessie
> voor aanbieders van kaarten waarbij detailvragen over de wijzigingen kunnen
> gesteld worden. Wees zeker welgekomen:
>
> Locatie:   Mobiliteitsbedrijf, Sint-Michielsplein 9, Gent
>
> Datum & tijd: 7 maart om 18u
>
> Honger?  Wij zorgen voor koffie en broodjes
>
> Uitgenodigd: TomTom, Here, Waze community, OpenStreetMap community.
>
> Ik vrees alleen dat dit wat vroeg is om alles dan al te mappen in OSM (of
> niet?). Is er interesse bij jullie om nog een aparte “mapping party” te
> houden in de week van 27/03? Of is het gemakkelijker om via elektronische
> weg vragen en tips uit te wisselen?
>
> ·We hebben ook een pakketje GIS-materiaal ter beschikking dat
> alle informatie over het circulatieplan zou moeten bevatten. Indien hier
> interesse in is, dan gooi ik het op wetransfer.
>
>
>
> Alvast bedankt voor jullie input!
>
>
>
>
>
> Met vriendelijke groeten,
>
>
>
> Seppe Santens
> Mobiliteitsbedrijf Stad Gent
> Bezoekadres: Ramen 21, 9000 Gent
> Postadres: stadhuis, Botermarkt 1, 9000 Gent
> TEL +32 (0)9 266 28 29 <+32%209%20266%2028%2029> GSM +32 (0)474 32 68 89
> <+32%20474%2032%2068%2089>
> Internet http://stad.gent/
>
>
> *Denk aan het milieu voor u mails print.*
>
> Aansprakelijkheidsbeperker
> Deze e-mail en bijlagen kunnen informatie bevatten die vertrouwelijk is
> en/of beschermd wordt door intellectuele eigendomsrechten. Lees meer ...
> <http://www.gent.be/gent.htm?id=131587>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] Mapper meeting in Louvain-la-Neuve next month

[Jo]

I remember having gone to Liège for a meetup, but that was so long ago,
that this one might just as well be considered the 'first' :-)

Jo

2017-02-23 10:17 GMT+01:00 joost schouppe :

> Yes! I feel a Tour de Wallonie  of meetups is long overdue. Thanks for
> taking the initiative Lionel.
>
> If any of you out there would like to meet mappers in their local area, do
> not hesitate to "Suggest a Meetup" on our meetup page [1], send a mail to
> commun...@osm.be or to this mailing list.
>
> [1] https://www.meetup.com/OpenStreetMap-Belgium/
>
> --
> Joost Schouppe
> OpenStreetMap <http://www.openstreetmap.org/user/joost%20schouppe/> |
> Twitter <https://twitter.com/joostjakob> | LinkedIn
> <https://www.linkedin.com/pub/joost-schouppe/48/939/603> | Meetup
> <http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/>
>
> ___
> 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] GR Routes

[Jo]

Hi Bart,

First off, you can upload your GPX traces before deleting them locally.

If you know in which changeset the path was deleted, you can use the
reverter plugint of JOSM to restore the path.

You can also use the first version of Potlatch, but it can only restore
ways:

Go to where you know the way was, the start Potlatch:

https://www.openstreetmap.org/edit?editor=potlatch2#map=14/51.2344/5.4288

take out 2 from the url:

https://www.openstreetmap.org/edit?editor=potlatch#map=14/51.2344/5.4288

Edit with Save

Advanced/Undelete

The deleted ways will appear in bright red.

This was using an undocumented feature of the API. It was not reimplemented
in any other OSM editor, which is a shame. If you revert this way, you're
recovering the original way with all its history. If you use JOSM's
reverter, you're creating new objects with the same geometry as the deleted
ones.

Polyglot

2017-02-15 6:30 GMT+01:00 Bart Vanherck :

> Hi all,
>
> I noticed that a path that I mapped is disappeared. Can I somewhere see
> who deleted that path? Or maybe it was a script that did this? The latter I
> think not, because the GR route I was mapping is still at the point where I
> left it.
>
> And if I have that changeset or so, can I easily revert that like in
> another version control system?
>
> It is not the route itself that is gone, but an "aanlooproute" The one in
> Neerpelt. Very frustrating, because I deleted the gpx trace that I walked
> there too. Now I have to walk it again :D
>
> The path is in the beginning where it leaves the GR561 identical as
> "Brabants Vennepad", but soon it leaves it and goes the other direction.
>
> Regards,
>
> Bart
>
> ___
> 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] a new National Mapathon - call for volunteers

[Jo]

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

I wouldn't mind extra help, of course!

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

Cheers,

Polyglot








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

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

Re: [OSM-talk-be] 90 --> 70 km/h

[Jo]

Dat ziet er inderdaad goed uit, als query. Ik wist zelfs niet dat het
mogelijk was om meerdere criteria mee te geven. Ik ging er altijd van uit
dat dat enkel werkte op name en name:xy.

Jo

Op 22 januari 2017 om 10:53 schreef Jakka :

> Op 21/01/2017 om 9:04 schreef Jakka:
>
>> Hoi Ruben,
>> overpass Query is nog niet mijn ding
>> Wat kan ik aanpassen om bijvoorbeeld alleen het arrondissement Kortrijk
>> West-Vlaanderen op te vragen (server time saving). Gans Vlaanderen heb
>> ik voorlopig niet nodig ;)
>> Vermoed dat met de assistent niet mogelijk is ?
>>
>
> Graag deel ik het met jullie... Met wat plak en knipwerk is het mij
> gelukt.. volgens regels van de kunst 
>
> http://overpass-turbo.eu/s/lpk
>
>
>
>
> ___
> 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] 90 --> 70 km/h

[Jo]

Frank,

Je zou Vlaanderen  kunnen vervangen door West-Vlaanderen. Dat is nog vrij
groot, maar toch al wat beperkter.

Jo

2017-01-21 9:04 GMT+01:00 Jakka :

> Hoi Ruben,
> overpass Query is nog niet mijn ding
> Wat kan ik aanpassen om bijvoorbeeld alleen het arrondissement Kortrijk
> West-Vlaanderen op te vragen (server time saving). Gans Vlaanderen heb ik
> voorlopig niet nodig ;)
> Vermoed dat met de assistent niet mogelijk is ?
>
> thx
>
> Op 21/01/2017 om 0:02 schreef Ruben:
>
>> I made an Overpass Query to search for roads lower than trunk that are
>> tagged with maxspeed=90. This is useful to know where you should go and
>> see whether there's a sign allowing you to drive 90km/h (most of the
>> times there won't be ;) ).
>>
>> The query takes about half a minute to run.
>>
>> http://overpass-turbo.eu/s/loF
>>
>>
>> PS: Maybe we could use a special (temporary) tag to mark roads as "still
>> 90" to be able to eliminate them from such queries.
>>
>> PPS: Does anyone know how to get rid of those way placeholders on
>> Overpass Turbo? I'm talking about those nodes that are all over the
>> place when there are a lot of ways that are 'too small to show', like on
>> the above map.
>>
>>
>> ___
>> 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

Re: [OSM-talk-be] OSM & Volvo Trucks Hackathon Challenge

[Jo]

Is 4 minuten niet wat kort door de bocht?

Jo

Op 19 januari 2017 om 11:27 schreef De bruyn Pieter <
pieter.de.br...@volvo.com>:

> Dag allen,
>
>
>
> Op 17-18/02 vindt de Volvo Trucks Hackathon Challenge plaats.
>
>
>
> Bedoeling is om de kost voor transport tussen punt A en punt B in kaart te
> brengen en vervolgens innovatieve oplossingen te vinden om deze kost te
> reduceren.
>
> Uiteraard zal onze eigen Volvo Trucks telematics data ter beschikking
> zijn, maar ook data van andere providers.
>
> De verschillende providers vindt u op www.volvotruckshackathonchallenge.be.
>
>
>
>
> Uiteraard willen we de deelnemers ook aansporen om OSM te gebruiken.
>
>
>
> Hiervoor zoek ik nog een persoon om OSM voor te stellen en aanwezig te
> zijn als coach :
>
> · Gedurende 4min tijdens het opening event (17/02 10-11u)
>
> o   Hoe de data kan worden binnen gehaald?
>
> o   Welke data er aanwezig is?
>
> o   Wat OSM juist is/doet ?
>
> o   …
>
> · Aanwezig te zijn als coach (17/02 12-16u en eventueel 18/02
> 9-12u) om vragen ivm OSM te beantwoorden.
>
>
>
> Uiteraard drinks en foods zijn voorzien.
>
>
>
> Ik zoek ook nog steeds slimme koppen om deel te nemen aan de hackathon,
> dus hierbij ook nog eens hiervoor een uitnodiging.
>
> Inschrijven kan op : https://s.chkmkt.com/?e=72672&;
> d=e&h=802C1FDF96C091D&l=en
>
> In bijlage vindt u ook nog even onze flyer. Twijfel zeker niet om deze te
> sharen.
>
>
>
> Alvast bedankt.
>
> Met vriendelijke groeten,
>
> Pieter
>
>
>
>
>
>
>
>
>
> This email message and any attachments may contain confidential
> information and may be privileged. If you are not the intended recipient or
> otherwise not authorized to receive this message, you are prohibited to
> use, copy, disclose or take any action based on this email or any
> information contained herein. If you are not the intended recipient, please
> advise the sender immediately by replying to this email and permanently
> delete this message and any attachments from your system.
>
> ___
> 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] fietspaden en verkeersteken D9

[Jo]

Iedereen kan dat. Ik zoek straks d link vr het bestand. Staat ergens op
josm Wiki, denk ik

On Dec 17, 2016 15:52, "Marc Gemis"  wrote:

> Ik vind dus dat de auteur van de roadsign plugin zijn plicht moet doen
> en de verkeerde tag "bicycle=official" moet wijzigen.
>
> 2016-12-17 12:40 GMT+01:00 Erik B :
> > Als er een verkeersbord staat bij een 'fietspad' gebruik ik ook de
> Roadsign
> > plugin voor Belgische verkeerstekens in JOSM,
> > die niet enkel het verkeersteken automatisch toevoegt maar ook de access
> > tags voor de highway.
> > Dan zal JOSM er bicycle=official bijzetten.
> > Dat werkt het snelst en ik ga dat niet meer corrigeren op basis van een
> > wiki.
> > Overigens is de Belgische verkeersteken wiki
> > http://wiki.openstreetmap.org/wiki/Road_signs_in_Belgium . Er is (nog)
> geen
> > Nederlandse vertaling.
> >
> > Bovendien is het belangrijk om een pad, voorbehouden voor fietsers (en
> > voetgangers), te taggen als fietspad.
> > Bij de routering op GPS stuurt een applicatie als Openfietsmap je als
> > fietser langs voorbehouden fietspaden (indien dat niet te veel omweg is).
> > Dat is de meerwaarde van bicycle=designated/official  of highway=cycleway
> >
> > Het is het zinvoller om energie te steken in het taggen van nieuwe dingen
> > dan in het voeren van een tagstrijd over de juiste manier van taggen van
> een
> > fietspad.
> >
> > Groeten,
> >
> > Erik
> >
> > Op 17-12-16 om 11:28 schreef Marc Gemis:
> >
> >> De "bijbel" imho voor zulke zaken voor België is :
> >> https://wiki.openstreetmap.org/wiki/User:Eimai/Belgian_Roads#Paths
> >>
> >> Wat de segregated tag aangaat: er staat inderdaad dikwijls het
> >> verkeerde bord bij.
> >>
> >> Wat de maxspeed aangaat: ik vind het feitelijk nog niet zo verkeer dat
> >> je in een zone 30 een maxspeed van 30 op een fietspad zet. Met somee
> >> electrische fietsen of op een racefiets kan je sneller dan 30.
> >>
> >> Wat die official aangaat  dat is een Duitse uitvinding. Het
> >> verkeersregels ivm met fietspaden zijn wat anders. Als er een blauw
> >> rond bord staat mag je er niet wandelen, ze hebben dan ook nog een
> >> rechthoekig bord met "frei" onder waar je als fietser mag, maar niet
> >> moet fietsen. In sommige streken van Duitsland zijn ze die official
> >> beginnen gebruiken om een van die varianten aan te geven. Ik dacht
> >> echter recent ergens gelezen te hebben dat ze daar toch weer gaan van
> >> afstappen. Ik zou het gewoon niet gebruiken in België.
> >>
> >> Het is al moeilijk genoeg om fietspaden goed te mappen. Dit is het
> >> gevolg dat verschillende landen verschillende wetgeving hebben.
> >> Oorspronkelijk had je footway (for public footpaths), cycleway en
> >> brindleways die overeenstemmen met de Britse situatie. Maar in
> >> Duitsland wilden ze wat anders, dan is highway=path ontstaan.
> >>
> >> Er is feitelijk nergens ens consensus over hoe je paden, bergpaden,
> >> fietspaden enz. moet mappen. Er zijn dus nogal wat regionale
> >> verschillen, wat zich ook uit in wiki pagina's en tools. Maar zoals
> >> gezegd, voor mij is de lijst van Eimai de gids bij het mappen. Wel pas
> >> ik dezelfde regels toe voor de kleine rechthoekige bordjes die je in
> >> provinciale domeinen e.d. tegenkomt.
> >>
> >> m.
> >>
> >> 2016-12-16 10:44 GMT+01:00 Guy Vanvuchelen :
> >>>
> >>> In mijn onmiddellijke omgeving mapte ik een fietspad, aangegeven met
> >>> verkeersbord D9 als volgt:
> >>>
> >>> highway = path
> >>>
> >>> bicycle=designated
> >>>
> >>> foot= designated
> >>>
> >>> segregated=yes
> >>>
> >>> maxspeed = 30
> >>>
> >>>
> >>>
> >>> Hierbij heb ik me gebaseerd op de Wiki “How to map”
> >>>
> >>>
> >>>
> >>> Onlangs bemerkte ik dat StijnRR langs gekomen was en
> “bicycle=designated,
> >>> foot=designated en segregated=yes” gewist had.
> >>>
> >>>
> >>>
> >>> Ik heb Stijn gecontacteerd om te vragen waarop hij zich baseerde en
> kreeg
> >>> volgend antwoord:
> >>>
> >>>
> >>>
> >>> “bicycle = designated : voegt dat iets toe? foot = designated : voegt
> dat
> >>> iets toe? highway = path : Een 'path' impliceert foot = yes en bicycle
> =
> >>> yes. Daarmee is alles toch gezegd? maxspeed = 30 : geldt er een maximum
> >>> snelheid op een (fiets)pad? name = Iepenpad segregated = no : dit zie
> ik
> >>> ook
> >>> eerder als een 'default' waarde. segregated = yes zou ik wel
> >>> toevoegen/behouden. En wat verkeersborden betreft: gemeentes zijn
> jammer
> >>> genoeg wel vaker goed in het gebruik van (totaal) verkeerde
> >>> verkeersborden... Ik ben daarom ook geen al te grote fan om de manier
> van
> >>> taggen al te hard te laten afhangen van de verkeersborden. Dat pad
> voelt
> >>> aan
> >>> als een gewoon verhard pad: dus eerder path dan cycleway.”
> >>>
> >>>
> >>>
> >>> Ik geeft toe dat maxspeed = 30 er uit moet. Ik had de hele wijk
> >>> geselecteerd
> >>> om de maxspeed 30 toe te voegen en had geen rekening gehouden met de
> >>> fietspaden.
> >>>
> >>> Zelf zou ik gaan voor highway=cycleway i.p.v. pad omwille van het
> >>> verkeersbord 

Re: [OSM-talk-be] GRB hackday december 11th

[Jo]

It wouldn't make sense for anybody to put a deadline on it. It's important
to communicate this to the 'integrators' though, that's the point I was
trying to make. I definitely didn't stress on it enough, when I prepared
the data for UrbIS.

Maybe we should also foresee procedures for cases where it's obvious people
take the data and just 'run with it'? If needed we shouldn't hesitate to
revert changesets. Who's going to follow up on that though? reverts should
ideally happen as quickly as possible.

About landuse that attaches to other landuse or buildings. JOSM has a tool
to nicely stitch those together. It's in the contourmerge plugin.

Jo

2016-12-15 11:38 GMT+01:00 Marc Gemis :

> On Thu, Dec 15, 2016 at 8:59 AM, Glenn Plas  wrote:
> >> A model import does not introduce errors that could be avoided by
> >> simply looking at aerial imagery
> >
> > Does, or does not ?
>
> I break the silence, just because you asked a question :-)
>
> every building imported via a model import should be checked
> individually. If you see that the aerial imagery does not show the
> building, look at a third source. Depending on the age of the sources
> take action.
> I have seen buildings that were destroyed, but visible on the
> grootschalige aerial images and GRB, but not in the field or on the
> kleinschalige aerial images. So you do not do an import then.
> Ideally, every building that you add is validated by the mapper. This
> is a slow process.
>
>
> Some of the problems I encountered during the church improvements
> - sub area of the church was marked as tower. This sub area add to be
> adapted to the new floorplan. 3D information will give the same
> problem.
> - almost every grave yard add to be added to nicely fit against the
> wall of the church. Maybe this problem is unique for churches as other
> buildings do not have landuse attached to it ?
> - in some cases you have to move paths as they would otherwise lead
> through the church. Also occurs for footpaths between 2 buildings.
>
> Other problems
> - addresses that do not match, the geometry merge plugin is not really
> helpful to see which address comes from GRB and which one was in OSM.
> - replacing multipolygons with individual buildings and somehow
> keeping the history.
> - Take a look at https://xian.smugmug.com/OSM/Screenshots/AGIV-Problems/
>
> so there are a lot of things to check while you add the data, all of
> them will slow you down during the import.
>
> @Jo, I am glad you do not put a deadline on it. Thanks !
>
> regards
>
> m
>
> ___
> 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] GRB hackday december 11th

[Jo]

I think it's important to stress (several times across the documentation)
that there is no rush. If it takes 10 years to do it right, so be it. It's
not a problem that the data isn't in there by next year.
What we should aim for is people who survey and who then use the data as a
complement to what they saw in the field (and ideally made pictures of).

Jo


2016-12-15 8:59 GMT+01:00 Glenn Plas :

> On 15-12-16 05:44, Marc Gemis wrote:
> > I'm really looking forward to read the procedure on how you guys came up.
> > You might have been lucky that I couldn't make it , now you only have
> > to ignore my annoying mails :-)
>
> No, not at all.  The church-issue was brought up without your help :)
>
> > I fail to see how documentation will prevent any participant from just
> > dumping the data from GRB into OSM without any check what so ever. The
> > same happened in The Netherlands where destroyed buildings were still
> > imported and not-yet existing house numbers where dumped in the dunes.
>
> The rule is you need to use the plugin to merge geometries, like this no
> history will be deleted , hence you can roll those back.  But we aggree
> you need some kind of formal training before getting unleashed on the
> data.  So we will give workshops etc, possibly hangouts.
>
> > A model import does not introduce errors that could be avoided by
> > simply looking at aerial imagery
>
> Does, or does not ?
>
> >
> > I've been working almost daily with the GRB data now for 6 months (*)
> > or so and have a pretty good idea how much work it takes to make this
> > a model import. I fail to see how 20-25 people can accomplish this is
> > a year, unless they really spend a lot of hours on it.
>
> I did Stekene and surroundings in a month (pretty large part in fact).
> It goes really fast when there are no houses yet, where buildings exist
> it will go a bit slower.   But it's not an import, the end result needs
> to be better than OSM and GRB seperately, it will be if we do it right.
>
> > But I am probably to critical right now and have to see what process /
> > documentation you guys came up with.
> >
> > so I shut up now and wait
>
> Think I asked for feedback on plenty of occasions, consider your job is
> well done and I prefer an early critic over a late one :)
>
> Glenn
>
>
>
> ___
> 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] Next BXL meeting date? Date du prochain meeting a BXL?

[Jo]

De foto's zijn wel.handig voor de rest van ons die daar niet lokaal is.

On Dec 8, 2016 19:46, "Karel Adams"  wrote:

> Et pour les Flamands, la même chose?
>
> On 08/12/16 18:20, Bessières, Marc wrote:
>
>  En Français + bas.
>
>
>
> Hello,
>
> I would like to organise another meeting in BXL at the beginning of next
> year.
>
> So I'd like to do it a day which would be the best for most people.
>
> Here is a poll to help me decide
>
> I proposed only beginning of the weeks in order to have enough room
>
>
>
> https://framadate.org/QUKq562oHK97TwhI
>
>
>
> Bonjour,
>
> Je voudrai organiser un nouveau meeting a BXL au debut de l'année prochaine
>
> Et pour ça je voudrais choisir la date qui sied au plus grand nombre.
>
> Voici donc un petit sondage pour trouver la meilleure date.
>
> Je ne propose que des jours en début de semaine, afin d'avoir assez de
> place.
>
> https://framadate.org/QUKq562oHK97TwhI
>
>
>
>
>
> ___
> Talk-be mailing 
> listTalk-be@openstreetmap.orghttps://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

Re: [OSM-talk-be] voetbalkantine

[Jo]

Kunnen we operator:wikidata gebruiken?
operator:wikidata=Q941193 Scouts en gidsen België
operator:wikidata=Q2749394 Chiro Vlaanderen
operator:wikidata=Q2041438 Patro Wallonie


Op 30 november 2016 14:13 schreef Steven Clays :

> Hallo mensen,
>
> vanuit de Ambrassade (vroegere Vlaamse Jeugdraad) plant men in februari de
> lancering van een puntgegevenslaag met alle clublokalen van de
> jeugdbewegingen in Vlaanderen. Dit in samenwerking met Mediaraven, die de
> GIS voor zich nemen. Misschien is het een idee dat jullie voor het
> hergebruik en de verdere ontsluiting van deze gegevens eens met hen contact
> opnemen?
>
> Steven Clays
> Trage Wegen
> Inhoudelijk coördinator en Beleid
> tel. 09 331 59 21 - fax 09 331 59 18 - gsm 0494 54 20 92
> Kasteellaan 349 A, 9000 Gent
>  www.tragewegen.be
>
> Op 30 november 2016 11:25 schreef Pieter Brusselman <
> pieter.brussel...@tragewegen.be>:
>
>
>>
>> Op 28/11/2016 om 15:48 schreef Marc Gemis:
>>
>>> 2016-11-28 14:26 GMT+01:00 Jorieke Vyncke :
>>>
 Ja, ik zou een jeugdhuis zeker niet mappen als een pub.
 Jeugdhuizen hebben een compleet andere finaliteit...
 http://www.formaat.be/jeugdhuizen/jeugdhuismethodiek/


>>> Ok, maar hoe maak je het onderscheid tussen een jeugdhuis en een
>>> chirolokaal als je club=youth op beiden zet ?
>>>
>>
>> Je zou kunnen specifiëren met community_centre:for=juvenile (zie
>> http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dcommunity_centre) voor
>> een jeugdhuis?
>>
>>
>>>
>>> Jeugdhuizen, scoutslokalen, chirolokalen, seniorenclubs, buurthuizen, ...
 Daar hebben we nog maar weinig mapping-richtlijnen op de wiki over, en
 zijn z aanwezig in onze Belgische samenleving.

>>> Geraak je al niet een heel eind met mijn antwoord in het begin ??
>>>
>>> Ter herinnering:
>>>
>>> amenity=community_centre + type community_centre=club_home
>>>
>>> ontdekt op de wiki pagina voor club
>>>
>>> http://wiki.openstreetmap.org/wiki/Key:club
>>>
>>> club=youth/senior/sport/...
>>>
>>> Dit is natuurlijk voor clubs en niet voor buurthuizen.
>>>
>>> ___
>>> 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-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] names

[Jo]

Ik zie absoluut geen reden om daar een spatie tussen te gaan zetten.

Op 25 november 2016 09:16 schreef Marc Gemis :

> Ik dacht dat er vroeger borden met de naam in de middenberm stonden,
> wat op "name" zou wijzen. Bijnaam zou eerder in loc_name kunnen,
> aangezien we geen nickname hebben.
> Ik zou wel proberen beide namen (op way en in relatie) gelijk te
> houden, dus niet Koning Boudewijn Snelweg en Koning Boudewijnsnelweg,
> maar voor het tweede gaan).
> Ik vind het vreemd dat ref en int_ref enkel zouden verschillen door
> een spatie na de E.
>
> hopelijk reageren er nog anderen
>
> mvg
>
> m
>
> 2016-11-24 20:14 GMT+01:00 Stijn Rombauts :
> > Is 'Boudewijnsnelweg' een naam, van dezelfde soort als een straatnaam of
> > eerder een bijnaam? Want nu zijn er maar enkele stukjes van de E313 in
> > Beringen die een 'name = Koning Boudewijn Snelweg' hebben. Of houden we
> de
> > Koning Boudewijnsnelweg enkel als relatie [1]?
> > En nog een andere vraag: hoe moet de ref en int_ref eruit zien? E313 of E
> > 313? De wiki lijkt me te zeggen ref = E313, int_ref = E 313. Klopt? Maar
> dat
> > is dan toch nog niet overal consequent toegepast.
> >
> > [1] http://www.openstreetmap.org/relation/5499606#map=11/50.7630/5.6738
> > (maar osm is blijkbaar niet altijd even happy als je die relatie
> > opvraagt...)
> >
> > StijnRR
> >
> >
> >
> > 
> > From: Guy Vanvuchelen 
> > To: 'OpenStreetMap Belgium' 
> > Sent: Thursday, November 24, 2016 11:46 AM
> > Subject: Re: [OSM-talk-be] names
> >
> > Helemaal akkoord, vooral met de laatste zin!
> >
> > Guy Vanvuchelen
> >
> > -Oorspronkelijk bericht-
> > Van: Marc Gemis [mailto:marc.ge...@gmail.com]
> > Verzonden: donderdag 24 november 2016 10:42
> > Aan: OpenStreetMap Belgium
> > Onderwerp: Re: [OSM-talk-be] names
> >
> > Ik ben het eens mei Eimai, dat E314 niet de naam is van de snelweg.
> > Er is bv. wel een Boudewijnsnelweg en er is ook nog een "Route de
> soleil" of
> > iets dergelijks onder Luik.
> > Dat zijn namen.
> >
> > JOSM heeft het niet altijd bij het rechte eind, ook al omdat die presets
> en
> > stijlen geschreven worden voor heel de wereld.
> > Er zijn misschien landen waar autosnelwegen wel namen hebben. Voor België
> > zou highway=motorway uit die no-name stijl mogen.
> >
> > m.
> >
> > 2016-11-24 9:14 GMT+01:00 Guy Vanvuchelen :
> >> In JOSM kan je wegen die geen ‘name’ hebben weergeven. Snelwegen staan
> >> daar meestal bij. Die hebben wel bijvoorbeeld:
> >>
> >> Int_ref = E 314
> >>
> >> ref = E 314
> >>
> >> nat_ref = A2
> >>
> >> maar meestal geen ‘name’.  Ik heb nu systematisch ‘name = E 314’
> >> toegevoegd maar blijkbaar is niet iedereen hiermee akkoord want ik zie
> >> dat ‘Eimai’ die names systematisch weer wegneemt.
> >>
> >> Ik neem aan dat ik dus beter stop met die snelwegen.
> >>
> >>
> >>
> >> 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-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

Re: [OSM-talk-be] cycleways met no name

[Jo]

Ik neig naar het kamp dat voorstander is om de naam wel te geven en zie er
geen graten in om dat ook voor een losgetekend voetpad te doen.

Jo

Op 25 november 2016 09:56 schreef Marc Gemis :

> Ik wou niet onmiddellijk reageren, anders ben ik het weer :-)
> Maar nu er nog geen reacties zijn:
>
> Moeilijke kwestie. is ook al ooit besproken op Duitse mailing list,
> zonder resultaat.
> Voorstanders van de naam op het fietspad wilden dat omdat zo de
> navigatiesystemen de naam van de straat konden uitspreken.
> Tegenstanders vonden dat het fietspad geen naam heeft, en dat je maar
> een "street"-relatie moet maken om alles samen te nemen. (of
> automatisch te laten berekenen).
>
> Moeten we afzonderlijke voetpaden dan ook de naam van de straat
> waarlangs ze liggen gaan geven ?
>
> Ik weet het ook niet, tot nu toe map ik een parallel fietspad zonder naam.
>
> m
>
>
>
> 2016-11-24 16:32 GMT+01:00 Guy Vanvuchelen :
> > Regelmatig kom ik fietspaden tegen die als track getekend staan naast een
> > autoweg. Dikwijls is daar een berm, aanplanting, enz. tussen.
> >
> > Moet/mag dat fietspad dezelfde naam krijgen als de autoweg?  Ik zou
> denken
> > van wel want als je de autoweg mapt met cycleway=track heeft hij
> > waarschijnlijk automatisch de naam van de autoweg.
> >
> >
> >
> > 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

Re: [OSM-talk-be] Missing Maps, in Belgium

[Jo]

If validation requires going into the field and cannot be performed the
armchair way, I'm not very confident it will be done. Unless we have some
sort of mobile way to do that validation.

Jo

2016-11-08 8:04 GMT+01:00 joost schouppe :

> As for Joost's suggestion for mapping shops in a town. Depending on
>> the data source, it might add too much out-of-date data. I fear that
>> armchair mappers will blindly copy the data without cross referencing
>> other sources that indicate that the shop was closed/moved. Using up
>> to date photo's from OpenStreetView or Mapillary could overcome this
>> problem, when the mapper is willing to spend enough time and does want
>> to be the mapper that finishes most tiles in the shortest period.
>>
>
> There is no open data source for shops that I'm aware of, so this would in
> fact be a collect data + map task. There is of course the option of taking
> an area that is already densely mapped in Mapillary (say, central Brussels)
> and define a task there. Then the "validation" step would be to go into the
> field and collect the last bits of info.
>
> ___
> 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] GRB-import voor centrum Antwerpen ?

[Jo]

Ik zou dat vooral zo blijven doen. Kleinschalig, maar beetje bij beetje
geraken de gebouwen er dan toch accuraat in.

Jo

Op 7 november 2016 12:52 schreef Marc Gemis :

> wat ik vooral jammer vind is dat het allemaal redelijk lang aansleept.
> (ik wijs naar niemand)
> Het is gewoon niet leuk om nu nog manueel gebouwen te gaan tekenen als
> je weet dat die toch gaan vervangen worden door betere examplaren.
> En je hebt die gebouwen nu eenmaal nodig om erfgoed tags of andere
> zaken te mappen. Je kan dan niet gewoon maar een puntje zetten.
>
> Dus ja, ik gebruik Glenn's tool nu al om die gebouwen te tekenen die
> ik nodig heb. Gemakkelijker en beter dan wat ik zelf zou tekenen.
> We mogen GRB toch als achtergrond gebruiken, niet ?
>
> m
>
>
> 2016-11-07 12:44 GMT+01:00 Ben Abelshausen :
> > Het is duidelijk dat dit, vanuit technologie standpunt de beste oplossing
> > is, dat is niet waar het probleem zit. Dit is zeker een elegante
> oplossing.
> > Het punt is dat we die wiki pagina moeten maken en er moet community
> > consensus zijn (min-of-meer) over de aanpak en ik geloof niet dat we dat
> op
> > deze manier gaan bereiken.
> >
> > Het is 100% zeker dat dit zever gaat geven met de import lijst en data
> > working group en ik heb gewoon geen goesting om mij daar weer mee bezig
> te
> > houden. En ik bedoel inderdaad mensen die op eigen houtje GRB gebouwen
> over
> > de bestaande hebben gezet... dat moeten we vermijden.
> >
> > Ik denk nog altijd dat het voldoende gaat zijn om sommige gebouwen
> éénmalig
> > te importeren en dan verder te onderhouden op de gangbare manier. Dit
> gaat
> > de weg van de minste pijn zijn, eenvoudig te implementeren en geen (of
> > minder) zever met de data working group of de import lijst.
> >
> > In het kort dus: Voor mij evengoed als we het kunnen regelen dat we die
> tags
> > allemaal kunnen meenemen maar ik heb dan niet veel zin om dit te
> > verdedigingen op de import lijst.
> >
> > Ik wou om deze reden dus ook face-to-face afspreken om te vermijden heel
> > deze discussie via mail te voeren...
> >
> > @marc: we zouden de source tag ook op de changeset kunnen zetten. Is ook
> > logischer omdat enkel de data die in die changeset nieuw is ook die bron
> > heeft.
> >
> > Met vriendelijke groeten,
> > Best regards,
> >
> > Ben Abelshausen
> >
> > Met vriendelijke groeten,
> > Best regards,
> >
> > Ben Abelshausen
> >
> > 2016-11-07 12:14 GMT+01:00 Marc Gemis :
> >>
> >> Ik ben echt niet gelukkig met source=GRB. Probeer dat maar eens te
> >> combineren met data die je op een andere manier hebt gevonden (bv. via
> >> survey of wikipedia).
> >> source:geometry of iets dergelijks ok, maar niet source aub.
> >>
> >> m.
> >>
> >> 2016-11-07 12:02 GMT+01:00 Glenn Plas :
> >> > On 07-11-16 11:51, Ben Abelshausen wrote:
> >> >> Glenn,
> >> >>
> >> >> Kijkend naar de BAG import wat denk je van dit:
> >> >>
> >> >> source = GRB
> >> >> ref:grb = 3746049-6379775 (oidn-uidn)
> >> >
> >> > Dat gaat een leuke query worden in de database, met regular
> expressions
> >> > en stuff. pfff.  En die uidn is volgens mij nog van een minder belang
> >> > dat de datum.  Die is leesbaar voor eindgebruikers, die uidn versie
> >> > nummer zegt echt niks.
> >> >
> >> > Ik ben trouwens niet akkoord met die ref tag.  het is geen ref, het is
> >> > een source ref.  daarom source:*
> >> >
> >> >> Die datum is niet echt relevant voor mappers en als ik het goed
> begrijp
> >> >> kunnen we dit via bovenstaande ref nog altijd uit de originele data
> >> >> halen? Zelfde voor entity? We zouden die entity types ook nog kunnen
> >> >> gebruiken om andere tags te genereren omdat daar toch wel
> verschillende
> >> >> zaken inzitten precies.
> >> >
> >> > Dat gebeurd nu ook, maar er is ook overlapping tussen entities.
> >> >>
> >> >> Ik heb altijd gedacht, we importeren wat gebouwen waar het nodig is
> >> >> (bijvoorbeeld dicht gebouwde steden). We hebben ookal werk van
> mappers
> >> >> overschreven gezien met GRB gebouwen (delete-upload), iets wat naar
> >> >> mijn
> >> >> menig een slechte zaak is.
> >> >
> >> > Nee, dan heb je niet opgelet ;-) !!!  wij deleten niets.  De history
> van
> >> > een gebo