You mean based on this url and the response content-type header i should be able to construct a url?
You don't really need to construct the URL further. Using that URL will get a response containing image data. Then you just use the content-type to process it. Although your image library might auto-identify it as well. There's also the content-disposition header that will give you the original file name.
You can't rely on that existing, though.
Wrt the HSL routing APIs, this is the starting point: https://digitransit.fi/en/developers/apis/1-routing-api/
Is https://dev.hel.fi/paatokset/v1/ still the way to go if I’m making a new application?
Onko kartan https://ulkoliikunta.fi/ liikuntapaikkojen kuntotietojen päivityskäyttöliittymä jaossa avoimena koodina?
@arvileino I notice the cocumentation is non-existent. As far as I know it's fairly standard and robust Webpack/React setup. If you run into problems, ping tituomin here. I know he is quite busy these days, but should be able to point you to the right direction if there is a specific problem. You can also file an issue in the repo!
Terve, onko teillä mahdollisesti suunnitelmissa muuttaa infopankki palvelun verkko-osoitteita lähiaikoina? Olemme tekemässä maahanmuuttajien koulutus appiin (SIMHE - hanke) web-view toteutusta ja haluamme olla varmoja että osoitteet pysyisivät ainakin jonkin aikaa samoina.
Hi, our team is building an app in the innovation project with the city of Helsinki and Metropolia.
We are running the linkedevents api locally for testing purposes but we noticed that we need to authenticate somehow to do POST requests.
How can we create the credentials needed / change the permissions to allow POST requests without authentication?
@RikuMantysalo well, most places where they have put up Linkedevents have implemented their own SSO that talks to Linkedevents. If you want to do those requests directly to Linkedevents, my suggestion would be to e.g. use the Django admin to add an api key to a data source in the database. Then you can add that api key to all requests to allow POST and PUT :)
I think that's the only way to do POST and PUT without external authentication :)
So the idea is that if Linkedevents DataSource has
apikey, then putting that in the apikey request header will allow the request to do POST and PUT in the /v1/event endpoint as long as the publisher in the json is the same organization as the Organization that owns the DataSource.
Other endpoints don't currently support POST and PUT, as we haven't needed to POST e.g. Places or Keywords. There is a pull request on that though
@joseymetro Hi, Josey.
You have found the correct place and deduced correctly that Tunnistamo participation is required :laughing:
Unfortunately at the moment we don't have a process for new applications to use Respa.
I'll see if I can get its project manager to see about this. And what it would require from our end to get Tunnistamo more welcoming to new apps.
You have found the correct place and deduced correctly that Tunnistamo participation is required :laughing:
Unfortunately at the moment we don't have a process for new applications to use Respa.
I'll see if I can get its project manager to see about this. And what it would require from our end to get Tunnistamo more welcoming to new apps.
@joseymetro a mobile app for Respa sounds very interesting! At the moment only our own services use Respa, but we would like to change that. Using Tunnistamo is required for Respa. At the moment only our services use Tunnistamo but technically it should be possible for your app to use Tunnistamo as well. I will dig into this and see what is possible and get back to you.
is there any GIS Developer on here ?
Hello There! :)
I'm from Brasil, my company is an outsourcing and turnkey projects specialist with many technologies, we have clients in Spain and the UK, and want to get new clients and opportunities around the world.
How is the outsourcing market in your country?
@gislayer sorry for not answering earlier, but in January we had never used pbf tiles :D Now I have been practicing creating an openmaptiles (https://openmaptiles.org/) pbf vector tileset and serving it with mapbox gl style. However, we haven't created any javascript openlayers clients for that yet.
So we have pbf tiles that are mostly meant for developers in new projects in the future.
Moido. Ajattelin heittää linkin myös tänne. Tein testimielessä tälläisen toteutuksen joka hakee Open311 API:n avulla palautteita ja niihin voi myös tehdä suodattavia hakuja. Github Pagesilla pyörivä versio on ensimmäinen raakile ja jatkossa ajatuksena oli tehdä esimerkiksi funktiot hakemaan aiemman vuoden kaikki palautteet ja suodattaa niistä erilaisia sisältöjä, kuten vaikka siirtokehoituksiin, kyltteihin, monttuihin jne liittyvät palautteet. Olettaen, että tiketit eivät jää vuosikausiksi roikkumaan Kaupungin puolelta. Tällä hetkellä myös vastuu-yksiköt/palvelukuvaukset ovat hieman "ylimääräistä" dataa, koska suurin osa palautteista näyttää olevan "Kaupunkiympäristön" alla. https://aarni-k.github.io/helsinki-pilalla/
Kiitos, hyvää työtä! Palautteiden metadatassa on valitettavasti hieman tiedostettua ongelmaa sen suhteen, miten hyvin "palaute hoidettu"-status vastaa oikeasti sitä, että itse ongelma on korjattu vs. ongelma on lähetetty alihankkijalle korjattavaksi. Koskee erityisesti kaupunkiympäristöä. Ihan vaan tiedoksi.
@aarni-k Näyttää mielenkiintoiselta! Voisiko sen lisätä Helsinki Region Infosharen sovellusgalleriaan (https://hri.fi/data/fi/showcase)?
@aarni-k Kiitos! Laitoin sen äsken HRI:hin, onko ok näin: https://hri.fi/data/fi/showcase/helsinki-pilalla. Kuvia, tekstiä ym. voi vielä toki muokata.
@aarni-k Toki voi. Muutoksista voi ilmoitella meille vaikka tätä kautta tai sähköpostitse hri@hel.fi.
@roginvs Respa doesn't use API keys as such, rather the API is open for anybody to browse, but actually PUT/POSTing reservations requires logging in with an SSO such as the Helsinki tunnistamo.
You can contact respa product owner petteri.l.laine@hel.fi to ask how to proceed (and are there plans to allow 3rd party UIs to authenticate with our SSO), but my first step would be just to create a client that can do GET requests and worry about authentication later on :)