[Imports] Import of Flemish Government data (building footprints and addresses)

Frederik Ramm frederik at remote.org
Mon Oct 29 14:09:46 UTC 2018


Hi,

On 10/29/18 11:34, Andy Mabbett wrote:
> I *strongly* recommend including links (or IDs, that can be used in
> links) to external databases. This is vital for two reasons: it
> indicates the *precise* provenance of the sourced data; and it makes
> OSM a better able to function as part of the web of linked-, open-,
> data.

OSM isn't the world's geodata melting pot, nor does it have the goal to
be "able to function as part of the web of linked open data".

The ideal building footprint in OSM is one that is surveyed or traced by
an individual member of our project. We are content creators, not
content re-users and distributors. We can occasionally incorporate a
third-party data set but if we do, the version in OSM becomes our master
version that we own, edit, modify, delete at will. We don't serve as a
"cache" for foreign data sets, where copies are stored in OSM and
updated whenever the foreign data source updates. Therefore, I find such
links an unnecessary bloat.

The idea of having an "audit trail" for every single geometry by way of
an Id for that individual geometry is interesting, but I think that it
is totally sufficient if a changeset carries the information that this
changeset has been imported from XYZ data source at time stamp T;
everything else can be researched down the line if the need should arise.

If someone wants to import this kind of foreign IDs into OSM they should
be able to present a solid use case - why is this good *for OSM*.
Neither the original poster nor you have been able to do so.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"



More information about the Imports mailing list