OpenSceneGraph Forum Forum Index OpenSceneGraph Forum
Official forum which mirrors the existent OSG mailing lists. Messages posted here are forwarded to the mailing list and vice versa.
 
   FAQFAQ    SearchSearch    MemberlistMemberlist    RulesRules    UsergroupsUsergroups    RegisterRegister 
 Mail2Forum SettingsMail2Forum Settings  ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
   AlbumAlbum  OpenSceneGraph IRC ChatOpenSceneGraph IRC Chat   SmartFeedSmartFeed 

VPB bug or faulty data?


 
Post new topic   Reply to topic    OpenSceneGraph Forum Forum Index -> General
View previous topic :: View next topic  
Author Message
Alejandro Aguilar Sierra
Guest





PostPosted: Sun Oct 26, 2008 5:53 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it apparently works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.


------------------
Post generated by Mail2Forum
Back to top
Ralf Stokholm
Guest





PostPosted: Sun Oct 26, 2008 8:05 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Alejandro

It seams you are missing projection information in the createt geotiff file.

VPB needs some sort of projection system information in the input or you should specify the projection in the commandline for VPB

It will be faster if you project your source data using ie gdalwarp, adal translate can also encode the projection data if its missing and you know what it should be.

Brgs.

Ralf Stokholm


2008/10/26 Alejandro Aguilar Sierra < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:
Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it apparently works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.
_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


------------------
Post generated by Mail2Forum
Back to top
Alejandro Aguilar Sierra
Guest





PostPosted: Mon Oct 27, 2008 1:32 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hi,

Actually the data has no projections, it is in plain
longitude/latitude coordinates. Which is the recomended projection for
data about 1 or two degrees long so I can have it in kilometers?

Regards,

-- A.

On Sun, Oct 26, 2008 at 2:04 AM, Ralf Stokholm <> wrote:
Quote:
Hi Alejandro

It seams you are missing projection information in the createt geotiff file.

VPB needs some sort of projection system information in the input or you
should specify the projection in the commandline for VPB

It will be faster if you project your source data using ie gdalwarp, adal
translate can also encode the projection data if its missing and you know
what it should be.

Brgs.

Ralf Stokholm

2008/10/26 Alejandro Aguilar Sierra <>
Quote:

Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it apparently
works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.








------------------
Post generated by Mail2Forum
Back to top
Ralf Stokholm
Guest





PostPosted: Mon Oct 27, 2008 7:06 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Alejandro
Im not 100% here, but I think you still need to specify some sort of projection basis, even plain lat lon uses some defenition of the geoid like WGS84 og similar.

Natrally it could be a problem with you GTiff file.

What version of VPB OSG are you using?

Brgs.

Ralf

2008/10/27 Alejandro Aguilar Sierra < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:
Hi,

Actually the data has no projections, it is in plain
longitude/latitude coordinates. Which is the recomended projection for
data about 1 or two degrees long so I can have it in kilometers?

Regards,

-- A.


On Sun, Oct 26, 2008 at 2:04 AM, Ralf Stokholm < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)> wrote:
Quote:
Hi Alejandro

It seams you are missing projection information in the createt geotiff file.

VPB needs some sort of projection system information in the input or you
should specify the projection in the commandline for VPB

It will be faster if you project your source data using ie gdalwarp, adal
translate can also encode the projection data if its missing and you know
what it should be.

Brgs.

Ralf Stokholm

2008/10/26 Alejandro Aguilar Sierra < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:

Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it apparently
works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.
_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org




------------------
Post generated by Mail2Forum
Back to top
?mit Uzun
Guest





PostPosted: Mon Oct 27, 2008 7:36 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Alejandro,

VPB is only understand well referenced WGS84 formatted data. So I advice you to use referenced images to create your terrain, if you are not familiar with reference data manipulation on images you should download prepared referenced data from http://seamless.usgs.gov/index.php or http://geoengine.nga.mil/geospatial/SW_TOOLS/NIMAMUSE/webinter/rast_roam.html You can find lots of web site to download these kind of data.

Best Regards.

Umit Uzun

2008/10/27 Ralf Stokholm < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:
Hi Alejandro
Im not 100% here, but I think you still need to specify some sort of projection basis, even plain lat lon uses some defenition of the geoid like WGS84 og similar.

Natrally it could be a problem with you GTiff file.

What version of VPB OSG are you using?

Brgs.

Ralf

2008/10/27 Alejandro Aguilar Sierra < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:
Hi,

