<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I’m going to throw an idea out for feedback — you don’t have to be gentle. <div class=""><br class=""></div><div class="">One solution to this would be to give preference to those dive sites that are tied to a dive in your dive log. The idea would be you could have a large number of sites imported that have zero dives associated with them, but once you either associate a dive with one of those sites, or create a site yourself that is associated with a dive, those sites would not be replaced by an imported site at the same geographic location.<div class=""><br class=""></div><div class="">With this, the user (e.g. Dirk) could create several sites with the same name that have slightly different geographical locations and those would be stored in his personal dive site table and any sites imported with the same geographical coordinates would be ignored. Also, if you translate the name, description or notes of the site into your native language, any imported sites at the same location would also be ignored.</div><div class=""><br class=""></div><div class="">Ideally the user will be able to search for sites that are near a particularly lat/long. If so, those that are already associated with dives in their log could be highlighted in some way as the preferred sites to use or edit.<div class=""><br class=""></div><div class="">-Doug</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Apr 11, 2019, at 2:53 PM, Hartley Horwitz <<a href="mailto:hhrwtz@gmail.com" class="">hhrwtz@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><br class=""><br class="">---------- Forwarded message ----------<br class="">From: Robert Helling <<a href="mailto:helling@atdotde.de" target="_blank" class="">helling@atdotde.de</a>><br class="">To: Dirk Hohndel <<a href="mailto:dirk@hohndel.org" target="_blank" class="">dirk@hohndel.org</a>><br class="">Cc: Doug Junkins <<a href="mailto:douglas.junkins@gmail.com" target="_blank" class="">douglas.junkins@gmail.com</a>>, "<a href="mailto:subsurface@subsurface-divelog.org" target="_blank" class="">subsurface@subsurface-divelog.org</a>" <<a href="mailto:subsurface@subsurface-divelog.org" target="_blank" class="">subsurface@subsurface-divelog.org</a>><br class="">Bcc: <br class="">Date: Thu, 11 Apr 2019 11:13:35 +0200<br class="">Subject: Re: Exporting dive sites as XML<br class=""><div style="word-wrap:break-word" class="">Hi,<br class=""><blockquote type="cite" class=""><blockquote style="text-transform:none;text-indent:0px;letter-spacing:normal;font-family:Menlo-Regular;font-size:11px;font-style:normal;font-weight:normal;text-decoration:none;word-spacing:0px;white-space:normal" type="cite" class=""><br class=""></blockquote></blockquote><div class="">this is really a tough one. Let’s keep in mind in which direction this (if it takes off at all) might go to: Rather than sharing your own dive sites between a few of your own log files (or maybe with your wife or your close friends), this whole dive site management becomes really powerful as soon as some big dive site collections are created (like all dive sites in a country, a continent or even globally) with the collections shared essentially between all Subsurface users. </div></div></blockquote><div class=""><br class=""></div><div class="">This is exactly how I would like things to go -- I'd gladly share my dive sites in my usual dive locations, but I'd really like to get a copy of someone else's dive sites for a trip to a location I've never been. That would be really powerful. </div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div style="word-wrap:break-word" class=""><div class="">…….</div></div></blockquote><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div style="word-wrap:break-word" class=""><div class=""> These collection could also be used to figure out where it is actually worth going to. Another aspect is of course language: We might want to remember the langue of a dive site description so that I can decide to only import those that are in a language that I can understand.</div></div></blockquote><div class=""><br class=""></div><div class="">I'd import the dive sites in my personal log, even if they aren't in my native language. If it is a dive site that I actual use, I'd probably translate or re-write the description to fit my needs.</div><div class=""> </div><div class="">….Hartley </div></div></div>
_______________________________________________<br class="">subsurface mailing list<br class=""><a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a><br class="">http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>