How are you using GeoTime?
The recommended system specifications for GeoTime depend greatly on the type of work being done. Some tasks may require higher-performance hardware in order to ensure the best GeoTime experience.
GeoTime produces an interactive 3D picture of your data. To allow you to interact with the picture, GeoTime must keep all of that data in memory. As the amount of data increases, GeoTime needs more computing resources to quickly redraw the picture every time it is changed. A computer that meets only the minimum requirements cannot support the demands caused by larger workloads.
Consider how your organization intends to use GeoTime. A computer that is intended to run only office applications and Internet browsers may have difficulty using GeoTime with larger data sets.
Which Configuration is Right for You?
The table below provides guidelines for three configurations. Each configuration is our minimum recommendation for consistent performance at that level.
IMPORTANT:These guidelines are intended to help you determine the required performance level of your workstations. This involves the amount of data that will be typically used with GeoTime by your users. We describe this data in terms of “rows” in a spreadsheet that can be simultaneously loaded into GeoTime. These are just estimates!
Typically, each “row” in a spreadsheet becomes a single event in GeoTime. Similarly, each cell tower and annotation count as additional objects. If you have 4000 towers, 4000 call events, and 50 annotations, there are 8050 objects that GeoTime must manage while you are working.
Due to the number of variables involved, Uncharted Software Inc. DOES NOT guarantee that performance will match or exceed the following estimates.
- Minimum: describes a workstation that can handle small amounts of data in GeoTime.
- Better: describes a mid-range workstation that is capable of handling larger amounts of data, but not the largest data sets.
- Best: a workstation capable of pushing GeoTime to its functional limits, with potentially hundreds of thousands of loaded Events.