Timestream weird behavior with measure name

Hi, the Latitude is not a special keyword. So no issues using Latitude.

• Measure names in Timestream are case sensitive. So Latitude and latitude will be two different measure names.
• Timestream offers flexible and incremental schema definition. This means you do not need to define schema upfront while creating a table. However, we do assign the type to a particular column (Latitude in this case) first time system ingests a measure name. if you first ingested Latitude with Big Int, it is not possible to change it to double. The system will treat Latitude as BIG INT.
• You can check the schema of your table (Types for each column in table) in the query editor mode of the console

Hope this helps.