Map error while doing vector map based rural simulation through the API

Roland Sipos

Hello,

We ran into another problem when doing vector DB based rural simulations through the API. After setting the WinProp_Scenario to "WINPROP_SCENARIO_INDOOR" as per Reiner's recommendation (we do this for all vector DB based rural models now, RRT, IRT, SBR, one slope), using the WinProp_Predict_Points() and a .tdv vector map,  we still get an error for all simulations, but this time it says " WinProp Error Code: 36 RECEIVER_OUTSIDE_TOPO The selected topography database is smaller than the prediction area! The receiver is located outside the topography."

But it's seemingly not, it's right in the middle of the map.

We do simulations for followig point/antennas:

"points/receivers": [

        {"x": 362204.467, "y": 5259261.465},

        {"x": 362202.465,"y": 5259261.513},

        {"x": 362202.512,"y": 5259263.509}

 

antennas:

            "antennaLongitudeX": 362074.675,   "antennaLatitudeY": 5259584.864,

            "antennaLongitudeX": 361249.531,   "antennaLatitudeY": 5258515.264,

            "antennaLongitudeX": 361231.645,   "antennaLatitudeY": 5261229.259,

            "antennaLongitudeX": 361231.645,  "antennaLatitudeY": 5261229.259,

 

It looks like Wallman doesn't properly converts Topo databases (and thus generating vector DBs), when I'm explicitly setting the bounds of the target database, cutting out a piece of the original map (or we do something wrong). Wallman, "convert topo database" option. It seems that no matter what bounds I set during the conversion, the resulting map will have the exact coordinate bounds that I gave it – but it will always put the bottom left section of the original map into the result map, no matter which section I specify. It happens with both conversion from GeoTiff tot .tdb,  and from .tdb to .tdb.
The map section that it cuts out also doesn't seem to always be proportional to the given area size, so not only the cut out position is wrong, but also it tends to use the same sized parts of the original map for different dimensions in the result map.

Thus in the resulting map the coordinates of the map, and the map section it displays don't match.
If I open it in Proman, it will say it's bounds are what I set during the conversion, but it will show a totally different map section that what actually corresponds to those coordinates.
If I make a simulation with that map on the Proman UI, it will do the simulation, using the coordinates it thinks it has (the results are using the same coordinates), but it uses the wrong map section and hence the wrong elevation values.

Here I attach an example:
I start out from the OpenDem 1 arc sec " N47E019" GeoTiff tile (https://openmaps.online/eudem_download/eu_4258/N47E019.zip), and either convert it to .tdb, and than cut out first it's bottom half, and than it's top half , or immediately cut the top and bottom half parts while converting from Geotiff to .tdb.
In both cases, the resulting coordinates will be correct for the top and bottom half maps, but the displayed map section will be almost the same for the both! 

N47E019:

bottom half:

 

top half (saves the bottom half topology as well with the top half coordinates):

Could you give some feedback for the "RECEIVER_OUTSIDE_TOPO" error, and this strange map conversion behaviour? 

Thank you, 
Best Regards
Roland Sipos

 

Roland Sipos

I missed out that the height of the calculated points was 1 meter ground relaive. 

Zeina

Hi Roland,

I am converting this into a Support Case so that we can check what's happening and follow up with you.

Best Regards,

Zeina