[GRASS-dev] improved suport for WMS in GDAL 1.5

GRASS GIS GRASS GIS developer
,
1

It looks like the new version of GDAL natively supports WMS:
http://www.gdal.org/frmt_wms.html

I have a feeling that this can be used to extend / enhance modules like
r.in.wms. Possibly by adjusting r.in.gdal itself- to create a temporary XML
config file to prep the GDAL library.

Just some thoughts,

Dylan

2

Dylan Beaudette wrote:

It looks like the new version of GDAL natively supports WMS:
http://www.gdal.org/frmt_wms.html

Same for 1" and 3" SRTMs. They are natively supported in
GDAL 1.5. We should consider disposing r.in.srtm in GRASS 7
for that. Could you add GDAL 1.5-related notes regarding
r.in.wms and r.in.srtm to GRASS 7 planning WIKI page?

Maciek

3

On Thursday 06 December 2007, Maciej Sieczka wrote:

Dylan Beaudette wrote:
> It looks like the new version of GDAL natively supports WMS:
> http://www.gdal.org/frmt_wms.html

Same for 1" and 3" SRTMs. They are natively supported in
GDAL 1.5. We should consider disposing r.in.srtm in GRASS 7
for that. Could you add GDAL 1.5-related notes regarding
r.in.wms and r.in.srtm to GRASS 7 planning WIKI page?

Maciek

added these items.

cheers,

--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341

4

Hi,

2007/12/10, Dylan Beaudette <dylan.beaudette@gmail.com>:

> r.in.wms and r.in.srtm to GRASS 7 planning WIKI page?
>
> Maciek

added these items.

BTW, it was not discussed here yet, I think it would be good to slowly
move dev's stuff from Mediawiki to Tracwiki, see

http://trac.osgeo.org/grass/wiki

E.g.

http://trac.osgeo.org/grass/wiki/Release/6.3.0RC3-News

and

http://grass.gdf-hannover.de/wiki/GRASS_6.3_Feature_Plan

User-related issues will be maintained using Mediawiki (which will be
also migrated to OSGeo), dev's topics should be part Trac instance.

I hope it make sense..., regards Martin

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

5

Martin Landa wrote:

BTW, it was not discussed here yet, I think it would be good to slowly
move dev's stuff from Mediawiki to Tracwiki, see

http://trac.osgeo.org/grass/wiki

E.g.

http://trac.osgeo.org/grass/wiki/Release/6.3.0RC3-News

and

http://grass.gdf-hannover.de/wiki/GRASS_6.3_Feature_Plan

User-related issues will be maintained using Mediawiki (which will be
also migrated to OSGeo), dev's topics should be part Trac instance.

I think there are very important reasons to keep the user and devel wikis as
one. It stresses the coupling of the two: in GRASS the users are the
developers, and the developers are some of the heaviest users. The less of a
split we have between the two, the more likely we will be to have users become
developers.

So the fewer barriers between the two the better, aka constructing artificial
barriers is to be avoided.

Having said that, I can see the advantages of splitting them:

* User wiki should be using (osgeo hosted) MediaWiki not Trac's wiki. MediaWiki
has a much richer feature set, and is more suited for documentation. e.g. for
images.

* If the devl pages are using Trac's wiki it can tie in better with the bug
tracker and SVN code commit revision ID's.

Is the technical trac integration tools the main reason to use that? Examples
from another OSGeo project using this?
Is this useful enough to outweigh the (intangible) culture damage caused by
splitting up the wiki into two parts/logins/links?

regards,
Hamish

      ____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs