You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Null reference exception is shown in _rasterIndexServiceResolver when I click on "Generate Real Points" button. Null value is set in _rasterIndexServiceResolver during initialization of RasterService.cs class of DEM.NET.Core project.
To Reproduce
Steps to reproduce the behavior:
Start the project in DEM.NET.TestWinForm and click on 'Générer un point réel' button.
It goes to GetPointsTestsByBBox() method of EchantillonsTestsServices.cs in DEM.NET.TestWinForm project.
In GetPointsTestsByBBox() method, DownloadMissingFiles() is called from ElevationServices class.
And then in DownloadMissingFiles() method, GenerateReport() method is called in which _rasterIndexServiceResolver value is set to null which shows Null reference exception.
Expected behavior
I want to generate real point and create dtm models.
Screenshots
My Error screenshot
Desktop (please complete the following information):
OS: [e.g. Windows 10 Home]
Browser [e.g. chrome]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. Samsung Galaxy J2]
OS: [e.g. Android]
Browser [e.g. stock browser]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Null reference exception is shown in _rasterIndexServiceResolver when I click on "Generate Real Points" button. Null value is set in _rasterIndexServiceResolver during initialization of RasterService.cs class of DEM.NET.Core project.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I want to generate real point and create dtm models.
Screenshots
My Error screenshot
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: