Keep a lookout in the App Store for a new iOS application from Acacia Lateral Technologies. More details soon.
Development is progressing, but we have encountered some issues with the iPhone audio chain...
Acacia Web Site
You may have noticed that you are viewing the Acacia news on a different domain - SportsDB.com. We have leased a server to support a new GeoFence app and have taken advantage of the infrastructure on this server to run a Joomla server. This allows us to more simply provide news and updates on products.
The original web site can still be found here but will progressively phased out.
The original web site continues to host
- The image and vector based map servers. These map servers and web site now use a HTTPS front end.
- The news feed for KayakNav
- Download pages for KayakNav and StoreShotMaker.
KayakNav Version 3.0
We have started preparing for the release of KayakNav 3.0 which will feature more efficient vector based maps. We now have a Vector map server covering the entire planet in place to support development of version 3.0. Preliminary testing indicates dramatic improvements to map rendering speed and memory footprint on the device.
This vector based map server does not require server side tile rendering and caching that is in place for the PNG based map tiles, so server side processing and downloads will be faster. The trade-off is that rendering of maps must be performed on the device using graphics hardware, so best performance will be achieved using the latest iPhone or iPad hardware.
The move to Vector based maps has not been straight-forward and work is on-going. Unfortunately the MapBox API used in the latest "Vector" version is not as "Open Source" as MapBox would have you believe. To use it, you can't use your own vector server and it appears that a subscription to MapBox is required to use the mapping facility.
Please see the Map Server article and check out the performance improvements by clicking some of the links like "Paris" etc. If viewed using your mobile device, this will give an indication of expected KayakNav 3.0 map performance.
- Implementation of a new Vector based map server and served via the SSL front end web server - completed.
- Upgrade of source code to the Vector Maps API - in progress.
Please check back here for updates.
KayakNav Version 2.5
We are getting closer to releasing KayakNav for iOS 9.3. This version of iOS was chosen so as to ensure compatibility with some of the older devices that will cannot be updated to iOS 10. This release is primarily an update to iOS 9.3, but required some changes to support SSL connections to the map server. This is an interim step in moving forward to Vector based maps as detailed in the "KayakNav Version 3.0" article.
- Implementation of SSL front-end for the existing image based map server - completed.
- KayakNav 2.5 is now running with the HTTPS map server, so it should be accepted into the App Store.
- Next step is testing and upload to the App Store.
Image Map Server
The first version of KayakNav downloaded and cached maps for various paddling routes from this server. When a map view is requested, the code in the application automatically loads individual PNG files from a caching database on the device. If the required images are not available and an internet connection is available, they are requested from the configured map tile server and stored into the internal Sqlite database. The tile server renders and caches these PNG files on the server then hands them down to the device when they are ready. This process is generally very fast, but when many requests for new map regions arrive, it can take some time (seconds) for these to render and be returned.
The use of pre-rendered image based tiles made it impossible to provide different map styles in KayakNav without doing client side image manipulation or rendering an entirely different set of night mode tiles. The rotation of maps in KayakNav was particularly difficult and required map tiles much larger than the visible screen area to be put on a image and that image rotated on the device.
Page 1 of 2