Forum Replies Created
-
Posts
-
We have solved this issue and it will be corrected in our next app update which will be available early April.
We have solved this issue and it will be corrected in our next app update which will be available early April.
We have identified the problem and are working to solve it. Thanks for the report and we will keep you posted!
The border lines shown on the map are OSM data, and should be pretty comprehensive. But I just checked, it looks like there is some issue preventing the Department lines from appearing. We will look into this further.
What is listed in the Maps list however is actually coming from another source because it was much easier to work with early on. We will be moving over to OSM data for this in the future which will be more comprehensive and have better multi-lingual and country specific support.Thanks for reporting that! I have updated my comment above, and we will add better support in our next app update for importing CSV files with alternate Line Endings and UTF formats.Not sure I understand. Are you talking about the entries in the Maps list under France or are you referring to the border lines drawn on the map itself?
PocketEarth only supports GPX import to track objects. In PocketEarth, the main advantage of routes is the navigation mode which gives turn by turn instructions as you move along the route, but the GPX file format does not include this information and thus we cannot import them as routes.
Note that rte and rtept information should be correctly imported into a track object. rtrpt’s are imported as markers on a Track Segment with a direct line connecting them. This is the best and most correct way that PocketEarth can interpret this information.
The language should default to your device’s current language setting. In the app, you can go to Settings > Data Cache to adjust the languages for map labels and Wikipedia articles.
Travel Guides are currently only available in English, but we are adding support for 6 languages in our next update, due out around April 1st.Our next update will include a 128km radius search option as well as a “Current Map” option.
We will consider the other suggestions here for a future update.
The Waypoint feature will show you a direct geodesic line to your selected destination. This is the shortest path possible and it is not a rhumb line. Rhumb lines tend to be somewhat longer (typically 1% to 30% longer), but can be convenient because they have a fixed compass heading (can be useful for sailors/pilots).
We will consider adding support for rhumb lines in a future update.You can try importing from a backup PE Archive file. It will not cause the 10 pins you have added since then to be deleted, rather the Import process always merges the data in. The import process gives you an option for how to handle duplicates. Change this to the “Replace” option, so your empty groups get replaced with the ones in the file (Otherwise it uses the most recently modified version which would be the ones in PE already which got modified when the were emptied).
No problem, glad it is resolved!
We have a major new version of the app coming in the next month or so. It includes literally 100’s of fixes, new features, usability improvements, and will fit in more with the new iOS 7 style.The scale bar became broken in v1.6.2 and was fixed 1 week later in v1.6.3. In that week, we had dozens of user reports about it. We have not had any reports since then and have not seen any issue with it since then.Please go to Settings > About to verify you have the latest v1.6.4 and if so please help us by posting a screenshot showing the scale bar being incorrect. You can generate a screenshot by pressing the Home & Power buttons simultaneously on your device. The screenshot with be added to your Camera Roll, and you can email it to info@geomagik.com or post it on this forum thread. Thanks and sorry for any inconvenience!Yea, this is an old bug that we were aware of already, but it kind of got forgotten about, so thanks for bringing it up! I will check into it and see if we can fix now.
We have a major update coming soon with literally hundreds of fixes, new features, and usability improvements.Thanks for reporting this! We are aware of this issue with Regional Map Coverage and hope to solve it in a coming app update. Basically we don’t have an extremely accurate way to connect Regions with their actual administrative boundaries and our process tends to create gaps in sparsely populated areas. The most reliable option for now is to download the entire country.
I can look into a short term work-around by patching these regions in Canada manually since they are probably some of the worse cases (big regions with sparsely populated northern parts).Thanks for suggestion, we will consider it for a future update!
Its worth noting that Apple devices have a device wide setting for this already which may be useful. Just go to Settings > General > Accessibility > Invert Colors.Thanks for reporting this issue! It has been corrected now. Sorry for the delay!
For more info check this google search or this blog.Our maps data processing server crashed over the holidays, and we had to rebuild it. This delayed our last update, which was finally published a few days ago. This is based on the OSM Planet dump from Jan 8th so it is about 2 weeks out of date now.We will look into the specific issue you mention with B4. Do you happen to know if this was an issue on the OSM website which was corrected after Jan 8th? If so, it will be corrected in our next update, otherwise we need to investigate it more in case there is a processing issue and this can take some time.
