Thanks, and thanks for removing it!

BTW, OSM tagging is getting a bit complex, but I like reading the docs. Would you say the OSM documentation is up to date? Does it generally keep up to date or go in spurts where it gets out of date then gets updated?

Typo, should have been:

Added access=customers

In reading access=customers

Similar to paid hotel parking for hotel customers only, would the correct taggin then be:
access=customers
fee=yes
Thanks!

I noticed you added capacity:disabled=1 but left the wheelchair:description=1 stall
Should the wheelchair:description=1 stall be removed?

I agree that ideally the name should be the name, but I tried construction:amenity=charging_station and nothing rendered differently. So, our position should be "too bad" if someone shows up to a charging station under construction because the standard OSM renderer doesn't show it as such? Is there anything in progress to address this? Many other vehicles besides Teslas now use these stations. In this case, it's not yet known if the station will be a NACS station (for any vehicle with a NACS port or adaptor) or also a MagicDock station, which does NACS + CCS Combo1.

Is that what you mean about access, because if the station supports NACS or CCS Combo1, anyone can show up and use the station without restriction. Of course, they have to pay. Is payment the restriction you're referring to. Please clarify.

This amenity is not under construction ( start_date: 2023-10-27). Maybe the comment was meant for another changeset?

Thanks for fixing this and giving me the clue to the correct tag. I see it now at the "Designated parking space" at wheelchair=*?uselang=en , which links to osm.wiki/How_to_map_for_the_needs_of_people_with_disabilities#Designated_parking_space

Station went live today.

Don't know what's the holdup on this station because it's *still* not live in the Tesla app or the car. Maybe this week will be the week.

Wish I had a long-distance drone that could fly over and see if Tesla is on site. Last Dec 20 they had 2 grey Model Ys used as Tesla work vehicles: https://teslamotorsclub.com/tmc/threads/supercharger-frisco-co-summit-blvd.325079/page-3#post-8545225

Oh, yeah, another thing is Tesla still shows the site "Under contruction" on their "Find Us" site:
https://www.tesla.com/findus?location=19060
I hope Tesla takes this station completely live on the network today!

Another consideration is that when Tesla is finalizing the site, they might have to power it down for a while. I'm not sure about this, but if someone in a Ford or Chevy or something showed up almost empty and then there was no power, that would be bummer. Fortunately, they can just roll down to the Silverthorne - RUby Ranch Supercharger, which is also NACS. https://supercharge.info/map?siteID=3244

This low-power behavior has been seen before with Supercharger stations that are not quite live in the car and the Tesla app. People thought they were going to get free electrons, but Tesla knew and billed them. I'd not personally mark as live because I just checked and the station is not live in my car (Model 3) or the app. So you can't navigate to it as a charging station and Tesla's routing software won't include it. So for Teslas and Rivians (which now are connected to the Supercharger network), it won't be an issue, but other cars might go there expecting 250 kW and they won't get it. This is the custom at both of these sites: * https://supercharge.info/map?siteID=7885
* https://teslamotorsclub.com/tmc/threads/supercharger-frisco-co-summit-blvd.325079/

You should also see a bill on your credit card for the charge session. People in the past thought they'd get free electrons in these situations, but Tesla billed them. :)
BTW , someone from Frisco said on the TMC forum that they saw a red Model Y plugged in yesterday afternoon. That might have been you. :)
Also, thanks for the rename. Once it goes fully live I'll remove the construction:amenity tag, which didn't change the rendering as far as I could tell.

It's still not showing up live in the Tesla app, and Tesla's "Find Us" page is still showing "Under Construction"
https://www.tesla.com/findus?location=19060
Tesla is probably still commissioning the site, and it will probably go live at full power in a day or two. Strange that you only got 38 kW, but if you had a cold battery or were almost fully charged, you'll get low power.

In fact, it's not even showing up in the Tesla app, which it won't until it's live.

People have gotten some electrons like this before, but the site's not formally live.

Are you in a Tesla or something else, because it's not showing live in the Tesla app or on Tesla's site.

Thanks, and I agree totally that the map should show the world as it is right now, which is why I added the stations while under construction. The issue here is that there are several ways to mark things under construction. BTW, the Gypsum CO station just went live today, so I just updated that one.

construction=* says the tag:

construction=yes

is deprecated and not recommended. So I found osm.wiki/Lifecycle_prefix , which recommended "construction:amenity= "

so I added this tag:

construction:amenity=charging_station

I don't see any difference in rendering in the 6 map layers in the OSM web site or in the GNOME Maps application under Linux (charging stations don't even appear!). So I think for now the best option to leave "(under construction)" appended to the name.

Thanks! Heh, heh, I just updated 5 of the 6 Superchargers currently under construction in CO with "(under construction)" in the name (I use https://supercharge.info/map).

However, I do like your ideas and I didn't know about the construction=yes tag or "area under construction". Will that change the appearance for casual map visitors? I'll test later. I did think of waiting to map until ready, but then decided it's worth it to get them on the map, especially since some have been there since May 2024, waiting on a transformer. I guess bottom line is thinking about what's least confusing for regular map users. "(under construction)" in the name will work, but maybe that's not the most elegant or proper way to handle this. Got to run!