Print

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

[SaltyNZ]

This software is amazing! I could not believe how lifelike it was looking even at this early point. I found the location of our house and plonked a pagoda there.

So I decided to fly through fjordland in southern NZ. But if you go to the Milford Sound (44°40'17.85"S, 167°55'32.24"E) you will see some obvious anomalies in the terrain data. Rectilinear chunks of ground that have been raised above sea level around the real cliff walls.

[cameni]

Yes, there are some bugs in the source data. I wonder if it could be somehow fixed by the community .. but since the source data are reprocessed by us, we must keep track of the buggy parts and try to fix it before the next terrain build.

[PRiME]

You could allow a toolset ingame similar to how roads are placed but let you select areas of terrain to alter then have a option of Update to Server, which then saves those changes to each users account for you guys to quickly checkout and bridge over the changes made? I.e. Like a small datapool allowed for user based terrain changes.

Pretty sure that would work great, people can post threads of their changes to the community with photos. If their serious.

[cameni]

That would require dynamic recompression and additional tools and server support, which can be done but there's enough of tasks as it is. For now it's much simpler to fix the source data, if one knows how/where.

The source data tiles can be downloaded for example from rmw.recordist.com, but you'll need some additional tools to repair the bugs.

[C. Shawn Smith]

That would require dynamic recompression and additional tools and server support, which can be done but there's enough of tasks as it is. For now it's much simpler to fix the source data, if one knows how/where.

The source data tiles can be downloaded for example from rmw.recordist.com, but you'll need some additional tools to repair the bugs.

What sort of tools?

[cameni]

In-engine tools for adjusting terrain nodes at the specific level covered by the downloaded data.

[C. Shawn Smith]

ahh, okay.  From what you said, it sounded like you were referring to a 3rd party program(s) that we could use to alter the raw data, send that in to you to be looked at.

[KelvinNZ]

It would be great to have the world terrain data checked for accuracy, perhaps somehow have the community start testing with relevant tools so that all terrain is accurate.

[KelvinNZ]

Here are the Anomolies reported above. In screenshot form.

[KelvinNZ]

The screenshots in my above post show the obvious anomalies. See this image to see what should be there ( or in this case what should not be there) The elevated group area is incorrect as well as this area is practically at sea level.

[monks]

Imo, it would be productive to have a way to register the locations of the
errors, but accept that it's going to be a medium long term fix via updating the terrain
with new sources that appear, or from users manually doing it. The overheads of coding an interface, might not be worth it, depending on how much folks could do this without the need to code.

 Getting the terrain back into Outerra database might be problematic...as I
suggested in the other thread, Leveller is the app to use IF you have to preserve
georef info in the file format and want a 3D view. To minimise the overheads
for the devs, users are going to have to submit terrain that just drops
back into the database.Photoshop is out for that reason- no preservation of
georef info and also you have the scaling problem of the whole terrain since
PS doesn't use any meaningful height measure. Maybe you have a solution for
reintegrating without georeff, but you need a solution that will work for
all resubmitted tiles, which may cover different area extents. The only app
(that I know of) that has both 3D view/paint tools and supports full
read/write of georef formats is Leveller.

It might be an idea Brano, for you to add support for a couple more formats to
xnview if folks decide to use say Wilbur, (Wilbur does read/write georef info
in a few useful formats, hfz,.bt, srtm, dem) but Leveller is big on format
support- it handles the native Geotiffs, ascii and a zillion others.You
can't really do that kind of editing in 2D like Wilbur, not well anyway, BUT
for the kind of correcting you're talking about here, I think you could get
away with using Wilbur if you stuck to the smooth tool (Leveller), lerp (Wilbur).

monks