* Introduction
* Features
* Requirements
* Installation
* Do first example map
* For Sitebuilders and Developers
* Future plans
* Contacts
Introduction
The module provide interface for converting any image to google map.
In example usage the module can help to make map for a pirate treasure or may be map for a campus, or whatever you want to present as eye candy map.
Features
* Adjust tile size
* CSS customizeable controls
* Customizeable pin images
* CTools pane plugin
* Markers
* Markers description popup (modal and native from google)
* API hooks
Requirements
Drupal 7.x
ImageMagick >= 6.5.8
PHP configuration should allow shell_exec()
Download
Project page: http://drupal.org/sandbox/dimitrov.adrian/1928930
git clone http://git.drupal.org/sandbox/dimitrov.adrian/1928930.git gmap_image_field
Instalation
1. Unarchive the zip and put directory into your sites/all/modules
2. Enable it from your admin panel -> Modules
3. (Optional) For using pins (markers) you should enable also and gmap_image_field_pin module.
4. Go your /admin/reports/status page and check if there is some problem marked with GMap Image Field, if there is nothing such, then all is okay, and the modules are ready for use and can skip next steps.
5. Install ImageMagick (version newer or 6.5.8), You can get it from http://www.imagemagick.org/script/binary-releases.php, there is also and description about installing.
That should be all steps to get module working.
DO FIRST EXAMPLE MAP
1. Do the INSTALLATION section.
2. Go your website admin panel -> Structure -> Article (or some other content type) -> manage fields.
3. Add new field from type GMap Image.
4. Let settings for Tile size and Tiles format to their default values (256 for size, and jpeg for format).
5. Allow pinning of the maps as selecting one of the content types from the checkboxes on "Allow pinning nodes on this image". (NOTE THAT "Articles" is not available for pinning because contain the maps)
6. Save the field settings.
7. Now go to the Article's content type "Manage Display".
8. Using the settings icon for the newly created field for the gmap image, setup the display as you wish.
9. Update display settings for the field, and save settings for the content type.
10. Now you are ready to upload images as maps from the "Add content", and selecting the content type that contain map (in our example this is Article) Upload some image with high resolution using the "Map image" -> Image
11. Add some pins, this can be done using the "Add content" and adding nodes from type that is selected for the pinning. So if you add field "GMap Image" to "Article" and give pinning ability to "Basic Page" from the field menu, then Article will be maps, and "Basic Page" will be pins.
For Sitebuilders and Developers
* Permissions:
** Administer GMap Image Field - give role ability to administer gmap images
* Drupal hooks
** hook_gmap_image_field_assets_css_alter($css_file);
** hook_gmap_image_field_map_settings_alter(&$gmap_image_field_map_setting);
* JS events
** gmap_image_field_marker_clicked, hook on map and accept pin
* Templates and themes
** theme gmap_image_field_show_map - presenting map field
** templates/gmap-image-field.tpl.php - presenting map field
** theme gmap_image_field_pin_content - presenting infowindow content
* Styling
You can disable including of built in stylesheet from admin configuration -> GMap IMage Field and disable, but recommeds to copy and modify the module's stylesheet for overriding.
* Drupal.behaviors is fired when marker's infowindow is opened.
Future plans
Plans about improving in the next version, if module get enough interest.
* Improve external JS markers loading.
* Rework backend using GD of PHP for tiling the images.
* UI for managing pins icons.
* Polylines, Polygons, Circles and Custom overlay builder.
Contacts
Developer: Adrian Dimtrov (adimitrov@propeople.dk)
Reviews of other projects:
http://drupal.org/node/1867346#comment-7115660
http://drupal.org/node/1943152#comment-7255826
http://drupal.org/node/1954036#comment-7255878
2nd part
http://drupal.org/node/1962318#comment-7262040
http://drupal.org/node/1964028#comment-7270440
http://drupal.org/node/1962734#comment-7270484
Screenshots:
| Comment | File | Size | Author |
|---|---|---|---|
| gmap-image-field-2.png | 132.95 KB | dimitrov.adrian | |
| gmap-image-field-1.png | 108.79 KB | dimitrov.adrian |
Comments
Comment #1
klausiProject 1: http://drupal.org/node/1587176
Project 2: http://drupal.org/node/1772350
Project 3: http://drupal.org/node/1453964
Project 4: http://drupal.org/node/1406352
Project 5: http://drupal.org/node/1438600
Project 6: http://drupal.org/node/1929114
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
Comment #2
dimitrov.adrian commentedComment #3
alfababy commentedThere is still a master branch, make sure to set the correct default branch: http://drupal.org/node/1659588 . Then remove the master branch, see also step 6 and 7 in http://drupal.org/node/1127732
Comment #4
mnico commentedManual Review
1) It should eliminate persistent variables on hook_uninstall
2) Maybe it's a good idea to add a hook_requirements and hook_enabled for ImageMagick.
Comment #5
dimitrov.adrian commentedMaster branch removed.
Implemented hook_requirements.
Comment #6
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #7
dimitrov.adrian commentedAdded manual reviews and bonus tag.
Comment #8
SamChez commentedPossibly update your README.txt, specifically the installation process and introduction, they're both slightly lacking as far as content goes. Otherwise the module is pretty much exactly what you make it out to be.
Comment #8.0
SamChez commentedadding manual reviews
Comment #8.1
dimitrov.adrian commentedREADME update
Comment #8.2
dimitrov.adrian commentedupdate README
Comment #9
dimitrov.adrian commented@SamChez you're right, updated just now.
Comment #9.0
dimitrov.adrian commentedupdate headings.
Comment #10
klausiReview of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
manual review:
But otherwise looks RTBC to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Assigning to cubeinspire as he might have time to take a final look at this.
Comment #10.0
klausiUpdate introduction.
Comment #10.1
dimitrov.adrian commentedAdd section howto
Comment #11
dimitrov.adrian commentedDone suggestions from #10, and added 3 more manual reviews.
Comment #12
klausino objections for more than a week, so ...
Thanks for your contribution, dimitrov.adrian!
I updated your account to let you promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and get involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #13.0
(not verified) commentedNew manual reviews and git clone command.
Comment #14
avpaderno