Okey dokey :-) Here is a short wrap-up about current discussion and questions raised so far, with some answers given from my perspective. First a few definitions… Municipality: Data_prov attribute in ODB data. It is the name of the municipality, region, or province/territory that provided the dataset. Each of these datasets usually covers many smaller cities, towns or villages as identified by the CSDNAME attribute in ODB data. Local import manager: Someone that identified himself as responsible for the import in a given municipality. We will need an entry in the wiki to identify them. Following is a list of his/her potential responsibilities. - He/she will ensure the whole import process respects the rules that we will put in place. - He/she will attempt to contact local mappers, if any, to get a local buy-in. - He/she will ask for pre-processing the data if required. - He/she will ask for setting up the task manager for that municipality. The local import manager is NOT responsible for doing the whole import, just ensuring that the process is done right (see Import Process paragraphs below). Now some topics raised in the thread… Importing locally - see proposal 2.1 - The proposal describes an approach that allows an import even where there are no local communities. As long as there is a local import manager, all available data should be imported (for urban and rural areas). The Task Manager - see proposal 2.3 1- - To make sure there in no wild import, an import task should be set-up only after a local import manager has required it. Without a local import manager, the data should not be made available through the task manager (i.e. NO import). - Being able to adapt the size of the working squares in the task manager is great news. We just have to identify what could be a reasonable volume of building to process, let’s say in an hour, to adjust the squares accordingly. The Import Process - see proposal 2.3 4- - It would be fun if we all got involved in importing data as a municipality becomes available for import. We might all have local knowledge to share even if we do not live in a given municipality. - The Conflation process is when you need to replace the geometry of an existing OSM building with the one from ODB data because it would significantly be improved. Consequently, not all buildings need to be changed using ODB data. Correction of already imported data - see proposal 2.3 2-, 3- - Identifying those who carried out these imports as de facto responsible for the corrections might seem like blame in some case. I suggest that anyone could identify themselves as local import manager for concerned municipalities, including those who made the first import if they wish. - Correction might be twofold: the correction of low quality building shapes and the correction of low positional accuracy of OSM content when it is the case.
Thanks for your interest! Daniel
_______________________________________________ Talk-ca mailing list Talk-ca@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ca
