|
Post by B.Smooth13 on Mar 29, 2019 7:10:02 GMT -5
Haven't forgotten about this, but it may take me a while to hear back/look into details more. I think we both have others things to do, so we're not stuck, but we'd both like to see this get made. Yea it's not an urgent, have to figure this out today thing, but I would like to start making meaningful progress at some point soon. If you can give me some basic guidance on what you're going to try to figure out and/or what might be a good starting point for me to attempt to help with that, I can definitely do my best to assist so it's not all on you. Just let me know.
|
|
|
Post by B.Smooth13 on Apr 4, 2019 7:25:23 GMT -5
chadgolf Wanting to get this moving in the right direction. If I tried to figure out any scaling-type issues, what would I need to confirm - the height units and foot/meter measures, based on your previous post, would be 2 things I think. What else can I do to determine if this is just something I need to work around in the designer, or to finally get it lined up properly? Thanks as always.
|
|
|
Post by chadgolf on Apr 4, 2019 18:43:24 GMT -5
1) It's a little bit complicated, but I'll try to find the initial flight specifications for you. That will let us know if the data was published incorrectly. Should tell us the horizontal unit, vertical unit, and what coordinate system the flight data intended to publish in.
2) The 2nd thing we'll need to look at is how much of the course is on huge slopes or mountains. If holes have a ton of vertical distance, the sat images from OSM may not always line up. This is most obvious for things like trees, where you can see the top of trees blocking and covering up the image. You may need to compromise and find the map that is the most "top down" instead of highest resolution. Trees will look circular in these views.
3) The final thing to check is, without OSM splines, do the playing surfaces, distances, and relative sizes seem to be working out. I know there were quite a few greens that don't seem playable with slow and soft green settings. As far as I can tell, the data matches google earth in all dimensions, but since we're doing the same thing as them - no guarantee that they didn't make mistakes as well.
I'll do #1 right now. I'll leave #2 and #3 to you. Our initial goal is to see if OSM or the lidar looks to be the troublemaker.
|
|
|
Post by chadgolf on Apr 4, 2019 18:59:12 GMT -5
I've requested two custom slices of lidar from the NOAA servers. One in the "original" dataset CA 3 projection and a second converted to UTM and meters. Maybe either of those will be good.
If you wanted to put off the project for a few months, 2018 lidar data should be available from FEMA within a year. This will be 3DEP.
|
|
|
Post by B.Smooth13 on Apr 15, 2019 11:51:28 GMT -5
Ok, I've reached the point here where I'm going to throw this out - if there's anyone who would like to help/assist/collaborate on Pasa, please reach out. In a nutshell, it's going to take many, many hours to line up everything, and I anticipate that's something that will mostly have to be done "by hand" in the designer. It's just a huge project that I'm not sure I can tackle on my own, at least not anytime soon, but I also want this course - done right, which is important to me - in the game.
So, if there's anyone who thinks they'd like to get involved in some form or fashion, please let me know.
|
|
|
Post by bradleystuart on Apr 15, 2019 12:40:46 GMT -5
Hey bud, I can probably help you out with this. Let me see if I can get the lidar for it downloaded tonight or tomorrow.
|
|
|
Post by B.Smooth13 on Apr 15, 2019 13:46:03 GMT -5
Hey bud, I can probably help you out with this. Let me see if I can get the lidar for it downloaded tonight or tomorrow. I'll shoot you a PM with the 3 different source I've looked at, and you can see what I've been mulling over...
|
|