2015
Pedestrian crossing points
Additional Information
| Field | Value |
|---|---|
| Last updated | unknown |
| Created | unknown |
| Format | CSV |
| License | uk-ogl3 |
| Created | over 10 years ago |
| Media type | text/csv |
| Size | 50,794 |
| cache last updated | over 9 years ago |
| csvlint json | {"in_progress": false, "data": {"num_errors": 3, "errors": [{"category": "context", "column": null, "body_html": "<p>Your CSV file is being delivered with an incorrect <code>Content-Type</code> of <code>application/vnd.ms-excel</code>. <br> We recommend that you configure your server to deliver CSV files with a <code>Content-Type</code> header of <code>text/csv; charset=utf-8</code></p>", "content": null, "title_html": "Context problem: <strong>Incorrect content type</strong>", "type": "wrong_content_type", "row": null}, {"category": "structure", "column": null, "body_html": "<p>There is no machine readable way (either via a schema, or <code>Content-Type</code> header) to tell if your CSV has a header line<br> Either revalidate this CSV with a schema, or make sure your web server sends the <code>Content-Type</code> of <code>text/csv; header=present</code> or <code>text/csv; header=absent</code> where appropriate.</p>", "content": null, "title_html": "Structure problem: <strong>Undeclared header</strong>", "type": "undeclared_header", "row": null}, {"category": "structure", "column": null, "body_html": "<pre>\n</pre><p>Your CSV has inconsistent line breaks (or your schema specified one line break style and the file uses another). You should make sure all line breaks are in the same form (i.e. CR-LF, or just LF). We recommend using CR-LF for maximum compatibility.</p>", "content": "\n", "title_html": "Structure problem: <strong>Inconsistent Line Breaks</strong> on row 595", "type": "line_breaks", "row": 595}], "success": true, "warnings": [{"category": "context", "column": null, "body_html": "<p>The encoding of your CSV file is not being declared in the HTTP response.<br> We recommend that you configure your server to deliver CSV files with a <code>Content-Type</code> header of <code>text/csv; charset=utf-8</code><br> If you are using a different encoding, then use an appropriate value for the <code>charset</code> parameter.</p>", "content": null, "title_html": "Context problem: <strong>No encoding</strong>", "type": "no_encoding", "row": null}], "num_warnings": 1, "encoding": null, "valid": false, "content_type": "application/vnd.ms-excel", "num_info_messages": 1, "schema_uri": null, "info_messages": [{"category": "structure", "column": null, "body_html": "<p>Your CSV appears to use <code>CR</code> line-breaks. While this will be fine in most cases, <a href=\"http://tools.ietf.org/html/rfc4180\">RFC 4180</a> specifies that CSV files should use <code>CR-LF</code> (a carriage-return and line-feed pair, e.g. <code>\\r\\n</code>). This may be labelled as \"Windows line endings\" on some systems.</p>", "content": null, "title_html": "Structure problem: <strong>Non-standard Line Breaks</strong>", "type": "nonrfc_line_breaks", "row": null}]}} |
| datastore json | {} |
| format | CSV |
| has views | True |
| hash | 26da514e0623bb671c5e127c345825b1 |
| id | e22c5f3e-4341-4376-a2d0-5828e09a214c |
| lazyboy json | {} |
| package id | b1a820fe-6aff-404f-85cd-ff3484142040 |
| revision id | f2e948ba-e60b-44df-9cf6-8c1c4fe9b30b |
| state | active |
| temporal coverage from | 26/06/2015 |
| temporal coverage to | 26/06/2015 |