As STA Green Mobility I would like that also charging stations that are not connected to a back-end system in real-time are statically inserted in the Open Data Hub and made available through it, so to have a better overview of all available charging offer in South Tyrol

noi-techpark / bdp-commons

GNU Affero General Public License v3.0

2 stars 12 forks source link

As STA Green Mobility I would like that also charging stations that are not connected to a back-end system in real-time are statically inserted in the Open Data Hub and made available through it, so to have a better overview of all available charging offer in South Tyrol #582

Closed rcavaliere closed 1 year ago

rcavaliere commented 1 year ago

[x] Data Collector development (linked to shared Google Excel file)

rcavaliere commented 1 year ago

@dulvui we can start with this small development

dulvui commented 1 year ago

@rcavaliere Okay I will start this week. Just to be sure, I just need to use our Google Sheets datacollector with the configuration for this sheet and create new Stations?

rcavaliere commented 1 year ago

Yes, we need the ability to give 3rd parties access to a Google sheet and let them insert their (static) charging stations

dulvui commented 1 year ago

@clezag will to do this task, so he also gets a little introduction to the data-collector side

rcavaliere commented 1 year ago

@clezag @dulvui I have prepared a short technical note with all relevant details on how the data should be inserted in the shared file and integrated in the Open Data Hub tables. There is some fine tuning needed with respect to this indications, i.e.:

[x] I would rename the column in the shared file "POINT_NAME" (plug is more associated to the outlet, which could be misleading
[x] I would foresee a slight different way to generate the stationcodes. I would suggest to have an additional name for the data provider (already inserted), which should be used for the prefix
[x] Please check if the plugs are correctly stored. Probably we need some example with real data to check this (I can provide some data!)
[x] Not all relevant metadata is currently stored. Make sure that all fields are present in the JSON here

230125_SpecificheIntegrazione_DatiStatici_NOI_v2.1.pdf

clezag commented 1 year ago

@rcavaliere Thanks for the feedback! I've implemented the changes outlined in the document. As discussed in person, there are some minor changes to how origin and stationcode are populated.

DB-side now looks fine to me at a cursory glance, but if you have some real data, that would certainly be useful to do a more thorough check.

rcavaliere commented 1 year ago

@clezag wonderful. Today I got a first list of real charging stations that we can use for testing. I will insert the data in the shared file, hopefully tomorrow

rcavaliere commented 1 year ago

@clezag I have inserted some real data of a real operator in the shared file. Let's see if we import it in the expected way!

rcavaliere commented 1 year ago

@clezag I tested this, seems OK for me. Nice work! I would however suggest to leave in the testing environment here until we have the first agreements signed with Data Providers wanting to share data in this modality, like for example VEK as in the real data example we have already implemented..

rcavaliere commented 1 year ago

@clezag we can put this Data Collector in production! The data in the file are already the one to be published

clezag commented 1 year ago

@rcavaliere the data collector is now in production

rcavaliere commented 1 year ago

@clezag very good! I think that our e-mobility web-components still do not show this data, but I open a new user story to check this for the next sprint

rcavaliere commented 1 year ago

@clezag the reference file for the production environment is always the same, or? We have another Data Provider!

clezag commented 1 year ago

@rcavaliere great news! Yes, the spreadsheet is still the same