Given a URI, dereference it and show the wktLiteral(s)

[pietercolpaert]

This is a feature request for an advanced functionality. When clicking a button “load URI”, a textbox should appear where a URI can be copy pasted. The URI should be requested, and then a wktLiteral on this page that can be found in the Linked Data should be visualized. Two options are possible of what the expect from such a URI:

• The URI to a geo:Geometry is given, and a page is returned with multiple literals → select the wkt literal that is linked to this subject URI
• The URL to a page is given with 1 or more WKT strings in it. Just select the first one found in this case

Functionalities to be taken into account:

• During this process, redirects must be followed.
• A HTTP proxy should be able to be configured (default, if enabled, can be: https://proxy.linkeddatafragments.org/)
• A short-cut to https://wktmap.com/#uri=... would be interesting for sharing purposes

Implementation

1. Using rdf-dereference, fetch the resource. Problem that will show up by adding this dependency is that we can’t alter the webpack configuration from a created react app workflow. Workaround documented here: https://marmelab.com/blog/2021/07/22/cra-webpack-no-eject.html
2. Loop through the triples, and filter all WKT literals. If multiple WKT literals given, select the one linked to the current page, else just select the first one.
3. Now the full WKT literal can be used in the rest of the application: important in this case is however not to change the URL parameters to this specific WKT literal

Limitations:

• WKT map can only visualize one WKT string and will only show one string from a map.
• WKT map won’t show details of the geometry that could potentially also be extracted from the Linked Data

Examples of pages that can be used for testing:

• The URI of a geometry: http://marineregions.org/mrgid/25336/geometries?source=80&attributeValue=25336
• Pages with multiple WKT literals in them:
  • http://marineregions.org/mrgid/25336 (content negotiation: set an Accept: text/turtle request header)
  • https://private-api.gipod.beta-vlaanderen.be/api/v1/ldes/mobility-hindrances?generatedAtTime=2020-12-28T09:36:09.72Z
• http://brt.basisregistraties.overheid.nl/top10nl/id/gebouw/101347042

I will do a first implementation of this

[pietercolpaert]

@pieterprovoost Before I start, I’d like to get your opinion about:

• Using the https://marmelab.com/blog/2021/07/22/cra-webpack-no-eject.html workaround for adding dependencies that require additional webpack configuration - is this indeed the way to go?
• The limitation of visualizing only 1 WKT string: do you agree with the approach? Or should we allow multiple WKT strings by concatenating them somehow for example?

[pietercolpaert]

For the first step: d21abe0 → this is what this would mean