Jump to content

Talk:List of Colorado county high points

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
[edit]

Hello fellow Wikipedians,

I have just modified one external link on List of Colorado county high points. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 23:30, 22 May 2017 (UTC)[reply]

Coordinate error

[edit]

{{geodata-check}}

Denver's highest point coordinates appear to be just outside the boundary of the City and County of Denver; i have confirmed this fault on Google Earth, Open Street Maps, and Denver's GIS service; a possible actual Denver high point is approx 33m north, 39°37′37″N 105°06′36″W / 39.626967°N 105.109877°W / 39.626967; -105.109877; this point's elevation is 5688 ft per Google Earth and 1736m (5696 ft) via query via the Open Elevation API;[1]; the Peakbagger entry referenced for this location has a map view that shows the out-of-boundary error more clearly when the default view is changed to ArcGIS or Open Streetmap (ArcGIS shows an non-orthogonal boundary that is inconsistent with other sources)

the location i suggest is on the roadway — the adjacent median and sidewalks are slightly higher; i have not field-verified this info, but a blogger has documented their efforts to visit this highest point, putting it on the adjacent sidewalk at 5680 ft, but not providing coordinates[2]

an alternative location that has been raised significantly by highway earthworks, is within the I-25 / I-225 interchange at 39°38′00″N 104°54′19″W / 39.633284°N 104.905293°W / 39.633284; -104.905293; Google Earth gives 5693 ft, yet Open Elevation API gives 1718m (5636ft) (possibly reflecting the pre-earthworks elevation)

Garbanzito (talk) 23:13, 28 November 2018 (UTC)[reply]

References

  1. ^ "Open Elevation API query for a point in Denver". Open Elevation API. Retrieved 28 November 2018.
  2. ^ "Denver High Point - Rise Near NE Corner of Kipling & Belleview". ColoradoGuy.com. Retrieved 28 November 2018.
I agree that Peakbagger isn't, perhaps, the most reliable source; but I think that it is, at least, more reliable than the ColoradoGuy blogger. Your objections to the location currently in the article and speculations about a possible revision seem to me to involve an unacceptable (for Wikipedia purposes) measure of original research. I'm going to close the {{geodata-check}} tag above so that it doesn't unnecessarily attract the attention of people who monitor Category:Talk pages requiring geodata verification, who probably can't do any more about the situation than I can. Discussion can continue here; but unless someone can come up with a reliable, published source giving a location different from the one currently specified in the article, I see no reason to change the coordinates. Deor (talk) 19:11, 30 November 2018 (UTC)[reply]
thanks, i understand the reason not to use the coordinates i speculated upon (which is why i didn't update the actual page); if Peakbagger is clearly referencing a point not within Denver, wouldn't it then make the most sense to simply remove that coordinate (and reference) from the table? if a reference is required to show that the point is not in Denver, would this JSON result from the FCC Enterprise Area API suffice? Garbanzito (talk) 22:50, 30 November 2018 (UTC)[reply]