Datasets encoding format

[AnaBelgun]

Question from a developer:
How do you support the differences in encoding format for different datasets. For example, sometimes data is encoded with the assumptions of Z-scores, sometimes it uses Googles S2 or Ubers H3 for tiling. Some data is just latitude and longitude.

There is also the question of data that is embedded on a map projection like Mercator or something.

[niktayv]

TerriaJS primarily handles spatial data location through standard Latitude/Longitude coordinates found in common formats (GeoJSON, KML, CSV) or served by standard services (WMS, WFS). It displays this data within standard map projections (WGS84/Geographic or Web Mercator). Specialized spatial indexing schemes like S2/H3 are not consumed directly as a primary data format but are usually handled by converting the data to a standard format (like GeoJSON) or via custom backend services. Z-scores relate to the attribute values of data, which TerriaJS uses for styling, rather than the spatial encoding itself. The flexibility comes from supporting various standard data types and services via its catalog system.

Please refer to the list of supported catalog items in the documentation here.