Will you use a CMS for your Web Site? That will provide user id, name handling. They submit using their id. If you want to use a name, their login name will be unique. Use either.
Are the points significant? On the Bouddi Coastal Walk, the Toorongong Lookout would be a named point while other excellent spots for photography have no named point. The same with a marathon. To allow setting of meaningful records, the courses are out and back. The start, turn around point, and end point are meaningful. SOme marathons have multiple checkpoints. You might want named points.
The rest of the design will work. SQL makes life easy when you want related data. Something like all the users who passed through a point.
Point identification can be a problem. Ten people passing through the one point could record ten sightly different GPS points.
You can plot the courses on OpenStreetMap.
You could use PostGreSQL as a database with GPS specific data types then you are locked into a database. Better to have something to work in any database.
With a few thousand users and typical plenty of server memory, a user id lookup will be instant as the index to the user table will be in memory. The same with hundreds of names. If you have 20 million users and 300 are out eventing, the 300 will be cached in memory. Good databases will handle that.
Good databases also make changes easy. You can instantly add an index to the userName if you need it.
Go with what you designed.
Are the points significant? On the Bouddi Coastal Walk, the Toorongong Lookout would be a named point while other excellent spots for photography have no named point. The same with a marathon. To allow setting of meaningful records, the courses are out and back. The start, turn around point, and end point are meaningful. SOme marathons have multiple checkpoints. You might want named points.
The rest of the design will work. SQL makes life easy when you want related data. Something like all the users who passed through a point.
Point identification can be a problem. Ten people passing through the one point could record ten sightly different GPS points.
You can plot the courses on OpenStreetMap.
You could use PostGreSQL as a database with GPS specific data types then you are locked into a database. Better to have something to work in any database.
With a few thousand users and typical plenty of server memory, a user id lookup will be instant as the index to the user table will be in memory. The same with hundreds of names. If you have 20 million users and 300 are out eventing, the 300 will be cached in memory. Good databases will handle that.
Good databases also make changes easy. You can instantly add an index to the userName if you need it.
Go with what you designed.
Statistics: Posted by peterlite — Thu Jun 13, 2024 8:34 am