<div dir="ltr"><div dir="ltr">Hi<div>I started importing, and it goes fine. I'm at cell 5 from around sixty. If you want to help, please join telegram group</div><div><a href="https://t.me/lvosm" target="_blank">https://t.me/lvosm</a></div><div>or write me in whatsapp +37126131239 (or at <a href="mailto:vlad@izne.com" target="_blank">vlad@izne.com</a>)</div><div><br></div><div>From my experience, validating and cleaning of an imported cell takes around one hour, depending on its density. Sometimes it is just 15-20 minutes, sometimes two hours. </div><div>Please note: <b>issues are inevitable with imports! </b>It is just a matter of compromise between occurrences or map corruption and benefits of a new data being imported. IMO, import still overweights some cases of corruption missed during validation.<br></div><div><br></div><div><b>About excluded roads. </b>All roads that are part of relation or have names same as roads in relation are excluded. Otherwise, it is too easy to corrupt relations.<br></div><div>Another thing that is not ideal is that we can't correct the geometries of the existing roads with the current approach. This is related to how Hootenanny works and is hard to overcome. </div><div>We have a reference map (OSM) and a merged map (LVM). Reference map is considered "better" and if something exists there, it is not modified. In our case, geometry exists, but tags sometimes do not. We can't switch the reference map to LVM, because it would cause another set of issues. Again, I am not an expert by any means, so this is just my understanding. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 30, 2021 at 2:53 PM Marat <<a href="mailto:maratu@gmail.com">maratu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Sorry, there should have been "Included in routes" -> those LVM roads that I've added\changed manually and that are part of route relation will be excluded from import :)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 30 Sept 2021 at 14:48, Rihards <<a href="mailto:rihards@nakts.net" target="_blank">rihards@nakts.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Ah cool - you mean exclusion in routes only, right?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 27 Sept 2021 at 09:46, Marat <<a href="mailto:maratu@gmail.com" target="_blank">maratu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Vladislav has removed highway excluded in routes on my request, as I have manually replaced those with LVM data and updated them accordingly. However later we can check those as well.<div dir="auto">Now he is on vacation and will proceed when he returns :) </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 27 Sep 2021, 09:41 Rihards, <<a href="mailto:rihards@nakts.net" rel="noreferrer" target="_blank">rihards@nakts.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Heya, any thoughts on this?</div><div>Very eager to see this moving forward :)<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 9 Sept 2021 at 23:38, Rihards <<a href="mailto:rihards@nakts.net" rel="noreferrer noreferrer" target="_blank">rihards@nakts.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>This is beautiful, thank you so much for the detailed process.</div><div>I looked at the example validated OSM file, and noticed "operator=LVM;Latvijas valsts meži", along with "operator:abbr=LVM".</div><div>I suspect this is caused by the existing road already having operator=LVM.</div><div>Perhaps it's worth overriding the operator tag instead of conflating the values?<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 6 Sept 2021 at 20:17, Vladislav Kugelevich via Talk-lv <<a href="mailto:talk-lv@openstreetmap.org" rel="noreferrer noreferrer" target="_blank">talk-lv@openstreetmap.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi</div><div>Everything is ready.</div><div dir="auto"><a href="https://wiki.openstreetmap.org/w/index.php?title=LV:LVM-import&redirect=no" rel="noreferrer noreferrer" target="_blank">https://wiki.openstreetmap.org/w/index.php?title=LV:LVM-import&redirect=no</a></div><div dir="auto"><br></div><div dir="auto">There is a link there to the github repo with sample files. It would be very helpful if someone can review and ask any questions.</div><div dir="auto"><br></div><div dir="auto">I am ready to start soon, coordination is by email or in the LV telegram group.</div><div dir="auto"><br></div><div>Thanks</div></div>
_______________________________________________<br>
Talk-lv mailing list<br>
<a href="mailto:Talk-lv@openstreetmap.org" rel="noreferrer noreferrer" target="_blank">Talk-lv@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-lv" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-lv</a><br>
</blockquote></div>
</blockquote></div></div>
_______________________________________________<br>
Talk-lv mailing list<br>
<a href="mailto:Talk-lv@openstreetmap.org" rel="noreferrer noreferrer" target="_blank">Talk-lv@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-lv" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-lv</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>