Oh, sorry forgot the link.
Not much to see yet honestly, most work is under the hood. It may or may not be working, throwing errors and such when/if you visit.
Here’s some nitty gritty details of what I’m doing…
First I researched…
As part of my research I looked at what others, my competitors if you will, were doing and how they were accomplishing it. What I learned was that they all are not doing it right … well, in my opinion at least. They’re all using AJAX to handle requests and updating the map without having to have the page refresh which is great for user experience which is exactly what I was planning to do myself.
But things break down after that…
Overall it’s pretty minor, but wanted to point it out.
On to other things I’ve found…
Basically others used one of two methods to load data in the map. The one group loaded it embedded in the page as the page is being created. The other group loaded it in the map after the page has loaded via AJAX. The former is really, really, really bad. The more data you have the slower the page will load. It simply will not scale. The later is not only the better way, it really should be the only way.
You may or maynot know what JSON, if you do not, it is basically a simple easy to read way to structure your data that is very widely supported. Within the JSON spec there are sub-standards, one being GeoJSON. This is simply a specific way to format geo data, for example, data from a directory. It so happens that Google Maps supports this natively. The spec is actually really sparse, basically only supporting name, latitude and longitude for feature points (a directory entry). It does have a properties value where more data about the point can be added. This is where the rest of the entry data will be stored in my GeoJSON responses. The rest of the entry details will adhere to the JSON-LD spec. This is basically a way to represent http://schema.org data within JSON which is backed by all the search giants. By utilizing both GeoJSON and JSON-LD standards not only makes it easier for me to do other things I have planned but also makes Connections compatible with the large ecosystem of other web apps that utilize them.
So… that how I’m planning on handling AJAX requests… now, how to display it…
Long and detailed response, I know … and that was just the birds eye view!