Enhance OGC API - Feature HTML representation to support complex features.
Add the possibility, this should be configurable, to inject he JSON-LD representation in an HTML representation, this useful for web crawlers.
The HTML thing is a bit weird, the reason behind it, is that web crawlers will use the JSON-LD to correctly categorize the the HTML page, more information available here.
@nmco
regarding the html representation for complex features. There are few problem in the ogcapi module that prevent the complex feature freemarker to work; having those fixed will result in a kind of Escher's Html with table nested inside parent table when dealing with complex attributes. also the ftl as it is seems to fail to provide many attribute values.
So here we need to fix the ftl before any json-ld inclusion.
But how should be the html representation of a complex feature? Nested tables as it is now? another way to handle this could be to flat the output by using one separate table for each complex attribute referencing the parent attribute in the table's header.
there is a bug in the ftl tempaltes that prevent them
to display the complex features in ogcapi ui. Fixing it will nonetheless makes the output
appearing very ugly and wrongly displayed.
An estimate in this case would be the necessary time to play with the free marker until obtain a clear html output for complex features that I guess will have to be a nested html table structure.
@nmco commented on Fri Jul 10 2020
This issues as two tasks:
The HTML thing is a bit weird, the reason behind it, is that web crawlers will use the JSON-LD to correctly categorize the the HTML page, more information available here.
@taba90 commented on Fri Jul 24 2020
@nmco regarding the html representation for complex features. There are few problem in the ogcapi module that prevent the complex feature freemarker to work; having those fixed will result in a kind of Escher's Html with table nested inside parent table when dealing with complex attributes. also the ftl as it is seems to fail to provide many attribute values. So here we need to fix the ftl before any json-ld inclusion. But how should be the html representation of a complex feature? Nested tables as it is now? another way to handle this could be to flat the output by using one separate table for each complex attribute referencing the parent attribute in the table's header.
@taba90 commented on Wed Mar 24 2021
there is a bug in the ftl tempaltes that prevent them to display the complex features in ogcapi ui. Fixing it will nonetheless makes the output appearing very ugly and wrongly displayed. An estimate in this case would be the necessary time to play with the free marker until obtain a clear html output for complex features that I guess will have to be a nested html table structure.
@taba90 commented on Wed Mar 24 2021
HTML output format trough template will be availabale trough xml feature templating support