1

which is suitable approach in gps tracking web application:
1)Save only latitude and longitude in database,And use reverse Geocoding for showing address of point to user in web application.
2)Save latitude and longitude with reverse geocoded address in database when gps device send latitude and longitude to server.
But i have problem for each approach:
for first approach: When i want to show history of fleet locations to user i need to reverse geocoding many point to show addresses of any point to user that it take many time to reverse geocoding with google maps api and other problem is google maps geocoding api has limitation(2500 request per day).
for second approach:If i save address of latitude and longitude in database because every 2 minutes gps device send new point to server and saving these addresses to database can make redundancy at database! or increase database.I use postgresql DBMS and i don't know how many data can i save on the database.
How can i solve this problem?
You can see history of fleet in the following picture with populated with addresses!.But i don't know how they can implemented it!.
enter image description here

4

1 回答 1

2

数据库中的数据量不是问题。

地理编码的最佳做法是在数据输入时进行。这样,您可以在需要时聚合它,并在报告中快速显示它,而无需重复地理编码。您将需要找到可以处理您的流量负载的地理编码提供商。鉴于您的需求,可能值得购买地址数据库并自己进行地理编码。

于 2012-08-20T14:38:21.457 回答