Quote:
Originally Posted by wulfir
Quote:
Originally Posted by dmnt
It's now reworked so that it will use Google API for terrain data but Google limits the amount of requests so please don't use it too much.
|
What is 'too much'?  |
Google has the following limit enforced:
https://developers.google.com/maps/d...n/usage-limits
2500 elevation API requests per day, 512 locations per request (we're using 480 per request) and 10 requests per second.
Every map has 31284 hexes to fill and it needs 66 requests per map. Therefore, my site can give you 37 map downloads per day, no more, unless I start paying google for the service. If you need more (like you created 40 maps a day...
) you can always download the code yourself from
https://github.com/tvenhola/SPMBT-maps - it's free as in beer - and try it out. You need to apply your own Google developer API key, free of charge.
The new version that uses Google API isn't yet documented in the README (so it's not mentioned on the github page) but it's a completely new approach: no downloading of satellite data files, no need to install image magick and no west-east constraint, but you need the Google api key. And still Linux or some way to make it work under Windows.
Requires: Perl, some Perl libraries such as libcurl-perl.
Map output will do some automagic stuff which should be mentioned in the user manual:
- The lowest point on map will be made "level 0"
- If anything is over 150 meters high from the lowest point, it's clipped
- Resolution may be poor, Google API gives lowest resolutions of "152 meters" for my neighborhood: that means that the distance between points of interpolation may be up to 3 hexes away and the result is lacking detail.
- At some points it may be overspecific, giving resolution between 2-8 meters. Then the point selected on map may affect too much the hex by picking some random rooftop or excavation and not the general terrain. If this happens, I'll give your money back.