Archive

When I decided to restart my blog a month ago, I wanted to move from Blogspot and use this opportunity to try some new technologies. Static website generators always looked like a very interesting technology and my blog seemed like an ideal candidate for the first try. There are many static website generators available, the most prominent ones are Jekyll, Hugo or Next. But my eye got caught by another one - Wyam. It has nice clear documentation, seems to be well maintained and it is written in C#, so when I need, I can dive into the source code without any problems.

I am working on a small side-project, that uses ASP.NET Core API. This application will be used only occasionally so it would really benefit from using the serverless approach. Unfortunately Azure Functions doesn't provide support for running ASP.NET applications, instead, you can use HttpTrigger. Azure Function documentation says:

In the previous post, I set up my blog to run on Azure Static Website. However, it was accessible only on the domain provided by Azure blogkabrtcz.z6.web.core.windows.net and I'd like to use my own domain blog.kabrt.cz.

It has been possible to host static files in Azure Storage for a long time, but there were some limitations. Probably the most important one - you weren't able to specify the default document for a directory. You could display a page with the URL https://blog.kabrt.cz/index.html, but URL https://blog.kabrt.cz would return the 404 page. There were ways around it (e.g. Azure Functions proxy), but it felt too cumbersome. With the introduction of Static Website in Azure Storage, this limitation is gone and I'd like to explore this feature and move my blog to Azure.

In the last few weeks I was doing some client-side development in TypeScript. It is amazing tool, that increased my productivity in client-side development dramatically.

We are using Entity Framework in our solutions and for this project we'd like to take advantage of new features of the Entity Framework, especially Code First development and data migrations.

In the previous post I have shown, how to do simple filtering of the OSM data with the SpatialLITE library. Today I will go a step further and do something more complicated - extract data from OSM file within specific bounding box.

I'm a big fan of the OpenStreetMap project, so when I released the first version of the SpatialLITE library last week, classes for working with OpenSteetMap data couldn't be missing in the project. Right now the library supports OSM XML files (without compression) and OSM PBF files, both for reading as well as writing. And how can you work with OSM data? How does SpatialLITE library compare with other tools in terms of speed? Let's find out