<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Bookman Old Style";
panose-1:2 5 6 4 5 5 5 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Bookman Old Style","serif";
color:navy;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Bookman Old Style","serif";
color:navy;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:66080330;
mso-list-type:hybrid;
mso-list-template-ids:-2086893226 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText>Hi Markus, <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thank you for prompt reply. I would like to further ask
you few more questions, and sure you would overlook my ignorance.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>My requirement is to make a strip down GIS tool using
GRASS engine focusing on raster image for the time being and preferably on
windows platform.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I would prefer to use the GRASS data format so that I am
not bounded on any commercial file format for my application and also provide
user the option to use GRASS or Quantum GIS. <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Please highlight the following doubts:<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>The grass would be providing me APIs where in I can
take any raster image, geo-reference it and then store in GRASS’s native
format. Can you please point out to the modules I would require just to perform
this action?<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Once I have converted to the GRASS native format, I would
like to display the image in visual form. Now you have pointed to several
options available with the existing version. I wanted to know is the display
eventually like a photo viewer especially when GRASS is layering the
information one over another. Also would grass provide me some standardized
output in terms of jpg, bmp etc which I can display in any application? Any
pointers to the similar options available on windows platform?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> 2. The input to the GDAL can be
any raster format like BMP, GeoTIFF,<o:p></o:p></p>
<p class=MsoPlainText>> TIFF, PNG etc. What would be the output format GDAL
produces after it<o:p></o:p></p>
<p class=MsoPlainText>> manipulates the original raster image.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> If the input is geo-coded incl. metadata, this is
respected. Otherwise it<o:p></o:p></p>
<p class=MsoPlainText>> is imported as XY map.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>So if the information is geo-coded already, GRASS would
not perform any additionally operation but will still convert and store in the
native format. Correct?<o:p></o:p></p>
<p class=MsoPlainText>Additionally, if I have to display a GDAL processed
input, does GRASS let me do that? Or are there tools which will help me see and
understand what exactly is the output. (I hope I am able to present my point)<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>It is my understanding, that OGR would be similar to GDAL
with focus on the vector data, which is further converted to the GRASS native
format for processing and viewing.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I have worked mostly on windows platform, hence there are
lot of questions as GRASS is based on Linux and current winGrass version is
using the cygwin. Though I was reading the full windows version would be out
soon.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The architecture diagram was really helpful in getting
the overall idea of where all libraries fit in.<o:p></o:p></p>
<p class=MsoPlainText>Thanks a lot..<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Regards,<o:p></o:p></p>
<p class=MsoPlainText>Kavitesh Singh<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-----Original Message-----<br>
From: neteler.osgeo@gmail.com [mailto:neteler.osgeo@gmail.com] On Behalf Of Markus
Neteler<br>
Sent: Wednesday, April 08, 2009 06:52 PM<br>
To: Kavitesh Singh <br>
Cc: GRASS developers list<br>
Subject: Re: [GRASS-dev] GDAL/Proj modules role in Grass<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>On Wed, Apr 8, 2009 at 1:52 PM,
<kavitesh.singh@wipro.com> wrote:<o:p></o:p></p>
<p class=MsoPlainText>> Hi All,<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> I am beginner at learning GRASS and was trying to
understand the overall<o:p></o:p></p>
<p class=MsoPlainText>> architecture of GRASS using various libraries like
GDAL/PROJ etc.<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> I wanted to know how GDAL and PROJ library fit into
GRASS for raster<o:p></o:p></p>
<p class=MsoPlainText>> processing of maps?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>These libraries are requirements for GRASS (see more
below).<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> I would like to verify my understanding of GDAL with
my current reading for<o:p></o:p></p>
<p class=MsoPlainText>> raster format like JPEG,BMP<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> 1. It is used for geo-referencing
any raster image by providing the<o:p></o:p></p>
<p class=MsoPlainText>> corner file data. Does the geo-referencing
internally call PROJ library to<o:p></o:p></p>
<p class=MsoPlainText>> reference according to any particular datum?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>It depends:<o:p></o:p></p>
<p class=MsoPlainText>- yes for r.proj and v.proj<o:p></o:p></p>
<p class=MsoPlainText>- no for i.rectify<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> 2. The input to the GDAL can be
any raster format like BMP, GeoTIFF,<o:p></o:p></p>
<p class=MsoPlainText>> TIFF, PNG etc. What would be the output format GDAL
produces after it<o:p></o:p></p>
<p class=MsoPlainText>> manipulates the original raster image.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>If the input is geocoded incl. metadata, this is
respected. Otherwise it<o:p></o:p></p>
<p class=MsoPlainText>is imported as XY map.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> 3. Once the output is generated,
is it available for processing in the<o:p></o:p></p>
<p class=MsoPlainText>> memory or it produces some file which is later read
by GRASS for<o:p></o:p></p>
<p class=MsoPlainText>> visualization?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>GRASS is storing its files in its internal format (except
for r.external and<o:p></o:p></p>
<p class=MsoPlainText>v.external). So, yes, files are produced.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I have just drawn the GRASS architecture:<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>http://trac.osgeo.org/grass/browser/grass-web/trunk/images<o:p></o:p></p>
<p class=MsoPlainText>- grass6_arch.odg<o:p></o:p></p>
<p class=MsoPlainText>- grass6_arch.png<o:p></o:p></p>
<p class=MsoPlainText>- grass7_arch.odg<o:p></o:p></p>
<p class=MsoPlainText>- grass7_arch.png<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>(please improve!)<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>See also here:<o:p></o:p></p>
<p class=MsoPlainText>http://download.osgeo.org/grass/grass6_progman/<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> 4. I wanted to know how GRASS uses
the geo-referenced raster image for<o:p></o:p></p>
<p class=MsoPlainText>> display. Is it using some 3rd party library or has
developed a display panel<o:p></o:p></p>
<p class=MsoPlainText>> specific to GIS needs.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>There is both in different implementations:<o:p></o:p></p>
<p class=MsoPlainText>- built-in display system (X11 based)<o:p></o:p></p>
<p class=MsoPlainText>- Tcl based display system<o:p></o:p></p>
<p class=MsoPlainText>- wxPython based display system<o:p></o:p></p>
<p class=MsoPlainText>- Cairo based display system<o:p></o:p></p>
<p class=MsoPlainText>- PS based display system<o:p></o:p></p>
<p class=MsoPlainText>- PNG based display system<o:p></o:p></p>
<p class=MsoPlainText>- HTML based display system<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>All of them are drivers.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> 5. It is my understanding that
GRASS data output directory is not related<o:p></o:p></p>
<p class=MsoPlainText>> to GDAL/PROJ.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Right. It is called GISBASE. See<o:p></o:p></p>
<p class=MsoPlainText>http://grass.osgeo.org/grass64/manuals/html64_user/helptext.html<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> This is native GRASS format and the GRASS engine
displays the<o:p></o:p></p>
<p class=MsoPlainText>> data on the panel using some inbuilt functions.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Right.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> Please excuse me, if the questions have been asked
before also. I would<o:p></o:p></p>
<p class=MsoPlainText>> appreciate any help in this regard.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Hope this helps,<o:p></o:p></p>
<p class=MsoPlainText>Markus<o:p></o:p></p>
</div>
<P><strong><span style='font-size:10.0pt;font-family:
"Palatino Linotype","serif";color:green'> Please do not print this email unless it is absolutely necessary. </span></strong><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
<p> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. </p>
<p>WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. </p>
<p>
www.wipro.com
</p>
</body>
</html>