Update (August 5, 2013)
This widget has been superceded by TileView. All future commits will be to TileView. MapView will be eventually discontinued entirely as TileView supercedes it.
Update (April 20, 2013):
Updating to 1.0.2, fixing a couple bugs, adding support for custom Bitmap decoders, improved intersection calculation (thanks to frankowskid), and some standardization. Also added the source for a sample app and a working .apk
- Fixed bug in pixel-based positioning created in 1.0.1
- Marker anchors are no longer "flipped" (if you want the marker to be offset by a negative value equal to half its width, use -0.5f... It used to be non-negative 0.5)
- Added new method (and interface) `setTileDecoder`, which allows the user to provide an implementation of a class to decode Bitmaps in an arbitrary fashion (assets, resources, http, SVG, dynamically-drawn, etc)
- Added concrete implementation of `MapEventListener` called `MapEventListenerImplementation`, that impelemts all signatures so you can just override the one's you're using
- Updated documentation
Update (March 28, 2013):
Updating to 1.0.1, fixing several bugs, reinstituting undocumented or previously removed features, and adding some experimental stuff.
- Fixed bug in draw path where start y position was incorrectly reading x position
- Fixed bug in setZoom where it was maxing to the minimum (this method should work properly now)
- Fixed bug in geolocation math where the relative scale of the current zoom level was not being considered
- Fixed bug in all slideTo methods where postInvalidate was not being called
- Fixed bug where a render request was not issued at the conclusion of a slideTo animation
- Fixed signature of removeHotSpot
- Reinstated support for downsamples images. See MapView.java for new signatures
- No longer intercepts touch events by default. This can be enabled with `setShouldIntercept(boolean)`
- No longer caches tile images by default. This can be enabled with `setCacheEnabled(boolean)`
- added `clear` and `destroy` methods. The former is appropriate for `onPause`, the latter for `onDestroy` (incl. orientation changes)
- added `resetZoomLevels` to allow different sets to be used during runtime
- onFlingComplete now passes the x and y value of the final position
- added onScrollComplete (fires when a slideTo method finishes)
- exposed lockZoom and unlockZoom methods. These can be used to prevent a tile set from changing (useful during animated or user-event driven scale changes)
- The positioning logic has gotten a little crummy. It works but is a little bloated and distributed across more parties than it should. I don't think experimental status fits, but it's close.
Note that the documentation has not been updated, nor has the jar - will get to those as soon as I get some time
Update (March 8, 2013):
While this component is still in beta, the version now available should behave predictably.
This commit entails a complete rewrite to more closely adhere to Android framework conventions, especially as regards layout mechanics. The changes were more significant than even a major version update would justify, and in practice this version should be considered an entirely new component. Since we're still debugging I'm not bothering to deprecate methods or even make any attempt at backwards compatability; the previous version in it's entirely should be considered deprecated, and replaced with this release.
The documentation has been updated as well.
An quick-n-dirty, undated, unversioned and incomplete changelog:
- The component no longer requires (or even supports) initialization. Rendering is throttled through handlers and managed directly via onLayout and event listeners. This also means no more "onReady" anything - it just runs. Just add some zoom levels and start using it. In theory, zoom levels can be added dynamically later (after the code block it was instantiated - e.g., through a user action), but this is untested.
- Zoom levels are now managed in a TreeSet, so are naturally unique and ordered by area (so they can now be added in any order, and you're no longer required to add them smallest-to-largest)
Image tiles now use caching, both in-memory (25% of total space available) and on-disk (up to 8MB). For the on-disk cache, you'll now need to include
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />. Testing for permission is on the todo list - right now you'll just get a runtime failure.
- Now supports multiple listeners (addMapEventListener instead of setMapEventListener). Note that the interface is now MapEventListener, not OnMapEventListener. We now also provide access to a lot more events, including events for the rendering process and zoom events (where zoom indicates a change in zoom level, in addition to the already existing events when the scale changed)
- We now intercept touch move events, so Markers won't prevent dragging. The platform is still janky about consuming and bubbling events, but I think this is about as good as it's going to get.
- Removed support for downsamples. That behavior wasn't visible in most other similar programs (e.g., google maps, CATiledLayer); it seemed to confuse some people; and it really hurt performance. I may consider a single low-res image as a background (rather than a different downsample per zoom level), depending on user feedback.
- Removed support for tile transitions. There was no way to keep this from eating up too much memory when abused (fast, repeated pinches between zoom levels), when we wanted to keep the previous tile set visible until the new one was rendered.
- Added support for zoom-level specific Markers and Paths - you can now specify a zoom index to addMarker/Path calls, which will hide those Views on all other zoom levels.
- Drastic refactorization and optimization of the core classes.
If you test this on a device, please let me know the results - in the case of either success or failure. I've personally run it on several devices running several different versions of the OS, but would be very interested in results from the wild. I'll be working on putting up a jar and a sample app.
Finally, thanks to everyone that's been in touch with comments and ideas on how to make this widget better. I appreciate all the input
The MapView widget is a subclass of ViewGroup that provides a mechanism to asynchronously display tile-based images, with additional functionality for 2D dragging, flinging, pinch or double-tap to zoom, adding overlaying Views (markers), multiple levels of detail, and support for faux-geolocation (by specifying top-left and bottom-right coordinates).
It might be best described as a hybrid of com.google.android.maps.MapView and iOS's CATiledLayer, and is appropriate for a variety of uses but was intended for map-type applications, especially high-detail or custom implementations (e.g., inside a building).
A minimal implementation might look like this:
MapView mapView = new MapView(this); mapView.addZoomLevel(1440, 900, "path/to/tiles/%col%-%row%.jpg");
A more advanced implementation might look like this:
MapView mapView = new MapView(this); mapView.registerGeolocator(42.379676, -71.094919, 42.346550, -71.040280); mapView.addZoomLevel(6180, 5072, "tiles/boston-1000-%col%_%row%.jpg", 512, 512); mapView.addZoomLevel(3090, 2536, "tiles/boston-500-%col%_%row%.jpg", 256, 256); mapView.addZoomLevel(1540, 1268, "tiles/boston-250-%col%_%row%.jpg", 256, 256); mapView.addZoomLevel(770, 634, "tiles/boston-125-%col%_%row%.jpg", 128, 128); mapView.addMarker(someView, 42.35848, -71.063736); mapView.addMarker(anotherView, 42.3665, -71.05224);
If you're targetting APIs less than 12, you'll need the Android compatability lib for the LruCache implementation.
Jake Wharton's DiskLruCache is also used. Here's a direct link to that jar. However, that package is bundled with mapviewlib.jar so is only needed if you're using the java files directly in your project.
```xml com.github.moagrius MapView 1.0.0 ``` Maven users
Javadocs are here.
Licensed under Creative Commons