Cool, and thanks for the code snippet. I kind of need the clickable map interface, as I’m in Africa and many of our locations are going to be sort of
$address ="http://maps.google.com/maps/geo?
=3km+past+the+big+baobab+tree,+left+at+the+watering+hole ...
etc
I think I am going to persevere with Coollocation set up on just one Map Objects weblog, and then relate these map objects to my accommodations, destinations, cities, towns etc.
That would be the easiest way, one can always include the map using embed and have a “maps” weblog. Or use an actual map (view source to see passing values from js to php/
..Ok, I’m not quite sure what you’re driving at here with “include the map using embed”, but I’m sure its important so I have to ask… Why do you make specific reference to the need to use embed in the template?
Thanks again. I am contemplating either creating a maps weblog (in addition to the map objects one) or just sticking with map objects and having a master object per map which defines the zoom level and center point for the map.
Why do you make specific reference to the need to use embed in the template?
I was assuming you wanted to show a map in other weblogs using the coolocation weblog to create the maps. In this case one would embed a map from that weblog. I don’t use the extension for the actual maps, just to geocode in the control panel.
Thanks again. I am contemplating either creating a maps weblog (in addition to the map objects one) or just sticking with map objects and having a master object per map which defines the zoom level and center point for the map.
What’s a map object?
Between so many ways of doing things in ee, and so many ways to make maps, it gets a bit complex lol .
A map object would be an entry in my map_objects weblog - the scope for this weblog is any map feature defined by the following custom fields: latitude, longitude, category (town, accommodation, waterfall etc) and zoom level.
These “map objects” are then “claimed” by my locations or accommodations weblog entries via a relationship field.
Make sense? thats what I have in mind anyhow, we’ll see how it pans out.. to me it seems like a fairly scalable and flexible setup.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.