Bit Map 10.0 was released on the App Store today (
https://apps.apple.com/au/app/bit-map/id1560781471 ). The complete list of changes is below.
The main changes to this release are based around work-flows that I find useful as a bushwalker. In particular, being able to edit tracks more easily to, eg, split a recorded track into two tracks (eg, at a track junction), merge two tracks together, delete vertices from tracks (eg, for locations where I got lost, or wandered around to go to the loo, or have lunch, etc), or even to move vertices (not so useful for bushwalking, but a valuable GIS feature, nonetheless).
Some of this was possible in previous versions, but it was difficult and unreliable. I always ended up exporting my tracks to a desktop GIS, editing them there, then importing them back into BitMap. This is way easier in BitMap now, and I think it's unlikely I'll ever need to use a Desktop GIS to make these kind of modifications to my recorded walking tracks in BitMap now.
The other main change is that tracks are now recorded with 'M' coordinates (in addition to X, Y, Z coordinates). 'M' (or 'Measured') coordinates can generally be used for any 4th dimension the user chooses in GIS's, but are most often used for timestamps. And this is what BitMap now uses the 'M' coordinate for when recording tracks. This means that when you split a recorded track into two (eg, I often do this afterwards to separate a recorded track into two at a track junction), BitMap can use these 'M' coordinates to calculate the new start/stop times for each of the two new track segments, and of course to calculate the walk-time (stop minus start) of that track segment. Note that existing users will have to remove (or rename/archive) their Tracks layers in order for Bit Map to start storing M coordinates. It cannot add M coordinates to a Track layer that does not already have M coordinates. (An alert will offer people with an existing Tracks data store the opportunity to archive (rename) the entire Tracks data store at the first launch of BitMap after the upgrade.)
It's worth noting that splitting a track results in the loss of the "Distance Travelled m" data for that track. This is data that is accumulated for all of the points that the GNSS (GPS) detects while walking that track, not just the straight line distances between each recorded point that is actually stored in the track. So BitMap now displays another "Line Length" distance, which is the length of the actual track geometry as-recorded (excluding the non-straight-line variations between the recorded points). This length is calculated on demand and is always shown in the line details view. The old "Distance Travelled" value will be shown in addition to the line length only when available.
There is even a new view pane in Bit Map in which you can see a list of all points (or vertices) in a feature's geometry - including 'M' coordinate values. The M coordinate is displayed as both its actual stored value (seconds since 1/1/1970) and as a more human-readable date and time.
All Changes:
- Select (vector) features by tapping them on the map view
- Merge multiple selected line features into a single line feature (Pro version only)
- Split selected line feature into two line features (at selected vertex) (Pro version only)
- Move vertex of selected feature by dragging (Pro version only)
- Delete vertex by double-tap on the vertex of a selected feature (Pro version only)
- Delete selected feature(s)
- Track Lines, Track Points and Waypoints coordinates include an ‘M’ (timestamp) coordinate (old non-M-aware Track layers should be archived/removed by the user to make way for new M-aware Track layers)
- Track line details includes line length (in addition to travelled distance)
- View all coordinates for a feature’s geometry (including Z/M, where they exist, M also displayed as formatted timestamp)
- Creation of a new layer includes an option to select an existing layer to use as a fields/attributes template (when used in conjunction with copy/paste of layers/features this can be used to convert between points/lines/polygons)
- Geometry type display names changed to more widely used names
- Added header geometry and spatial reference system to Layer/Features table view
- New Feature dialogue’s initial look improved