Trip Syntax
Table: Overview
The first table in your SQLite file is named bewa_Overview with fields according to following.
Note
Regarding validation: Some fields are checked for syntax and must comply to that.
| Column | Description |
|---|---|
| InnerId | The InnerId is used to connect each row to date notes in table bewb_Events. It consists of a six characters long string generated randomly in Sqlite with lower(hex(randomblob(3)))Syntax: <xxxxxx> |
| ParticipantGroup | Could e.g. be Family, Private, or Work. Syntax: <string> |
| OuterId | The OuterID is exposed to end-user of the web app. Normally you can take the first letter of the TripDomain and the first letter of ParticipantGroup and add a chronological number. Syntax: <letters and dashes and serial numbers of your choice> |
| OverallDestination | Type in you trip primary destination. E.g. Finland, or Italia, Spain etc. Syntax: <string> |
| DepartureDate | Your departure date in ISO format. Syntax: YYYY-MM-DD |
| ReturnDate | Your return date in ISO format. Syntax: YYYY-MM-DD |
| MapPins | The main stops of your trip that you want to plot on the map. Syntax (multi-line accepted): [ NAME_OF_MAP_PIN ]( LATITUDE, LONGITUDE ) |
| TripDescription | A short description that explain the aim of the trip. E.g. My fantastic summer trip to France. Syntax: <string> |
| PhotoStarttime | For use with Immich. If you leave your home at let say 8 pm and don’t want to include photos from earlier on departure day, then you can set a time here. If left empty, all photos from departure day will be included. Syntax: HH:MM |
| PhotoEndtime | For use with Immich. Same as above, but for return day. Syntax: HH:MM |
Table: Events
The second table in your SQLite file is named bewb_Events with fields according to following.
Note
Regarding validation: Some fields are checked for syntax and must comply to that.
| Column Name | Description |
|---|---|
| InnerId | Reference to corresponding InnerId in table bewa_Overview.Syntax: <xxxxxx> |
| Date | Your date in ISO format. Syntax: YYYY-MM-DD |
| Events | This is your fully description of what you did this day. Syntax (multi-line accepted): <string> |
| Accommodation | The name and the address of your accommodation. Syntax: <string> |
| AccommodationCountry | The name of the country you stayed in during the night. Syntax: <string> |
| AccommodationCoordinateAccuracy | Possibility to mark the accuracy of the coordinates. Syntax: <string> |
| AccommodationCoordinates | The gps coordinates of your accommodation, e.g. 59.329444, 18.068611. Syntax: lat_decimal,lng_decimal |
| TravelParticipants | The name of your travel buddies, separated by comma. N.B. Not exposured in web app. Syntax: <string> |
| AdditionalNotes | N.B. Additional notes not exposured in web app. Syntax (multi-line accepted): <string> |
| CountriesDuringDay | This field is for enhanced statistics. Enter all countries in cronologial order during that day, separated by comma. The country names need to conform to the country names defined in ContinentCountries. In front of the country name prefix *, **, and + is allowed. Read more under Special syntax used for Countries During Day (Events).Syntax (prefix allowed): <country name without space>, <country name without space>, <country name without space> [...] |
Special syntax used for Countries During Day (Events)
| Prefix | Function |
|---|---|
| * | Shorter visit of significant importance |
| ** | Very short visit of without significant importance |
| + | Restore, counts only if * and ** count |
Note
Countries During Day: When a prefix is used in front of a country name in field CountriesDuringDay in table
bewb_Eventsit affect the Statistics page.