Forum Replies Created
So turns out I already had a MapBox account set up in the site, and I think we were using that originally. At some point it seems to have defaulted to the Leaflet/Algolia. A few weeks ago, I realized my Pro account had expired, and had to renew and upgrade. Maybe happened then? This was the first time I noticed any major issue with the map locations.
I really should spend some time learning more about MapBox, cause there is probably a lot more we could be doing with these maps.
I did some research and testing, and we did have it on Leaflet with the default Algolia geocoder.
I think I did this originally cause we liked the look of the Leaflet maps better than Google, and seemed an easier setup than Mapbox.
I just tried a test keeping it on Leaflet but switching the geocoder to Nominatim. Tested one of those addresses and it was much more accurate.
My main goal is to not disrupt the current map (which I shared above, as well as 15 other smaller individual ones through the site) or change the look of them, but to make the addresses plot more accurately on new ones we add going forward.
Does this seem like a good solution?
Both address I noticed the problem on today were on long streets that go through multiple towns, so thought that might be part of the problem.
2345 Commonwealth Avenue, Newton, MA 02466
524 Lowell St, Peabody, MA 01960
both plotted miles off.
But I tested my own address after that on a smaller street and it was also about a half mile off.
This is the map page in question:
I’ll have to look into the geocoder setup. It was over a year ago I set this up, so kind of forget how that all worked. Will check that out.