Wurstkoffer
Member
Yes, that could be a solution. But the more I think about it, the more I realize that an implementation with point clouds in a database exceeds my possibilities. Let's say, for example, we have 10 points in x and y. RTB queries a height for x=2.5 / y=4.2. Then the script must calculate the height based on the nearest neighbors. I am sure that there are extremely clever solutions for this. but I don't want to deal with it right now.The format varies. Sometimes only a list of Z values at a know grid spacing. But, if the user pre-formats the LIDAR data into google format then I guess, your method would just pick it straight up.
Actually, I only wanted to rebuild a few roads, which I know from reality and like to drive. Then I was so disappointed with the resolution of Google's elevation data that I thought up an alternative. And this alternative is now based on the use of WMS, which I want to perfect as far as possible.
Speaking of WMS. You can of course use Lidar data with a WMS server. And you can install a WMS server on your own computer. For example http://geoserver.org/. Getting Lidar data via WMS would work more or less out of the box with my current solution. The server then interpolates the elevation data between the available points. So i recommend to do some research on Lidar Data & GeoServer.