Matching Mollweide extent?Understanding the Map Tile creation propertiesVSIMalloc3() and UnifiedSrcDensity...
A Cautionary Suggestion
My adviser wants to be the first author
Define, (actually define) the "stability" and "energy" of a compound
How to explain that I do not want to visit a country due to personal safety concern?
(Calculus) Derivative Thinking Question
How to write cleanly even if my character uses expletive language?
How to deal with a cynical class?
How can you use ICE tables to solve multiple coupled equilibria?
How to make healing in an exploration game interesting
Gantt Chart like rectangles with log scale
Does Mathematica reuse previous computations?
Why does Bach not break the rules here?
Most cost effective thermostat setting: consistent temperature vs. lowest temperature possible
How Could an Airship Be Repaired Mid-Flight
Who is flying the vertibirds?
Time travel from stationary position?
What should tie a collection of short-stories together?
If I can solve Sudoku can I solve Travelling Salesman Problem(TSP)? If yes, how?
Happy pi day, everyone!
What are substitutions for coconut in curry?
What approach do we need to follow for projects without a test environment?
Why doesn't the EU now just force the UK to choose between referendum and no-deal?
Existence of subset with given Hausdorff dimension
Use of undefined constant bloginfo
Matching Mollweide extent?
Understanding the Map Tile creation propertiesVSIMalloc3() and UnifiedSrcDensity mask errors when running gdal_warp in OSGEO4w shellRasterize shapefile to a new gtiff file with gdal_rasterize utility,however,I cannot open the tif file?How can I fix badly specified geographic coordinate system with units in arc-seconds?how to georeference my png using gdalGetting origin as long, lat in GDAL without knowing EPSGCan gdalwarp reproject from ESPG:4326 (WGS84) to UTM?Import GDAL_TRANSLATE IMAGE GOES-13Clipping raster takes forever in QGIShow to reduce Geoserver WMTS rendering time?
I'm trying to match two rasters to same size, so i can do cell to cell analysis on them. The first cell That I'm trying to match is in Mollweide projection, with 250 m resolution. Here is the gdalinfo of the file:
Driver: GTiff/GeoTIFF
Files:
Size is 141969, 60829
Coordinate System is:
PROJCS["World_Mollweide",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137.0,298.257223563]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Mollweide"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
UNIT["Meter",1.0]]
Origin = (-17619594.547443531453609,8722279.461868489161134)
Pixel Size = (250.000000000000000,-250.000000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left (-17619594.547, 8722279.462)
Lower Left (-17619594.547,-6484970.538)
Upper Right (17872655.453, 8722279.462)
Lower Right (17872655.453,-6484970.538)
Center ( 126530.453, 1118654.462)
Band 1 Block=128x128 Type=Float32, ColorInterp=Gray
NoData Value=-3.4028234663852886e+38
The second file that I'm trying to match to the first file is in "" projection, with 100m resolution. Here is the gdalinfo of the second file:
Driver: GTiff/GeoTIFF
Size is 400302, 134668
Coordinate System is:
PROJCS["Custom_Goode",
GEOGCS["GCS_Sphere_GRS_1980_Authalic",
DATUM["D_Sphere_GRS_1980_Authalic",
SPHEROID["Sphere_GRS_1980_Authalic",6371007.0,0.0]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Goode_Homolosine"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
PARAMETER["Option",0.0],
UNIT["Kilometer",1000.0]]
Origin = (-20015.107512752761977,7429.758556314830457)
Pixel Size = (0.100000000000000,-0.100000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -20015.108, 7429.759)
Lower Left ( -20015.108, -6037.041)
Upper Right ( 20015.092, 7429.759)
Lower Right ( 20015.092, -6037.041)
Center ( -0.008, 696.359)
Band 1 Block=128x128 Type=Byte, ColorInterp=Gray
Min=0.000 Max=72.000
Minimum=0.000, Maximum=72.000, Mean=6.100, StdDev=2.983
NoData Value=-128
Overviews: 200151x67334, 100076x33667, 50038x16834, 25019x8417, 12510x4209, 6255x2105, 3128x1053, 1564x527, 782x264, 391x132
Metadata:
STATISTICS_MAXIMUM=72
STATISTICS_MEAN=6.100308069419
STATISTICS_MINIMUM=0
STATISTICS_SKIPFACTORX=1
STATISTICS_SKIPFACTORY=1
STATISTICS_STDDEV=2.9825236321
I'm trying to match the second file to the first file, but after warping, I get a file that has boundaries bigger than the actual world! The file has the other side of the world on each side (see below). For example ecos of Russia is seen on the left side of North America and ecos of North America is seen at the right side of Russia.
I think the problem is that the original file's extent is actually non-existance in it's own projection. But even after cutting the the first file's extra extent on the side's, I still have problem. It seems like the Mollweide projection is not well suited for the "-te" option. Also providing gdalwarp with a simple globale shapefile to cut it for extent, takes a billion years for some reasons.
Here is the thing, since each interpolation causes loss of data and the analysis seems to be sensitive to that, I would like to get the second file to match the first file's projection and resolution, with minimum steps and without changing the first file. Thats why "-tap" option is out of picture, as if I -tap the second file, I have to do it to the first file as well so that the cells are aligned.
Any ideas where the problem is and what I can do for it?
raster gdal extents gdalwarp
edited 4 mins ago
PolyGeo♦
53.7k1781244
asked 4 hours ago
Dr proctorDr proctor
143
add a comment |
I'm trying to match two rasters to same size, so i can do cell to cell analysis on them. The first cell That I'm trying to match is in Mollweide projection, with 250 m resolution. Here is the gdalinfo of the file:
Driver: GTiff/GeoTIFF
Files:
Size is 141969, 60829
Coordinate System is:
PROJCS["World_Mollweide",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137.0,298.257223563]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Mollweide"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
UNIT["Meter",1.0]]
Origin = (-17619594.547443531453609,8722279.461868489161134)
Pixel Size = (250.000000000000000,-250.000000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left (-17619594.547, 8722279.462)
Lower Left (-17619594.547,-6484970.538)
Upper Right (17872655.453, 8722279.462)
Lower Right (17872655.453,-6484970.538)
Center ( 126530.453, 1118654.462)
Band 1 Block=128x128 Type=Float32, ColorInterp=Gray
NoData Value=-3.4028234663852886e+38
The second file that I'm trying to match to the first file is in "" projection, with 100m resolution. Here is the gdalinfo of the second file:
Driver: GTiff/GeoTIFF
Size is 400302, 134668
Coordinate System is:
PROJCS["Custom_Goode",
GEOGCS["GCS_Sphere_GRS_1980_Authalic",
DATUM["D_Sphere_GRS_1980_Authalic",
SPHEROID["Sphere_GRS_1980_Authalic",6371007.0,0.0]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Goode_Homolosine"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
PARAMETER["Option",0.0],
UNIT["Kilometer",1000.0]]
Origin = (-20015.107512752761977,7429.758556314830457)
Pixel Size = (0.100000000000000,-0.100000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -20015.108, 7429.759)
Lower Left ( -20015.108, -6037.041)
Upper Right ( 20015.092, 7429.759)
Lower Right ( 20015.092, -6037.041)
Center ( -0.008, 696.359)
Band 1 Block=128x128 Type=Byte, ColorInterp=Gray
Min=0.000 Max=72.000
Minimum=0.000, Maximum=72.000, Mean=6.100, StdDev=2.983
NoData Value=-128
Overviews: 200151x67334, 100076x33667, 50038x16834, 25019x8417, 12510x4209, 6255x2105, 3128x1053, 1564x527, 782x264, 391x132
Metadata:
STATISTICS_MAXIMUM=72
STATISTICS_MEAN=6.100308069419
STATISTICS_MINIMUM=0
STATISTICS_SKIPFACTORX=1
STATISTICS_SKIPFACTORY=1
STATISTICS_STDDEV=2.9825236321
I'm trying to match the second file to the first file, but after warping, I get a file that has boundaries bigger than the actual world! The file has the other side of the world on each side (see below). For example ecos of Russia is seen on the left side of North America and ecos of North America is seen at the right side of Russia.
I think the problem is that the original file's extent is actually non-existance in it's own projection. But even after cutting the the first file's extra extent on the side's, I still have problem. It seems like the Mollweide projection is not well suited for the "-te" option. Also providing gdalwarp with a simple globale shapefile to cut it for extent, takes a billion years for some reasons.
Here is the thing, since each interpolation causes loss of data and the analysis seems to be sensitive to that, I would like to get the second file to match the first file's projection and resolution, with minimum steps and without changing the first file. Thats why "-tap" option is out of picture, as if I -tap the second file, I have to do it to the first file as well so that the cells are aligned.
Any ideas where the problem is and what I can do for it?
raster gdal extents gdalwarp
edited 4 mins ago
PolyGeo♦
53.7k1781244
asked 4 hours ago
Dr proctorDr proctor
143
add a comment |
I'm trying to match two rasters to same size, so i can do cell to cell analysis on them. The first cell That I'm trying to match is in Mollweide projection, with 250 m resolution. Here is the gdalinfo of the file:
Driver: GTiff/GeoTIFF
Files:
Size is 141969, 60829
Coordinate System is:
PROJCS["World_Mollweide",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137.0,298.257223563]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Mollweide"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
UNIT["Meter",1.0]]
Origin = (-17619594.547443531453609,8722279.461868489161134)
Pixel Size = (250.000000000000000,-250.000000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left (-17619594.547, 8722279.462)
Lower Left (-17619594.547,-6484970.538)
Upper Right (17872655.453, 8722279.462)
Lower Right (17872655.453,-6484970.538)
Center ( 126530.453, 1118654.462)
Band 1 Block=128x128 Type=Float32, ColorInterp=Gray
NoData Value=-3.4028234663852886e+38
The second file that I'm trying to match to the first file is in "" projection, with 100m resolution. Here is the gdalinfo of the second file:
Driver: GTiff/GeoTIFF
Size is 400302, 134668
Coordinate System is:
PROJCS["Custom_Goode",
GEOGCS["GCS_Sphere_GRS_1980_Authalic",
DATUM["D_Sphere_GRS_1980_Authalic",
SPHEROID["Sphere_GRS_1980_Authalic",6371007.0,0.0]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Goode_Homolosine"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
PARAMETER["Option",0.0],
UNIT["Kilometer",1000.0]]
Origin = (-20015.107512752761977,7429.758556314830457)
Pixel Size = (0.100000000000000,-0.100000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -20015.108, 7429.759)
Lower Left ( -20015.108, -6037.041)
Upper Right ( 20015.092, 7429.759)
Lower Right ( 20015.092, -6037.041)
Center ( -0.008, 696.359)
Band 1 Block=128x128 Type=Byte, ColorInterp=Gray
Min=0.000 Max=72.000
Minimum=0.000, Maximum=72.000, Mean=6.100, StdDev=2.983
NoData Value=-128
Overviews: 200151x67334, 100076x33667, 50038x16834, 25019x8417, 12510x4209, 6255x2105, 3128x1053, 1564x527, 782x264, 391x132
Metadata:
STATISTICS_MAXIMUM=72
STATISTICS_MEAN=6.100308069419
STATISTICS_MINIMUM=0
STATISTICS_SKIPFACTORX=1
STATISTICS_SKIPFACTORY=1
STATISTICS_STDDEV=2.9825236321
I'm trying to match the second file to the first file, but after warping, I get a file that has boundaries bigger than the actual world! The file has the other side of the world on each side (see below). For example ecos of Russia is seen on the left side of North America and ecos of North America is seen at the right side of Russia.
I think the problem is that the original file's extent is actually non-existance in it's own projection. But even after cutting the the first file's extra extent on the side's, I still have problem. It seems like the Mollweide projection is not well suited for the "-te" option. Also providing gdalwarp with a simple globale shapefile to cut it for extent, takes a billion years for some reasons.
Here is the thing, since each interpolation causes loss of data and the analysis seems to be sensitive to that, I would like to get the second file to match the first file's projection and resolution, with minimum steps and without changing the first file. Thats why "-tap" option is out of picture, as if I -tap the second file, I have to do it to the first file as well so that the cells are aligned.
Any ideas where the problem is and what I can do for it?
raster gdal extents gdalwarp
edited 4 mins ago
PolyGeo♦
53.7k1781244
asked 4 hours ago
Dr proctorDr proctor
143
I'm trying to match two rasters to same size, so i can do cell to cell analysis on them. The first cell That I'm trying to match is in Mollweide projection, with 250 m resolution. Here is the gdalinfo of the file:
Driver: GTiff/GeoTIFF
Files:
Size is 141969, 60829
Coordinate System is:
PROJCS["World_Mollweide",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137.0,298.257223563]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Mollweide"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
UNIT["Meter",1.0]]
Origin = (-17619594.547443531453609,8722279.461868489161134)
Pixel Size = (250.000000000000000,-250.000000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left (-17619594.547, 8722279.462)
Lower Left (-17619594.547,-6484970.538)
Upper Right (17872655.453, 8722279.462)
Lower Right (17872655.453,-6484970.538)
Center ( 126530.453, 1118654.462)
Band 1 Block=128x128 Type=Float32, ColorInterp=Gray
NoData Value=-3.4028234663852886e+38
The second file that I'm trying to match to the first file is in "" projection, with 100m resolution. Here is the gdalinfo of the second file:
Driver: GTiff/GeoTIFF
Size is 400302, 134668
Coordinate System is:
PROJCS["Custom_Goode",
GEOGCS["GCS_Sphere_GRS_1980_Authalic",
DATUM["D_Sphere_GRS_1980_Authalic",
SPHEROID["Sphere_GRS_1980_Authalic",6371007.0,0.0]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Goode_Homolosine"],
PARAMETER["False_Easting",0.0],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",0.0],
PARAMETER["Option",0.0],
UNIT["Kilometer",1000.0]]
Origin = (-20015.107512752761977,7429.758556314830457)
Pixel Size = (0.100000000000000,-0.100000000000000)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -20015.108, 7429.759)
Lower Left ( -20015.108, -6037.041)
Upper Right ( 20015.092, 7429.759)
Lower Right ( 20015.092, -6037.041)
Center ( -0.008, 696.359)
Band 1 Block=128x128 Type=Byte, ColorInterp=Gray
Min=0.000 Max=72.000
Minimum=0.000, Maximum=72.000, Mean=6.100, StdDev=2.983
NoData Value=-128
Overviews: 200151x67334, 100076x33667, 50038x16834, 25019x8417, 12510x4209, 6255x2105, 3128x1053, 1564x527, 782x264, 391x132
Metadata:
STATISTICS_MAXIMUM=72
STATISTICS_MEAN=6.100308069419
STATISTICS_MINIMUM=0
STATISTICS_SKIPFACTORX=1
STATISTICS_SKIPFACTORY=1
STATISTICS_STDDEV=2.9825236321
I'm trying to match the second file to the first file, but after warping, I get a file that has boundaries bigger than the actual world! The file has the other side of the world on each side (see below). For example ecos of Russia is seen on the left side of North America and ecos of North America is seen at the right side of Russia.
I think the problem is that the original file's extent is actually non-existance in it's own projection. But even after cutting the the first file's extra extent on the side's, I still have problem. It seems like the Mollweide projection is not well suited for the "-te" option. Also providing gdalwarp with a simple globale shapefile to cut it for extent, takes a billion years for some reasons.
Here is the thing, since each interpolation causes loss of data and the analysis seems to be sensitive to that, I would like to get the second file to match the first file's projection and resolution, with minimum steps and without changing the first file. Thats why "-tap" option is out of picture, as if I -tap the second file, I have to do it to the first file as well so that the cells are aligned.
Any ideas where the problem is and what I can do for it?
raster gdal extents gdalwarp
raster gdal extents gdalwarp
edited 4 mins ago
PolyGeo♦
53.7k1781244
asked 4 hours ago
Dr proctorDr proctor
143
edited 4 mins ago
PolyGeo♦
53.7k1781244
asked 4 hours ago
Dr proctorDr proctor
143
edited 4 mins ago
PolyGeo♦
53.7k1781244
edited 4 mins ago
PolyGeo♦
53.7k1781244
edited 4 mins ago
PolyGeo♦
53.7k1781244
53.7k1781244
asked 4 hours ago
Dr proctorDr proctor
143
asked 4 hours ago
Dr proctorDr proctor
143
asked 4 hours ago
Dr proctorDr proctor
143
143
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f315694%2fmatching-mollweide-extent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f315694%2fmatching-mollweide-extent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
