<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Nov 14, 2020, 11:14 by mgl.branco@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>1) Those areas require a previous conflate, yes. I've done so using JOSM and JOSM/conflation add-on for most of the areas. I indicate "yes, merged" in wiki tables to note if they’re conflated and are ready to upload. I have to edit some areas yet but when necessary I’ll use conflation too. <br></div></div></blockquote><div>If no useful, already present in OSM data will be lost then it is fine.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>2) About the data of accuracy/positioning in relation to OSM data. When working with IET data (shapefiles), I did a double checkout: compare imports with <a href="http://mapas.xunta.gal/visores/basico/" rel="noopener noreferrer" target="_blank">mapas.xunta.gal/visores/basico/ </a>(government official map viewer) and the official documents that parliament passed by to declare natural protected areas (In our case those are published in "Diario Oficial de Galicia – DOG", that contain their maps). I saw no problem about protected areas' position: they fall in their provinces, councils, include or not some villages and so on. In fact, there’s some of them already mapped in osm that have some pitfalls. This import would correct those mistakes. <br></div></div></blockquote><div>Great! I was asking because I have seen imports where someone made mistake with projection<br></div><div>and everything was offset by 100 meters.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>About the detail too, yes, in some cases source data has too much detail. But a random reduction of it can mean including or not e.g. a small village or even a protected tree from a natural park. That’s why I think that we need to avoid data reduction here.<br></div></div></blockquote><div>I think that it is needed only for extreme overnoding (100 nodes for one meter of border type of thing).<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>About source date, that date is the latest release date for that IET’s data package.<br></div></div></blockquote><div>User actual source data. If after 9 years it is still up to date, then importing it is fine.<br></div><div><br></div><div>But, please, check that to avoid - for example - deleting more up to date OSM data<br></div><div>to replace it with an outdated snapshot.<br></div> </body>
</html>