Verfasste Forenbeiträge
-
Beiträge
-
This information is not shown in the current version of Pocket Earth. Our next update will include a speed & altitude vs. time graph which will show visually the change in speed and altitude over the course of the recording.
We do support a notion of Track Markers which do show you this info at a specific point on the track. Currently, however, you can only create these live as you are recording (it adds a marker at the current location of the track). Perhaps it would be useful to allow creation of such markers anytime and allow them to be dragged along the track to see the info at different moments.Our next update will include better controls for hiding map layers such as this. We are also hoping to include a Map Key/Legend.
You may be right that this is what is happening. If for some reason there are more than 1 instruction in a short distance from one another, the latter one (which may be more important) might be skipped. We will investigate such possibility and correct if possible.Thanks for reporting this, it is a bug in PE that we only recently became aware of. This only happens when the street text contains both LTR and RTL language scripts (example: both Arabic and English are used in the street name). We will try to correct this in the next update.The OSM database license changed some months ago, and a small amount of data was removed causing some loss of map detail in some specific places. This is most likely what you are seeing. In most places where this happened the OSM community has been very active in recovering the data by re-mapping the areas.This issue with GPS coordinates not matching those of the data on the map is beyond our control at the most basic level. This occurs in most map apps and devices but only in China. There is a lot of discussion online about this without anything conclusive, but its apparent that GPS devices sold in China are correct (or corrected) to show an accurate GPS coordinate on the map, while devices sold outside of China general have this issue. At least one other app we have seen offers adjustment controls to allow the user to manually align the two to correct this issue, and we may take this approach in the future.Thanks for reporting this issue! It will be corrected in the next app update.
A new update v1.6.4 is available. Please let us know if this update solves the issue.
CSV is a very generic format, not at all specific to map Pin or POI data. This means that the CSV file must have easily identifiable column headers to know how to interpret the data. The first row (header row) of the CSV file must have the following names:
Required (1 of following):• lat/latitude AND lon/long/longitude: to specify location in separated lat/lon coordinates• loc/location: to specify location in any of our supported coordinate strings (see Help Manual for full list of supported formats)Optional:• name: name of pin
• notes: notes stored on pin
• icon: type of icon – this may be any one of the following values (corresponding to the 10 icons offered on the Pin Detail screen):• marker-pin• marker-pin-small• marker-pin-flag• marker-pin-home• marker-pin-contact• marker-pin-camera• marker-pin-sleep• marker-pin-food• marker-pin-footprint• marker-pin-star• color: color of icon – may be any CSS color name (red, green, purple, etc) or hex color code (#FFFFFF)
• address: address stored on pinAll other headers/columns are ignored.The CSV files you linked have there own header naming scheme, so you will have to edit the CSV file to change the headers to what I described.[Edit]: Additionally the CSV file should be saved in standard comma separated, quoted fields in UTF-8 format with Unix Line Endings (LF). All modern software should use these settings by default, but if you are using an older version of Excel on Windows, you may need to change this when saving/exporting the file from Excel.Yes this could be very helpful, we are considering an Auto-Waypoint mode for our next major update to do just this.
For now, see my comment on your other question. You can add multiple items as Waypoints on a track and quickly switch between them by rolling the selector wheel.This isn’t a bug per se, but rather the current interface is a bit clunky. You can have multiple Waypoints and multiple Recordings on a single Track, but only 1 thing may be selected at a time. After you start a recording, you can roll the wheel on the left side of the track info panel to re-select the waypoint you want displayed.
This will be improved in the next major update to show you info about both the current recording and the current waypoint.Not 100% sure this is the issue you are having, but:
The record button will only appear after the first accurate GPS fix comes in so we can avoid recording bad data. However, sometimes the GPS will not give any update if you are not moving. Also, if you have just turned on the GPS (and the WiFi and Cellular are disabled), it can sometimes take up to 2 minutes to get an accurate fix (generally its not this long though, especially with an external GPS device). We are working to improve this in our next major update. In the meantime, moving a few meters might cause the record button to appear.Hi, thanks for reporting this issue! We have been able to reproduce it and are working on a solution. In the meantime, if you see it again, I believe simply rotating the device will correct it.
Best RegardsSorry for the delay, we have corrected this issue! We will submit a new update to Apple on Monday and it should be available for download in about 1 week.
As a work around to this issue: you can open the favorites screen and find the item you want to route to, then tap the blue arrow next to it to get to its Detail screen, and finally, tap the Route button.You can also add Waypoints by selecting any POI or Pin on the map (or by pressing and holding anywhere to make a temporary Pin), then tap its Info Panel to bring up the Detail screen. Finally press the Route/Track button and it will be added to the current Track as a Waypoint.
This was fixed in v1.6.3 released last Thursday. Let me know if you continue to have this issue on the new update.
@den: I don’t think Google provides any ability by which we could integrate directly, though it may have a way for you to export the data as KML or GPX. If so, you should be able to import the data into PocketEarth.
@BuckyE: It seems the OSM data which Cloudmade uses is horribly out of date, by maybe 6 months (not sure exactly). If it allowed you to make a driving route over a footpath, its very likely that the path was incorrectly marked in OSM at some point in the past and Cloudmade hasn’t gotten the correction yet. Not completely sure though, its just a guess.. we have seen things like this before.
@OG2404: Straight line routes which can be made offline would be handy and we hope to include it in one of our coming update.Settings > Map Layers allow you to disable a number of things, as well as enable a few extra layers, but it doesn’t include Peaks and Islands in the current version.
Our next major update will allow you to turn off any of the ~140 types of POI icons on the map!There is no icon for islands, did you mean some other kind of icon or the island landmass area itself?Okay, thanks for reporting this! The latest version of PocketEarth, v1.6.3, was just released on Thursday, could you get or verify that you have this version, and let us know if you continue to have this problem?
Thanks!@BuckyE: I believe open cycle map does show both contour lines and relief shading. Doing it all server side is pretty easy actually. But the data is ridiculously large and so it doesn’t work very well for offline mobile use.
Myself I will be trekking in Nepal very soon (as I do every year) and would also love to have topo maps onboard. We did make some good progress early on, but the data was ridiculously large and we have had to defer it as we work out issues and feature requests which we receive emails for every day.After our next major release, we do plan to re-focus on this feature and the tracking/waypoint nav features. Though it will likely still take some months of development to do it well (and by some, I mean it could be up to 6 months from the next major release, hopefully not more).There are some apps available that provide offline topo, but they are all raster image based. In this form the data is huge meaning you can fill your entire device just downloading a tiny map area. We are hoping to do it differently, by re-packaging the source height map data from the NASA SRTM project in a unique format that allows us to keep it extremely small, and then to dynamically shade it in our app’s rendering engine. This should allow a data size reduction by maybe a factor of 5,000x as compared to raster image based approaches. Then the next step would be adding the contour lines on top of this relief shaded layer and this is another story entirely: One option is to try to dynamically generate the contours on the device, though this is a very computationally difficult task and at this point we don’t know if it is even feasible on a mobile device. We suspect it can at least work on the newer (faster) devices. The alternative is to package the contours as vector data. This much we have actually been able to do and get working in PE already, though again the data is quite large. Not as large as raster image data but still about 5x larger then the current map data available in PE. It also has the limitation of requiring separate datasets for US and Metric units.Okay, so there is the status update I’ve been meaning to post for a while. I will keep this thread updated with our developments after the next major update is out.
