Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cameni]

It will automagically fix with the lake system, since there will basically be a global water level map that will flood all terrain depressions, and terrain for which we do not have water depth info will be artificially adjusted to make river and lake beds (based on distance from shore and type).

In the meantime there might be a tweak that extends the range in which the vector data load, depending on the width, as this needs to be done for roads anyway.

[HiFlyer]

I know that X-plane faced similar issues with whole areas that just popped into existence in front of the viewer (I did videos similar to this one at the time) but they weren't able to address it really until they went 64bit and had the headroom to preload distant objects out further. Memory cost was high.

Glad to know there is a solution in mind, here.

[josem75]

OSM is incomplete and inconsistent, fixing it will require a lots of community effort. It's not reasonable to think it will be done anytime soon. Also, even if it was complete and clean tomorrow, as a map source it still lacks data like altitude above sea level that's needed for 3D reconstruction but not necessary for maps. And given the inconsistencies in the existing data, it would not be something we could rely upon. Fixing all the mess in the data is what takes most of the time spent on the importer by far.

During the OSM river import we are querying our elevation data to ensure 2D features match with the terrain.
If all seas, lakes and rivers were defined in OSM, we could use that to build the water level layer instead of using satellite reflectance data, but we'd still have to look up into the elevation data to determine the water levels.

We prefer more reliable data like satellite imagery that contains the water masks, but these are in lower resolution than proper OSM data and suffer from aliasing and filtering. One of the possibilities is to combine the two into a higher detail water mask map, so that we'd have ~30m resolution water bodies for the whole world, and finer shapes where they are available in OSM. However, this also brings in all the problems of OSM - it's not easy to determine algorithmically which OSM entities are erroneous and would actually introduce artifacts, and which ones are a refinement and can replace the rough raster data.

Very interesting mix.
I am thinking. Maybe using this 30m or even 60m satellite data for water masks, would be posible to try also for define the shorelines around the world?
You know. In many places we have water from sea coming inside the "cities". This satellite data surelly are showing the water line correct, not coming inside the city.  Maybe would be useful for fix that shorelines problem.

[KW71]

Talking about bad OSM data... A river flowing in two directions:

[HiFlyer]

Hmmmmm..... I know the hudson river (estuary, really) can flow in two directions, but I presume this is not an example of that sort of thing.....

[HiFlyer]

Wonder if this could be useful, not particularly for rivers, but generally.

http://openpoimap.org/

https://wiki.openstreetmap.org/wiki/OpenPoiMap

http://openpoimap.org/?map=hotels&zoom=15&lat=37.78674&lon=-122.41575&layers=B00FFFFFTT