Conversation
Conversion from google doc created html tables. Should this be converted to MD? Conversation continuing in google doc https://docs.google.com/document/d/194Ow1JfPsocukSKMJ2JuxwZXLWlz_miT74OuG6wwL-A/edit?usp=sharing
guides/point-location-data.md
Outdated
</tr> | ||
<tr> | ||
<td>Dalby </td> | ||
<td>[151.2660, -27.1944]</td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the comma in the data value, how should it be entered so the CSV file is considered valid?
Also, Should I add example CSV files and DataPackages to GitHub for more complete, testable, examples? |
also add office to schema fix links attempt internal links
{ | ||
"fields": [ | ||
{ | ||
"name": "Office)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo
{ | ||
"fields": [ | ||
{ | ||
"name": "Office)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo
guides/point-location-data.md
Outdated
* Lat, Lon or Lon, Lat - you choose the order | ||
* No way to force a pair of coordinates and support missing values. | ||
* If you add a required constraint to both, you can’t have a missing location. | ||
* If you don’t add required constraint, you could have lat without lon or vise versa. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vice versa
guides/point-location-data.md
Outdated
|
||
## Introduction | ||
|
||
This guide explores the options available to represent point location data in a CSV file within a data package. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My personal preference is to capitalize Data Package on this site.
Hi Stephen, I think this is a really great walkthrough of the various options for storing geospatial point data in a tabular format and the pros/cons of each approach. Given the variety of options I think this is useful research and the guide is a good vehicle for sharing it. Thoughts:
To your questions:
We are redoing the site soon, including guides (frictionlessdata/frictionlessdata.io#332). I am open to suggestions for where this could go in the new structure.
I don't necessarily think so, but I will keep this in mind while updating the guides.
See above for thoughts on redoing guides. Do you think a publishing section is still helpful?
This will change, so focus on the content.
When I first wrote the guides, I created this repo: https://github.com/frictionlessdata/example-data-packages We can update the packages therein and you are free to add your examples as well. |
- Capitalise Data Package - vice versa - link to github min/max issue todo - example csv and data packages - incorporate feedback from others
@danfowler thanks for your feedback. I will focus on the content and add examples as you suggest. I hope my last commit addressed the points you raised. I did plan to write a similar guide for more complex geometries once people were happy with this guide. Feedback from others is very welcome 😃 |
@Stephen-Gates i think this is great. @danfowler @Stephen-Gates I'd recommend getting this up asap and then iterating on the live doc to avoid any risk of the PR getting stale or conflicted. |
@rufuspollock @danfowler ready to go. Added a link in Index.md - feel free to adjust if it's not in the right place. |
Great! Will review and publish! |
Thanks again, @Stephen-Gates ! |
Work in progress. Advice requested on:
Feel free to edit as I'll be on holidays for 2 weeks.
From the google doc originally posted on the forum.