B4A Library GoogleMapsExtras

GoogleMapsExtras is an ongoing project to implement more of the Google Maps Android v2 classes in Basic4Android.

Currently the library allows you to create these objects:

• BitmapDescriptor
• BitmapDescriptorFactory
• Circle
• CircleOptions
• GroundOverlay
• InfoWindowAdapter
• MarkerOptions
• Point
• Projection
• OnInfoWindowClickListener
• OnMarkerDragListener
• OnMyLocationChangeListener
• Polygon
• TileOverlay
• VisibleRegion

Tutorials for each object will be uploaded to the Google Maps Android v2 tutorial thread.

Martin.

 

[warwound]

Well i'm pretty sure if not a GoogleMaps related problem so you'd best start a new thread or post in the AHQuickAction thread.

Martin.

 

[marcick]

I did another test with a backup copy of my project and restored GoogleMapextras 1.61.

I open it with B4A 3.2 and it compiles correctly.
I update to GoogleMapextras 1.7 and it compiles correctly.
I edit the manifest as described and add the #AdditionalRes line and I get the compile error.

It seems a conflict with AHquickaction library ...

 

[warwound]

Do both AHQuickAction and GoogleMaps require an #AdditionalRes entry and you're only including one entry for GoogleMaps?
I did read a thread that explained how to add more than one value to the #AdditionalRes attribute - can find that thread now.

Martin.

 

[marcick]

AHQuickAction does not require #AdditionalRes entry, I'm using it since a long time

I see now that the compile error appears adding the

#AdditionalRes: C:\android-sdk\extras\google\google_play_services\libproject\google-play-services_lib\res, com.google.android.gms

And disappear removing it

 

[warwound]

GoogleMapsExtras updated to version 1.71

This update adds support for the TileOverlay and TileOverlayOptions FadeIn feature.

TileOverlay
Properties:

• FadeIn As Boolean
  Get or Set whether the tiles should fade in.
  Default value is True.

TileOverlayOptions
Methods:

• GetFadeIn As Boolean
• SetFadeIn (FadeIn As Boolean) As TileOverlayOptions
  Set whether the tiles should fade in.
  Default value is True.

The FadeIn feature is part of the January 2014 update to the Google Play Services library:
https://developers.google.com/maps/documentation/android/releases#january_2014

Be sure to update your SDK if you wish to use the new FadeIn feature.

Version 1.71 is attached to the first post in this thread.

Martin.

 

[scrat]

Hello,
I'm trying to use xml themes with mapsforge.
I just encounter a problem with resource files.
What is the default path?

Xml file contains this type of declaration

<rule e="way" k="building" v="church|cathedral|chapel" zoom-min="14">
       <symbol src="file:/symbols/church.png" />
</rule>

Thanks

 

[scrat]

It works if I change

file:

by

jar:/assets

is it possible to define a custom directory same as xml file ?

 

[warwound]

To be honest i don't really know!

This isn't something i've really tried to do myself yet.
I'm sure it's possible to set the resource path to anything you want but exactly what syntax is required is probably a case of trial and error til you find what works.
Absolute and relative paths are possible - again i don't know enough to answer your question.

This page is worth a read, though it doesn't seem to address resource paths: http://code.google.com/p/mapsforge/wiki/RenderThemeAPI
An answer may be on this page: https://groups.google.com/forum/?fromgroups&hl=en#!topic/mapsforge-dev/wUMudj8-zHM
Where post #2 states that modifying the render theme xml requires changing jar: to file: as you seem to have already found.

Martin.

 

[scrat]

Thanks Martin.
I continue my research

Just a workaround for this bug

The MapsForge library which i have created the MapsForgeTileProvider from has had a bug when rendering tiles which contain both land and sea for a long while.

in osmarender.xml you can add

  <!-- sea patch-->
    <rule e="way" k="natural" v="*">
        <rule e="way" k="natural" v="sea">
            <area fill="#b5d6f1" />
        </rule>
        <rule e="way" k="natural" v="nosea">
            <area fill="#f8f8f8" stroke="#f8f8f8" stroke-width="1.5" />
        </rule>
    </rule>

and tiles with sea/land is rendered correctly

 

[warwound]

Thanks Martin.
I continue my research

Just a workaround for this bug


in osmarender.xml you can add

  <!-- sea patch-->
    <rule e="way" k="natural" v="*">
        <rule e="way" k="natural" v="sea">
            <area fill="#b5d6f1" />
        </rule>
        <rule e="way" k="natural" v="nosea">
            <area fill="#f8f8f8" stroke="#f8f8f8" stroke-width="1.5" />
        </rule>
    </rule>

and tiles with sea/land is rendered correctly

That's very interesting - i'll try it later.
If it works i can incorporate it into the default render theme xml file included with the library.

