WEBVTT

1
00:00:00.000 --> 00:00:05.000
It looks no different from a typical map site.

1
00:00:05.000 --> 00:00:09.000
The layers are listed in this list box.

1
00:00:09.000 --> 00:00:18.000
Each layer is a hyperlink, and each one refers to content from a different domain.

1
00:00:18.000 --> 00:00:25.000
For example, this is rainfall information from the Meteorological Office. As you can see, there are many layers.

1
00:00:25.000 --> 00:00:31.000
This is the original page being referred to.

1
00:00:31.000 --> 00:00:43.000
This is a weather chart. The weather chart is drawn in Stereographic Projection, but its transformation is also made in this way.

1
00:00:43.000 --> 00:00:51.000
This is a hazard map showing tsunami hazard levels from the Ministry of Land, Infrastructure, Transport and Tourism.


1
00:00:54.000 --> 00:01:07.000
This is information from live cameras on rivers. You can get not only the location of the cameras, but also their respective live images.

1
00:01:12.000 --> 00:01:17.000
Next, let's look at one of the effective use cases for hyperlayering.

1
00:01:17.000 --> 00:01:28.000
The Japanese Cabinet Secretariat's Information Gathering Satellite has published images of the damage caused by the January earthquake on the Web.

1
00:01:28.000 --> 00:01:39.000
First, trace the affected area from this image. Next, superimpose it on the map. When zoomed in, we can get a detailed damage for each house.

1
00:01:39.000 --> 00:01:43.000
However, it is difficult to do this with original content alone.

1
00:01:43.000 --> 00:01:55.000
As you can see, since hyperlayering can be expected to have great benefits, it may require a newly discussion on copyrights.

1
00:01:57.000 --> 00:02:04.000
In fact, I have built over 1000 layers. This is probably the largest number of layers in Japan.

1
00:02:04.000 --> 00:02:09.000
As mentioned above, each of these sites offers its own map service.

1
00:02:09.000 --> 00:02:19.000
Naturally, they are built on various heterogeneous mapping frameworks and cannot be immediately referenced as layers in the SVGMap.


1
00:02:19.000 --> 00:02:25.000
To overcome the differences, an architecture called Layers as Web Apps is provided.

1
00:02:25.000 --> 00:02:35.000
It is possible to build encapsulated web apps for each layer, which can offer interactivity and absorb formatting differences for each service.

1
00:02:38.000 --> 00:02:42.000
Next, look at the performance of the SVGMap.

1
00:02:42.000 --> 00:02:50.000
Maps have to deal with a huge number of objects.　How efficiently it can be displayed is important.

1
00:02:50.000 --> 00:02:53.000
As you can see, the display is fairly quick.

1
00:02:53.000 --> 00:03:02.000
Usually such processing uses server side dynamic processing, however, which goes against the client centric philosophy.

1
00:03:02.000 --> 00:03:09.000
So, with a technique called Quad Tree Composite Tiling, we simply put static hyperdocuments on the server. 

1
00:03:09.000 --> 00:03:14.000
This means that the JamStack design pattern is utilized thoroughly.

1
00:03:16.000 --> 00:03:32.000
Moreover, the capabilities of the SVGMap go beyond simply overlaying layers of maps.

1
00:03:32.000 --> 00:03:36.000
First, let's display the layers of the clinics.

1
00:03:36.000 --> 00:03:46.000
Next, a layer of seismic intensity distribution for the Noto Peninsula earthquake that occurred on New Year's Day this year is displayed.

1
00:03:50.000 --> 00:04:04.000
Then, we can perform operations between these layers to extract medical facilities that have been subjected to major quakes of intensity 5+ or higher.

1
00:04:04.000 --> 00:04:08.000
The operations are performed on the client side with crawling.

1
00:04:09.000 --> 00:04:15.000
Completed. Results are marked in red and CSV data is also displayed.

1
00:04:17.000 --> 00:04:30.000
The demonstration is now over. We hope you have felt the benefits of client side interoperability and hyper layering in web mapping.