需要地理跟踪数据库设计建议
我开始设计一个地理跟踪系统,我将不胜感激任何有关数据库结构的建议。数据库应记录点、方向、速度和轨迹
I'm starting to design a geo tracking system and I would apreciate any suggestions regarding DB structure. Database should log points, directions, speed and track
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
在考虑数据库设计时,通常最好列出您想要执行的查询类型以及执行它们的频率。表结构通常不会出现这种情况。
当你只给出一句话描述时,很难推荐一个设计。
When thinking about database design, it's usually best to list out the types of queries that you will want to perform and how often you will perform them. The table structures will usually fall out of that.
It's hard to recommend a design when you only give a 1 sentence description.
PostGIS 在这方面非常受欢迎。
PostGIS is pretty popular for that purpose.
我可以告诉你不应该做什么:不要将所有路径的点作为链接列表存储在一个表中,唉:
获取路径的所有点会变得非常昂贵。
I can tell you what not to do: don't store all your paths' points in one table as linked lists, ala:
Getting all the points for a path gets very expensive very fast.