[OSM-talk-be] OSM and SIAMU

[PONCELET Nadia]

Thank you all for your answers and ideas!

For those interested, this national registry number can be found in UrbIS under the name 'pnmc' in several tables like public names (pn) and street surfaces (ss), but not directly in street axis. As this reference number is published in UrbIS, I was tempted to consider that it was under the same type of license as UrbIS itself, but I may be wrong.

I must say I am not convinced anymore that adding this national registry reference number in osm would really help us in the long term. I met some people from UrbIS team this week. Like Joost said, it seems indeed that the data model of the national registry is about to change. It is still not very clear to me how and when. According to UrbIS people, “UrbIS Adresses” will officially become in 2018 the official reference for addresses in Brussels Region, just like CRAB in Flanders and ICAR in Wallonia. But it does not seem clear yet what kind of identifiers will be used for adresses (and shared with the national registry) in this context. Wait and see...

From what I had understood about what OpenLR does, I first thought it couldn't be really useful in our case as the SIAMU doesn't have a street database with its own geometry to be matched with OSM but only a streetname dictionary (without geometry) to be matched with OSM highways. But after Ben's short explanation, I think I should probably try to use it myself before to get to that conclusion. @Ben : I will probably recontact you on this question one day.

I didn’t take time yet to get more information about wikidata objects but it certainly looks like an interesting idea.

Nadia


De : Glenn Plas [mailto:glenn at byte-consult.be]
Envoyé : lundi 27 novembre 2017 10:37
À : OpenStreetMap Belgium <talk-be at openstreetmap.org>; Ben Abelshausen <ben.abelshausen at gmail.com>; Jo Simoens <WinFixIT at gmail.com>
Objet : Re: [OSM-talk-be] OSM and SIAMU

Hi Ben,

I'm really missing something in the logic, but how can 2 seperate datasets get common ground on this ?  aka: how does it work that this single ID would be generated identically for 2 different datasets, given the fact that coordinates are not exactly 100% the same.  I don't see that connection with openLR.  Would love to know this.

tx,

Glenn

On 23-11-17 20:21, Ben Abelshausen wrote:
I think this problem can be solved with OpenLR, or at least to a level of acceptable quality comparable to mapping the ID's in OSM. I'm willing to help out with that, how that would work for examples for brussels:

OpenLR, encodes a location on a network in a kind of ID like this:

KwMXmiQm5xt0Af+x/79bBGY=

This decodes into a segment like this:

http://openlr.itinero.tech/?code=KwMXmiQm5xt0Af+x/79bBGY=
In your internal database you keep the code above, and link the streetname to that segment, the segment always decodes no matter who updates the map or the ID's of the OSM ways. As long as the road still exists the code will work. It's a perfect way to associate data to a road network for cars (or in this case firetrucks) without having a dependency on the network ID's or mapped ID's on the network.
Other examples:

http://openlr.itinero.tech/?code=KwMXuCQnBSOKAQB6/76jGoQ=
http://openlr.itinero.tech/?code=KwMaESQmxiOVBP9E/zOjBaw=
http://openlr.itinero.tech/?code=KwMZgSQmHSOaBP+mANRjEUQ=
Generating codes can be done by just clicking on the map if you want to generate your own.

All this software is open-source and can be setup locally.

Met vriendelijke groeten,
Best regards,

Ben Abelshausen



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20171128/3596b56c/attachment.htm>