You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(204) |
Jul
(85) |
Aug
(211) |
Sep
(145) |
Oct
(41) |
Nov
(114) |
Dec
(142) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(188) |
Feb
(98) |
Mar
(69) |
Apr
(72) |
May
(93) |
Jun
(119) |
Jul
(129) |
Aug
(80) |
Sep
(110) |
Oct
(72) |
Nov
(85) |
Dec
(145) |
2007 |
Jan
(246) |
Feb
(89) |
Mar
(105) |
Apr
(94) |
May
(116) |
Jun
(248) |
Jul
(110) |
Aug
(144) |
Sep
(118) |
Oct
(92) |
Nov
(96) |
Dec
(168) |
2008 |
Jan
(100) |
Feb
(86) |
Mar
(92) |
Apr
(145) |
May
(71) |
Jun
(122) |
Jul
(97) |
Aug
(90) |
Sep
(76) |
Oct
(54) |
Nov
(51) |
Dec
(44) |
2009 |
Jan
(55) |
Feb
(38) |
Mar
(86) |
Apr
(123) |
May
(111) |
Jun
(116) |
Jul
(107) |
Aug
(107) |
Sep
(86) |
Oct
(54) |
Nov
(63) |
Dec
(78) |
2010 |
Jan
(103) |
Feb
(76) |
Mar
(117) |
Apr
(218) |
May
(106) |
Jun
(170) |
Jul
(77) |
Aug
(61) |
Sep
(69) |
Oct
(109) |
Nov
(67) |
Dec
(135) |
2011 |
Jan
(87) |
Feb
(49) |
Mar
(43) |
Apr
(77) |
May
(85) |
Jun
(81) |
Jul
(89) |
Aug
(109) |
Sep
(56) |
Oct
(96) |
Nov
(81) |
Dec
(41) |
2012 |
Jan
(84) |
Feb
(20) |
Mar
(70) |
Apr
(46) |
May
(34) |
Jun
(65) |
Jul
(50) |
Aug
(19) |
Sep
(20) |
Oct
(40) |
Nov
(35) |
Dec
(91) |
2013 |
Jan
(47) |
Feb
(95) |
Mar
(61) |
Apr
(40) |
May
(32) |
Jun
(30) |
Jul
(73) |
Aug
(52) |
Sep
(21) |
Oct
(24) |
Nov
(20) |
Dec
(29) |
2014 |
Jan
(9) |
Feb
(48) |
Mar
(13) |
Apr
|
May
(34) |
Jun
(31) |
Jul
(46) |
Aug
(21) |
Sep
(7) |
Oct
(5) |
Nov
(9) |
Dec
(21) |
2015 |
Jan
(14) |
Feb
(10) |
Mar
(47) |
Apr
(39) |
May
(23) |
Jun
(15) |
Jul
(17) |
Aug
(12) |
Sep
(15) |
Oct
(15) |
Nov
(30) |
Dec
(11) |
2016 |
Jan
|
Feb
(1) |
Mar
(39) |
Apr
(6) |
May
(12) |
Jun
(10) |
Jul
(16) |
Aug
(13) |
Sep
(7) |
Oct
(3) |
Nov
(4) |
Dec
(2) |
2017 |
Jan
(7) |
Feb
(5) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
(7) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
|
2018 |
Jan
(3) |
Feb
(6) |
Mar
(3) |
Apr
|
May
(14) |
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(13) |
Oct
|
Nov
|
Dec
(6) |
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Garrett P. <po...@cf...> - 2005-07-25 10:55:53
|
Hello All: I will look at it this morning. I see an inefficiency in the replaceAllThatMatch and will fix that also. Take care Garrett On Jul 24, 2005, at 9:36 AM, David Burken wrote: > Paul: > > I've checked in a temp fix for the below problem. You'll need to > update: > ossim_qt/src/ossimDataManager.cpp > > The problem is the call to "ossimString::replaceAllThatMatch" is > doing an infinite loop. > I've temporarily just slapped "Equalization chain: " in front of > the description. > > We'll get a good fix on Monday... > > Sorry for the inconvenience, > Dave > > Paul Surgeon wrote: >> On Saturday, 23 July 2005 18:18, David Burken wrote: >> >>> No it should be instant. I try and duplicate. Probably won't >>> have a >>> fix until Monday though. >>> >>> What are the bit depths of your images? We need to re-work our >>> histogram stuff for non-8bit images so it takes a number of >>> buckets... >>> Say you have a 16 bit image, you probably don't have 65,000 >>> discrete dn >>> values. >>> >>> Dave >>> >> I'm using 8 bit RGB images created from Landsat ETM+ data. >> I created a composite using the MS bands and then pan-sharpened them. >> They are still in their original UTM projection (if that is of any >> importance). >> >> I'm glad that it should be fast - I was starting to think that >> histogram >> matches were going to be out of the question due to the slow speed. >> >> Thanks >> Paul >> |
From: Paul S. <su...@te...> - 2005-07-24 15:26:15
|
Thanks a ton David It could have waited a bit though - I'm not in that much of a hurry. Regards Paul On Sunday, 24 July 2005 15:36, David Burken wrote: > Paul: > > I've checked in a temp fix for the below problem. You'll need to update: > ossim_qt/src/ossimDataManager.cpp > > The problem is the call to "ossimString::replaceAllThatMatch" is doing > an infinite loop. > I've temporarily just slapped "Equalization chain: " in front of the > description. > > We'll get a good fix on Monday... > > Sorry for the inconvenience, > Dave > > Paul Surgeon wrote: > >On Saturday, 23 July 2005 18:18, David Burken wrote: > >>No it should be instant. I try and duplicate. Probably won't have a > >>fix until Monday though. > >> > >>What are the bit depths of your images? We need to re-work our > >>histogram stuff for non-8bit images so it takes a number of buckets... > >>Say you have a 16 bit image, you probably don't have 65,000 discrete dn > >>values. > >> > >>Dave > > > >I'm using 8 bit RGB images created from Landsat ETM+ data. > >I created a composite using the MS bands and then pan-sharpened them. > >They are still in their original UTM projection (if that is of any > >importance). > > > >I'm glad that it should be fast - I was starting to think that histogram > >matches were going to be out of the question due to the slow speed. > > > >Thanks > >Paul |
From: David B. <db...@co...> - 2005-07-24 13:37:09
|
Paul: I've checked in a temp fix for the below problem. You'll need to update: ossim_qt/src/ossimDataManager.cpp The problem is the call to "ossimString::replaceAllThatMatch" is doing an infinite loop. I've temporarily just slapped "Equalization chain: " in front of the description. We'll get a good fix on Monday... Sorry for the inconvenience, Dave Paul Surgeon wrote: >On Saturday, 23 July 2005 18:18, David Burken wrote: > > >>No it should be instant. I try and duplicate. Probably won't have a >>fix until Monday though. >> >>What are the bit depths of your images? We need to re-work our >>histogram stuff for non-8bit images so it takes a number of buckets... >>Say you have a 16 bit image, you probably don't have 65,000 discrete dn >>values. >> >>Dave >> >> > >I'm using 8 bit RGB images created from Landsat ETM+ data. >I created a composite using the MS bands and then pan-sharpened them. >They are still in their original UTM projection (if that is of any >importance). > >I'm glad that it should be fast - I was starting to think that histogram >matches were going to be out of the question due to the slow speed. > >Thanks >Paul > > |
From: Paul S. <su...@te...> - 2005-07-23 17:39:41
|
On Saturday, 23 July 2005 18:18, David Burken wrote: > No it should be instant. I try and duplicate. Probably won't have a > fix until Monday though. > > What are the bit depths of your images? We need to re-work our > histogram stuff for non-8bit images so it takes a number of buckets... > Say you have a 16 bit image, you probably don't have 65,000 discrete dn > values. > > Dave I'm using 8 bit RGB images created from Landsat ETM+ data. I created a composite using the MS bands and then pan-sharpened them. They are still in their original UTM projection (if that is of any importance). I'm glad that it should be fast - I was starting to think that histogram matches were going to be out of the question due to the slow speed. Thanks Paul |
From: David B. <db...@co...> - 2005-07-23 16:18:59
|
Paul, Paul Surgeon wrote: >Are histogram matches normally a slow process? >I am trying to match two 762MB images (RGB 17354 x 15358 pixels). >I killed ImageLinker after 5 hours. > >Memory consumption was low (about 100MB) but CPU usage was over 90% for the >entire duration on an Athlon 2000 XP. > >Should it take this long or is it in some infinite loop somewhere? > >Thanks >Paul > > > No it should be instant. I try and duplicate. Probably won't have a fix until Monday though. What are the bit depths of your images? We need to re-work our histogram stuff for non-8bit images so it takes a number of buckets... Say you have a 16 bit image, you probably don't have 65,000 discrete dn values. Dave |
From: Paul S. <su...@te...> - 2005-07-23 15:56:37
|
Are histogram matches normally a slow process? I am trying to match two 762MB images (RGB 17354 x 15358 pixels). I killed ImageLinker after 5 hours. Memory consumption was low (about 100MB) but CPU usage was over 90% for the entire duration on an Athlon 2000 XP. Should it take this long or is it in some infinite loop somewhere? Thanks Paul |
From: Chris H. <ch...@op...> - 2005-07-23 11:12:13
|
> Over in OSSIM land we are currently focused on prioritizing > functionality and wrapping in WSDLs for SOAP interfaces. Scottie is > taking a look at regenerating JOSSIM with swig. I'm cross posting > this and Scottie can respond with his comments and thoughts. Could > you walk me through why it would be smarter to target GeoServer/ > GeoTools - haven't kept up with all that is going on... Ok, my understanding of OSSIM is thin, like how exactly it would integrate. But a few general thoughts. Targeting GeoServer/GeoTools vs. WSDLs for SOAP interfaces should not be mutually exclusive. We're planning a rewrite of GeoServer to make it much more of an application framework, basically a web gis framework to match udig's desktop - with the ability to plug-in services. So I'd see WSDL + SOAP interface for OSSIM as another (very nice) plug-in to have for GeoServer. This is a bit long term, but I think there's more short term advantages. Udig is built on GeoTools as well, so basically if the work is done at udig at that level, we get it in GeoServer for free. This leads to more bug reports and fixing, a wider community feeding into things. GeoServer and Udig both support very pluggable data access at the data level, so if ossim had integration at that level then both could easily use it. And any other project starting up using geotools could also make use of it. So basically you'd get a lot more users/bug testers, ect. I also noticed in this post: http://xserve.flids.com/pipermail/earthviewer/2004-August/000041.html that you're using open map as a WMS server? OpenMap isn't primarily a GIS server afaik, whereas geoserver is. So to have a very good WMS/WCS server for OSSIM you'd just need to maintain the data access level, we've got a solid community to handle all the rest, a nice gui framework, ect. In the fall it looks like there's going to be anywhere between 4 and 10 developers working in and around geoserver at any given time. And our raster guys are going full force right now, so if you get OSSIM in Java with SWIG soon they might be able to help out a good bit on integrating at the geotools level. So yes, I suspect there may be two levels of integration possible, one at the lower level, loading in data and putting it into geotools, which will give udig more native access and give geoserver access. Not sure on the details for configuration and all that, but I think this would be possible. And from what I understand, a higher level for each, in udig more just making use of their widgets, as a bit more separate from geotools, and then in geoserver eventually as a plugin to expose the wsdl and soap bindings. And then things would probably be made smoother in each by integration between levels, like in geoserver the image chain being easily exposed as WMS/WFS, in udig doing ossim processing with geotools loaded data (? my knowledge is fuzzy here, but I'd imagine there's something) > We've been in contact with some of the South Africa folks, they we've > really been impressed with some of their comments and submissions. Very cool. They had me down a couple months ago to present on geoserver and open source, and one of the things I tried to emphasize was the importance of giving good feedback and contributing where possible. But they were probably doing such things before I came along, they've got a good eye towards open source. best regards, Chris ---------------------------------------------------------- This mail sent through IMP: https://webmail.limegroup.com/ |
From: Mark L. <mlu...@ma...> - 2005-07-23 02:26:12
|
Over in OSSIM land we are currently focused on prioritizing functionality and wrapping in WSDLs for SOAP interfaces. Scottie is taking a look at regenerating JOSSIM with swig. I'm cross posting this and Scottie can respond with his comments and thoughts. Could you walk me through why it would be smarter to target GeoServer/ GeoTools - haven't kept up with all that is going on... We've been in contact with some of the South Africa folks, they we've really been impressed with some of their comments and submissions. Mark On Jul 22, 2005, at 7:50 PM, Chris Holmes wrote: >> Jody, >> > > >> Good news about the potential of an OSX uDig. At lunch today we >> (OSSIM people) were talking about osgPlanet http://www.ossim.org/ >> tiki-read_article.php?articleId=3 and the fact that we need to wrap >> it in a nice gui with OGC widgets etc. The discussion turned to >> making it into an Eclipse plugin and running it with uDig. So far >> everything is built in C++ (libraries are osgPlanet, OSSIM, >> OpenSceneGraph, libwms and the usual suspects - GDAL, GeoTiff >> etc...). We are going to start taking a look at Eclipse/uDig etc to >> see if we can figure it out. Thoughts, pointers, comments? >> > > >> Mark >> > > _I_ think this would be the coolest thing ever. Or at least one of > them. Not that I'm a udig developer, but I'm all for it! If you guys > did integration at the geotools level, then we could easily get it > into > GeoServer, which I think would be great. I've actually been wondering > about the state of JOSSIM lately for that very reason. We have two > awesome developers doing raster support for GeoServer/GeoTools, and > they were interested since if there were JOSSIM bindings it'd be > easier > than doing our own swig ones for gdal. Some guys in South Africa > (CSIR > SAC) are also interested in OSSIM with GeoServer/Web Services. They > downlink landsat and modis from satellites, and want to distribute to > all of Africa, but they are huge. They were thinking of allowing > clients to define the image processing chains on the server side, so > they could get the results of the processing they wanted, instead of > having to download the large raw datasets. Lots of interesting > issues, > and it's probably a good way off, but they were the ones to turn me on > to OSSIM, and it's really some incredible work that I would love to > see > integrated with the Java world. > > Oh yeah, I tried OSG planet windows installer 1.0.1 I think, but all I > got was an uninstall shortcut. I've been meaning to email the list > about it, but haven't found the time. > > best regards, > > Chris > > ---------------------------------------------------------- > This mail sent through IMP: https://webmail.limegroup.com/ > |
From: Mark L. <mlu...@ma...> - 2005-07-22 20:51:28
|
Yes, Same as in OpenSceneGraph, http://www.ossim.org/tiki-view_faq.php?faqId=3#q3 Mark On Jul 22, 2005, at 4:15 PM, Tyler Mitchell wrote: > Hi guys, thanks a lot for tips. I will try my best. I've got > SRTM, so it's a good start anyway. Your pointers should be good to > get me going. I'm just going to have to get into OSSIM even more, > I suspect :) > > Are there "tilting" controls that I need to know about? > > Tyler > > Garrett Potts wrote: > >> Hello : >> Make sure you download the unix version of the geoid. >> Take care >> Garrett >> On Jul 22, 2005, at 3:26 PM, David Burken wrote: >> >>> Tyler, >>> >>> Tyler Mitchell wrote: >>> >>> >>> >>>>>> Tyler Mitchell wrote: Hi all, >>>>>> Anyone have a kwl that shows the syntax for setting up >>>>>> terrain for osgPlanet? >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>>> Look at "osgPlanet/examples/osgplanetviewer/archive_manager.kwl" >>>>> >>>>> >>>> >>>> >>>> I've seen this already, but am a bit confused. These examples >>>> cover local images and WMS images. But what about 3D/terrain >>>> data speficially. I assumed there was a different "type" and >>>> that it would take tif images. >>>> >>>> Tyler >>>> >>>> >>>> >>> >>> The ossim core can auto load both dted and srtm for terrain. >>> If you have a tif it will have to be converted to an srtm format >>> using orthoigen (see ossim/etc/templates/orthoigen_srtm.kwl). >>> >>> You will need: >>> - Goid grid: http://earth-info.nga.mil/GandG/wgs84/gravitymod/ >>> egm96/egm96.htm >>> - Set environment variable "OSSIM_PREFS_FILE" point it to your >>> preferences file. >>> - An ossim preferences file. There is one in "ossim/etc/ >>> templates". Here is a cut from mine: >>> - Elevation data (dted or srtm). For dted it must be in the >>> standard directory tree. SRTMS can go in one directory. >>> >>> // Elevation stuff... >>> // srtm_directory1: /work/drb/image_formats/elevation/srtm/1arc >>> // srtm_directory1: /home/dburken/work/images/elevation/ned_srtm >>> dted_directory2: /work/drb/image_formats/elevation/ned >>> dted_directory1: /work/drb/image_formats/elevation/1arc >>> // default_elevation_path: /home/dburken/work/images/elevation/ >>> ned_srtm >>> default_elevation_path: /work/drb/image_formats/elevation/1arc >>> autoload_dted_elevation: true >>> elevation.enabled: true >>> elevation.auto_sort.enabled: true >>> elevation.auto_load_dted.enabled: true >>> // --- >>> // Geoid support (you can get by with just egm96 which is >>> actually the vertical datum of DTED) >>> // --- >>> >>> // GEOID 99: Set keyword to the directory containing the GEOID >>> 99 grids. >>> geoid_99_directory: /work/drb/image_formats/elevation/geoid99 >>> >>> // GEOID EGM 96: Set keyword to the path to the egm96.grd >>> geoid_egm_96_grid: /work/drb/image_formats/elevation/geoid96/ >>> egm96.grd >>> >>> Hope this helps a little, >>> Dave >>> >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is sponsored by: Discover Easy Linux Migration >>> Strategies >>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>> informative Webcasts and more! Get everything you need to get up to >>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>> _______________________________________________ >>> www.ossim.org >>> Ossim-developer mailing list >>> Oss...@li... >>> https://lists.sourceforge.net/lists/listinfo/ossim-developer >>> >>> > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: Tyler M. <tj...@ti...> - 2005-07-22 20:15:29
|
Hi guys, thanks a lot for tips. I will try my best. I've got SRTM, so it's a good start anyway. Your pointers should be good to get me going. I'm just going to have to get into OSSIM even more, I suspect :) Are there "tilting" controls that I need to know about? Tyler Garrett Potts wrote: > Hello : > > Make sure you download the unix version of the geoid. > > > Take care > > Garrett > On Jul 22, 2005, at 3:26 PM, David Burken wrote: > >> Tyler, >> >> Tyler Mitchell wrote: >> >> >>>>> Tyler Mitchell wrote: Hi all, >>>>> Anyone have a kwl that shows the syntax for setting up terrain for >>>>> osgPlanet? >>>>> >>>> >>>> >>> >>> >>>> Look at "osgPlanet/examples/osgplanetviewer/archive_manager.kwl" >>>> >>> >>> >>> I've seen this already, but am a bit confused. These examples cover >>> local images and WMS images. But what about 3D/terrain data >>> speficially. I assumed there was a different "type" and that it >>> would take tif images. >>> >>> Tyler >>> >>> >> >> The ossim core can auto load both dted and srtm for terrain. If you >> have a tif it will have to be converted to an srtm format using >> orthoigen (see ossim/etc/templates/orthoigen_srtm.kwl). >> >> You will need: >> - Goid grid: http://earth-info.nga.mil/GandG/wgs84/gravitymod/ >> egm96/egm96.htm >> - Set environment variable "OSSIM_PREFS_FILE" point it to your >> preferences file. >> - An ossim preferences file. There is one in "ossim/etc/ templates". >> Here is a cut from mine: >> - Elevation data (dted or srtm). For dted it must be in the standard >> directory tree. SRTMS can go in one directory. >> >> // Elevation stuff... >> // srtm_directory1: /work/drb/image_formats/elevation/srtm/1arc >> // srtm_directory1: /home/dburken/work/images/elevation/ned_srtm >> dted_directory2: /work/drb/image_formats/elevation/ned >> dted_directory1: /work/drb/image_formats/elevation/1arc >> // default_elevation_path: /home/dburken/work/images/elevation/ ned_srtm >> default_elevation_path: /work/drb/image_formats/elevation/1arc >> autoload_dted_elevation: true >> elevation.enabled: true >> elevation.auto_sort.enabled: true >> elevation.auto_load_dted.enabled: true >> // --- >> // Geoid support (you can get by with just egm96 which is actually >> the vertical datum of DTED) >> // --- >> >> // GEOID 99: Set keyword to the directory containing the GEOID 99 >> grids. >> geoid_99_directory: /work/drb/image_formats/elevation/geoid99 >> >> // GEOID EGM 96: Set keyword to the path to the egm96.grd >> geoid_egm_96_grid: /work/drb/image_formats/elevation/geoid96/egm96.grd >> >> Hope this helps a little, >> Dave >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> www.ossim.org >> Ossim-developer mailing list >> Oss...@li... >> https://lists.sourceforge.net/lists/listinfo/ossim-developer >> > > > |
From: Garrett P. <po...@cf...> - 2005-07-22 19:59:50
|
Hello : Make sure you download the unix version of the geoid. Take care Garrett On Jul 22, 2005, at 3:26 PM, David Burken wrote: > Tyler, > > Tyler Mitchell wrote: > > >>>> Tyler Mitchell wrote: Hi all, >>>> Anyone have a kwl that shows the syntax for setting up terrain >>>> for osgPlanet? >>>> >>> >>> >> >> >>> Look at "osgPlanet/examples/osgplanetviewer/archive_manager.kwl" >>> >> >> >> I've seen this already, but am a bit confused. These examples >> cover local images and WMS images. But what about 3D/terrain data >> speficially. I assumed there was a different "type" and that it >> would take tif images. >> >> Tyler >> >> > > The ossim core can auto load both dted and srtm for terrain. If > you have a tif it will have to be converted to an srtm format using > orthoigen (see ossim/etc/templates/orthoigen_srtm.kwl). > > You will need: > - Goid grid: http://earth-info.nga.mil/GandG/wgs84/gravitymod/ > egm96/egm96.htm > - Set environment variable "OSSIM_PREFS_FILE" point it to your > preferences file. > - An ossim preferences file. There is one in "ossim/etc/ > templates". Here is a cut from mine: > - Elevation data (dted or srtm). For dted it must be in the > standard directory tree. SRTMS can go in one directory. > > // Elevation stuff... > // srtm_directory1: /work/drb/image_formats/elevation/srtm/1arc > // srtm_directory1: /home/dburken/work/images/elevation/ned_srtm > dted_directory2: /work/drb/image_formats/elevation/ned > dted_directory1: /work/drb/image_formats/elevation/1arc > // default_elevation_path: /home/dburken/work/images/elevation/ > ned_srtm > default_elevation_path: /work/drb/image_formats/elevation/1arc > autoload_dted_elevation: true > elevation.enabled: true > elevation.auto_sort.enabled: true > elevation.auto_load_dted.enabled: true > // --- > // Geoid support (you can get by with just egm96 which is actually > the vertical datum of DTED) > // --- > > // GEOID 99: Set keyword to the directory containing the GEOID 99 > grids. > geoid_99_directory: /work/drb/image_formats/elevation/geoid99 > > // GEOID EGM 96: Set keyword to the path to the egm96.grd > geoid_egm_96_grid: /work/drb/image_formats/elevation/geoid96/egm96.grd > > Hope this helps a little, > Dave > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: David B. <dav...@ti...> - 2005-07-22 19:26:54
|
Tyler, Tyler Mitchell wrote: >>> Tyler Mitchell wrote: Hi all, >>> Anyone have a kwl that shows the syntax for setting up terrain for >>> osgPlanet? >> > >> Look at "osgPlanet/examples/osgplanetviewer/archive_manager.kwl" > > > I've seen this already, but am a bit confused. These examples cover > local images and WMS images. But what about 3D/terrain data > speficially. I assumed there was a different "type" and that it would > take tif images. > > Tyler > The ossim core can auto load both dted and srtm for terrain. If you have a tif it will have to be converted to an srtm format using orthoigen (see ossim/etc/templates/orthoigen_srtm.kwl). You will need: - Goid grid: http://earth-info.nga.mil/GandG/wgs84/gravitymod/egm96/egm96.htm - Set environment variable "OSSIM_PREFS_FILE" point it to your preferences file. - An ossim preferences file. There is one in "ossim/etc/templates". Here is a cut from mine: - Elevation data (dted or srtm). For dted it must be in the standard directory tree. SRTMS can go in one directory. // Elevation stuff... // srtm_directory1: /work/drb/image_formats/elevation/srtm/1arc // srtm_directory1: /home/dburken/work/images/elevation/ned_srtm dted_directory2: /work/drb/image_formats/elevation/ned dted_directory1: /work/drb/image_formats/elevation/1arc // default_elevation_path: /home/dburken/work/images/elevation/ned_srtm default_elevation_path: /work/drb/image_formats/elevation/1arc autoload_dted_elevation: true elevation.enabled: true elevation.auto_sort.enabled: true elevation.auto_load_dted.enabled: true // --- // Geoid support (you can get by with just egm96 which is actually the vertical datum of DTED) // --- // GEOID 99: Set keyword to the directory containing the GEOID 99 grids. geoid_99_directory: /work/drb/image_formats/elevation/geoid99 // GEOID EGM 96: Set keyword to the path to the egm96.grd geoid_egm_96_grid: /work/drb/image_formats/elevation/geoid96/egm96.grd Hope this helps a little, Dave |
From: Mark L. <mlu...@ma...> - 2005-07-22 19:12:37
|
Tyler, Good to hear from you again. I think you are asking how to load elevation surfaces into osgPlanet so that the textures (local or remote) are draped over the elevation surface in 3D. osgPlanet and osgplanetviewer are built on top of OSSIM and OpenSceneGraph. We use OSSIM's understanding of elevation surfaces. OSSIM understands elevation surfaces in DTED and SRTM format. You can have a structured tree of SRTM or DTED files and OSSIM will figure out how to navigate it and what parts to use given what you are looking at. We have utilities that will translate many other elevation formats into these file formats and structures. The elevation surface you use is specified in your ossim_preferences file. Additionally, we use the 96 Geoid which also needs to be available. All of this demonstrates that we don't have documentation in place to show someone how to set it all up. I'll try and write some instructions up for the FAQ and we also need to upload the geoid file to the download section. (it would seem good authors are hard to find :-) ) Anyway, once this is all in place you can enable elevation and specify an elevation exaggeration factor in your parameter list when calling up osgplanetviewer (that part is documented) osgplanetviewer is currently a technical demonstration of the osgPlanet library. We need a fancy gooey app that makes it easy to use and configure. Over lunch we were talking about what it would take to run it through Eclipse and combine it with uDig.. I'll post again when I get something in place on the FAQ. Mark On Jul 22, 2005, at 2:24 PM, Tyler Mitchell wrote: >>> Tyler Mitchell wrote: Hi all, >>> Anyone have a kwl that shows the syntax for setting up terrain >>> for osgPlanet? >>> > > >> Look at "osgPlanet/examples/osgplanetviewer/archive_manager.kwl" >> > > I've seen this already, but am a bit confused. These examples > cover local images and WMS images. But what about 3D/terrain data > speficially. I assumed there was a different "type" and that it > would take tif images. > > Tyler > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: Tyler M. <tj...@ti...> - 2005-07-22 18:24:27
|
>> Tyler Mitchell wrote: Hi all, >> Anyone have a kwl that shows the syntax for setting up terrain for >> osgPlanet? > Look at "osgPlanet/examples/osgplanetviewer/archive_manager.kwl" I've seen this already, but am a bit confused. These examples cover local images and WMS images. But what about 3D/terrain data speficially. I assumed there was a different "type" and that it would take tif images. Tyler |
From: David B. <dav...@ti...> - 2005-07-22 18:14:48
|
Tyler, > > Tyler Mitchell wrote: Hi all, > Anyone have a kwl that shows the syntax for setting up terrain for > osgPlanet? > > Tyler > Look at "osgPlanet/examples/osgplanetviewer/archive_manager.kwl" If you don't have the code see: http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/examples/osgplanetviewer/archive_manager.kwl?rev=1.6;content-type=text%2Fplain Or easier yet: // Note: If you are specifying opacity values then the // bottom layer is not applied since it is just initially copied into the destination // All layers after that are blended based on the apacity. The default opacity is 255 // which indicates completely opaque and anything less than that defines how // translucent the layer is. // // Note: You must name each layer archive0 upto archive<n-1> . // So currently if you delete a layer you must manually re-number // each keyword in the list. // // We support local and remote files. Currently for remote we only support // wms and you must give the full string for STYLES and layers you want and // make sure you end it with an &. // //archive0.type: local //archive0.file0: /data/earth/land_shallow_topo_east_tiled.tif //archive0.file1: /data/earth/land_shallow_topo_west_tiled.tif //archive0.transparent_color_flag:0 //archive0.transparent_color: 0 0 0 //archive0.opacity: 255 archive0.type: wms archive0.server: http://neptune.flids.com/cgi-bin/ngos.cgi?LAYERS=Earth_Image,ngos archive0.cache_dir: c:/data/wms/ngos/all //archive0.server: http://wmt.jpl.nasa.gov/cgi-bin/wmt.cgi?STYLES=visual&LAYERS=global_mosaic&sharp=0.0& //archive0.cache_dir: c:/data/wms/nasa //archive0.opacity: 255 Dave |
From: Tyler M. <tj...@ti...> - 2005-07-22 17:45:35
|
Hi all, Anyone have a kwl that shows the syntax for setting up terrain for osgPlanet? Tyler |
From: James E. H. <JAM...@sa...> - 2005-07-22 17:33:27
|
Hi Garrett, No i am afraid not. Its really nice to have this as a framework! now i can keep old versions around by adding them to the application bundle of my apps. this way i don't have to retest everything when i update ossim. best jim On Jul 22, 2005, at 1:24 PM, Garrett Potts wrote: > Hello James: > > Would like to but that Make system is generated from qmake from > the .pro files. I would need to figure a way to add scripting into > the .pro files. I have not taken the time to see about custom > scripting capabilities into the .pro files. If it's doable then > this should not be a problem. > > Have you ever tried custom scripting inside a .pro file? > > Take care > > Garrett > > On Jul 22, 2005, at 1:05 PM, James E. Hopper wrote: > > >> Garrett, >> >> you new make file that creates ossim library as a framework is >> very nice. any intent to do the same for ossim_qt library? >> >> >> jim >> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration >> Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> www.ossim.org >> Ossim-developer mailing list >> Oss...@li... >> https://lists.sourceforge.net/lists/listinfo/ossim-developer >> >> > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: Garrett P. <po...@cf...> - 2005-07-22 17:24:53
|
Hello James: Would like to but that Make system is generated from qmake from the .pro files. I would need to figure a way to add scripting into the .pro files. I have not taken the time to see about custom scripting capabilities into the .pro files. If it's doable then this should not be a problem. Have you ever tried custom scripting inside a .pro file? Take care Garrett On Jul 22, 2005, at 1:05 PM, James E. Hopper wrote: > Garrett, > > you new make file that creates ossim library as a framework is very > nice. any intent to do the same for ossim_qt library? > > > jim > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |
From: James E. H. <JAM...@sa...> - 2005-07-22 17:06:58
|
Garrett, you new make file that creates ossim library as a framework is very nice. any intent to do the same for ossim_qt library? jim |
From: Garrett P. <po...@cf...> - 2005-07-21 11:14:26
|
Hello: > Hi, > > just been looking at the screenshots for ogsPlanet, how can I > create elevation in osgPlanet (so to render SRTM from NASA WMS say), > and then sit on top of the dem in a walkaround mode as the screen > shots suggest? Are you familiar with OSSIM? We use the OSSIM infrastructure for the elevation post queries. So setting up elevation for osgPlanet is actually setting up for OSSIM. Basically you have a preference file and the OSSIM_PREFS_FILE environment variable points to it. In the preference file you can list elevation directories. For srtm it is srtm_directory0: <directory to srtm elev data> srtm_directory1: : : > > The urban models are fantastic, is there any documentation on this, > in particular how to put a geotiff into osgPlanet (via a WMS), and > then > place the model, is the urban model pulled from a WFS? We don't have a good Urban layer. I put a flight file in but that was for testing. When I get back to the osgPlanet coding again I plan on adding some additional layering capabilities. Currently we have a land layer that handles textures and elevation and a hud layer for fly through display of coordinates. > > I have some files from the CityGML project (http:// > www.citygml.org/) which seems to be related to the OGC W3DS > proposed standard, would > it be possible to convert these into osgPlanet city model format? > Also what is the city model format? I used a quick flight file. But like I said we need to still add layering support for more generic fly throughs and also our own model loaders that use osg loaders but then transform and massage the input to what ever coordinate system we are currently rendering to. DOCUMENTATION LINKS: 1. This is a link on how to create osgplanet keywordlists for the test application osgplanetviwer. http://www.ossim.org/tiki-read_article.php?articleId=8 2. For OSSIM there is an annotated ossim_preference file found in the src distribution (best from CVS) under the directory ossim/etc/ templates. > > Apologies for the newbie questions, the screenshots are amazing! Hey, cool! |
From: Norman B. <nb...@rs...> - 2005-07-21 09:38:15
|
Hi, =20 just been looking at the screenshots for ogsPlanet, how can I create = elevation in osgPlanet (so to render SRTM from NASA WMS say), and then sit on top of the dem in a walkaround mode as the screen shots = suggest? =20 The urban models are fantastic, is there any documentation on this, in = particular how to put a geotiff into osgPlanet (via a WMS), and then place the model, is the urban model pulled from a WFS? =20 I have some files from the CityGML project ( http://www.citygml.org/) = which seems to be related to the OGC W3DS proposed standard, would it be possible to convert these into osgPlanet city model format? Also = what is the city model format? =20 Apologies for the newbie questions, the screenshots are amazing! =20 Many thanks, =20 Norman =20 |
From: Mark L. <mlu...@ma...> - 2005-07-16 12:38:19
|
Thought this was interesting and decided to cross post it. Begin forwarded message: > From: Jody Garnett <jga...@re...> > Date: July 15, 2005 7:24:55 PM EDT > To: Geotools-devel <geo...@li...>, User- > friendly Desktop Internet GIS <udi...@li...>, > geoserver-devel <geo...@li...>, Joshua > Lieberman <jo...@ok...> > Subject: [udig-devel] Mad Metadata plan > Reply-To: User-friendly Desktop Internet GIS <udig- > de...@li...> > > > Well as promised I have finally been able to write up my mad > metadata plan inspired by the OSG'05 conference ... > > http://weblogs.java.net/blog/jive/archive/2005/07/mad_metadata_pl.html > > I would love to work on this if anyone has spare budget :-) Or if > there is interest enough for volunteers I can set it up see what > happens ... > > Jody > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > |
From: Mark L. <mlu...@ma...> - 2005-07-14 17:32:12
|
Thought this would be of interest to OSX Xcode programmers. mrl > I've recently upgraded to Xcode 2.1 on tiger, and I'm having issues > with cvs/subversions. I have been a long-time user of cvs, and > checking out Xcode projects has never before been a problem, but > now whenever I checkout one of my Xcode projects over ssh the > project.xcodeproj "bundle" checks out as a regular directory. The > result is that I cannot open the project anymore. After doing a > cvs co <project> I fire up Xcode and do a File->Open... and browse > to the project.xcodeproj "file" (appears in Finder as a directory) > and get nothing when I click Open. > > I attempted the same process with a subversion repository I have > access to, only to get the same result. Doing a local checkout > from the machine with the repository on the local filesystem does > not have this issue, only when I do a checkout over cvs/subversions > to my powerbook. > Previous versions of cvs client on Mac OS X used the deprecated "cvswrapper" feature to handle bundled files (project files, nibs, etc.) In Mac OS X 10.4 we updated cvs to the most current version, which unfortunately dropped wrapper support. The old version of cvs is still avaliable as /usr/bin/ocvs; we recommend you set your SCM system to that version, and be sure to copy the "cvswrappers" file from /Developer/Tools to your home directory in "~/.cvswrappers". Subversion has never supported wrapped files, so it is behaving correctly. |
From: <vi...@ec...> - 2005-07-14 13:39:10
|
Hi all, I'm experimenting a bit with ossim, I might want to implement one of our (=SarVision, www.sarvision.nl) monitoring chains (partially) in it. However, I'm more a man of the text editor than of the visual drag'n'drop thing (read: vce), though the vce and chain editor in imagelinker are very handy to get started with. Then I decided I wanted to try to make my (now still very simple) spec files a bit more readable by changing the id (and thus also input/output connection) numbers to names, and the prefixes too. E.g. I want to have a object1.object1 called inputChain1.opener instead, and I want to have this as id inputOpener_1, and the next object would have as inputconnection inputOpener_1 instead of some random 5-digit number. This would make reading and editing spec files lots and lots easier. Changing the object id's works for some objects, but not for all, for example the bandSelector converts all it's keyword values to <int>, and segfaults when it encounters something else. Changing the object prefixes simply does not work. So my questions: - what do you think about this idea of mine, to be able to have more expanatory names for object id's and prefixes? - is this supposed to work, actually, or not (yet)? - will it work sometime in the (near) future? - if this is a good idea, it might be also a good idea to have objects that generate a prefix use a more logical name then just 'objectx'. btw I read somewhere that the spec file will be xml sometime. True? I'll be on holidays the next weeks, so don't expect any more discussion from this side shortly about this. Also I would be willing to try and make some patches after that (if I have time, currently it is more of a hobby/trial thing, low priority), but my c++ skills are not too good. I could learn, though :) Regards, Vincent. |
From: Garrett P. <po...@cf...> - 2005-07-14 10:59:19
|
Hello Ben: They should do a single library build. A dll would probably be the best bet. The command line makefile.vc produces a single ossim.dll file. Try making the the result be a single .dll and then link osgPlanet to that dll. Thank you for the help. You can send the new project files to me and I will add them. Take care Garrett On Jul 13, 2005, at 8:07 PM, Ben Discoe wrote: > I built OSSIM today using the MSVC project file, from CVS. This > resulted in > the following libraries: > Debug: ossim_id.lib, ossimd.dll > Release: ossim_i.lib, ossim.dll > > Next, i tried to build osgPlanet, also using the project file, also > from > CVS. It compiled, but at link time it can't find the OSSIM > libraries. It > is looking for: > "ossim.lib ossim_elevation.lib ossim_font.lib ossim_init.lib > ossim_matrix.lib ossim_plugin.lib ossim_polyclip.lib ossim_vec.lib > ossim_visual_sim.lib ossim_vpf.lib" > > It looks like osgPlanet expects OSSIM to be built as a static lib, > or more > precisely a large number of static libs. Is this the case? Anyone > know why > this doesn't match how OSSIM is configured to build? What does the > OSSIM > command-line method produce, the "makefile.vc": > 1. a DLL > 2. a static lib > 3. a whole bunch of static libs? > > Should i change and submit osgPlanet.vcproj to link with OSSIM's > project? > > Thanks, > Ben > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event > hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > www.ossim.org > Ossim-developer mailing list > Oss...@li... > https://lists.sourceforge.net/lists/listinfo/ossim-developer > |