We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relating to Best Practice 25: Make your entity-level data indexable by search engines, more discussion is required on how to structure meaningful (spatial) queries with search engines (e.g. based on identifier, location, time etc.).
The text was updated successfully, but these errors were encountered:
During the SDW f2f meeting during TPAC, Sapporo, @danbri demonstrated that Google can provide search over structured content; example of structured markup (https://developers.google.com/structured-data/testing-tool/?url=http://travel.cnn.com/tokyo/sleep/hokutosei-sleeper-train-tokyo-sapporo-905418) which has 'City' named 'Tokyo' … Google Custom Search restricted to pages describing a schema:City: https://cse.google.com/cse/publicurl?cx=013484121852858951051:_k8pkh6pfio
schema:City
Can this be turned into an example / commentary? (not necessarily by @danbri - but his help would be useful).
Sorry, something went wrong.
At the SDW face-to-face meeting in London, December 2016, we agreed the following:
this is not a data publishing issue; you need to create the rich data before you can begin to do simple queries
Creating the queries is beyond the scope of our discussion about how to publish spatial data on the Web.
Closing this ISSUE.
No branches or pull requests
Relating to Best Practice 25: Make your entity-level data indexable by search engines, more discussion is required on how to structure meaningful (spatial) queries with search engines (e.g. based on identifier, location, time etc.).
The text was updated successfully, but these errors were encountered: