duplicated schema-org annotation & parsing failure #574
Labels
enhancement
New feature or request
Comments
pvgenuchten
pushed a commit
to pvgenuchten/pygeoapi
that referenced
this issue
Nov 18, 2020
pvgenuchten
pushed a commit
to pvgenuchten/pygeoapi
that referenced
this issue
Nov 18, 2020
|
See #444 |
tomkralidis
pushed a commit
that referenced
this issue
Nov 19, 2020
|
#575 had negative side-effect, so we should keep this open |
tomkralidis
pushed a commit
that referenced
this issue
Dec 1, 2020
* google expects plain schema-org url https://yoast.com/json-ld/ resolves #574 * Revert "google expects plain schema-org url" This reverts commit 7f09d4c. * hack to replace full path for short path, because pyld requires full, search engine expects short
|
confirming here that the merge made datasets crawlable again through google tooling
|
pvgenuchten
pushed a commit
to pvgenuchten/pygeoapi
that referenced
this issue
Jan 18, 2021
pvgenuchten
pushed a commit
to pvgenuchten/pygeoapi
that referenced
this issue
Jan 18, 2021
* google expects plain schema-org url https://yoast.com/json-ld/ resolves geopython#574 * Revert "google expects plain schema-org url" This reverts commit 7f09d4c. * hack to replace full path for short path, because pyld requires full, search engine expects short
francbartoli
pushed a commit
to francbartoli/pygeoapi
that referenced
this issue
Jul 8, 2021
francbartoli
pushed a commit
to francbartoli/pygeoapi
that referenced
this issue
Jul 8, 2021
* google expects plain schema-org url https://yoast.com/json-ld/ resolves geopython#574 * Revert "google expects plain schema-org url" This reverts commit 7f09d4c. * hack to replace full path for short path, because pyld requires full, search engine expects short
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some observations when validating https://demo.pygeoapi.io/master/collections/lakes in https://search.google.com/structured-data/testing-tool
Duplicated annotation
The pygeoapi templates still have microdata 'itemscope' attributes, combined with the embedded json-ld, it leads to duplicated parsing in validation tools. validator extracts the same dataset information twice
Parse error
The embedded json-ld throws a parse error on
error:
This results in the object described being a:
In other implementations I notice this string seems to work fine:
In that case the type is recognized as:
The text was updated successfully, but these errors were encountered: