<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 22, 2015 at 3:53 AM, Nikos Alexandris <span dir="ltr"><<a href="mailto:nik@nikosalexandris.net" target="_blank">nik@nikosalexandris.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On 22.01.2015 10:32, Helmut Kudrnovsky wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> > I find the fact that GRASS does not provide a default<br>
> > projection system, but forces the user to think about projection from the<br>
> > start, one of its strengths, both for work and for teaching.<br>
</blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
>> On of it strenghts, yes. But I have been teaching GRASS a lot to GIS<br>
>> professionals who got trained on different systems. And many asked<br>
>> "why this screen? why cannot you just start like the other GIS"? And I<br>
> >tend to agree (again: optionally). The point is that we, on the<br>
> >contrary to many other GIS, still have all the control mechanisms in<br>
>> place which avoid that the user mixes projections. So that's all fine.<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
And what will you do after 'just starting'? Do you have your data as LL? Or<br>
</blockquote>
will you use -o flag to ignore<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
the projection check?<br>
</blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I agree. I can't see any benefit to be automatically in a LL location, as in<br>
many cases your data will be in other SRSs.<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
what may be make sense: define your projection/srs by import your first data<br>
and offer this option in a prominent way in the welcome screen and not<br>
"hidden" in the location wizzard as at the moment.<br>
</blockquote>
<br></span>
+1<span class=""><font color="#888888"><br>
<br></font></span></blockquote><div><br></div><div>This is was my suggestion allows us to add "Location from data/GIS file". Default place would be under New, Rename and Delete buttons together with "Unpack location from ZIP", "Create LL", and "Create XY". Alternative placement would be at the top or bottom of the Select GRASS Location group box. This could serve to both novices and advanced users unlike other solutions.<br><br></div><div>"Skip, and start GRASS session" button can be at the bottom. The functionality as described by Markus Metz makes sense, create grassdata in user home and get demolocation from source code. We can also just create this location automatically if the GISDBASE is not set (1) or is empty, do the think which would "Skip" button do and then you can just use standard "Start GRASS session".<br><br></div><div>The advantage of my suggestion is that we can actually make it to the release of 7.0 (2) and then add improvements later.<br><br></div><div>(1) Now, we show an error dialog which looks that everything is wrong which after OK, shows Browse dialog which without reading is hard to understand and this is what people starting GRASS for the first time get. I replaced a lot of these dialogs (errors or just warnings) by the message shown in the windows. This one will be next.<br></div><div><br></div><div>(2) It's basically done, with user testing (it does not require much) and backports it should be ready on Monday morning.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=""><font color="#888888">
Nikos</font></span><span class="im"><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
and what I've learned from GRASS GIS :-) when using other GIS software:<br>
first check SRSs of my data, open GIS software, define SRS and then load<br>
data.<br>
<br>
my 0.02c<br>
</blockquote></span><div class=""><div class="h5">
______________________________<u></u>_________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/grass-dev</a><br>
</div></div></blockquote></div><br></div></div>