eipar issueshttps://git.nilu.no/rextapi/eipar/-/issues2018-08-21T09:42:46Zhttps://git.nilu.no/rextapi/eipar/-/issues/4no presence of station ID in api results2018-08-21T09:42:46ZJean-Marie Lepioufleno presence of station ID in api resultsWhile sending a request to your endpoint aq_measurment, output related to the station is only the name of the station.
This information is highly case/space/utf8 sensitive. Many user will have problems related to this.
Besides, the info...While sending a request to your endpoint aq_measurment, output related to the station is only the name of the station.
This information is highly case/space/utf8 sensitive. Many user will have problems related to this.
Besides, the information called rawreadingid seems to be the ID of the timeseries which confused me a bit at the beginning.
It would be easier to get the ID of the station, like 'D6', which corresponds to the station at Pearse Street,Dublin.https://git.nilu.no/rextapi/eipar/-/issues/3endpoint in order to get metadata of the stations in the api2018-08-29T13:00:37ZJean-Marie Lepioufleendpoint in order to get metadata of the stations in the apiThere is so far no possibility of getting the metadata of the stations through the api.
As a first solution, I went on https://gis.epa.ie/EPAMaps/default and gathered manually all of the metadata with EPA gis tool.
You can find the data...There is so far no possibility of getting the metadata of the stations through the api.
As a first solution, I went on https://gis.epa.ie/EPAMaps/default and gathered manually all of the metadata with EPA gis tool.
You can find the dataset in the folder /inst/docmeta_aq_stations_jml.csv. These are the information one required.
I added this dataset to the R-package and called it 'unofficial'.
Because taken manually, I am sure the dataset contains error (especially the LAT/LON values).
Besides, some stations might be missing, and I only managed to get the element measured (PM10, NOX...) but not the timeresolution, so Icould not get in the metadata element information such as PM10_1 or PM10_24 as present in your api.
It will be nice to have a metadata endpoint to you API, like /aq_metadatahttps://git.nilu.no/rextapi/eipar/-/issues/2swagger with uncomplete information regarding the paths2018-08-21T09:16:38ZJean-Marie Lepioufleswagger with uncomplete information regarding the pathsThe current swagger doc at https://air-tst.epa.ie/api-docs does not describe well the different paths;
for instance operationId is not given, and the names of the parameters either.
As a consequence, it makes the automatic building of th...The current swagger doc at https://air-tst.epa.ie/api-docs does not describe well the different paths;
for instance operationId is not given, and the names of the parameters either.
As a consequence, it makes the automatic building of the client api not possible.
As a first solution, I added a swagger schema ( in folder/inst/doc/swagger_jml.json) with all the required information. The file is called then instead of the one at https://air-tst.epa.ie/api-docs.
If someone at EPA could update the swagger file according to what I wrote, it would be nice.