Martin.

 

[scrat]

after changing the xml file in your library I have this result

 

[warwound]

The XML patch didn't work here.
Rivers rendered correctly just as they did before the patch.
But any tiles containing sea still render sea with the tile's default background color.

Screenshot attached.

Martin.

 

[scrat]

I think you use the map file from mapsforge.
I use the map file from http://www.openandromaps.org/en/downloads/europe because it has a full coverage for France
This file surely have a change to use the patch.
you can try the file for your country, I think it works.

Edit The Great Britain file works

 

[warwound]

MapsForgeTileProvider updated to version 1.01

This update contains a very slightly modified render theme xml file.
Have a read of this post: http://www.b4x.com/android/forum/threads/googlemapsextras.26277/page-6#post-221952.

Forum member scrat reported that this render theme modification when used in conjunction with map database files downloaded from openandromaps results in perfectly rendered tiles which contain both land and sea.

The old and ongoing problems with tiles that contain both land and sea is fixed with this update and a map database from openandromaps.

Version 1.01 of MapsForgeTileProvider is attached to the first post in this thread.

Martin.

 

[ronnhdf]

Can you please add the Libary
https://developers.google.com/maps/documentation/android/utility/heatmap

LG Ronny

 

[warwound]

Can you please add the Libary
https://developers.google.com/maps/documentation/android/utility/heatmap

LG Ronny

That looks interesting - and useful too!
I'll find some time in the week ahead to take a detailed look at it.

Martin.

 

[warwound]

The entire Utility Library looks to have some very nice features.
I've just compiled the demo app and uploaded it to my webserver.
If anyone's interested in taking a look you'll find it here: http://b4a.martinpearman.co.uk/googlemapsextras/AndroidMapsUtilsDemo.apk.

The demo includes a Heatmap example as well as some very slick looking marker clustering!

Martin.

 

[scrat]

Thank you Martin for the demo
Heatmap seems very interesting.

 

[rboeck]

Hi Martin,

i think the use of heat maps offers new possibilities for the use of google maps. I imagine maps with infection data of fungal diseases in wineyards etc. Farmes may send an warning sms to center station with their gps position; the center could automaticly generate a maps with the current status.

 

[warwound]

GoogleMapsExtras updated to version 1.80

This update adds support for the StreetView features found in the May 2014 Google Play Services update.
More info about the May 2014 update can be found here: https://developers.google.com/maps/documentation/android/releases#may_2014.

Google Street View provides panoramic 360-degree views from designated roads throughout its coverage area.
The coverage available through the Google Maps Android API v2 is the same as that for the Google Maps app on your Android device.
The list of currently supported cities for Street View is available at the Google Maps Help Center.

The StreetViewPanorama class models the Street View panorama in your application.
Within your UI, a panorama is represented by a StreetViewPanoramaFragment or StreetViewPanoramaView object.

I've not implemented the StreetViewPanoramaFragment object, instead i've just implemented the StreetViewPanoramaView object.

The StreetViewPanoramaView object can not only display 'official Google StreetView', it can also display 'user contributed photospheres' hosted on Google Views.
More info about photospheres can be found here: https://www.google.co.uk/maps/about/contribute/photosphere/.
(The StreetViewPanoramaView can only display remote content - it cannot display local device based content).

Once you have submitted a photosphere to Google Views, it is assigned a unique string panoid, you need the panoid in order to display the photosphere using a StreetViewPanoramaView.
A submitted photosphere will also automatically be moderated for inclusion in the official Google Maps website, if accepted for inclusion then the photosphere is discoverable and viewable to any user of the Google Maps website.
(When the Google Maps user enables StreetView using the 'pegman', photospheres appear as blue dots which the user can hover over or click on).

You can display a photosphere using a StreetViewPanoramaView regardless of whether or not the photosphere was accepted for inclusion in Google Maps.

The StreetViewPanoramaView allows full programmatic control - bearing, zoom level and tilt are all settable.
You can enable/disable touch and zoom gestures, user navigation and the display of street names too.

The StreetViewPanoramaView can be used in a b4a project alongside a GoogleMap or it can be used standalone in a project with no GoogleMap.
Note though that even if you do not use a Google Map you will still require an API key and need to make the manifest modifications required just as you must do if you do use a Google Map.
More onfo on the API key and manifest modifications can be found here: http://www.b4x.com/android/forum/threads/google-maps-android-v2-tutorial.24415/.

I've created a couple of b4a example projects and shall upload them to the Google Maps tutorial thread.

Version 1.80 is attached to the first post in this thread.

Martin.

[edit]The two example projects can be found here: http://www.b4x.com/android/forum/threads/google-maps-android-v2-tutorial.24415/page-23#post-250550[/edit]