Closed rcavaliere closed 1 month ago
@rcavaliere I've had a look at the draft, and in my opinion putting this into station metadata could lead to a bunch of issues (e.g. translations, validation, and currently no way to even store or request an image), and it looks much more like POI data in tourism. Even more so if we think about the domains as timeseries vs content.
So before starting with any implementation, I will have a discussion with Rudi to see what similar data he currently has, and explore if and how it could potentially be put into tourism and linked with the mobility API
In addition, Antonietta has brought up that IDM and LTS are themselves in talks with IndependentL about getting accessibility data in the tourism space. Maybe we can find out what they are talking about about, there could be overlap with this issue. e.g. maybe it turns out that in the end we can have a single data stream of accessibility data, combined into a new POI accessibility data set, and link to it from the mobility side.
@clezag @RudiThoeni that's fine for me. But remember that we also have to provide them a possibility to give this data to the Open Data through the Data Browser. They are already waiting us in order to start the data upload. Please find here attached an example of accessibility data associated to a charging station.
I will check this in this sprint. With the latest changes on the Authorization System on Tourism it should be possible to manage that only certain POIs can be edited by some Independent User
@clezag can you provide me the call to get all the public charging stations from the mobility api so i can insert them as pois into the tourism api
Next steps are
@rcavaliere what is the call to get the E-Chargingstation which i should import as Poi, because this here returns a lot :) https://mobility.api.opendatahub.com/v2/flat/EChargingStation/*/latest?limit=0
@RudiThoeni I would just import the metadata of the stations -> https://mobility.api.opendatahub.com/v2/flat,node/EChargingStation?limit=0 probably you should just consider the active stations, then https://mobility.api.opendatahub.com/v2/flat,node/EChargingStation?limit=0&wheresactive.eq.true
ok and consider only stations in south tyrol or all?
you are right, just South Tyrol could be sufficient now. @clezag can you provide here the API call with the bounding box you defined for the web-components with the KPIs (https://webcomponents.opendatahub.com/webcomponent/mobility-e-charging-dashboard)
Yes, already shared that with Rudi. Something like https://mobility.api.opendatahub.com/v2/flat/EChargingStation/?limit=0&where=sactive.eq.true,scoordinate.bbc.(10.377487,46.141620,12.485895,47.105445,4326)
First release by @RudiThoeni - test environment: https://databrowser.opendatahub.testingmachine.eu/dataset/table/tourism/v1/ODHActivityPoi?tagfilter=electric+charging+stations
@rcavaliere is testing and checking if everything is OK. Then we will then set up everything so that IndepententL can start uploading their data
@RudiThoeni today I was finally able to test your development. Looks everything OK, I think IndependentL should have everything for their activity! I will then start contacting them so to introduce the tool. I will ask for the user details that should have access grants with edit power for this specific data. Shall we work directly in production mode or better organize some tests in the testing environment? In the first case, we should set up the production environment first
Hi @rcavaliere I can also deploy everything on production and we start from there...... will inform you when done...... The first step is they register an user on keycloak and i assign the rights to access and edit the data....... They can already do it... go to https://databrowser.opendatahub.com/ then on login go to New user? Register
fill out the Registration Form and give us the names so we can set up everything.......
@RudiThoeni the users are:
Can you please create them and set up the access rights?
@rcavaliere the process is that they register on keyckloak setup their password etc... after this is done i will add the access rights https://databrowser.opendatahub.com/ Right above Login --> New user? Register
@RudiThoeni thanks. In the meantime, I imagine they can do the same also in the testing environment, isn't it? They would like first to make some tests here. Another request: would it be possible to put the coordinates as additional column in this view?
@rcavaliere Yes they can do it also on the testing environment, let me know when they first logged, so i can add the roles, i saw only marianne.viskanic@independent.it logged until now (added her rights to modify) https://databrowser.opendatahub.testingmachine.eu/dataset/table/tourism/v1/ODHActivityPoi?tagfilter=electric+charging+stations
i added a reduced GPS View in the databrowser table view.....
@RudiThoeni perfect, I give her feedback that she has already grants!
@RudiThoeni feedback from IndependentL shared via mail. They request to have the view at plug level and to make some changes to the available fields, both in the general list and in the station detail
Blocked until STA and IndependentL understand how to manage the accessibility characterization at plug level
@RudiThoeni @sseppi I have put in the main description of the user story the detailed requests of IndependentL that we need to analyze together. I will now organize a joint meeting to discuss them
@rcavaliere thank you for the integration of the IdipendentL feedbak.
I share here below the link to the document that summarizes the test to input data from mobile I did today on the charging staton level, but I think that the relationship parent/child shouldn't be a problem:
@ohnewein @sseppi @RudiThoeni @clezag short summary about our meeting today:
Other decisions:
Hi @rcavaliere I changed the dataimport to import each plug. deleted the old one and reimported all data
For scode,sname i was not sure....... There are often strange names, at example here
"scode": "Leitner Energy:CSU Soc. Coop. - Parkdeck - 11kW - Bozen/Bolzano - A. Volta Str. 13/Via A. Volta 13:1",
"sname": "1",
So now I am storing
scode as Id prefixed by echarging_
sname into Title
both are shown in the Databrowser and it is possible to filter for this values
filter on id
filter on title
@sseppi I think the "like" should be the default operator in the Databrowser filtering, also noticed that when I am on page 2, the filtering does show "no results found" this is a bug maybe you already inserted it as issue
i think is ready for testing now
@sseppi I think the "like" should be the default operator in the Databrowser filtering, also noticed that when I am on page 2, the filtering does show "no results found" this is a bug maybe you already inserted it as issue
@RudiThoeni Thank you for the updates and for finding the bug, I will do some testing and create a dedicated issue for it.
@RudiThoeni I tested the updates you did and I found a Bug.
If you try to open the station (ID: echarging_leitner energy:kronplatz - parkplatz 10 - 22kw - reischach/riscone - seilbahnstraße 10:1) at the following link you get a 404 error message:
But if you try to open the following one (ID: echarging_ecogy gmbh:firmensitz ecogy:1) you don't get it:
By trying with other station, I noticed that the 404 problem occurs every time that there is a / character in the ID string, could it be that the browser and the API misinterpret this kind of character?
Can you please have a look and let us know?
@sseppi yes you are right the error is because of the "/" in the Id it is interpreted as a route......... will fix this by simply removing this character.....
But first i need an answer from @rcavaliere if scode or sname or both of them are the fields they are searching / filtering........
I think sname is the right field, i will store this field into the title.
What i could do is also store scode + sname into the Title field so with the like filter it should be searchable both?
But as sais before there are a few examples (see https://mobility.api.opendatahub.com/v2/flat,node/EChargingPlug?select=scode,sname&where=sactive.eq.true,scoordinate.bbi.(10.233765,46.236853,12.568359,47.249407,4326)&limit=0) where sname contains only a number and scode contains the naming, i think this has to be fixed on mobility datacollector side ;)
Here some examples
{
"scode": "Leitner Energy:CSU Soc. Coop. - Parkdeck - 11kW - Bozen/Bolzano - A. Volta Str. 13/Via A. Volta 13:1",
"sname": "1",
},
{
"scode": "ECOGY GmbH:Taser - Seilbahn / Funivia / Cable Car:2",
"sname": "2"
},
{
"scode": "Leitner Energy:Kronplatz - Parkplatz 12 - 22kW - Reischach/Riscone - Seilbahnstraße 10:1",
"sname": "1"
},
{
"scode": "VEK:HYC_150_19BZ00056_Glurns:1",
"sname": "1"
},
@RudiThoeni the e-charging stations mentioned here are a special case, in this case we don't have an API with real-time data, but just static information. In this case the data is automatically retrieved from this Google Spreadsheet: https://docs.google.com/spreadsheets/d/1ucCQzAVGmvyRpeq-lIPffALQaWcG4LfPakc2mjt79fY/edit#gid=0
I am not sure if IndependentL will evaluate also these charging stations (probably yes), in this case having just sname won't work. So probably what you could do is to implement such a logic:
if origin != [one of the organizations listed in this Google Spreadsheet, column "Data Provider"] then consider just sname
otherwise consider scode
Ok i implemented your suggestion, for spreadsheet data i used scode, and for all other sname as Title In the Databrowser now we visualize only the Title and not more the Id otherwise it creates confusion
i think it is ready to test
@RudiThoeni perfect, I also think so! I think @sseppi wants to test first some front-end aspects improved by the MetaEsse, and then IndependentL could start making some tests on the field.
@rcavaliere @RudiThoeni thank you for your contribution.
I have a meeting with IndipendentL planned beginning of next week to present our solution. I will keep you updated.
Reminder: current functionalities for IndependentL are at the moment in testing environment (Data Browser)
All changes has been put in testing and can be tested at the following link: https://databrowser.opendatahub.testingmachine.eu/dataset/table/tourism/v1/ODHActivityPoi?tagfilter=electric+charging+stations
Since all required feature are now online into production, I close this issue. In case of bugs or other requests from the client, I suggest to open dedicated issues.
You can see the Dataset at the following link: https://databrowser.opendatahub.com/dataset/table/tourism/v1/ODHActivityPoi?tagfilter=electric+charging+stations
Expected workflow:
231002_IndependentL_Vorschlag-Erhebungsdaten.pdf
Test environment: https://databrowser.opendatahub.testingmachine.eu/dataset/table/tourism/v1/ODHActivityPoi?tagfilter=electric+charging+stations
Additional requests:
To do:
24-08-06_Vorschlag-Erhebungsattribute Traduzione.xlsx