Actually the data has no projections, it is in plain
longitude/latitude coordinates. Which is the recomended projection for
data about 1 or two degrees long so I can have it in kilometers?

Regards,

-- A.


On Sun, Oct 26, 2008 at 2:04 AM, Ralf Stokholm < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)> wrote:
Quote:
Hi Alejandro

It seams you are missing projection information in the createt geotiff file.

VPB needs some sort of projection system information in the input or you
should specify the projection in the commandline for VPB

It will be faster if you project your source data using ie gdalwarp, adal
translate can also encode the projection data if its missing and you know
what it should be.

Brgs.

Ralf Stokholm

2008/10/26 Alejandro Aguilar Sierra < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:

Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it apparently
works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.
_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org





_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



------------------
Post generated by Mail2Forum
Back to top
Robert Osfield
Guest





PostPosted: Mon Oct 27, 2008 9:13 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Umit,

On Mon, Oct 27, 2008 at 7:36 AM, ?mit Uzun <> wrote:
Quote:
VPB is only understand well referenced WGS84 formatted data.

This is not correct, VPB can handle a wide range of projections,
including no projections if your manually provide the projections.
However, I would very strongly recommend that you provide data with
proper projections for them, it makes the whole build process far far
easier and reliable.

Robert.


------------------
Post generated by Mail2Forum
Back to top
?mit Uzun
Guest





PostPosted: Mon Oct 27, 2008 9:26 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Robert,

Thanks for clarification. But I remember that, VPB can manipulate only WGS84 referenced data. But it may be valid for only BlueMarble viewer. Sorry for wrong comment Smile

Best Regards.

Umit Uzun

2008/10/27 Robert Osfield < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:
Hi Umit,

On Mon, Oct 27, 2008 at 7:36 AM, ?mit Uzun < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)> wrote:
Quote:
VPB is only understand well referenced WGS84 formatted data.

This is not correct, VPB can handle a wide range of projections,
including no projections if your manually provide the projections.
However, I would very strongly recommend that you provide data with
proper projections for them, it makes the whole build process far far
easier and reliable.

Robert.
_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


------------------
Post generated by Mail2Forum
Back to top
Robert Osfield
Guest





PostPosted: Mon Oct 27, 2008 9:40 am    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Umit,

On Mon, Oct 27, 2008 at 9:25 AM, ?mit Uzun <> wrote:
Quote:
Thanks for clarification. But I remember that, VPB can manipulate only WGS84
referenced data. But it may be valid for only BlueMarble viewer. Sorry for
wrong comment Smile

When building geocentric databases VPB reprojects the data into WGS84
and then builds the data, if you are using vpbmaster then you'll need
to do this reprojection as a prior step to calling vpbmaster. The
vpbcache utility can do this reprojection for you. If you are just
using osgdem standalone then it can do the reprojection for you.

The key is that your source data should have at least a projection
that GDAL recognizes otherwise you end up having to build your own
projection. GDAL has tools to allow you to do this.

Robert.


------------------
Post generated by Mail2Forum
Back to top
Alejandro Aguilar Sierra
Guest





PostPosted: Mon Oct 27, 2008 4:32 pm    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Ralph,

I am using the last versions from svn. Perhaps this warning from
gdalinfo gives a hint on what is wrong with this data?

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength

because otherwise it recognizes that there is no projection but has
all georeferencing information needed.

Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)

I built it with gdal_translate directly from the BIL file
gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif

The header of the BIL file says:

NROWS 3600
NCOLS 7200
NBANDS 1
NBITS 16
BYTEORDER I
LAYOUT BIL
SKIPBYTES 0
NODATA 0.000000
BYTEORDER I
XDIM 0.000277777777777778
YDIM 0.000277777777777778
ULXMAP -98.99986111111112
ULYMAP 19.999861111111112

Apparently it misses vertical information, but that is not the problem
right now.

Regards,

-- A.


On Mon, Oct 27, 2008 at 1:06 AM, Ralf Stokholm <> wrote:
Quote:
Hi Alejandro
Im not 100% here, but I think you still need to specify some sort of
projection basis, even plain lat lon uses some defenition of the geoid like
WGS84 og similar.

Natrally it could be a problem with you GTiff file.

What version of VPB OSG are you using?

Brgs.

Ralf

2008/10/27 Alejandro Aguilar Sierra <>
Quote:

Hi,

