Yes, you are right. It’s a lot like working in IT, with special data types and some processing.
In typical setting we basically separate the system in three layers: (1) data - file servers and databases, (2) services - Servers that read this data and offer API endpoints that programs can call, that return visualised data in form of images or individual features (see: WMS, WMTS, WFS…) and (3) User/presentation layer - the (web) applications that endusers access (think Google maps / Google Earth and similar type of apps)
On my typical work day I work on one or more of above “layers”. Be it data aquisition, server administration, debugging services, programming end user application, or simply helping our users understand how to use the data… being in IT though means that there also are a lot of nonse meetings involved :)
Yes, you are right. It’s a lot like working in IT, with special data types and some processing.
In typical setting we basically separate the system in three layers: (1) data - file servers and databases, (2) services - Servers that read this data and offer API endpoints that programs can call, that return visualised data in form of images or individual features (see: WMS, WMTS, WFS…) and (3) User/presentation layer - the (web) applications that endusers access (think Google maps / Google Earth and similar type of apps)
On my typical work day I work on one or more of above “layers”. Be it data aquisition, server administration, debugging services, programming end user application, or simply helping our users understand how to use the data… being in IT though means that there also are a lot of nonse meetings involved :)