[OSM-talk-be] Completing the belgian postal code boundaries
Pieter Vander Vennet
pietervdvn at posteo.net
Fri Dec 10 17:03:49 UTC 2021
Hi Pierre,
First of all: thanks a lot for your excellent and hard work on the postal codes. I wanted to help out by offering this alternative dataset.
And no, my approach is far from perfect, so there are indeed issues with my boundary set.
Your approach is good as well, I just wanted to outline the minimal requirements for a postal code boundary.
At last, how comes you don't reuse the admin-level9 if they are the same?
Kind regards,
Pieter
Dec 10, 2021 15:37:20 Pierre Parmentier <pierrecparmentier at gmail.com>:
> Hello Pieter,
>
> Nice view and helpful.
>
> Some comments:
* > There is a problem for Buzenol. I shall try to fix it.
* > The commune/gemeente Ixelles is in two parts. East and west of avenue Louise/Louizalaan. On the west side there is no identification. Enclave/exclave!
> I have completed all postal_code boundaries in the province of Luxembourg. It was done at the request of user 'jfonda' who added many addresses in SE Belgium.
>
> When doing so:
1. > I created relations with boundary=postal_code + type=boundary + name=nnnn + postal_code=nnnn tags
2. > The tag name is useful in the relations list in JOSM. It makes it easy to find a relation in the list!
3. > The boundaries are based on bpost (1) for the /approximate/ direction of the ways.
4. > As it appears that the postal boundaries are often based on admin_level=9 boundaries, I add these boundaries first.
5. > admin_level=9 boundaries are from the Belgian MinFin web site.
6. > If we create postal_code boundaries from bpost data we will only get /approximate/ boundaries. And we will add unnecessary ways to OSM!
7. > Furthermore we will create a separate network and, later on, difficulties to merge the tripoints of both networks.
8. > When it appears that admin_level=9 and boundary=postal_code boundaries are the same, I am in favor of creating a separate relation. Not to give the admin_level=9 an additional tag.
> Pierre
>
> (1) Namespace BE.BPOST; Resource identifier 2b1a5f4f-5263-11ea-8b43-34e12d0f0423; https://www.geo.be/catalog/details/2b1a3840-5263-11ea-acd1-34e12d0f0423?l=en
>
>
>
> Le ven. 10 déc. 2021 à 13:07, <talk-be-request at openstreetmap.org> a écrit :
>> Send Talk-be mailing list submissions to
>> talk-be at openstreetmap.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.openstreetmap.org/listinfo/talk-be
>> or, via email, send a message with subject or body 'help' to
>> talk-be-request at openstreetmap.org
>>
>> You can reach the person managing the list at
>> talk-be-owner at openstreetmap.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Talk-be digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Completing the belgian postal code boundaries
>> (Pieter Vander Vennet)
>> 2. Re: Completing the belgian postal code boundaries
>> (Pieter Vander Vennet)
>> 3. Re: Completing the belgian postal code boundaries
>> (Jonathan Beli?n)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 9 Dec 2021 16:49:51 +0000
>> From: Pieter Vander Vennet <pietervdvn at posteo.net>
>> To: talk-be at openstreetmap.org
>> Subject: [OSM-talk-be] Completing the belgian postal code boundaries
>> Message-ID: <5fcdf3f6-a03a-bb97-d60c-9db9a125a6c7 at posteo.net>
>> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>>
>> Hi all,
>>
>> Recently, I got the challenge to get all postal codes in Belgium. Turns
>> out that there is no open dataset available to do this (yet).
>>
>> OpenStreetMap already got me a long way (hooray!) but Wallonia is still
>> a bit... lacking and has big holes. Time to fix this!
>>
>> (Of course, I also setup a MapComplete theme with the postal codes
>> <https://pietervdvn.github.io/mc/develop/postal_codes.html?z=9&lat=50.51866&lon=5.158081&fs-export=true&language=en#relation/224757>)
>>
>> So, after some talk on Matrix, I downloaded an Open Address dataset
>> <https://opendata.bosa.be/index.nl.html> (with postal codes) of
>> Wallonia. A few scripts later, I had a geojson of addresses for every
>> postal code, which I then could run through a convex hull algorithm,
>> getting the boundaries of each postal code with an open license...
>>
>>
>> The last step is to get these outlines integrated into OSM. While it is
>> quite fun to map, adding a few hundred of them is a bit too much work,
>> which is why I'm asking you all for some help. If you have experience
>> with JOSM and have spare time, please, pick out a few postal code
>> boundaries and add them.
>>
>> *How to add a postal code boundary
>> *
>>
>> 1. Grab the dataset over here
>> <https://github.com/pietervdvn/pietervdvn.github.io/blob/master/missing_postal_code_boundaries.geojson>2.
>> Load the data into JOSM
>> 3. Download the OSM-boundary data of the relevant area (e.g. with the
>> 'query overpass'-mode in the download field)
>> 4. Create a multipolygon-relation, reusing already existing border lines
>> of create a new line alltogether. /It is discouraged to use the actual
>> geometry, as they can be jittery and jump from address point to address
>> point
>> /5. Upload the data
>> 6. ????
>> 7. Profit!
>> //
>>
>> //Kind regards,
>> Pieter
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20211209/d8cc9a9d/attachment-0001.htm>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 9 Dec 2021 16:55:10 +0000
>> From: Pieter Vander Vennet <pietervdvn at posteo.net>
>> To: talk-be at openstreetmap.org
>> Subject: Re: [OSM-talk-be] Completing the belgian postal code
>> boundaries
>> Message-ID: <94af6f56-241b-ddcf-1984-36d95fdc246e at posteo.net>
>> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>>
>> PS: The tagging for a postal code boundary relation is: `type=boundary;
>> boundary=postal_code; postal_code=*`. Alternatively, if a postal code
>> aligns 100% with an administrative boundary, one can also add
>> `postal_code=*` on it.
>>
>> addr:postcode or addr:postalcode are incorrect for this purpose - there
>> are still a few of those out there, but I'm gradually cleaning them up.
>>
>> Kind regards,
>> Pieter
>>
>> On 09.12.21 17:49, Pieter Vander Vennet wrote:
>>>
>>> Hi all,
>>>
>>> Recently, I got the challenge to get all postal codes in Belgium.
>>> Turns out that there is no open dataset available to do this (yet).
>>>
>>> OpenStreetMap already got me a long way (hooray!) but Wallonia is
>>> still a bit... lacking and has big holes. Time to fix this!
>>>
>>> (Of course, I also setup a MapComplete theme with the postal codes
>>> <https://pietervdvn.github.io/mc/develop/postal_codes.html?z=9&lat=50.51866&lon=5.158081&fs-export=true&language=en#relation/224757>)
>>>
>>> So, after some talk on Matrix, I downloaded an Open Address dataset
>>> <https://opendata.bosa.be/index.nl.html> (with postal codes) of
>>> Wallonia. A few scripts later, I had a geojson of addresses for every
>>> postal code, which I then could run through a convex hull algorithm,
>>> getting the boundaries of each postal code with an open license...
>>>
>>>
>>> The last step is to get these outlines integrated into OSM. While it
>>> is quite fun to map, adding a few hundred of them is a bit too much
>>> work, which is why I'm asking you all for some help. If you have
>>> experience with JOSM and have spare time, please, pick out a few
>>> postal code boundaries and add them.
>>>
>>> *How to add a postal code boundary
>>> *
>>>
>>> 1. Grab the dataset over here
>>> <https://github.com/pietervdvn/pietervdvn.github.io/blob/master/missing_postal_code_boundaries.geojson>2.
>>> Load the data into JOSM
>>> 3. Download the OSM-boundary data of the relevant area (e.g. with the
>>> 'query overpass'-mode in the download field)
>>> 4. Create a multipolygon-relation, reusing already existing border
>>> lines of create a new line alltogether. /It is discouraged to use the
>>> actual geometry, as they can be jittery and jump from address point to
>>> address point
>>> /5. Upload the data
>>> 6. ????
>>> 7. Profit!
>>>
>>> Kind regards,
>>> Pieter
>>>
>>>
>>> _______________________________________________
>>> Talk-be mailing list
>>> Talk-be at openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-be
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20211209/b632e13b/attachment-0001.htm>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Thu, 09 Dec 2021 18:37:05 +0100
>> From: Jonathan Beli?n <list at jbelien.be>
>> To: talk-be at openstreetmap.org
>> Subject: Re: [OSM-talk-be] Completing the belgian postal code
>> boundaries
>> Message-ID: <bfd70f80-7d48-4c32-9aba-1f027b91a750 at www.fastmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Excellent initiative Pieter !
>>
>> I think we should also check with the official postal code dataset from *bpost* !
>> The dataset itself is useless (not open data and bad geometry) but I think it can be used to visually compare.
>>
>> You can view that dataset here : https://www.geo.be/catalog/details/2b1a3840-5263-11ea-acd1-34e12d0f0423?l=en
>>
>> There are some "weird" postal codes situation that geometry based on addresses won't take into account.
>>
>> Have a nice evening.
>>
>> Jonathan Beli?n
>>
>>
>> Jeu 09 d?c 2021, ? 17:55, Pieter Vander Vennet a ?crit?:
>>>
>>> PS: The tagging for a postal code boundary relation is: `type=boundary; boundary=postal_code; postal_code=*`. Alternatively, if a postal code aligns 100% with an administrative boundary, one can also add `postal_code=*` on it.
>>>
>>> addr:postcode or addr:postalcode are incorrect for this purpose - there are still a few of those out there, but I'm gradually cleaning them up.
>>>
>>> Kind regards,
>>> Pieter
>>>
>>> On 09.12.21 17:49, Pieter Vander Vennet wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Recently, I got the challenge to get all postal codes in Belgium. Turns out that there is no open dataset available to do this (yet).
>>>>
>>>>
>>>> OpenStreetMap already got me a long way (hooray!) but Wallonia is still a bit... lacking and has big holes. Time to fix this!
>>>>
>>>> (Of course, I also setup a MapComplete theme with the postal codes <https://pietervdvn.github.io/mc/develop/postal_codes.html?z=9&lat=50.51866&lon=5.158081&fs-export=true&language=en#relation/224757>)
>>>>
>>>> So, after some talk on Matrix, I downloaded an Open Address dataset <https://opendata.bosa.be/index.nl.html> (with postal codes) of Wallonia. A few scripts later, I had a geojson of addresses for every postal code, which I then could run through a convex hull algorithm, getting the boundaries of each postal code with an open license...
>>>>
>>>>
>>>>
>>>> The last step is to get these outlines integrated into OSM. While it is quite fun to map, adding a few hundred of them is a bit too much work, which is why I'm asking you all for some help. If you have experience with JOSM and have spare time, please, pick out a few postal code boundaries and add them.
>>>>
>>>> *How to add a postal code boundary*
>>>>
>>>>
>>>> 1. Grab the dataset over here
>> <https://github.com/pietervdvn/pietervdvn.github.io/blob/master/missing_postal_code_boundaries.geojson>2. Load the data into JOSM
>>>> 3. Download the OSM-boundary data of the relevant area (e.g. with the 'query overpass'-mode in the download field)
>>>> 4. Create a multipolygon-relation, reusing already existing border lines of create a new line alltogether. *It is discouraged to use the actual geometry, as they can be jittery and jump from address point to address point
>> *5. Upload the data
>>>> 6. ????
>>>> 7. Profit!
>>>>
>>>>
>>>> Kind regards,
>>>> Pieter
>>>>
>>>>
>>>> _______________________________________________
>>>> Talk-be mailing list
>>>> Talk-be at openstreetmap.org
>>>> https://lists.openstreetmap.org/listinfo/talk-be
>>>>
>>> _______________________________________________
>>> Talk-be mailing list
>>> Talk-be at openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-be
>>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20211209/ea5de421/attachment-0001.htm>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Talk-be mailing list
>> Talk-be at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
>>
>>
>> ------------------------------
>>
>> End of Talk-be Digest, Vol 168, Issue 2
>> ***************************************
> _______________________________________________
> Talk-be mailing list
> Talk-be at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20211210/8aed06f3/attachment-0001.htm>
More information about the Talk-be
mailing list