Category: Gmap (Google Map)

Using 1.10 cvs from mid june 2007

To reproduce:
# Create a new tracker with Google map field, plus other fields, on a tiki site created with basic profile for easy use.
# Log in as registered user (not admin)
# Insert an item (as registered).
# Edit the item, to click to "Google map locator" to geolocate the tracker item
# After cliking on the map (so that having coordinates and zoom for this item), you click on "Save clicked point" button
+ After that, you see on top: "OKOK", and the Google Map locator again.
"The OKOK" message should be removed, and I suggest that the user is automatically taken back to the tracker item after clicking on the "Save clicked point" button

Geolocating tracker items (through Google maps) are not working anymore, but they were before.

Using recent 1.10 update (from end of november or so) nowadays.
Example:
[http://intercanvis.net/tiki-view_tracker_item.php?itemId=2&trackerId=2&show=view]

Contributors

Contributors

on tiki-gmap-locator.php the check of $p['x'] > -90
should have been $p['x'] > -180

Same with the positive values.
Otherwise, you cannot choose places in China, Australia, etc.

After clean installation on tiki-wiki 2.2 (2.1)
the gmap plugin does not work.

For example following string
{img src=images/code.png}%%% {CODE()} {GMAP(type=>page, width=>560, height=>350, controller=>large, mode=>normal)/} {CODE}
in wiki-page does not generate any html-code.

The Google Map key issued for an nternationalized domain name is not accepted by the system with an pop up error saying like "the key is issued for another site"

Google Maps integration is an excellent feature. It would be helpful to provide [http://openlayers.org/|OpenLayers] as as an alternative.

Contributors

Current mod GMAP does not work in 4.2.

Not sure about other versions

GMAP(type=structure) should, at least as an option, map only children of the node in a structure.

Ie, one could have a Travel Structure listing travels, and sections for given trips or themes:

1. United States
1.1 Alaska
1.1.2 Fairbanks
1.1.3 Jeuno

Etc, GMAP(type=structure) in 1.1 would only map Alaskan locations, 1.1.2 would only map Fairbanks locations (assuming something was below Fairbanks in the structure, anyway.)

I have created an tracker with the google maps field.

When I try to add an location with the help from the "Google Map Locator" it doesn't have a "back" button and doesn't save any data back to the form/tracker.

URL generated by the tracker to Google Map Locator:
tiki-gmap_locator.php?for=item&itemId=&trackerId=&fieldId=3


{img src=show_image.php?name=map_locator_from_tracker.png&galleryId=1 }

This is an issue that has been pervasive since Tiki 3.x through 5.3. I believe I had advocated for the need to have a usable Google Geolocator comparable w/Mediawiki ([http://www.mediawiki.org/wiki/Extension:Semantic_Maps|SMW Mapping]). I have included a screen shot of both how Tiki displays the mapping and my other site in Mediawiki.

Here's the deal: If you go to Google Maps for a tracker situation in Tiki it first kicks you to another page. This, in and of itself is a problem; however, can be fairly easily overcome. The ''real'' problem is that the geocoder __does not__ work! Let me explicitly describe this: you click the Find Address button and nothing happens. So, why put the feature in? Even if it did work, you are now on another page, so you've lost your train of thought and have to click a BACK button which does not exist.

I spoke with folks on this; we even sent folks up to several TikiFests to describe in person during Tiki 3.x. My opinion is that displaying visual locations is more crucial than bells and whistles such as 3D, Web Conferencing, etc. Collaboration is great, but take the simple aspects of displaying (in a definitive, user friendly aspect) where the next TikiFest will be. I mean a person in Germany ''may'' not know where Kallispel, Montana, is.

I fervently believe that the ability to both geocode on the same page and display samesaid page is ''integral'' to any type of wiki.

With that said, I commend the coders for moving this far with the mapping.

{img id=114}
{img id=115}

Importantly, Google Maps Javascript API V3 is simply just faster than v2. Another big plus is that V3 does not need an api key. The currently used v2 api's key verification is known to have problems. It is also deprecated by google.
Read more here:
http://code.google.com/intl/fr/apis/maps/documentation/javascript/basics.html

Perhaps something for Tiki7?

Or would not it be part of Tiki6 as optional and experimental?