Skip to content

Registration handles #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Bald888Eagle opened this issue May 21, 2019 · 3 comments
Open

Registration handles #19

Bald888Eagle opened this issue May 21, 2019 · 3 comments

Comments

@Bald888Eagle
Copy link

I really like the ease-of use of this, and am currently trying to implement the depth map grayscale image for a heightfield that will be overlayed with satellite terrain or street map data.

The hightmapper VASTLY simplifies obtaining elevation data, however the satellite and map images I want to pair with that are not in register.

I'm thinking that if the Lat/Long values of two corners was displayed, that would give an orientation vector to work with.
An option to manually "mark" the elevation map with user-defined single-pixel-max-height "pins" would allow for visually recognizing / locating / aligning other map data.

If there was a way to pass the location and dimensions of the height map view rectangle to something like an online mapping website, then it would greatly simplify getting that complementary data to pair with the elevation map.

Does the exported height map file have a header?
Information such as the min and max elevation would be useful to have when trying to implement multiple files, and visualizing elevation contour lines.

Thanks for a great, easy to use tool!
Bill

@meetar
Copy link
Member

meetar commented May 22, 2019

No, nothing has headers at the moment. These are all good ideas!

@Bald888Eagle
Copy link
Author

Thanks :)
I know you're just collecting and displaying the data, but do you know anything about the collection and the source attributes of the elevation data? So, is the data based on true North, and is that +/- some angle? Is it LIDAR? What constitutes the surface reported as ground? I mean - how does the data collection method discard houses, metal buildings, skyscrapers, forest, etc, and not display a whole lot of holes for people's basements and foundations...?

Is this data, and data such as used in street map websites or satellite image websites different in terms of orientation, projection, or other "form"?

It seems that data has to be transformed to get it all to fit together nicely (stitched or overlaid).

https://courses.cs.washington.edu/courses/cse576/05sp/papers/MSR-TR-2004-92.pdf
https://gis.stackexchange.com/questions/66469/how-to-align-georeference-images-using-qgis

Looks like you've got a team of wizards over there! Keep up the great work :)
I look forward to using this a lot more and learning a lot in the process.
Thanks again.

@meetar
Copy link
Member

meetar commented May 23, 2019

The data is all projected in Web Mercator. The sources came from lots of places: documentation about them lives with the code used to process them all: https://github.com/tilezen/joerd/blob/master/docs/data-sources.md

(Note that the docs refer to the Mapzen Terrain Service, which is defunct, but which included source information in the headers. I don't think the current Nextzen service includes them but I could be wrong!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants