Further steps with OJET, doing the research and solving blockers

Picking up from where we last off, I promised some discussion around some of the more complex components in OJET. However, as you know i’m towards the beginning of my journey, especially with this tool, so some background work was required before diving into the ‘complex’ components the cookbook had to offer.

In terms of using the thematic map, some background knowledge of geoJSON was the first port of call. Getting my head around polygons and multi-polygons bore fruit later in the development process as we encountered an issue around placing markers on the map.

I’d recommend using this link to get yourself upto speed:
https://macwright.org/2015/03/23/geojson-second-bite.html

One of the many maps the cookbook provides, pre-built

So what was the problem? A multi-polygon for those who don’t know is exactly what it says; an area defined in JSON (JavaScript Object Notation ) made of more than one shape. We were placing ‘markers’ on the map, basically circles which would display information on-hover, and found that mapping the markers to a multi-polygon would result in the marker being displayed in the middle of the two shapes. Think a marker in France appearing in the middle of the Ocean between the mainland and a island territory.

Sunbursts can be an extremely efficient method of modelling data

Next up was sunbursts. Just looking at the component you can see a lot is happening. The main issue was, how do we pass dynamic data from an API call into a component along these lines effectively? We had to look at the oj-event. To cut a long story short, we decided (and this was with help from more senior colleagues) to first log the event and have a look what was happening. From the long ream of information logged to the console we were able to pick out specific aspects of clicks on certain areas of the chart and have them pass information onto the next relevant step. A learning curve indeed.

That’s all for now, but i’ll update my progress again soon – this time revisiting an internal project that’s taken on a far greater, and interesting, scope.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s