Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible Flanders, Belgium data #3002

Closed
migurski opened this issue May 18, 2017 · 9 comments
Closed

Possible Flanders, Belgium data #3002

migurski opened this issue May 18, 2017 · 9 comments

Comments

@migurski
Copy link
Member

Report of new data via Twitter: https://twitter.com/emacgillavry/status/865086118097805312

@nvkelso
Copy link
Member

nvkelso commented Jun 12, 2019

This is now ready to download, sounds like new source for whole country including Flanders, CC-BY:

For posterity, here's the before image:

image

@nvkelso
Copy link
Member

nvkelso commented Jun 12, 2019

@trescube want to have a crack at this one?

@barthanssens
Copy link
Contributor

barthanssens commented Jul 4, 2019

Hi, I'm the maintainer of the opendata.bosa.be website and the data.gov.be open data portal in Belgium.

I'm actually coaching a few students on the OpenKnowledge "Open Summer Of Code 2019" to convert the custom XML files to csv and other formats, so we could do the work for you (creating separate files per region and hosting them somewhere) and create a few pull requests

The data fully covers the three regions of Belgium, by the way, but unfortunately each of them has a slightly different license, but it is delivered directly from the authoritative sources of these regions.

We have a demo day on July 25th, so it would be great if we could already show some stuff, like integration with openaddresses

@iandees
Copy link
Member

iandees commented Jul 4, 2019

That'd be great, @barthanssens! Let us know how we can help.

@barthanssens
Copy link
Contributor

Thanks @iandees, we've created a first set of CSV files and a PR (#4582)

I do have a question: can the same CSV be used for partially translated addresses ?

For the Brussels-Capital Region it is quite easy (even mentioned in the docs as an example, thank you !) because everything is always available in 2 languages.
But in the Flemish and Walloon Region, the vast majority is in 1 language, with the exception of a few municipalities (due to historical/political reasons) that do provide official translations in another language (see also https://en.wikipedia.org/wiki/Municipalities_with_language_facilities)

Now the question is: would it be a problem if we use the same CSV file with separate columns per language + separate metadata JSON files per language, just like Brussels, even if that means that in the vast majority of rows there will be no "second" language (= lot of empty cells for e.g street names) ?

Or should we create an additional CSV file per region, with these exceptions (= avoiding to have empty cells) ?

@iandees
Copy link
Member

iandees commented Jul 9, 2019

Hmm, that's a good question. I'd say that using the same file is fine for now.

@barthanssens
Copy link
Contributor

Thanks, we'll do that.

Another question if I may, is there an attribute to indicate parts of a city ?

Many small villages merged into larger municipalities in the 70s, but quite a few people still use the names of these villages, while others use the new names... (yes, we love to make things complicated in .be)

@barthanssens
Copy link
Contributor

I'd suggest to close this issue, since the official sources are merged and have been used for quite some time (see http://results.openaddresses.io/sources/be/vlg/bosa-region-flanders-nl)

@iandees
Copy link
Member

iandees commented Jun 25, 2020

👏

@iandees iandees closed this as completed Jun 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants