I have a request for DEM in eastern PA. Tremont, PA in Schuylkill County to Elizabethtown, PA in Lancaster County following former Reading and PRR railroad lines. It's for a project. https://en.wikipedia.org/wiki/Lebanon_and_Tremont_Branch#/map/0
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I've always had an issue with that. To me, thats like saying someone with Photoshop can't make a graphic or someone with 3ds can't make a model for someone. Just my opinion.Anyone with the Trainz version of TranzDEM is not allowed to produce DEM's with their licence other than for the construction of their own route which of course may be uploaded to the DLS.
Wow, that pretty much ends my route building in Trainz.Anyone with the Trainz version of TranzDEM is not allowed to produce DEM's with their licence other than for the construction of their own route which of course may be uploaded to the DLS.
I think I have something already made, but it doesn't go as far a Lancaster County. I would have to look at my collection.So what, asking someone to make a DEM for you is against the terms of service of TransDEM or is it allowed? BlackDiamond, I was almost going to ask you if you could do it.
PM SentBlackDiamond, even if you had Tremont to Lebanon I would take that. I have a DEM from Lebanon to the south from the DLS.
Phil, I've come across a very strange effect in a DEM I downloaded for the DLS, with the aim of possibly using it in the future, the track cannot be raised, in fact when I try to do anything with it, it dives down 50 feet below ground and for some reason refers to -50.4ft ( 3000 ). It occurs with any track, deleting old track makes no difference. Do you have ANY idea what might have happened here ? Its probably Trainz related and not a particular transdem issue as I've never seen it happen before. its in trs 2022, I've yet to test if the same thing occurs in 2019.Nothing has changed. And, of course, you can share your routes based on TransDEM generated terrain with others and publish them. If you want to do that commercially, then please purchase a commercial TransDEM license. Otherwise, the only thing I ask is that you actually build a route of your own, and surpass a "threshold of originality" (copyright law terminology). And I do not object you working in a route builder team, with one of you doing the geo data stuff and exchange TransDEM output with other team members, but please keep it within your team.
This discussion comes up every other year. TransDEM for Trainz has celebrated its 20th anniversary this year. And there could be a reason why it is living so long and I have not given up on this project. My tiny cottage industry is a one person enterprise. Billion dollar companies like Adobe, mentioned in a post above, may have different license policies. I am not competing with them.
There was a feature in early versions of Trainz for splines to cling to the surface. More recent Trainz versions no longer acknowledge this. Current TransDEM sets spline points at DEM elevation.the track cannot be raised, in fact when I try to do anything with it, it dives down 50 feet below ground and for some reason refers to -50.4ft ( 3000 )
I opened it in 2019 , I could raise track up and down , no issues , I saved under my kuid and imported into 2022. Same issue as before, track plunges into the depths.I noted that in the route info the creator states that hes fixed an "elevation cap" issue, I think that is probably what the problem is, the height of the route was lowered by 1900 m and this is now causing problems in trs 2022. DRAT !Dan, I don't know what DEM you are using. But I DL'd the "Colorado Midland Ry. - Colo Springs to Granite - DEM [unedited]" into TRS19sp5 to see if anything was unusual. The track strings are sitting on the surface of the terrain just fine. They also let me change the height, without complications.
Many times I'll use JOSM to capture trackage from OpenStreetMaps to import the trackage into TransDem, and later into Trainz. OSM trackage has no elevation data and ends up at elevation 0 meters until the vertex height is cleared using surveyor track tools. At which point it rises to the terrain surface. But what you are describing sounds very different.
So perhaps TRS19sp5 isn't doing what you are seeing in your build of TRS22.
Edit: I need to admit that I'm still using TransDem 2.6.6.2 in case the latest version handles zero-height vertexes differently.