[Imports] Belgium address import

Hi, This summer here in Belgium a lot of addressing data was released as open data. A lot of local mappers are very eager to do something with this data and OSM. We have worked the past couple of months discussing, writing tools and documentation to prevent this new data from being used without th

Re: [Imports] Belgium address import

Two questions: 1) The screenshots on the wiki page mention the use of associatedStreet relation, but your e-mail mentions that you will remove it. In the end, the data will only have nodes with addr:* tags? 2) I'm not familiar with the addr.openstreetmap.fr tool, but it sounds like it duplicates

Re: [Imports] Belgium address import

On Sat, Nov 23, 2013 at 2:17 PM, Ian Dees wrote: > 1) The screenshots on the wiki page mention the use of associatedStreet > relation, but your e-mail mentions that you will remove it. In the end, the > data will only have nodes with addr:* tags? > The screenshot will have to be changed, I misse

Re: [Imports] Belgium address import

On Sat, Nov 23, 2013 at 7:27 AM, Ben Abelshausen wrote: > > On Sat, Nov 23, 2013 at 2:17 PM, Ian Dees wrote: > >> >> 2) I'm not familiar with the addr.openstreetmap.fr tool, but it sounds >> like it duplicates functionality of the OSM Tasking Manager. Have you >> considered using that? >> > > Thi

Re: [Imports] Belgium address import

Ben, As someone who is overseeing a large import as well (though not as large as all of Belgium), I have a number of questions: 1. What QA have you done on the data to see that it's both good and consistent? Belgium is a large area and what we have found in the past is that data may be great in

Re: [Imports] Belgium address import

Hi Ben! As far as I can see, this import only covers the Flemish Region (Brussels excluded), not the whole country. So, there aren't any multilingual municipalities (like Brussels), are there? Can you tell us more about where this data comes from? Is it government data? It looks like as

Re: [Imports] Belgium address import

On Sat, Nov 23, 2013 at 03:37:34PM +0100, Martin Raifer wrote: > Hi Ben! > > As far as I can see, this import only covers the Flemish Region > (Brussels excluded), not the whole country. So, there aren't any > multilingual municipalities (like Brussels), are there? Yes, it only covers the Flemish

Re: [Imports] Belgium address import

Hi Ben, > - And last but not least an import-plan: > http://wiki.openstreetmap.org/wiki/AGIV_CRAB_Import I did not see any handling of abbreviations in your python code. If the source data has abbreviations, they should get expanded by the conversion scripts. Regardless, you should talk about abb

Re: [Imports] Belgium address import

On Sat, Nov 23, 2013 at 08:39:20PM -0500, Jason Remillard wrote: > Hi Ben, > > > - And last but not least an import-plan: > > http://wiki.openstreetmap.org/wiki/AGIV_CRAB_Import > > I did not see any handling of abbreviations in your python code. If > the source data has abbreviations, they shoul

Re: [Imports] Belgium address import

Hi Kurt, Ben, > This is a good point. I've already seen cases where we have the > full name currently in osm but the data we get contains some > abbreviatiated form. > > I'll try to look at it. I currently find 970 street names with > a '.' in it. > You should probably go back to your local Bel

Re: [Imports] Belgium address import

I think most of the abbreviations found in the OSM data will be first names which were written in abbreviated form on the street name tag signs. Those are mostly expanded in the source data. Regarding streets with same names. The most common case is a main street which connects 2 cities which main

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 08:12:17AM +0100, Jo wrote: > I think most of the abbreviations found in the OSM data will be first names > which were written in abbreviated form on the street name tag signs. Those > are mostly expanded in the source data. Looking at the CRAB data, most of the abbriviated

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 01:33:48PM +0100, Kurt Roeckx wrote: > > Regarding multilingual names. There are villages in Belgium which have > > 'facilities' for French speaking 'immigrants' from the other side of the > > country. > > > > For those I think they should be tagged as follows: > > > > nam

Re: [Imports] Belgium address import

After thinking about this import- I think that it's overall a bad idea because the addresses are not tied to physical structures. It would be better, IMHO, until the areas have building coverage, to use this as an external resource. Nonetheless I will reply to this address expansion because I hav

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 07:53:30AM -0500, Serge Wroclawski wrote: > After thinking about this import- I think that it's overall a bad idea > because the addresses are not tied to physical structures. > > It would be better, IMHO, until the areas have building coverage, to > use this as an external

Re: [Imports] Belgium address import

What's the benefit of tying the address to the structure? I've seen this spoken about quite a bit. - Randal Hale, GISP North River Geographic Systems, Inc http://www.northrivergeographic.com 423.653.3611 rjh...@northrivergeographic.com twi

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 11:10:48AM -0500, Randal Hale wrote: > What's the benefit of tying the address to the structure? I've seen > this spoken about quite a bit. I'm not sure I understand your question. Why would you want to have a node with the address information when you can do it on the bui

Re: [Imports] Belgium address import

I worked this summer on an addressing project - all the addresses were points. In OSM I've seen discussion on relating the address to a structure or putting an address on a structure - I would rather keep it as a point within the structure (and not relating it to the building) - but that's just

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 11:31:35AM -0500, Randal Hale wrote: > I worked this summer on an addressing project - all the addresses > were points. In OSM I've seen discussion on relating the address to > a structure or putting an address on a structure - I would rather > keep it as a point within the

