badenk's Comments
| Changeset | When | Comment |
|---|---|---|
| 116631815 | over 3 years ago | Interesting Development While just checking the current situation on Sentinel2, I noticed that there was construction activity on 180D to the west from Valladolid, similar to the section between Valladolid and Cancun. This new routing was confirmed by: So, I take it the jungle train concept to get near Chichen Itza has been abandoned. |
| 116631815 | over 3 years ago | Hi Aaron:
Between Valladolid and Cancun, the north lane of the existing 4 lane cuota is being converted to 4 lanes with a concrete divider. The south lane is then being converted to host the Tren Maya, which will be double tracked and electrified. ICA is the cuota concessionaire and also the contractor for the conversion and railway section, so it should expedite the process. I have currently left out the interchanges, which will have enhanced complexity, until relevant imagery details the new routes. I imagine that temporary detours allow bi-directional traffic flow. https://everythingplayadelcarmen.com/update-on-how-the-train-maya-project-is-coming-along/ thanks, Baden |
| 105906567 | over 3 years ago | 感谢您的帮助 |
| 105906567 | over 3 years ago | 你可以说得更详细点吗?
|
| 117897296 | almost 4 years ago | Herr Hohe Schule: "On new railway lines built in the United Kingdom such as High Speed 1, the position along the alignment is still called "chainage" although the value is now defined in metres.[13]" |
| 48852902 | almost 4 years ago | I would sure think so, thanks! |
| 115405072 | almost 4 years ago | Hi Maps: Would you know about any imagery that shows:
thanks,
|
| 78702033 | about 4 years ago | 你可以更具体,或自己删除吗? 谢谢 |
| 113779908 | about 4 years ago | Hi: 1L17 is gone. 2L129 is in. Check out the details on: This could also be changed (incl. routes) on the islands. thanks,
thanks,
|
| 94961469 | about 4 years ago | Here is some HVDC information: https://en.wikipedia.org/wiki/HVDC_Vancouver_Island I hope this helps,
|
| 113750326 | about 4 years ago | Hi Mr. Glassman: I looked at the Mississippi, and the lower section has "ship=yes", but that does not signify much on: access=*#Water-based_transportation As for 'navigable', I like to refer to "The African Queen". {:-) Perhaps you might be inclined to change the Columbia relation name(s) to something you consider appropriate. I have no qualms, save that they are unique. thanks,
|
| 113750326 | about 4 years ago | Hi Mr. Glassman: I think there are several items which need to be considered here: - I do not see the relation names actually being rendered anywhere. - The relation names do not seem to be identical to the legal cartographic name. Looking at the Trans Canada Highway as an example, there are relations and super relations. A relation name is "Trans-Canada 1 (BC eastbound: mainland)", and the super relation name is "Trans-Canada 1 (BC, AB, SK, MB) (super)" - Ideally, as you suggested, relations and a super relation might work, but the super relations have problematic rendering, as the example above can illustrate. - I am not exactly sure what "Navigable" term's utility is. I searched and found that there is some basis in an U.S.A. maritime law for waterways which are accessible to seagoing vessels. - Pasco appears to be a upper limit for this activity, but the Columbia River and reservoirs are continuously navigable by commercial vessels from Grand Coolee Dam to Revelstoke, and separately on Revelstoke and Kinbasket reservoirs. - I looked at the Mekong River for some guidance, and the entire waterway is under one "Mekong River" relation with many different national way names along its length. - The Mekong lower reaches have an additional unnamed relation with the sole tag "navigable=yes". - Perhaps the easily implemented and politically correct proper fix would be to rename the upper river relation "Columbia 2" to the unambiguous and distinct native name "swah'netk'qhu". This would be much less confusing than "Columbia 2". {;-) thanks,
|
| 113750326 | about 4 years ago | Hi Mr. Glassman: I made some changes to the Columbia River at Mica, including relations. I noticed that there were two relations, IIRC, the second was just a "Waterway", to which I added the name "Columbia River". Subsequently, when applying relations to the ways I had built, there was some confusion and errors, as I noted there were then two "Columbia River" relations, the second with a note, "Columbia River: non-navigable part". I then appended a "2" to its name to segregate and identify the two relation names. Ideally, the second should be a subset of the first, or they should be mutually exclusive. Having two relations with the same name for the same way is confusing, and maybe you could suggest a more appropriate name? thanks,
|
| 113122898 | about 4 years ago | Hi mueschel: I am confused. Are you stating these tags already exist, or are you suggesting their use? If the latter, I prefer "power:source:water_head" as it is the most precise and unambiguous. Additionally, "max" and "min" might be beneficial sub categories. As for tags, do you know if there is an overall OSM tag list or tree? A tag tree, especially hyperlinked to definitions and a list would be very valuable. The wiki is adequate, but often incomplete and confusing. thanks,
|
| 113122898 | about 4 years ago | Hi mueschel: What I desired, was a tag to define the pressure head in a hydro installation. In a typical dam storage system, it is not as significant as in an elevated reservoir system like this one. I checked the OSM world, and nothing was found. The most appropriate English language term (which wikipedia uses) is "hydraulic head", which I thought was possibly too complex for this purpose, and difficult to translate. "Hydraulic head" additionally requires a denoted liquid and possibly density and temperature to be precise. (eg. 263.4 cm mineral oil SG 0.732). In a hydro installation, the "hydraulic head" would include a length and liquid, (i.e. water) so "630 m water". I thought using "water_head" would be simple, self explanatory, and easily translated. German seems to have the ideal term, "Fallhöhe", which is exactly defined in metres. What would you consider as the most appropriate tag label? thanks,
|
| 106648443 | about 4 years ago | Hi Dinar: The way is a circle template for the railway curve and tunnel awaiting improved imagery. On the imagery topic, I suggest you do not use Maxar imagery for the surrounding mountainous area, as it is very distorted. For example, this is a straight highway: osm.org/query?lat=22.51700&lon=104.00293#map=19/22.51702/104.00331 thanks,
|
| 109635000 | over 4 years ago | Hi Sherbet: I had repetitive and continuing instances where editors (usually "import account") have modified and reverted the SGR right of way to incorrect legacy ways based on obsolete sources. If they look at Google Maps, they may get a more current image. I was going to also suggest Sentinel2 Explorer, but that might be beyond most competencies. thanks,
|
| 100305847 | over 4 years ago | Hi Bert et al: I have recently discovered that both iD editor and Go Map!! have similar properties for (re)combining ways. In both programs, first ascertain which way has the original (multiple) history and select it first, then add the adjoining way. The resultant combined way retains the first way's history. This information should allow you the ability to correct all the anomalies you discover. I restored the the history for the particular taxiway you were concerned about. thanks,
|
| 99538583 | over 4 years ago | Hi Mr. George Rhodes et al: I have recently discovered that both iD editor and Go Map!! have similar properties for (re)combining ways. In both programs, first ascertain which way has the original (multiple) history and select it first, then add the adjoining way. The resultant combined way retains the first way's history. This information should allow you the ability to correct all the anomalies you discover. I restored the the history for the particular way you were concerned about. thanks,
|
| 106882188 | over 4 years ago | Hi Jyunhou: You are correct.
|