Welcome to the RAS Solution › Forums › HEC-RAS Help › Terrain from EPSG:3310 file is 475′ south of Web Imagery?
- This topic has 2 replies, 478 voices, and was last updated 6 years, 2 months ago by LorenAmelang.
-
AuthorPosts
-
September 2, 2018 at 10:50 am #7026LorenAmelangParticipant
I just created a new project from scratch in RAS Mapper from v5.05. I had tried the Web Imagery in my previous project, which was in EPSG:2226, and it all lined up perfectly. But the California DSOD requires EPSG:3310 “California Teale Albers”, so I re-projected my DEM using QGIS. And drew everything fresh, manually, based on it.
The DEM “Terrain – Layer Properties” file info clearly shows all the 3310 details, so I think it must be correct. RAS Mapper project properties shows the same 3310 details. I find several web postings about people finding similar problems, manually displacing their other layers to match the Web Imagery, and ending up with a useless mess, so I’m not inclined to try that. And I can’t find any way to displace the Web Imagery to match my DEM…
But I exported Web Imagery from QGIS as a 3310 GeoTIFF, and it lines up with RAS Mapper’s native Web Imagery! So it isn’t just direct from web rasters that seem displaced.
So I just exported the DEM and River layers from RAS Mapper, and opened them in QGIS – where they are displaced 475′ south of all the web imagery and of the DEM I originally exported to RAS Mapper! So now I’m thinking maybe Importing an EPSG:3310 DEM into a RAS Mapper Terrain layer displaces it 475′ south ???
It is far too late to go any deeper tonight… Does anyone understand this? Is there some standard test file or procedure that would show who is displaced?
[Next day…]
I’ve convinced myself the Web Imagery is projected correctly, and RAS Mapper’s import of my EPSG:3310 DEM is wrong. It imports the original NAD83 version properly.
RAS Mapper importing original USGS DEM (yes, it can import from Erdas Imagine Images (.img) files!:
—
File: C:\…\USGS_NED_one_meter_x47y436_CA_FEMA_R9_Russian_2017_IMG_2018.imgDriver: HFA/Erdas Imagine Images (.img)
Files: C:\…\USGS_NED_one_meter_x47y436_CA_FEMA_R9_Russian_2017_IMG_2018.img
C:\…\USGS_NED_one_meter_x47y436_CA_FEMA_R9_Russian_2017_IMG_2018.img.aux.xml
Size is 10012, 10012
Coordinate System is:
PROJCS[“NAD_1983_UTM_Zone_10N”,
GEOGCS[“NAD83”,
DATUM[“North_American_Datum_1983”,
SPHEROID[“GRS 1980”,6378137,298.257222101,
AUTHORITY[“EPSG”,”7019″]],
TOWGS84[0,0,0,-0,-0,-0,0],
AUTHORITY[“EPSG”,”6269″]],
PRIMEM[“Greenwich”,0,
AUTHORITY[“EPSG”,”8901″]],
UNIT[“degree”,0.0174532925199433,
AUTHORITY[“EPSG”,”9122″]],
AUTHORITY[“EPSG”,”4269″]],
PROJECTION[“Transverse_Mercator”],
PARAMETER[“latitude_of_origin”,0],
PARAMETER[“central_meridian”,-123],
PARAMETER[“scale_factor”,0.9996],
PARAMETER[“false_easting”,500000],
PARAMETER[“false_northing”,0],
UNIT[“Meter”,1],
AUTHORITY[“EPSG”,”26910″]]
Origin = (469994.000000000000000,4360006.000000000000000)
Pixel Size = (1.000000000000000,-1.000000000000000)
Metadata:
AREA_OR_POINT=Area
Corner Coordinates:
Upper Left ( 469994.000, 4360006.000) (123d20’54.38″W, 39d23’20.48″N)
Lower Left ( 469994.000, 4349994.000) (123d20’52.77″W, 39d17’55.70″N)
Upper Right ( 480006.000, 4360006.000) (123d13’55.84″W, 39d23’21.52″N)
Lower Right ( 480006.000, 4349994.000) (123d13’54.76″W, 39d17’56.74″N)
Center ( 475000.000, 4355000.000) (123d17’24.44″W, 39d20’38.66″N)
Band 1 Block=64×64 Type=Float32, ColorInterp=Undefined
Description = Layer_1
Min=295.365 Max=1015.863
Minimum=295.365, Maximum=1015.863, Mean=666.227, StdDev=180.519
NoData Value=-3.4028234663852886e+38
Metadata:
LAYER_TYPE=athematic
STATISTICS_MAXIMUM=1015.8628540039
STATISTICS_MEAN=666.22659794113
STATISTICS_MINIMUM=295.36517333984
STATISTICS_STDDEV=180.51920675931
—
Computation Task | hh:mm:ss
———————————————————————————————
Importing 1 of 1: USGS_NED_one_meter_x47y436_CA_FEMA_R9_Russian_2017_IMG_2018.img -> TerrainDirUSGS.USGS_NED_one_meter_x47y436_CA_FEMA_R9_Russian_2017_IMG_2018.tif
Step 1 of 4: Translating to GeoTiff and reprojecting…
Warning 1: for band 1, destination nodata value has been clamped to -340282346638528859811704183484516925440, the original value being out of range.
Step 1 of 4: Translating to GeoTiff and reprojecting… | 16
Step 2 of 4: Rounding and Generating Statistics… | 14
Step 3 of 4: Generating Histogram… | 4
Step 4 of 4: Adding Overlays… | 10
USGS_NED_one_meter_x47y436_CA_FEMA_R9_Russian_2017_IMG_2018.img Import Complete. | 45
———————————————————————————————
Final Processing: TerrainDirUSGS.hdf
Step 1 of 3: Creating TerrainDirUSGS.vrt… | 0
Step 2 of 3: Creating TerrainDirUSGS.hdf… | 10
Step 3 of 3: Creating Stitch-TIN for merging rasters… | 1
———————————————————————————————
Terrain Complete | 57
—The Terrain imported directly from the USGS “NAD_1983_UTM_Zone_10N” file matches the Web Imagery closely. This new terrain is shorter in the N-S direction than the previous bad one, and shorter toward the west than the east – so I can’t just move my vector layers. The new terrain opens properly aligned in QGIS.
Here is what RAS Mapper GDAL sees in the 3310 file it imported incorrectly:
—
File: C:\…\DEM_3310.tifDriver: GTiff/GeoTIFF
Files: C:\…\DEM_3310.tif
Size is 10012, 10662
Coordinate System is:
PROJCS[“NAD83 / California Albers”,
GEOGCS[“NAD83”,
DATUM[“North_American_Datum_1983”,
SPHEROID[“GRS 1980”,6378137,298.257222101,
AUTHORITY[“EPSG”,”7019″]],
TOWGS84[0,0,0,0,0,0,0],
AUTHORITY[“EPSG”,”6269″]],
PRIMEM[“Greenwich”,0,
AUTHORITY[“EPSG”,”8901″]],
UNIT[“degree”,0.0174532925199433,
AUTHORITY[“EPSG”,”9122″]],
AUTHORITY[“EPSG”,”4269″]],
PROJECTION[“Albers_Conic_Equal_Area”],
PARAMETER[“standard_parallel_1”,34],
PARAMETER[“standard_parallel_2”,40.5],
PARAMETER[“latitude_of_center”,0],
PARAMETER[“longitude_of_center”,-120],
PARAMETER[“false_easting”,0],
PARAMETER[“false_northing”,-4000000],
UNIT[“metre”,1,
AUTHORITY[“EPSG”,”9001″]],
AXIS[“X”,EAST],
AXIS[“Y”,NORTH],
AUTHORITY[“EPSG”,”3310″]]
Origin = (-288454.026300000026822,157662.521000000007916)
Pixel Size = (1.030469526568122,-0.969388829487901)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( -288454.026, 157662.521) (123d21′ 7.56″W, 39d23’20.11″N)
Lower Left ( -288454.026, 147326.897) (123d20’52.30″W, 39d17’45.50″N)
Upper Right ( -278136.965, 157662.521) (123d13’56.29″W, 39d23’31.72″N)
Lower Right ( -278136.965, 147326.897) (123d13’41.57″W, 39d17’57.09″N)
Center ( -283295.496, 152494.709) (123d17’24.43″W, 39d20’38.66″N)
Band 1 Block=10012×1 Type=Float32, ColorInterp=Gray
NoData Value=-3.4028234663852886e+38
—And here is the project coordinate system:
—
PROJCS[“NAD83 / California Albers”,GEOGCS[“GCS_North_American_1983”,DATUM[“D_North_American_1983”,
SPHEROID[“GRS_1980”,6378137,298.257222101]],
PRIMEM[“Greenwich”,0],UNIT[“Degree”,0.017453292519943295]],
PROJECTION[“Albers”],
PARAMETER[“standard_parallel_1”,34],
PARAMETER[“standard_parallel_2”,40.5],
PARAMETER[“latitude_of_origin”,0],
PARAMETER[“central_meridian”,-120],
PARAMETER[“false_easting”,0],
PARAMETER[“false_northing”,-4000000],
UNIT[“Meter”,1]]
—Sure looks to me like the RAS Mapper import just projected the EPSG:3310 version incorrectly. The file it imported from opens properly in QGIS, the file it created is offset. PCI Geomatics FreeView shows the same offset.
Is there some better way to report possible bugs than the eMail address given in the Release Notes?
—
Reporting of suspected program errors is unrestricted and we will reply to all
correspondence concerning such errors. We are continuously working to improve
the program and possible bugs should always be reported. Reports should include
a written description of the steps that lead to the problem and the effects that
result from it. If we cannot reproduce the reported problem, we may ask you to
send a copy of your project.
Report program errors through the following channels:
• Go to our web site at http://www.hec.usace.army.mil then go to the HEC-RAS
support page.
• Send email to [email protected] on the internet.
—The instructions at
http://www.hec.usace.army.mil/software/hec-ras/bug_report.aspx
just say to send an eMail.I sent a detailed report of a series of exceptions thrown by RAS Mapper two weeks ago, and have received no reply, not even an automated one. Maybe they are that far behind?
September 23, 2018 at 9:38 am #11687cameronParticipantThe answer is simple. Do everything in Stateplane and then convert the final floodplain and results to the DSOD required projection.
January 6, 2021 at 6:21 pm #11688benpParticipantProblem solved here with square pixel instead of rectangular(look at my post):
http://hec-ras-help.1091112.n5.nabble.com/Problem-with-misaligned-spatial-projection-prj-British-National-Grid-td3753.html#nonehttp:// -
AuthorPosts
- You must be logged in to reply to this topic.