I am pleased to announce the beta release of my latest volunteer project: the Provita Geoportal. In previous posts I discussed some of the design and implementation details of the project, but I was waiting for the public release of the product to share the end-user and admin functionality of the site.

The purpose of the Geoportal is to enable professionals, researchers, academics and the general public to find, pre-view and download geospatial data sets about Venezuela. These data sets are published by the Provita team and are associated with the organization’s mission and projects.

Here, I continue discussing implementation details of the Provita Geoportal. In my first post on the topic, I discussed the overall design of the Geoportal. I followed with a more detailed description focused on data organization and storage.

In this post (Updated Feb 17, 2021), I describe the approach used to provide an access control mechanism for Admin users to populate and maintain the content of the Geoportal.

This is a follow up to my earlier post discussing the design of a Geoportal for Provita. In that post, I mentioned that we use the serverless JAMStack approach, with no servers and no databases to monitor and maintain.

So, “without” servers or databases, how are we organizing and managing the data of the site?

In this post, I answer the question by describing the data organization and the storage aspects of the Geoportal.

Wow! I can’t believe it’s been five years since I developed Rikitraki. A lot of things have changed in Web development since then, so I think it is time to implement some sorely needed renovations.

Some of the changes are simply to bring the code up to snuff with today’s best practices. But some other changes will be functionality improvements that I have been thinking about for a long time.

In this post, I lay out what I am thinking for the next big release. Comments and suggestions are greatly appreciated.

Over the past few months, I have been working on a cool new project for the Provita folks.

Provita wants to maintain and publish a collection of geospatial data sets to enable researchers, 3rd party organizations, and casual users to have access to up-to-date Geographical Information Systems (GIS) data for supporting ecology, biodiversity, and environmental protection applications, studies and analyses.

In this post, I introduce key project requirements and the overall design of the app.

Back in September, I described the deployment details of the Venezuelan Red List of Ecosystems site (Libro Rojo de los Ecosistemas Terrestres de Venezuela).

In this post, I discuss the approach I used for content management.

Deploying the site

In March (wow, it feels like eons ago!), I posted a discussion on the design of the Venezuelan Red List of Ecosystems site (Libro Rojo de los Ecosistemas Terrestres de Venezuela).

In this post, I describe how the project is deployed in production using Netlify.

New Project Results

Back in September, I got involved in a new project with the Provita Non-Government Organization (NGO) to publish the content of the Venezuelan Red List of Ecosystems (Libro Rojo de los Ecosistemas de Venezuela) on the web.

Today, after a few months of teamwork, I am excited to share the results:

New Project

I am really excited about a new project that I am starting for Provita. Provita is an environmental Non-Government Organization (NGO) in Venezuela which has been working hard for decades for the conservation of endangered species and their habitats in my country of birth. I am honored to have been accepted as a volunteer in this great organization, and I am looking forward to contributing my efforts to the mission.

As soon as I have some results to show, I will be posting the details here. For the time being, I wanted to take this opportunity to discuss the requirements of the project and how I went about selecting the development tools that I chose.

The logging visualization site integrates data from multiple sources

The purpose of this post is to document the data processing steps applied to the original sources of the data, to create the layers used by the logging visualization site.