On 29 Jan 2015, at 17:49, Dirk Hohndel <d...@hohndel.org> wrote: > > Our "Location" text becomes the key for a dive site data base. How this > key into this data base is structured is primarily up to the user. We > will not enforce any schema on this.
Or maybe just a numeric ID? That way we don't have to update all dives whenever we edit the name. But I guess that's not too much of a hassle anyway. > Let's ignore this and say that we switched into "dive site mode". Every > dive site has a number of items associated with it. > > GPS coordinates > Site name (= (part of) our location string?) > Description > Local notes What's the difference between Description and Local notes? I suggest just having one Notes field. > The first two are mandatory. If you don't have a name and GPS coordinates, > you don't have an entry in this data base. I disagree to this. It has happened to me many times that I add a site and some notes and a picture, but I add the GPS coordinates later. It would be a pain (at least for me) to have that coordinate requirement. And what would we do when importing a lot of dives and sites from another software, and there are no GPS coordinates? Do we drop the site descriptions? So I suggest that just the name is mandatory. > Based on what some website do, we could add more items, but I'm not sure I > want to do that; feedback welcome: > > Currents > Hazards > Water type > Marinelife > Maxdepth > Mindepth I'm not sure I like these at all, at least not before there is a definite request for it. Most of those variables could be fetched as statistics from the related dives, and I think it's a good idea not to over-engineer this from the start. So, lot's of good stuff here. But it's a good idea to start simple, I think. Cheers, Henrik _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
