Andrew Kirmse

No, I had to disable the corresponding feature. It works in the part of my app that uses Google Maps. That sure doesn't make Mapbox look too good! On Tue,...

Yes, this is expected. -f deletes the "runoffs", which are intermediate entities that are needed if the output is to be merged further. You can read more about runoffs at...

Hm, yes, that's true, there's not really a well-defined prominence value for the highest point < 0. For Everest, using the elevation matches intuition as the high point of a...

I ran the following two commands on each input tile: ``` \mountains\code\release\prominence.exe -f SRTM 72 73 2 3 \mountains\code\release\merge_divide_trees -f output prominence-72x00-002x00-divide_tree_pruned_100.dvt ``` What I found is similar to what...

I did some careful debugging and did see a tiny difference in one calculation that I couldn't explain. I did a diff of the two rasters in QGIS and found...

It's also possible that QGIS is producing false positives due to floating point rounding.. just wanted to be sure you know that the two rasters are exactly 4000 apart everywhere.

Up to you.. I haven't looked at it again. I'd need to know more about how the shift of 4000 was done before investigating further, in case that's what introduced...

+1, I would never integrate a library manually in this way when there are package systems.