Actually the data has no projections, it is in plain
longitude/latitude coordinates. Which is the recomended projection for
data about 1 or two degrees long so I can have it in kilometers?

Regards,

-- A.

On Sun, Oct 26, 2008 at 2:04 AM, Ralf Stokholm <>
wrote:
Quote:
Hi Alejandro

It seams you are missing projection information in the createt geotiff
file.

VPB needs some sort of projection system information in the input or you
should specify the projection in the commandline for VPB

It will be faster if you project your source data using ie gdalwarp,
adal
translate can also encode the projection data if its missing and you
know
what it should be.

Brgs.

Ralf Stokholm

2008/10/26 Alejandro Aguilar Sierra <>
Quote:

Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it
apparently
works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.














------------------
Post generated by Mail2Forum
Back to top
Robert Osfield
Guest





PostPosted: Mon Oct 27, 2008 4:39 pm    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Alejandro,

There is no coordinate systeml information for VPB to go on, and empty
string for the coordinate system is not sufficient for determining the
coordinate system, the origin and pixel size info aren't sufficient
on their own.

Robert.

On Mon, Oct 27, 2008 at 4:32 PM, Alejandro Aguilar Sierra
<> wrote:
Quote:
Hi Ralph,

I am using the last versions from svn. Perhaps this warning from
gdalinfo gives a hint on what is wrong with this data?

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength

because otherwise it recognizes that there is no projection but has
all georeferencing information needed.

Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)

I built it with gdal_translate directly from the BIL file
gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif

The header of the BIL file says:

NROWS 3600
NCOLS 7200
NBANDS 1
NBITS 16
BYTEORDER I
LAYOUT BIL
SKIPBYTES 0
NODATA 0.000000
BYTEORDER I
XDIM 0.000277777777777778
YDIM 0.000277777777777778
ULXMAP -98.99986111111112
ULYMAP 19.999861111111112

Apparently it misses vertical information, but that is not the problem
right now.

Regards,

-- A.


On Mon, Oct 27, 2008 at 1:06 AM, Ralf Stokholm <> wrote:
Quote:
Hi Alejandro
Im not 100% here, but I think you still need to specify some sort of
projection basis, even plain lat lon uses some defenition of the geoid like
WGS84 og similar.

Natrally it could be a problem with you GTiff file.

What version of VPB OSG are you using?

Brgs.

Ralf

2008/10/27 Alejandro Aguilar Sierra <>
Quote:

Hi,

Actually the data has no projections, it is in plain
longitude/latitude coordinates. Which is the recomended projection for
data about 1 or two degrees long so I can have it in kilometers?

Regards,

-- A.

On Sun, Oct 26, 2008 at 2:04 AM, Ralf Stokholm <>
wrote:
Quote:
Hi Alejandro

It seams you are missing projection information in the createt geotiff
file.

VPB needs some sort of projection system information in the input or you
should specify the projection in the commandline for VPB

It will be faster if you project your source data using ie gdalwarp,
adal
translate can also encode the projection data if its missing and you
know
what it should be.

Brgs.

Ralf Stokholm

2008/10/26 Alejandro Aguilar Sierra <>
Quote:

Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it
apparently
works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.
















------------------
Post generated by Mail2Forum
Back to top
Alejandro Aguilar Sierra
Guest





PostPosted: Mon Oct 27, 2008 4:43 pm    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Robert and Umit,

As probably you already read it, my data is georeferenced but has no
projection info (plain latitude, l,ongitude). Using plain osgdem
produces a wrong 1 dimension field (a line).

osgdem -d volcanes.tif -l 8 -v 1.0 -o kk

I have to give some approximated --xx and --yy data to make it work
and even so it does wrongly, creating the mirror image in the Y
direction, as you can see comparing the texture image with the
produced terrain.
Any hint?

Where can I find documentation about vpbmaster, vpbcache and vpbsize?

Regards,

-- A.

On Mon, Oct 27, 2008 at 3:40 AM, Robert Osfield
<> wrote:
Quote:
Hi Umit,

On Mon, Oct 27, 2008 at 9:25 AM, ?mit Uzun <> wrote:
Quote:
Thanks for clarification. But I remember that, VPB can manipulate only WGS84
referenced data. But it may be valid for only BlueMarble viewer. Sorry for
wrong comment Smile

When building geocentric databases VPB reprojects the data into WGS84
and then builds the data, if you are using vpbmaster then you'll need
to do this reprojection as a prior step to calling vpbmaster. The
vpbcache utility can do this reprojection for you. If you are just
using osgdem standalone then it can do the reprojection for you.

