2Go/Map2Go
1
8
Fork
You've already forked Map2Go
0

Custom charging station editor #38

Closed
opened 2026年04月13日 02:46:08 +02:00 by GA-Kevin-Codes · 0 comments

Charging stations in OpenStreetMap (https://osm.wiki/charging_station) are a uniquely complex and technical element to tag. As such, to make it easier on editors, Map2Go should lean on suggestions from open data sources.

Current tags that would be useful in a generic preset:

  • Brand (with existing Wikidata search)
  • Operator (with existing Wikidata search)
  • Access (with existing suggestions based on TagInfo combinations)
  • Fee (and if so, charge), fee is a yes/no toggle like elsewhere on editing sheets, charge would be a in the format [number] [ISO currency code] [kWh / minute]. If a user selects yes for fee, a charge builder should show a number picker (including decimals), currency picker (suggested to same as payment is, by device location), and a slicer for kWh or minute. This would build into a value of, for example, charge=0.45 USD / kWh or charge=0.45 USD / minute. See the wiki page (https://osm.wiki/charge) for more detail on structure expected.
  • Opening Hours - can show same opening hours editing as normal.
  • Capacity - a numeric value stepper.
  • ref - present on most stations

Finally on sockets, which will likely require its own custom editing card at the top of the editing page under the name card.
At first, the user should be presented with the first dispenser / EVSE they see. It should simply ask what cable is on the end. A list of suggestions can use SF symbols for charge ports and names.

  • Type 1
  • Type 1 Combo
  • Type 2
  • Type 2 Combo
  • GB/T AC
  • GB/T DC
  • CHAdeMO
  • NACS
  • MCS

Since only a few of these are worldwide, the app should determine which to display based off location.

When a connector is chosen, ask the user for speed (in kW), volts (in V), and amps (in A) if available. Note these are likely on a regulatory label.

A user should also be asked how many of this configuration there are. From there, the app can form the complex tags required.

As an example:

Charging station has 4 chargers, each with 1 CCS and 1 NACS connector in the US:

  • User selects Type 1 Combo and NACS, inputs kW, V, A, and that there are 4.
  • The app can then suggest the capacity is 4, socket:type1_combo is 4, socket:nacs is 4, and other subkeys for output, voltage, and current.

In addition to this helpful flow, suggestions can be made by parsing the following sources to start:

Charging stations in OpenStreetMap (https://osm.wiki/charging_station) are a uniquely complex and technical element to tag. As such, to make it easier on editors, Map2Go should lean on suggestions from open data sources. Current tags that would be useful in a generic preset: - Brand (with existing Wikidata search) - Operator (with existing Wikidata search) - Access (with existing suggestions based on TagInfo combinations) - Fee (and if so, charge), `fee` is a yes/no toggle like elsewhere on editing sheets, `charge` would be a in the format `[number] [ISO currency code] [kWh / minute]`. If a user selects yes for fee, a charge builder should show a number picker (including decimals), currency picker (suggested to same as payment is, by device location), and a slicer for kWh or minute. This would build into a value of, for example, `charge=0.45 USD / kWh` or `charge=0.45 USD / minute`. See the wiki page (https://osm.wiki/charge) for more detail on structure expected. - Opening Hours - can show same opening hours editing as normal. - Capacity - a numeric value stepper. - ref - present on most stations Finally on sockets, which will likely require its own custom editing card at the top of the editing page under the name card. At first, the user should be presented with the first dispenser / EVSE they see. It should simply ask what cable is on the end. A list of suggestions can use SF symbols for charge ports and names. - Type 1 - Type 1 Combo - Type 2 - Type 2 Combo - GB/T AC - GB/T DC - CHAdeMO - NACS - MCS Since only a few of these are worldwide, the app should determine which to display based off location. When a connector is chosen, ask the user for speed (in kW), volts (in V), and amps (in A) if available. Note these are likely on a regulatory label. A user should also be asked how many of this configuration there are. From there, the app can form the complex tags required. As an example: Charging station has 4 chargers, each with 1 CCS and 1 NACS connector in the US: - User selects Type 1 Combo and NACS, inputs kW, V, A, and that there are 4. - The app can then suggest the `capacity` is `4`, `socket:type1_combo` is `4`, `socket:nacs` is `4`, and other subkeys for `output`, `voltage`, and `current`. In addition to this helpful flow, suggestions can be made by parsing the following sources to start: - United States Department of Energy's Alternative Fuel Data Center (https://afdc.energy.gov) - Supercharge[dot]info (https://github.com/supercharge-info/supercharge.info)
GA-Kevin-Codes referenced this issue from a commit 2026年04月17日 01:27:12 +02:00
Sign in to join this conversation.
Milestone
Clear milestone
No items
Projects
Clear projects
No items
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
2Go/Map2Go#38
Reference in a new issue
2Go/Map2Go
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?