[GRASS-dev] GSOC Week 4 report : Adding WMS layer support to update WXGUI
Hi all, This is my 4th week report. Please find it at following link. http://grass.osgeo.org/wiki/WxGUI_WMS_service_rendering_GSoC_2011#Report_.234_24-06-2011 . thanks sudeep ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GSOC Week 3 report : Adding WMS layer support to update WXGUI
Hi all, This is my 4th week report. Please find it at following link. http://grass.osgeo.org/wiki/WxGUI_WMS_service_rendering_GSoC_2011#Report_.234_24-06-2011 . thanks sudeep ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Weekly reports #4 wxNviz
Hi, 1) What do I have completed this week? I added new nviz features in workspace (light, view, constant planes). It took quite a lot of time to make it work properly. I will add other features continuously. 2) What am I going to achieve for next week? It seems that thematic points will be postponed. So I will follow the project plan (update nviz_cmd) and I will keep fixing bugs. 3) Is there any blocking issue? No Anna ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Make-system question
Hi Glynn, > This won't work with Multi.make, as HTMLSRC will be empty and so $< > will end up as "thumbnails.py". Instead, use: > > r.colors.tmp.html: $(BIN)/r.colors$(EXE) thumbnails.py > and: > r3.colors.tmp.html: $(BIN)/r3.colors$(EXE) thumbnails.py This works perfectly, thanks a lot! The new r3.colors implementation is available in svn. Still missing is the "-e" flag for r3.colors. I think i have to implement something similar to the Cell_stats approach in the raster library based on tiles in the g3d library. Best regards Soeren ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Make-system question
Soeren Gebbert wrote: > i face some Make-system problems while implementing r3.colors on top > of r.colors. Because i have no clue how the make system actually works > i am lost. I have modified the r.colors Makefile to handle now > different main files to build two binaries: > The source code compile well, but i broke the thumbnail preview > creation. Here the compilation report and error: ... LC_ALL=C thumbnails.py --html-description < /dev/null | grep -v Why is it trying to generate a manual page for thumbnails.py? Ah: r.colors.tmp.html: $(HTMLSRC) thumbnails.py $(call htmldesc,$<,$@) This won't work with Multi.make, as HTMLSRC will be empty and so $< will end up as "thumbnails.py". Instead, use: r.colors.tmp.html: $(BIN)/r.colors$(EXE) thumbnails.py and: r3.colors.tmp.html: $(BIN)/r3.colors$(EXE) thumbnails.py -- Glynn Clements ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Re: [GRASS GIS] #1330: wxGUI: "UnicodeEncodeError: 'ascii' codec can't encode characters" in pl_PL.UTF-8
Martin Landa wrote: > >> are you also changing opacity level at this point? > > or renaming the map layer (using non-ascii characters). > > I did not change the opacity AFAIK, but yes, there somehow appeared the (průhlednost 100%) note in the list of layers and that was the cause (in english there is (opacity 100%)). BTW the word "průhlednost" is wrong translation, there shoud be "neprůhlednost". -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/GRASS-GIS-1330-wxGUI-UnicodeEncodeError-ascii-codec-can-t-encode-characters-in-pl-PL-UTF-8-tp6189279p6511786.html Sent from the Grass - Dev mailing list archive at Nabble.com. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Re: sample dataset update
On Fri, Jun 24, 2011 at 11:13 AM, Markus Metz wrote: > On Thu, Jun 23, 2011 at 6:44 AM, Helena Mitasova wrote: >> Below are some plans for data updates. It would be useful to put this on wiki >> so that others can comment, add, modify. I was thinking about >> http://grass.osgeo.org/wiki/Sample_datasets >> but this is really for downloads, so perhaps as a new section here? >> http://grass.osgeo.org/wiki/GRASS_7_ideas_collection > > I would suggest to keep GRASS 7 ideas and the sample datasets separate > because 1) we do not know when GRASS 7 will be released and 2) the > additional datasets you listed below are very interesting, also for > GRASS 6.x. Therefore I would tend to add any new datasets to > http://grass.osgeo.org/wiki/Sample_datasets > even though this is currently for downloads only, but the two main > sites for sample data download are > http://grass.osgeo.org/download/data.php > and > http://www.grassbook.org/data_menu3rd.php > so it could be ok to add new ideas and TODO's to the wiki? I have updated http://grass.osgeo.org/wiki/Sample_datasets OK? Markus M > > I like the idea of having separately downloadable mapsets for the two > existing sample locations. This keeps download size manageable and > users can pick the sample data they are interested in. Of course > additional sample locations are also an option and I think that there > are already some new sample locations in preparation, e.g. for Italy. > > Another issue are the examples based on the sample data, both in the > book and in the documentation. All the examples for vector network > analysis that use cost columns are wrong. I am busy updating the > v.net.* manuals for GRASS 7 and will (hopefully) soon backport the > manuals to 6.5 and 6.4. Other examples in the manuals, and the manuals > themselves, may need a closer look too... > > With regard to GRASS 7 vector format, I want to change it further and > would therefore postpone a GRASS 7 sample dataset a bit. > Forward/backward compatibility will be limited: rebuilding topology > will be required when switching from 6.x to 7 or back (currently GRASS > 6.x can read GRASS 7 vectors as they are). For the existing sample > datasets spearfish and nc_spm, v.build.all takes less than a minute on > my laptop (6.x and 7), so this is not really an obstacle. > > For external file formats, we could also provide more links to free > datasources, however, examples based on these data may not work when > these datasources are updated. > > Markus M > >> >> Feel free to post it on wiki (or suggest where it would fit and I will post >> it). >> After I get some feedback I will prepare the first version of the new >> mapsets for networks and timeseries >> to test whether they are suitable, >> >> thanks, Helena >> >> >> >> Prepare new data sets (grass7 vector format?): >> - provided as separate MAPSETS that can be inserted into nc_spm_08 or >> gisdemo_ncspm (or their grass7 versions) >> - packaged all into single location (nc_spm_11) which could reach 1GB. >> - each MAPSET will have an example of application >> >> proposed new MAPSETS: >> >> Road and street networks (nconemap, ncdot) >> http://www.ncdot.org/it/gis/DataDistribution/DOTData/default.html >> LRS road network, Integrated Statewide Road network, Bike Paths >> - streets for wake http://www.wakegov.com/gis/services/data.htm` >> -add boundaries and POI for reference? >> -include emergency centers ? hurricane evacuation routes? potential >> emergency shelters? >> -include stream network? >> >> Time_series_coast >> coastal lidar point clouds, 1m res DEMs, orthos, 15 years in 10-15 snapshots >> extended version of this >> http://courses.ncsu.edu/mea582/common/media/01/NagsHead_series.zip >> also used for coastal analysis toolbox add-ons >> >> Landuse_img >> new 4 channel 1m res 2009 imagery NAID >> new NLCD 2006 from USGS and NLCD2001 >> 0.15m res ortho? >> include any post storm, post hurricane, post flood imagery for training >> purposes? >> see example here: >> http://www.ncdot.org/it/gis/DataDistribution/SpecialData/NCStormDamageAndCleanup.html >> >> Time_series_census >> this may take more time to prepare, >> data are available for 1970,80,90,2000,2010 >> combine with election districts? >> >> LOCATIONS: >> - cleanup and provide nc_ll, nc_utm, nc_spf for testing projections >> >> EXTERNAL data sets for testing external data formats >> - point cloud asci, las >> - shape >> - geodatabase? >> - MRsid, geotiff? >> >> Anything else from here? >> http://courses.ncsu.edu/mea582/common/GIS_anal_lecture/GIS_Anal_webdata.html >> http://www.nconemap.com/Default.aspx?tabid=286 >> http://www.wakegov.com/gis/services/data.htm >> (we provide link to this so only data to be used for GRASS tutorials and >> testing should be in the data set) >> >> >> On Jun 20, 2011, at 11:15 AM, Markus Metz wrote: >> >>> Hi all, >>> >>> we may want to think about an up
Re: [GRASS-dev] GRASS Make-system question
Hello Glynn,
i face some Make-system problems while implementing r3.colors on top
of r.colors. Because i have no clue how the make system actually works
i am lost. I have modified the r.colors Makefile to handle now
different main files to build two binaries:
{{{
MODULE_TOPDIR = ../..
LIBES = $(G3DLIB) $(RASTERLIB) $(GISLIB)
DEPENDENCIES = $(G3DDEP) $(GISDEP) $(RASTERDEP)
PROGRAMS = r.colors r3.colors
r_colors_OBJS = raster_main.o edit_colors.o rules.o stats.o
r3_colors_OBJS = raster3d_main.o edit_colors.o rules.o stats.o
include $(MODULE_TOPDIR)/include/Make/Multi.make
default: multi
# Insert thumbnail previews
r.colors.tmp.html: $(HTMLSRC) thumbnails.py
$(call htmldesc,$<,$@)
sed 's!^\([a-z0-9.]*\):! \1:!' "$@" > "$@.tmp"
mv -f "$@.tmp" "$@"
$(MAKE) thumbnails
thumbnails: $(BIN)/r.mapcalc$(EXE)
-$(call run_grass, ./thumbnails.py)
$(BIN)/r.mapcalc$(EXE):
$(MAKE) -C ../r.mapcalc
.PHONY: thumbnails
.INTERMEDIATE: r.colors.tmp.html
}}}
The source code compile well, but i broke the thumbnail preview
creation. Here the compilation report and error:
{{{
Makefile:17: warning: overriding commands for target `r.colors.tmp.html'
../../include/Make/Multi.make:30: warning: ignoring old commands for
target `r.colors.tmp.html'
test -d OBJ.x86_64-unknown-linux-gnu || mkdir -p OBJ.x86_64-unknown-linux-gnu
gcc -ggdb -Wall -Werror-implicit-function-declaration -fno-common
-fopenmp
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-D_FILE_OFFSET_BITS=64 -DPACKAGE=\""grassmods"\"
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-o OBJ.x86_64-unknown-linux-gnu/raster_main.o -c raster_main.c
gcc -ggdb -Wall -Werror-implicit-function-declaration -fno-common
-fopenmp
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-D_FILE_OFFSET_BITS=64 -DPACKAGE=\""grassmods"\"
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-o OBJ.x86_64-unknown-linux-gnu/edit_colors.o -c edit_colors.c
gcc -ggdb -Wall -Werror-implicit-function-declaration -fno-common
-fopenmp
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-D_FILE_OFFSET_BITS=64 -DPACKAGE=\""grassmods"\"
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-o OBJ.x86_64-unknown-linux-gnu/rules.o -c rules.c
gcc -ggdb -Wall -Werror-implicit-function-declaration -fno-common
-fopenmp
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-D_FILE_OFFSET_BITS=64 -DPACKAGE=\""grassmods"\"
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-o OBJ.x86_64-unknown-linux-gnu/stats.o -c stats.c
: && gcc
-L/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/lib
-L/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/lib
-lgomp -Wl,--export-dynamic
-Wl,-rpath-link,/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/lib
-o
/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/bin/r.colors
OBJ.x86_64-unknown-linux-gnu/raster_main.o
OBJ.x86_64-unknown-linux-gnu/edit_colors.o
OBJ.x86_64-unknown-linux-gnu/rules.o
OBJ.x86_64-unknown-linux-gnu/stats.o-lgrass_g3d.7.0.svn
-lgrass_raster.7.0.svn -lgrass_gis.7.0.svn -lm
gcc -ggdb -Wall -Werror-implicit-function-declaration -fno-common
-fopenmp
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-D_FILE_OFFSET_BITS=64 -DPACKAGE=\""grassmods"\"
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-I/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/include
-o OBJ.x86_64-unknown-linux-gnu/raster3d_main.o -c raster3d_main.c
: && gcc
-L/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/lib
-L/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/lib
-lgomp -Wl,--export-dynamic
-Wl,-rpath-link,/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/lib
-o
/home/soeren/src/grass7.0/grass_trunk/dist.x86_64-unknown-linux-gnu/bin/r3.colors
OBJ.x86_64-unknown-linux-gnu/raster3d_main.o
OBJ.x86_64-unknown-linux-gnu/edit_colors.o
OBJ.x86_64-unknown-linux-gnu/rules.o
OBJ.x86_64-unknown-linux-gnu/stats.o-l
[GRASS-dev] Re: sample dataset update
On Thu, Jun 23, 2011 at 6:44 AM, Helena Mitasova wrote: > Below are some plans for data updates. It would be useful to put this on wiki > so that others can comment, add, modify. I was thinking about > http://grass.osgeo.org/wiki/Sample_datasets > but this is really for downloads, so perhaps as a new section here? > http://grass.osgeo.org/wiki/GRASS_7_ideas_collection I would suggest to keep GRASS 7 ideas and the sample datasets separate because 1) we do not know when GRASS 7 will be released and 2) the additional datasets you listed below are very interesting, also for GRASS 6.x. Therefore I would tend to add any new datasets to http://grass.osgeo.org/wiki/Sample_datasets even though this is currently for downloads only, but the two main sites for sample data download are http://grass.osgeo.org/download/data.php and http://www.grassbook.org/data_menu3rd.php so it could be ok to add new ideas and TODO's to the wiki? I like the idea of having separately downloadable mapsets for the two existing sample locations. This keeps download size manageable and users can pick the sample data they are interested in. Of course additional sample locations are also an option and I think that there are already some new sample locations in preparation, e.g. for Italy. Another issue are the examples based on the sample data, both in the book and in the documentation. All the examples for vector network analysis that use cost columns are wrong. I am busy updating the v.net.* manuals for GRASS 7 and will (hopefully) soon backport the manuals to 6.5 and 6.4. Other examples in the manuals, and the manuals themselves, may need a closer look too... With regard to GRASS 7 vector format, I want to change it further and would therefore postpone a GRASS 7 sample dataset a bit. Forward/backward compatibility will be limited: rebuilding topology will be required when switching from 6.x to 7 or back (currently GRASS 6.x can read GRASS 7 vectors as they are). For the existing sample datasets spearfish and nc_spm, v.build.all takes less than a minute on my laptop (6.x and 7), so this is not really an obstacle. For external file formats, we could also provide more links to free datasources, however, examples based on these data may not work when these datasources are updated. Markus M > > Feel free to post it on wiki (or suggest where it would fit and I will post > it). > After I get some feedback I will prepare the first version of the new mapsets > for networks and timeseries > to test whether they are suitable, > > thanks, Helena > > > > Prepare new data sets (grass7 vector format?): > - provided as separate MAPSETS that can be inserted into nc_spm_08 or > gisdemo_ncspm (or their grass7 versions) > - packaged all into single location (nc_spm_11) which could reach 1GB. > - each MAPSET will have an example of application > > proposed new MAPSETS: > > Road and street networks (nconemap, ncdot) > http://www.ncdot.org/it/gis/DataDistribution/DOTData/default.html > LRS road network, Integrated Statewide Road network, Bike Paths > - streets for wake http://www.wakegov.com/gis/services/data.htm` > -add boundaries and POI for reference? > -include emergency centers ? hurricane evacuation routes? potential emergency > shelters? > -include stream network? > > Time_series_coast > coastal lidar point clouds, 1m res DEMs, orthos, 15 years in 10-15 snapshots > extended version of this > http://courses.ncsu.edu/mea582/common/media/01/NagsHead_series.zip > also used for coastal analysis toolbox add-ons > > Landuse_img > new 4 channel 1m res 2009 imagery NAID > new NLCD 2006 from USGS and NLCD2001 > 0.15m res ortho? > include any post storm, post hurricane, post flood imagery for training > purposes? > see example here: > http://www.ncdot.org/it/gis/DataDistribution/SpecialData/NCStormDamageAndCleanup.html > > Time_series_census > this may take more time to prepare, > data are available for 1970,80,90,2000,2010 > combine with election districts? > > LOCATIONS: > - cleanup and provide nc_ll, nc_utm, nc_spf for testing projections > > EXTERNAL data sets for testing external data formats > - point cloud asci, las > - shape > - geodatabase? > - MRsid, geotiff? > > Anything else from here? > http://courses.ncsu.edu/mea582/common/GIS_anal_lecture/GIS_Anal_webdata.html > http://www.nconemap.com/Default.aspx?tabid=286 > http://www.wakegov.com/gis/services/data.htm > (we provide link to this so only data to be used for GRASS tutorials and > testing should be in the data set) > > > On Jun 20, 2011, at 11:15 AM, Markus Metz wrote: > >> Hi all, >> >> we may want to think about an update of the sample datasets. I have >> recently updated the documentation of the v.net.* modules including >> examples and noticed that roads digitized as multilanes have wrong >> line directions, i.e. not matching drive directions. This makes >> assignment of different forward/b
