Is it reasonable to import architectural data?

Sorry, I’m new here, but I’ve been using OSM in my app for five years now. It’s dedicated to architecture and contains 200,000 points worldwide.
These aren’t just points of interest, as they’re well-filtered by architectural style, creation time, and architect. Each object has a wiki description.
So, the question is: is importing into OSM worth considering, or is it a very specific and uninteresting thing?
My reason: I’m 65 years old, and someday there will come a time when I won’t be able to maintain my app and the data on the Hetzners server.
Here is data:

Thanks in advance

8 Likes

Without knowing what kind of data you are thinking of importing, in general it might be worth to look into it.

There are already tags used in that field, like architect=* or building:architecture=*, as well as the general start_date.

Do you think I should provide this link in topic?
Here is data:

Definitely that helps and it seems like I wasn’t that far off. The main challenge what I see is the conflation, like find the already existing object in OSM that matches your dataset.

3 Likes

is importing into OSM worth considering, or is it a very specific and uninteresting thing?

It’s very interesting thing! The biggest challenge will probably be matching your points with the building outlines in the OSM.

It seems that my internet is a bit corrupted (or probably your site is not working properly, because on https://apalladio.org/ I just see the Apache default page), and I cannot open your site. If you share your data on the google drive, I will see what can be done.

1 Like

No “appaladio.org” is wrong url, it is just shown so in editor (I do not know why).
Just open link with click on it.
Correct url is:
Architecture Around - Discover Historical Buildings & Monuments

1 Like

Super neat project! Conflation and standardization to osm tags would be the two challenges.

You may also want to investigate the various tags that use wikidata ids as linkage, it helps avoid name collisions etc (ex: architect:wikidata).

There’s a lot of ways to tackle this but even just making the data available for other mappers to work with is a huge help!

4 Likes

I’ve manage to open it. Your project is really nice!

In order to proceed, I guess, we would like to see data as json, or, say, excel file, and some kind of copyright declaration, because in osm we can upload datasets compatible with ODBL.

1 Like

Yes, it is clear, thanks

1 Like

around here were lots of points, but all of them seemed to be derived from wikipedia, are there other sources as well?

1 Like

Yes, the source is wikipedia (there is one exclusion for Munich, but it plays no role).
Technically (if you are asking about technik) - it is not wiki API, because wiki API does not bring such fullness and such filters.

1 Like

It would obviously be great.

I wonder if you had suggestions for the project to make it easier to integrate such data.

Building a better interface (or even map layer) to access it assumes we already have a reasonable coverage at least in some regions.

Personally, I find that OSM tends to struggle with keeping building or street information together prioritizing routing and shopPOI over cultural information.

2 Likes

No, there are no proposals yet.
It won’t be a quick story, but I’ll need to get through it.

Actually, I need to figure out how import works in general, with its tags and so on.

The most natural thing would be, of course, to create a layer, if possible.
And to algorithmically avoid duplication, even if at the cost of losing a small (hopefully) amount of data.

2 Likes

Thank you all so much. The import could take a year (or several years) of painstaking work.
Here’s what I decided now:
I simply shared the entire database (SQL dump), and it’s available to everyone.
Github: GitHub - MyropolskyiHennadii/ArtefactsLocation-data: SQL database dump for 200,000+ architectural objects · GitHub
Zenodo:

There’s also a Java model:

If anyone wants to collaborate and/or maintain the database and/or has questions, they’re welcome.

What is the rough geographic distribution? Is it all in Germany? In the database table, I just noticed “Bavaria”.

No, it is worldwide. Look at the longitude/latitude

What concerns geographic distribution: addresse, cities, lands and so on - it is just what returns https://api.bigdatacloud.net for geoposition.
What api.bigdatacloud.net knows about this geoposition, that is completed.

I had a look on the license and it is cc-by-sa which unfortunately is not usable for OpenStreetMap. Are you able and would you be willing to give OpenStreetMap special permission?

Here is a blog post from the OpenStreetMap-Foundation why even cc-by is not compatible: Use of CC BY 4.0 licensed data in OpenStreetMap | OpenStreetMap Blog

1 Like

Yes! I’ll do it, I’ll change license tomorrow/after tomorrow ang set a special permission for OpenStreetMap and let you know.

Permission granted in both sources!

“This database is licensed under CC BY-SA 4.0 with explicit permission
for OpenStreetMap use under ODbL”

Let me know, if it is not ok or there is something else to check.

1 Like