It looks no different from a typical map site.
The layers are listed in this list box.
Each layer is a hyperlink, and each one refers to content from a different domain.
For example, this is rainfall information from the Meteorological Office. As you can see, there are many layers.
This is the original page being referred to.
This is a weather chart. The weather chart is drawn in Stereographic Projection, but its transformation is also made in this way.
This is a hazard map showing tsunami hazard levels from the Ministry of Land, Infrastructure, Transport and Tourism.
This is information from live cameras on rivers. You can get not only the location of the cameras, but also their respective live images.
Next, let's look at one of the effective use cases for hyperlayering.
The Japanese Cabinet Secretariat's Information Gathering Satellite has published images of the damage caused by the January earthquake on the Web.
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.
However, it is difficult to do this with original content alone.
As you can see, since hyperlayering can be expected to have great benefits, it may require a newly discussion on copyrights.
In fact, I have built over 1000 layers. This is probably the largest number of layers in Japan.
As mentioned above, each of these sites offers its own map service.
Naturally, they are built on various heterogeneous mapping frameworks and cannot be immediately referenced as layers in the SVGMap.
To overcome the differences, an architecture called Layers as Web Apps is provided.
It is possible to build encapsulated web apps for each layer, which can offer interactivity and absorb formatting differences for each service.
Next, look at the performance of the SVGMap.
Maps have to deal with a huge number of objects. How efficiently it can be displayed is important.
As you can see, the display is fairly quick.
Usually such processing uses server side dynamic processing, however, which goes against the client centric philosophy.
So, with a technique called Quad Tree Composite Tiling, we simply put static hyperdocuments on the server.
This means that the JamStack design pattern is utilized thoroughly.
Moreover, the capabilities of the SVGMap go beyond simply overlaying layers of maps.
First, let's display the layers of the clinics.
Next, a layer of seismic intensity distribution for the Noto Peninsula earthquake that occurred on New Year's Day this year is displayed.
Then, we can perform operations between these layers to extract medical facilities that have been subjected to major quakes of intensity 5+ or higher.
The operations are performed on the client side with crawling.
Completed. Results are marked in red and CSV data is also displayed.
The demonstration is now over. We hope you have felt the benefits of client side interoperability and hyper layering in web mapping.