The key is that your source data should have at least a projection
that GDAL recognizes otherwise you end up having to build your own
projection. GDAL has tools to allow you to do this.

Robert.





------------------
Post generated by Mail2Forum
Back to top
Alejandro Aguilar Sierra
Guest





PostPosted: Mon Oct 27, 2008 4:48 pm    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Robert:

Yes but they are perfectly georeferenced. What shoud I do?
--geocentric is enough?

-- A.

On Mon, Oct 27, 2008 at 10:38 AM, Robert Osfield
<> wrote:
Quote:
Hi Alejandro,

There is no coordinate systeml information for VPB to go on, and empty
string for the coordinate system is not sufficient for determining the
coordinate system, the origin and pixel size info aren't sufficient
on their own.

Robert.

On Mon, Oct 27, 2008 at 4:32 PM, Alejandro Aguilar Sierra
<> wrote:
Quote:
Hi Ralph,

I am using the last versions from svn. Perhaps this warning from
gdalinfo gives a hint on what is wrong with this data?

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength

because otherwise it recognizes that there is no projection but has
all georeferencing information needed.

Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)

I built it with gdal_translate directly from the BIL file
gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif

The header of the BIL file says:

NROWS 3600
NCOLS 7200
NBANDS 1
NBITS 16
BYTEORDER I
LAYOUT BIL
SKIPBYTES 0
NODATA 0.000000
BYTEORDER I
XDIM 0.000277777777777778
YDIM 0.000277777777777778
ULXMAP -98.99986111111112
ULYMAP 19.999861111111112

Apparently it misses vertical information, but that is not the problem
right now.

Regards,

-- A.


On Mon, Oct 27, 2008 at 1:06 AM, Ralf Stokholm <> wrote:
Quote:
Hi Alejandro
Im not 100% here, but I think you still need to specify some sort of
projection basis, even plain lat lon uses some defenition of the geoid like
WGS84 og similar.

Natrally it could be a problem with you GTiff file.

What version of VPB OSG are you using?

Brgs.

Ralf

2008/10/27 Alejandro Aguilar Sierra <>
Quote:

Hi,

Actually the data has no projections, it is in plain
longitude/latitude coordinates. Which is the recomended projection for
data about 1 or two degrees long so I can have it in kilometers?

Regards,

-- A.

On Sun, Oct 26, 2008 at 2:04 AM, Ralf Stokholm <>
wrote:
Quote:
Hi Alejandro

It seams you are missing projection information in the createt geotiff
file.

VPB needs some sort of projection system information in the input or you
should specify the projection in the commandline for VPB

It will be faster if you project your source data using ie gdalwarp,
adal
translate can also encode the projection data if its missing and you
know
what it should be.

Brgs.

Ralf Stokholm

2008/10/26 Alejandro Aguilar Sierra <>
Quote:

Hello:

I got DEM data from INEGI (Mexican Geographic Institute) and convert
it to Geo Tiff.

gdal_translate -of GTiff -co "TILED=YES"
MDE-n200000s190000e0970000o0990000.bil volcanes.tif
gdaladdo -r average volcanes.tif 2 4 8 16 32

