# Best way to store data

**URL:** <https://community.influxdata.com/t/best-way-to-store-data/28471>\
**Category:** InfluxDB 2\
**Tags:** influxdb\
**Created:** [February 7, 2023, 10:20am UTC](https://community.influxdata.com/t/best-way-to-store-data/28471 "2023-02-07T10:20:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![marco.morgia](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/marco.morgia/32/12588_2.png) [@marco.morgia](https://community.influxdata.com/u/marco.morgia)\
**Post date:** [February 7, 2023, 10:20am UTC](https://community.influxdata.com/t/best-way-to-store-data/28471/1 "2023-02-07T10:20:36Z")

</div>

Hello everyone,

I’ve a c# application that read some data in JSON format from a WS. Thi data contains info like :  
Name  
Speed  
Latitude  
Longitude

I want to know what is the best way to store this data.  
E.G. A single insert with same timestamp for each value (1 insert for name, 1 for speed and soo on), or maybe insert unique string for timestamp for all data and for example make a field comma separated?

Thanks

---

<div class="post-metadata">

**Author:** ![grant1](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/grant1/32/15107_2.png) [@grant1](https://community.influxdata.com/u/grant1)\
**Post date:** [February 7, 2023, 10:40am UTC](https://community.influxdata.com/t/best-way-to-store-data/28471/2 "2023-02-07T10:40:11Z")

</div>

Welcome @marco.morgia to the InfluxDB forum.

To collect your data, there are many ways (Telegraph, [loading annotated CSV](https://docs.influxdata.com/influxdb/cloud/write-data/developer-tools/csv/), Node-RED, etc.).

To help you decide the best way to store your data, I found [this webinar from Influxdb about Schema Design for IoT](https://www.youtube.com/watch?v=d99oCnOyA4k) to be extremely helpful. Watch it all the way through, then think about your own data. Write down your field names & tag names, then go back and watch the video again to make sure it still makes sense.

An hour of planning how you want to store your data will go a long way. If you jump right in, you may find yourself living with poor planning decisions.