Custom Google map generator for the Apostrophe content management system
apostrophe-map adds interactive maps to the Apostrophe content management system.
apostrophe-map provides both backend and frontend components, including a friendly UI built on Apostrophe's rich content editing features.
apostrophe-sandbox project for a demo of usage. Setup is similar to
apostrophe-snippets. The geocoder is automatically started.
The "get" method of the maps module accepts these options, in addition to everything
pages.get will accept:
geo: a GeoJSON point. When this option is passed, results are sorted by distance from this point.
maxDistance: results are restricted to points within this many meters of "geo".
maxKm: same for kilometers.
maxMiles: same for miles.
Prior to 3/12/15 this was very difficult due to the timing of the way the map object was constructed.
Here is an example of code that overrides the method that generates an info box:
// This code lives at your project level, in// lib/modules/apostrophe-map/public/js/content.jsvar superAposGoogleMap = AposGoogleMap;var self = this;superAposGoogleMapcallself item id mapOptions;alert'Do this instead of displaying the info box';;;
Note the use of the "super pattern," much as we do on the server side when extending methods of Apostrophe modules.
You'll find that the browser-side code in
content.js has been broken down into many individual methods, all of which can be easily overridden in this way.
We've made a change to the way the map module stores coordinates. This change enables the use of a 2dsphere index for fast searches for addresses and other locations. And we've introduced cool options that leverage that. But, there's a bc break required.
Previously there was a "coords" property which contained "lat" and "lng" properties.
Now, we're storing a GeoJSON point in a "geo" property.
It looks like:
locationgeo = type: 'Point' coordinates: longitude latitude ;
IMPORTANT: LONGITUDE COMES FIRST.
(MongoDB's choice, not ours, but it does fit with the newer convention that X always comes before Y, even if you're talking about maps.)
FOR OLD SITES, YOU SHOULD RUN "node app apostrophe:migrate", otherwise the map module will have to geocode your coordinates again based on their address field. Which is not the end of the world, but it's nice to skip it especially if you have a lot of them.
coords = LatLngitemgeocoordinates1 itemgeocoordinates0;
.coords property in old sites will hang around, because it's not hurting anyone and migrations should be as gentle as possible. But it won't be updated anymore, so don't be fooled.
You no longer need to add script tags for the Google Maps API to your
base.html file. Instead, these dynamically load on their own, and only when they are actually needed.
base.html files that do load these scripts the hard way will still work, but you are slowing your users down on every page, so stop doing that.