Wednesday 01 June 2016 19:50:48, Sander Deryckere:
> Note that the GRB data mentions it's "voorlopig", and often, the data shows
> an offset from parcel boundaries. At those places, I would expect the
> boundaries to follow parcel boundaries (and I expect parcel boundaries to
> be of better quality
Note that the GRB data mentions it's "voorlopig", and often, the data shows
an offset from parcel boundaries. At those places, I would expect the
boundaries to follow parcel boundaries (and I expect parcel boundaries to
be of better quality).
2016-06-01 19:01 GMT+02:00 joost schouppe :
> very tru
>
> very true... 100 meters would be vast imho. A difference of 5 meters I
> would think that is pretty much ok, although the importance of that can
> be big when borders cross buildings.
>
> Exactly, I think the definition of correct is pretty narrow here.
> More important: remember that those b
Hey Joost,
On 01-06-16 16:19, joost schouppe wrote:
> Well, it depends on your definition of vastly :)
very true... 100 meters would be vast imho. A difference of 5 meters I
would think that is pretty much ok, although the importance of that can
be big when borders cross buildings.
> (I haven't
Well, it depends on your definition of vastly :)
(I haven't looked at the size of the differences yet)
I was talking about municipal borders (admin_level=8), postal codes as in
your example are a wholly different beast, one I wouldn't want to tackle
right now.
But yes, they have a lot of things st
Hi,
I'm not sure they can be vastly improved, it probably depends a lot on
what boundary.
In that understanding that there is lot's of stuff attached to those
boundaries that shouldn't be there. So when you are working to improve
boundaries, you'll need to address plenty of those cases, and that
Hi,
It would be a fairly trivial task, don't think we need import approval
from upstream for a few thousand single nodes. It would be a bit like
importing VELO nodes (bike sharing). The license of this DAE data is open.
I've made a quality assessment tool to compair VELO nodes from VELO
website
RIP Marc.
So I understand the geometry of the municipal boundaries could be vastly
improved.
I'm guessing the easiest workflow would be to load just the geometry of the
municipalities and just the OSM municipalities in JOSM, then merge the
nodes of the OSM municipalities to the external data. Aft
Heel wat van de grenzen zijn gemapt door Marc De Ridder (die jammer genoeg
te vroeg van ons heengegaan is:
https://lists.openstreetmap.org/pipermail/talk-be/2013-January/003565.html
).
Zelf heb ik ook de grenzen leren mappen van Marc, en heb ik een groot deel
van de West-Vlaamse grenzen gemapt. De
Personally for Flanders I wouldn't worry to much. Lets wait maybe a a year or 2
to get the municipals time to correct/update their borders in AGIV (GRB).
But form the things I compared, I found the current borders to be are rather
good.
I'm going to assume they are rather old too. As such they h
Hi,
I got a question about municipal boundaries in Belgium. I had a look here
[1], but it seems to be lacking detailed information about how this data
was added to OSM and what the source is. I do remember seeing some info
about this, but we should probably have a bit more formal documentation,
ri
[EN]
Hello,
The "Ligue Cardiologique Belge / Belgische Cardiologische Liga" just issued
a set of 2000 defibrillators (DAE) in Belgium in the Brussels open datastore
http://opendatastore.brussels/en/organization/liguecardioliga (csv or xls)
It would be great to import them in OSM... There are now
12 matches
Mail list logo
