ele_derrick: elevation of the well drilling derrick above sea.
In the US, the standart of elevation is "ft", like the maxspeed standart is "maxspeed=X mph".
The depth values should probably get an "ft" added, I agree.
This import was documented in the wiki and discussed on the forum.

I fixed those four nodes you mentioned.

reverted per osm.wiki/United_States/2021_Highway_Classification_Guidance#Motorway
guideline

damn, forgot it once again.

But actually those lines added here don't rely on any external sources, except one "Fayetteville Gathering Company" operator tag based upon some company's SEC reports.

Common stuff like field compressor stations are obivious if you know how they look.

Those pipelines are almost all perfectly visible on the Bing and especially the 2011 Esri Clarity Imagery. (the pipeline right-of-ways, to be exact - by cuttings, ground color changes & aboveground valves/junctions etc)
The start_date 2009 is the date when the shale gas fracking boom took of in this area, and all lines which look like they've been constructed very recently on esri clarity got this tag.

usage=gathering is also obvious

Hope this helps, thanks for the remainder

those tags were automatically added at massive scale by the id-editor without it ever being properly discussed, so they can & should be removed in the same matter

thanks for letting me know.
I apparently drew that but forgot to split it and add the proper cables/circuits tags.

fixed it now.

No worries. I just saw those notes and looked what I could do, weather those roads are now tagged as SR 58 or not... I don't really care, that's not my area of intrest.

Just for your information, there is an "unsigned_ref=*" key, which might or might not fit better - but I'm not judging that

Are you sure that SR 58 still goes through Chattanooga?

There are
note/3507391
and
note/3507392
which say it dosen't.

I also looked at streetview images, and pretty much the section you added to the relation is not signed as being SR 58.

They are not "completely seperate".

power=generator represents a individual generating unit within a power plant, not "this area is used for power production".
It dosen't make sense to tag rows of solar panels as being seperate power=generator - a row of solar panels is not a generating unit.
(unless the only reason for adding them is that it the map looks prettier, then it dosen't matter)

If one really want to tag every individual generator within a solar farm, you would need to tag every single solar panel - even small 5MW farms have already multiple thousands, so that's obivously nonsense.

Therefore, I'm doing it like the U.S. Energy Information Administration does it within their US Generator Inventory, an Excel file containing every generating unit in the United States. They consider solar farms as being "one generating unit" per default - if the solar farm is expanded later, then that's another generating unit.

To cite a guideline, that would be the "one feature, one OSM object" one.

yes, I think

-sorry for the late reply

Hello,
"maop" refers to the "Maximum allowable operating pressure" (https://en.wikipedia.org/wiki/Maximum_allowable_operating_pressure).
This is usually different from the actual average pressure, sometimes even extremely different. This has various reasons, common example are changing natural gas markets.

The normal "pressure" key dosen't make an obvious distinction between those two types of pressure, therefore I created this key.
I don't know if it's a good solution, maybe it's better to use only one key, maybe not. I don't have strong opinions on it.

Hello, part of the quarry data is from the US Mine Safety & Health Administration's Mine Data Retrieval System, at https://www.msha.gov/data-and-reports/mine-data-retrieval-system
(Thus the ref:US:MSHA, you can look up addidional data on a specific quarry using the "search by mine ID")
Unfortunaly, none of this is georeferenced other than state/county and sometimes an address. The exact locations then have to be researched using the companies website or other means.
However, it is still a very good source (the website is unfortunaly very slow, but hey, it works).

It also includes thousands of abandoned quarries, many from the 90s, 80s, 70s and even earlier. They are usually still somewhere hidden in the woods, but the data is not not georeferenced, so very extensive research will be needed there.

Hope this helps you!

"actual" source? I didn't tag any source at all. geojson described in the other comment.

Nothing from any outside sources was added here.

It is visible, from cuttings, valves, pig launchers, meter stations, markers etc... the other details are from the public domain https://pvnpms.phmsa.dot.gov/PublicViewer/ and other details researched via https://elibrary.ferc.gov/eLibrary/search, a government database containing 2 million regulatory documents related to the US power sector (probably hundreds of millions of pages), you'll find basically everything there if you know how to use it.

Some public domain data (for example nat. gas compressors, manufacturing facilities, pumping stations, gas storages) from the US HIFLD & Alltheplaces excerpts which I use as reference. (still everything is confirmed via the websites or other means, (for example HIFLD manufacturing is +10 years old, so this is also obviously nesessary)) I could also open the data in a new tab, and use it as a reference then, but this saves time and is especially more comfortable.

(using data as a reference is not copying, and especially not importing)

This is public domain HIFLD data which I use as reference.

Source? Probably logic?
Tagging an single row of solar panels dosen't make sense, because it isn't a "generating unit".

A solar generating unit is either

- a single solar cell/solar panel. A solar farm this size consists of ~+250,000 individual panels. - Mapping every single of those as a generator might be correct, but is BS for obvious reasons.

- or all panels as one generating unit. (with exceptions) This is how the US EIA Electric Generator inventory handles it (US generation standart), and it is the best option. It dosen't yield absurd results like "this solar farm consists of 5,6k generators" (it consists of 250k generators). Also tags like generator:output:electricity are impossible to tag on those small areas.

TLDR: Mapping 5k ways might look good on the renderer, but dosen't look good on the background of electric generation data.
(This MP is the solar farm's generating unit > those 5000 areas are the solar farms' generating units, which is wrong)

I'm unsure which "detailed information" you mean as this isn't particularly detailed?
rail tags/geometries are obvious, name/operator "Rail Logix" is from multiple job openings.
The other industry details are researched from companies' websites.

Which information exactly do you mean?
Most is from the aerial imagery.

The voltage tags are inferred from connecting lines. They are additionally verified via company documents & reports and government reports (for example at https://elibrary.ferc.gov/eLibrary/search, FERC Form 1 Substations)

operator is similar. If I know the general operating area of an utility (example https://www.swepco.com/lib/docs/company/about/SWEPCOServiceTerritory_Cities2018.pdf), and public records at FERC indicate presence of substations/lines by that company, they're tagged as part of that company.
Also a very important aspect is just general (local) knowledge about how the electric transmission grid works. With the knowledge I have today, there's actually a lot of 'old'/my first power/electricity mapping of mine in Georgia, which I had (&still have) to clean up, by the way.

The reason this was uploaded with JOSM was simply because there were unresolveable conflicts while I tried to upload with iD (related to note/3726315), so I downloaded my changes into JOSM to resolve the conflicts/upload from there.

Hope this answers the questions.

Hello,
the source is the US Mine Safety & Health Administration (ref:US:MSHA, https://www.msha.gov/data-and-reports/mine-data-retrieval-system - government data, loads very slowly but is at least public domain)

I invented the rock_type tag because well; I want to express weather the mined dimension rock is granite or marble. I also invented aggregate:rock_type, to express which rock type the aggregate consists of - granite, limestone or something else. ("aggregate" is probably better known as "crushed rock", used for concrete, asphalt and other construction)
I also invented "ref:US:MSHA" because the MSHA records contain further valuable information, such as operator history, accidents, safety violations & more stuff. (Key's format based at similar "ref:US:EIA" for US power plants)

Hope this answers your questions!
Greetings

way/1153386544 and
way/1120071971
hasn't been conflated, should be fixed.

I appreciate your work nonetheless.