Please do this discussion and send me as soon as possible.
i will be waiting for your response.
The chart you select to represent your data will be influenced by many factors. Kirk (2016) has put each chart into the five main families below:
Select a chart type from the text and discuss what the chart is used for and why you selected it. (The author has included a lot of different chart types in our course book).
I am answering your question with aspect to the data:
(More information is needed if you are asking about any another aspect)
Hierarchical Chart: It is used when one object is directly related to another object and it is also used to define its own properties (somehow similar to the parent child relationship).
- It enables a user to easily understand the entire working structure.
- It is used to define many real life examples like if there is a parent organization and it has various child organizations and they all have different properties.
- The information is shown in the form of different levels.
Relational Chart: It is used for describing relation among various entities/Categories. It has below advantages:
- Using this chart we can define the different types of relations among varoius categories/entities(how they are connected).
- With the help of relations it is easy to understand by the working user.
- This chart is similar with the practical world as everything is corelated with each other. So we can define one object easily by refrencing from the other object.
Temporal Chart: It usually stores data in form of Valid time and Transaction time.It is used to represent time periods.
- It has ability to define valid and transaction time period attributes and bitemporal relations
- The transaction time is maintained by system.
- They have various constraints like non-overlapping uniqueness and referential integrity
- Temporal queries can be done at current time, time points in the past or future, or over durations
- They predicates for querying time periods.
Spatial Chart: Spatial data can represent rich geospatial attributes in a condensed manner that’s semantically easier to understand and reason about.
- Running queries on spatial data requires geometry and geospatial operators that are implemented in most advanced relational database systems such as PostgreSQL.
- However, spatial data is hard to run query on. Especially certain join queries that require many geospatial measurement or operation for join condition.
- Spatial data also hard to partition.That's why it is harder to query.
- Spatial data also requires good visualization to make sense. While this is easy for point based queries or geolocation type of queries, it’s harder for complex geometry types.
Please do this discussion and send me as soon as possible. i will be waiting for...