Giovanni,
I have severe problems with your process. First, yes it is an import. You called it an import
yourself ("manually importing") here, and on the Italien list where you first asked about the
tagging [2]. Where did you see a "100 nodes" limit documented? You are copying from one database
into another, and if you do just one node a day, it is a slow import.
Imports require the Import Guidelines to be followed [4]. I cannot see any discussion with the
community. I cannot see any check of license compatibility. There is no documentation. There is no
entry in the import catalogue.
You were criticized for stretching the opening_hours syntax to describe seasonal operations ("Jan 01
- Dec 31"), but did not respond nor adjust your tagging.[3]
The link on your Umap site leads to [5], which is licensed under the Italian Open Data License,
linked here [6]. It requires attribution, machine-translated: "On condition of: indicate the source
of the Information and the name of the Licensor, including, if possible, a copy of this license or a
link (link) to it."
You have not attributed correctly. You changesets, e.g. [7], give in the CS comment "RAFVG source",
which is an incomprehensible acronym if you don't know the context. The CS has no source tag at all
(although the editor you use has a mechanism for it), thus you do not name the source correctly, you
do not name the Licensor, and you do not include a link although possible. You have also not checked
if the attribution on the changeset only would be sufficient.
Your import does not include any check, how current or old the data in the imported set are. In the
hotel business, things can change very fast. Hotels open and close, and change ownership and
operations.
Your import focuses on soft business policies, such as allowing pets or supervising kids. Such
policies can change even more rapidly, and are better shown in separate datasets and not OSM itself.
You use and advertise in your umap the use of Level0 as an editor. This tool is excellent for
quickly fixing a tag, but I would find it error-prone to upload mass changes without a validation step.
Thus I conclude: Visualising the dataset in your Umap approach [1] is an excellent idea, unreviewed
copying of the data into OSM is not.
[2] https://lists.openstreetmap.org/pipermail/talk-it/2019-February/065837.html
[3] https://lists.openstreetmap.org/pipermail/talk-it/2019-February/065839.html
[4] https://wiki.openstreetmap.org/wiki/Import/Guidelines
[5]
https://www.dati.friuliveneziagiulia.it/Istruzione-cultura-e-sport/Strutture-Alberghiere-e-RTA/fiiw-i5su
[6] https://www.dati.gov.it/content/italian-open-data-license-v20
[7] https://www.openstreetmap.org/node/2088900846/history
Tom
On 09.03.2019 12:19, Cascafico Giovanni wrote:
[1] http://umap.openstreetmap.fr/it/map/turismo-fvg_295722
Il sab 9 mar 2019, 12:18 Cascafico Giovanni <[email protected] <mailto:[email protected]>> ha
scritto:
In short (I'm on phone)...
Please find here [1] umap used for manual conflation. For source data and
license, follow footer
info link.
AFAIK <100 nodes don't fall in import category.
Il sab 9 mar 2019, 11:46 Tom Pfeifer <[email protected]
<mailto:[email protected]>> ha
scritto:
On 09.03.2019 10:10, Cascafico Giovanni wrote:
> Well, hotels dataset I'm manually importing has a boolean
baby-sitting field (as for
"pets" in other
> ML thread).
> I think that a generic info is better than no info, particularly if
hotel features
childcare=yes and
> whatever contact tag.
Giovanni,
can you please let us know, which hotels dataset you are importing,
under what license this dataset is published,
and where you discussed the import with the OSM community?
Please not that an import is an import even if you do just one hotel
per day.
tom
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
