The world of Geospatial is, like any other technology, going to have some inherent risk. Part of making a program stronger should be looking at those risks and planning strategies to mitigate them. This article covers risks and mitigations in three sections, Program, Technology, and Operational, then wraps up with a recap and final thoughts.
Tip of the Day – Create indexes for all spatial and attribute tables
Today’s Tip Create indexes for all spatial and attribute tables Discussion Today’s tip arises as a result of setting up layers using a Foreign Data Wrapper in Postgres. The layers were initially loading quite slowly, and I realized that I had not added a UniqueID, which I mentioned in TOTD 002, or any sort of an index. Before we get …
Tip of the Day – Ensure you have a Unique Identifier for each table in your database
Today’s Tip Ensure that you have a unique identifier attribute for each table in your database Discussion This is another tip that arises from me doing a task, and realizing I forgot something critical. In this case, the task involved creating a table, trying to perform an operation on said table, and encountering an error or limitation due to a …
Tip of the Day: Consult subject matter experts before removing existing attributes
It begins Welcome to the first “Tip of the Day” on Get Spatial. This series will be used to capture particular events that stick out at me during the course of a workday. These tips could range from map design to database development, or data conversion to business practices. Each tip will be presented and then followed with more detailed …