gdalinfo volcanes.tif
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength
Driver: GTiff/GeoTIFF
Files: volcanes.tif
Size is 7200, 3600
Coordinate System is `'
Origin = (-99.000000000000000,20.000000000000000)
Pixel Size = (0.000277777777778,-0.000277777777778)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -99.0000000, 20.0000000)
Lower Left ( -99.0000000, 19.0000000)
Upper Right ( -97.0000000, 20.0000000)
Lower Right ( -97.0000000, 19.0000000)
Center ( -98.0000000, 19.5000000)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
NoData Value=0
Overviews: 3600x1800, 1800x900, 900x450, 450x225, 225x113
Warning 1: TIFFReadDirectory:volcanes.tif: Wrong "StripByteCounts"
field, ignoring and calculating from imagelength


If I try to create the terrain database this way I get only a line
osgdem -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

so I have to give approximate pixel size with xx and yy and it
apparently
works.
osgdem --xx 33 --yy 33 -d volcanes.tif -l 8 -v 1.0 -o volcanes.ive

Is there not enough information in the geotiff file? or this is a bug?

Regards,

-- A.


















------------------
Post generated by Mail2Forum
Back to top
Robert Osfield
Guest





PostPosted: Mon Oct 27, 2008 4:54 pm    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Alejandro,

Your data *is* the problem, please add the coordinate system info.
Using the --xx etc options really is not a good solution going
forward. Use properly set up data and things will work fine. Please
go check out the gdal website for info on how to set up your data.

As for VPB docs, I haven't had a chance to write full docs for all the
utilities yet. There are some notes online.

Robert.

On Mon, Oct 27, 2008 at 4:43 PM, Alejandro Aguilar Sierra
<> wrote:
Quote:
Hi Robert and Umit,

As probably you already read it, my data is georeferenced but has no
projection info (plain latitude, l,ongitude). Using plain osgdem
produces a wrong 1 dimension field (a line).

osgdem -d volcanes.tif -l 8 -v 1.0 -o kk

I have to give some approximated --xx and --yy data to make it work
and even so it does wrongly, creating the mirror image in the Y
direction, as you can see comparing the texture image with the
produced terrain.
Any hint?

Where can I find documentation about vpbmaster, vpbcache and vpbsize?

Regards,

-- A.

On Mon, Oct 27, 2008 at 3:40 AM, Robert Osfield
<> wrote:
Quote:
Hi Umit,

On Mon, Oct 27, 2008 at 9:25 AM, ?mit Uzun <> wrote:
Quote:
Thanks for clarification. But I remember that, VPB can manipulate only WGS84
referenced data. But it may be valid for only BlueMarble viewer. Sorry for
wrong comment Smile

When building geocentric databases VPB reprojects the data into WGS84
and then builds the data, if you are using vpbmaster then you'll need
to do this reprojection as a prior step to calling vpbmaster. The
vpbcache utility can do this reprojection for you. If you are just
using osgdem standalone then it can do the reprojection for you.

The key is that your source data should have at least a projection
that GDAL recognizes otherwise you end up having to build your own
projection. GDAL has tools to allow you to do this.

Robert.








------------------
Post generated by Mail2Forum
Back to top
Ralf Stokholm
Guest





PostPosted: Mon Oct 27, 2008 7:58 pm    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Alejandro

You can use gdalwarp to (stamp) the projection information into you data.

try using something similar to the following:

//call gdalwarp to project my data to wgs84
//This will create a virtual raster (vrt) which does not copy the data of the original raster
//but creates a sort of filter for reading the data.
gdal_translate -of vrt -a_srs EPSG:4326 volcanes.tif volcanes.vrt

//Then use the vrt as input
osgdem -d volcanes.vrt -l 8 -v 1.0 -o kk


EPSG:4326 is short form defenition of a basic lat lon coordinate system, same format you will receive ie landsat data in.

Hope this helps.

Brgs.

Ralf Stokholm

2008/10/27 Robert Osfield < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)>
Quote:
Hi Alejandro,

Your data *is* the problem, please add the coordinate system info.
Using the --xx etc options really is not a good solution going
forward. Use properly set up data and things will work fine. Please
go check out the gdal website for info on how to set up your data.

As for VPB docs, I haven't had a chance to write full docs for all the
utilities yet. There are some notes online.

Robert.


On Mon, Oct 27, 2008 at 4:43 PM, Alejandro Aguilar Sierra
< (
Only registered users can see emails on this board!
Get registred or enter the forums!
)> wrote:
Quote:
Hi Robert and Umit,

As probably you already read it, my data is georeferenced but has no
projection info (plain latitude, l,ongitude). Using plain osgdem
produces a wrong 1 dimension field (a line).

osgdem -d volcanes.tif -l 8 -v 1.0 -o kk

I have to give some approximated --xx and --yy data to make it work
and even so it does wrongly, creating the mirror image in the Y
direction, as you can see comparing the texture image with the
produced terrain.
Any hint?

Where can I find documentation about vpbmaster, vpbcache and vpbsize?

Regards,

-- A.

On Mon, Oct 27, 2008 at 3:40 AM, Robert Osfield
< (
Only registered users can see emails on this board!
Get registred or enter the forums!
)> wrote:
Quote:
Hi Umit,

On Mon, Oct 27, 2008 at 9:25 AM, ?mit Uzun < (
Only registered users can see emails on this board!
Get registred or enter the forums!
)> wrote:
Quote:
Thanks for clarification. But I remember that, VPB can manipulate only WGS84
referenced data. But it may be valid for only BlueMarble viewer. Sorry for
wrong comment Smile

When building geocentric databases VPB reprojects the data into WGS84
and then builds the data, if you are using vpbmaster then you'll need
to do this reprojection as a prior step to calling vpbmaster. The
vpbcache utility can do this reprojection for you. If you are just
using osgdem standalone then it can do the reprojection for you.

The key is that your source data should have at least a projection
that GDAL recognizes otherwise you end up having to build your own
projection. GDAL has tools to allow you to do this.

Robert.
_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
(
Only registered users can see emails on this board!
Get registred or enter the forums!
)
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org




------------------
Post generated by Mail2Forum
Back to top
Alejandro Aguilar Sierra
Guest





PostPosted: Mon Oct 27, 2008 8:51 pm    Post subject:
VPB bug or faulty data?
Reply with quote

Hi Ralph,

It works, thank you very much! Smile

-- A.


On Mon, Oct 27, 2008 at 1:57 PM, Ralf Stokholm <> wrote:
Quote:
Hi Alejandro

You can use gdalwarp to (stamp) the projection information into you data.

try using something similar to the following:

//call gdalwarp to project my data to wgs84
//This will create a virtual raster (vrt) which does not copy the data of
the original raster
//but creates a sort of filter for reading the data.
gdal_translate -of vrt -a_srs EPSG:4326 volcanes.tif volcanes.vrt

//Then use the vrt as input
osgdem -d volcanes.vrt -l 8 -v 1.0 -o kk


EPSG:4326 is short form defenition of a basic lat lon coordinate system,
same format you will receive ie landsat data in.

Hope this helps.

Brgs.

Ralf Stokholm

2008/10/27 Robert Osfield <>
Quote:

Hi Alejandro,

Your data *is* the problem, please add the coordinate system info.
Using the --xx etc options really is not a good solution going
forward. Use properly set up data and things will work fine. Please
go check out the gdal website for info on how to set up your data.

As for VPB docs, I haven't had a chance to write full docs for all the
utilities yet. There are some notes online.

Robert.

On Mon, Oct 27, 2008 at 4:43 PM, Alejandro Aguilar Sierra
<> wrote:
Quote:
Hi Robert and Umit,

As probably you already read it, my data is georeferenced but has no
projection info (plain latitude, l,ongitude). Using plain osgdem
produces a wrong 1 dimension field (a line).

osgdem -d volcanes.tif -l 8 -v 1.0 -o kk

I have to give some approximated --xx and --yy data to make it work
and even so it does wrongly, creating the mirror image in the Y
direction, as you can see comparing the texture image with the
produced terrain.
Any hint?

Where can I find documentation about vpbmaster, vpbcache and vpbsize?

Regards,

-- A.

On Mon, Oct 27, 2008 at 3:40 AM, Robert Osfield
<> wrote:
Quote:
Hi Umit,

On Mon, Oct 27, 2008 at 9:25 AM, ?mit Uzun <>
wrote:
Quote:
Thanks for clarification. But I remember that, VPB can manipulate only
WGS84
referenced data. But it may be valid for only BlueMarble viewer. Sorry
for
wrong comment Smile

When building geocentric databases VPB reprojects the data into WGS84
and then builds the data, if you are using vpbmaster then you'll need
to do this reprojection as a prior step to calling vpbmaster. The
vpbcache utility can do this reprojection for you. If you are just
using osgdem standalone then it can do the reprojection for you.

The key is that your source data should have at least a projection
that GDAL recognizes otherwise you end up having to build your own
projection. GDAL has tools to allow you to do this.

Robert.














------------------
Post generated by Mail2Forum
Back to top
Display posts from previous:   
Post new topic   Reply to topic    OpenSceneGraph Forum Forum Index -> General All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Similar Topics
Topic Author Forum Replies Posted
No new posts Custom data within nodes or drawables arennuit General 2 Thu Aug 24, 2017 9:52 am View latest post
No new posts How to replace the texture data in th... xdfanfan General 1 Wed Apr 05, 2017 12:44 pm View latest post
No new posts 答复: osg-users Digest, Vol 105, Is... 韩志平 General 1 Thu Feb 09, 2017 3:03 am View latest post
No new posts Changing another thread's node's Stat... CTW_Liu General 4 Mon Dec 05, 2016 7:49 am View latest post
No new posts source data samples for VPB Trajce Nikolov NICK General 4 Tue Nov 08, 2016 12:34 pm View latest post


Board Security Anti Bot Question MOD - phpBB MOD against Spam Bots
Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP