b.getTimezoneOffset is not a function
FNakano opened this issue · comments
I believe you can help me with this... It is more of a Date/Time encoding issue - not a LinkedDataHub issue.
http://50.62.81.50:8890/sparql is a SPARQL endpoint. The database has some data in it.
In LinkedDataHub I created a service, to access it and run the query:
prefix sosa: <http://www.w3.org/ns/sosa/>
select * where {
?s ?p sosa:Observation .
?s sosa:hasSimpleResult ?o1 .
?s sosa:resultTime ?o2 .
} LIMIT 100
... got a b.getTimezoneOffset is not a function error message:
Directly querying it results in rows contanining data like:
| s | p | o1 | o2 |
|---|---|---|---|
| http://each.usp.br/Observation/1639690208#press | http://www.w3.org/1999/02/22-rdf-syntax-ns#type | "92683.500000 hPa"^^http://w3id.org/lindt/custom_datatypes#pressure | 2021-12-16T21:30:08.077998Z |
Is the DateTime format in the data source, wrong?
Thanks in advance.
Hi again. No the data looks correct. I think the problem is that the conversion from the SPARQL results JSON to DataTable treats date(time)s as string.
@namedgraph, thank you!
... just to show a working result...
Beautiful :) Glad it helped.
@FNakano what features are you using mostly?
@namedgraph , I intend to use LinkedDataHub to design/deploy sensor data analysis and decision-making based on (web) semantics.
Thanks :) What I meant is what features in LDH are you using/planning to use: storing queries, creating/editing documents, creating structured content etc. That would be helpful to know.
Oh! I missed the abstraction level... sorry...
- store queries - yes;
- create documents and other content- yes;
- (re-) organize content based on preferences - yes;
- store knowledge graphs, merge with sensor data, query the resulting graph - yes