enhance HTML representations

geopython / pygeoapi

pygeoapi is a Python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

https://pygeoapi.io

MIT License

483 stars 258 forks source link

enhance HTML representations #26

Closed tomkralidis closed 4 years ago

tomkralidis commented 6 years ago

The f=html responses need a better layout. The goal here should be to enhance layout (especially the maps) without introducing too many external dependencies.

jorgejesus commented 5 years ago

Something every simple like: https://bulma.io/documentation/

jorgejesus commented 5 years ago

Suggestion from Paul van Genuchten

Make proposed page easy to customize using configuration options. and possibility of adding icons

pvgenuchten commented 5 years ago

The templating system seems a good option to change the layout according to user needs https://github.com/geopython/pygeoapi/blob/master/pygeoapi/templates/base.html

Some comments to improve the generic base template:

head-title/keyword/abstract should not be filled using generic config, in stead it should use properties from the collection or feature exposed on that page (title will be displayed on google search result), so would be interesting to configure for each Collection which property of Feature can be used as title (aka schema.org/name)
if the css were based on less, it would be nice to allow to define a color-scheme & font.
add an organisation logo (upload logo.png from admin)
add option to configure links in the header or footer (contact, disclaimer, help etc)

thijsbrentjens commented 5 years ago

@pvgenuchten this is a really good point:

head-title/keyword/abstract should not be filled using generic config, in stead it should use properties from the collection or feature exposed on that page (title will be displayed on google search result), so would be interesting to configure for each Collection which property of Feature can be used as title (aka schema.org/name)

I just tested the results in Google Search. Google indexes up to the individual item, which is really nice (and could be useful for some datasets). But the HTML representation could be improved. See for example https://www.google.com/search?q=site:demo.pygeoapi.io&start=70

Improvements like: add a specific H1 header (and title element) for an item (there is no H1 currently), preferably a human readable title, but that may require some more work (e.g. an optional title_field per provider for example). It may not be today, but I could maybe implement something for this

tomkralidis commented 4 years ago

Closing given we probably have enough given our current HTML representation. Feel free to reopen if we missed anything. Having said this, I will open a new ticket for being able to modify look and feel.

pvgenuchten commented 4 years ago

I agree with Thijs (sorry missed this discussion) we should make sure to list at least the id of the feature in the title, now google shows same title for each feature

I'll work on a PR

pvgenuchten commented 4 years ago

or maybe better to move this to a new issue...

tomkralidis commented 4 years ago

FYI #296 opened for review/comment.

justb4 commented 4 years ago

Think this also can be closed, the scope is also is rather broad but at the time of opening the HTML was rather barren. Better to have more specific/targeted issues like #361.