Tekin Uslu

On his LinkedIn profile, Tekin describes his field in one sentence (in Dutch):

Sinds 2006 bouw ik aan de brug tussen geo-informatie, data engineering en IT-architectuur

In English: since 2006 he has been building the bridge between geo-information, data engineering and IT architecture. That is his own statement. On this site we therefore consistently use the wording "by his own account since 2006". It refers to Tekin's personal experience, not to the experience of TechinFlow B.V., which is a new company.

His GitHub profile (github.com/tekinuslu) is in the name of Tekin Uslu, with Haarlem as the location and a short description of his focus on geo-ICT software and product development. The account was created on 16 March 2014. GitHub shows that date publicly, so anyone can check it without an account.

The three fields in his own description are reflected in what TechinFlow offers: geo-information in the GIS and digital map solutions, data engineering in the data platforms and IT architecture in technology and software consultancy.

Tekin's GitHub account holds his own repositories and forks. A fork is a copy of someone else's project. We leave forks out here because they are not his own work. The table shows the own repositories that relate to geo-information, with the description shown on GitHub. They are public on GitHub; we make no statements about what they were used for.

Licence according to GitHub on 12 October 2026: atlas_prototype carries an MPL-2.0 licence. The other three repositories have no licence file, so reusing that code requires permission.

The Locatieserver repository covers the same ground as the guide to address search with PDOK on this site: searching for addresses and showing them on a map with the national geodata services.

On 28 January 2026 Tekin announced on LinkedIn a live online workshop, held on 13 February 2026: "Python voor GIS (BAG → ArcGIS Online)". In the announcement he describes the content. It covers reading and filtering BAG data (the Dutch national register of addresses and buildings) with ArcPy and GeoPandas, error handling when a source is offline or the data is corrupt, logging, and automatically updating layers in ArcGIS Online. According to the announcement, the aim is a production-ready script rather than a "Hello World" example.

In a post of 12 February 2026 he describes The MasterDev (Geo)Data Challenge. This is an in-company day for GIS and data teams, in which a team works on a pipeline using its own data and its own use case. In it he mentions, among other things, logging, ownership of a pipeline and the question of how to secure this in an architecture with ArcGIS, FME, Azure and SQL. The associated site is themasterdev.nl.

Both posts show which subjects Tekin writes about publicly. They say nothing about clients. The workshop's subject, processing geodata from a base registration reliably and automatically, comes back in the guide to publishing open data as a municipality (in Dutch).

Below are Tekin's areas of expertise, each with the public source that shows it. We include only subjects for which such a source exists.

This list is deliberately short. An area that only comes up in a CV or a conversation belongs here only once a public source exists. When a new source appears, such as a publication, a talk or a new own repository, we update the table and the date at the top of the page. You can see how these areas feed into the company's services in the GIS viewer for municipalities and the open data platform.

A founder's profile usually lists employers, clients and projects. This one does not, for three reasons.

First, work that Tekin did before TechinFlow is not work of TechinFlow B.V. Projects the founder carried out before TechinFlow are not references of TechinFlow B.V. A list of names on the company's site would blur that difference.

Second, we name an organisation only if we can support it with a public source and the organisation has given permission. For Tekin's employers and clients that is not arranged at present, so they are not listed.

Third, we leave out forks on GitHub. Whoever forks a project makes a copy; that says nothing about who built it.

If you are looking for references of the company for a tender: there are none yet. Once TechinFlow has completed assignments of its own, we will share references in a tender on request and with the client's permission. More about the company itself is on the about page; you can ask a question through the contact page.