Re: [Imports] Belgium address import

Ahhh - OK - good luck with all of this! - Randal Hale, GISP North River Geographic Systems, Inc http://www.northrivergeographic.com 423.653.3611 rjh...@northrivergeographic.com twitter:rjhale http://about.me/rjhale On 11/24/2013 11:35 AM,

Re: [Imports] Belgium address import

There seems to be a misunderstanding. While it is true that the person who is handling the 'import' receives points with address data. These contributors have to draw buildings around those points based on really good imagery we have available. So, calling it an import is probably a misnomer. What

Re: [Imports] Belgium address import

I ask because I will (hopefully) be faced with a comparable problem in 2014 - I will have address data with no structure and it's going to be up to me/the client/or volunteers to add the buildings (if they want them). I didn't know there were tools in josm for automatically handling address/bu

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 11:10 AM, Randal Hale wrote: > What's the benefit of tying the address to the structure? I've seen this > spoken about quite a bit. There are a number of reasons: 1. What OSM objects represent In OSM, we generally talk about ground observable truth and our attributes are

Re: [Imports] Belgium address import

Hi On 24.11.2013 19:26, Serge Wroclawski wrote: >> What's the benefit of tying the address to the structure? I've seen this >> spoken about quite a bit. > > 3. Almost always, the points are either wrong or meaningless I'd like to second that. If there is a compelling reason to not tie the addre

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 12:53 PM, Frederik Ramm wrote: > Hi > > On 24.11.2013 19:26, Serge Wroclawski wrote: > >> What's the benefit of tying the address to the structure? I've seen this > >> spoken about quite a bit. > > > > 3. Almost always, the points are either wrong or meaningless > > I'd li

Re: [Imports] Belgium address import

What's the ultimate goal of address data - geocoding? Networking? Information for the sake of Information? I'm all for having it - but there seems to be an unclear goal. To me it's more important to relate the address point to the street as opposed to the building though either a relation or a

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 7:53 PM, Frederik Ramm wrote: > I'd like to second that. I also completely agree with this. This is also in our import proposal, there is a clear agreement on putting the information on building outlines as has been the case already with surveyed addresses here in Belgiu

Re: [Imports] Belgium address import

Hi, On 24.11.2013 20:17, Randal Hale wrote: > What's the ultimate goal of address data - geocoding? Networking? > Information for the sake of Information? I am assuming that most people will want addresses for geocoding (potentially as a precursor to routing): "I want to go to 1234 Someroad, how

Re: [Imports] Belgium address import

I agree having a map of an area is a good thing if provided an address. It just seems like there's been too much worry over tying it to a building or a front door. I would (this is just me) want to tie it to the street - that way if the street changes there's some process of having that address

Re: [Imports] Belgium address import

On Sun, Nov 24, 2013 at 3:22 PM, Randal Hale wrote: > I agree having a map of an area is a good thing if provided an address. It > just seems like there's been too much worry over tying it to a building or a > front door. I would (this is just me) want to tie it to the street - that > way if the s

Re: [Imports] Belgium address import

The reason why we never considered adding addresses as nodes on the streets is that it wouldn't be clear on which side of the street the address was lying. So several years ago, we put addresses on nodes, Just like POIs. Then aerial imagery improved and we became able to draw buildings from it (Th

Re: [Imports] Belgium address import

In France, we "import" addresses since ~2010. I can provide some feedbacks here: - "address on building vs node" : we see two camps here although a majority seems to agree that on densified urban zones, the node model is better because it is easier for multiple addresses on the same building and y

Re: [Imports] Belgium address import

I think it's time to get it going again. We have such a nice and precise DB and are not using it at all. Reading this discussion, I propose to NODES OR OUTLINES - Put address on buildings when it's clear enough. F.e. in the case of separated residential buildings with one street next to it (like

Re: [Imports] Belgium address import

I agree. We should move forward with this. I add streetnames from CRAB occasionally. Housenumbers are not my main focus though. 7 bus stops don't scare me. But there must be millions of housenumbers. In Brussels we had both the building contours and the housenumbers in vector form. Now that wa

Re: [Imports] Belgium address import

Hi, There was a TODO-list on this last year and I asked the talk-be list for help but there was nobody willing to do this at the time: - Get a better feel for the quality of the data and formulate this in a better way than just saying 'good enough'. - Find a way to keep track of progress. - Find

Re: [Imports] Belgium address import

2014-10-06 9:59 GMT+02:00 Ben Abelshausen : > Hi, > > There was a TODO-list on this last year and I asked the talk-be list for > help but there was nobody willing to do this at the time: > > - Get a better feel for the quality of the data and formulate this in a > better way than just saying 'good

Re: [Imports] Belgium address import

2014-10-06 13:49 GMT+02:00 Sander Deryckere : > From what I see, the address nodes are in the exact centre of the parcels. > This is often not on a building, or near the entrance, but the precision of > the parcel boundaries (and thus the precision of those nodes) is way higher > than any OSM data

Re: [Imports] Belgium address import

Only the nodes are given as free data. No building contours or no parcel boundaries. It's to empower businesses to have more exact data on their customers (so they can query near potential customers, or map/ correct addresses in their databases), in which case the coordinates are considered enough