Skip to content
New issue

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

Specify input/output format in Readme #1

Open
freenerd opened this issue Jun 11, 2015 · 5 comments
Open

Specify input/output format in Readme #1

freenerd opened this issue Jun 11, 2015 · 5 comments

Comments

@freenerd
Copy link
Contributor

The readme should specify exactly which input and output formats exist. Is coordTimes a universally accepted property or something we came up with?

planemad added a commit that referenced this issue Jun 11, 2015
@planemad
Copy link
Contributor

@freenerd Readme updated, it seems like coordTimes is something @tmcw came up with since there is no standard to do this in the geojson spec.

@tmcw
Copy link
Contributor

tmcw commented Jun 11, 2015

Yep, I would love for this to be slightly more standard but that's a job for mr. @sgillies specification author

@sgillies
Copy link

Tell me more about coordTimes. Sounds like a good candidate for a GeoJSON extension. What it would need to be a good extension is its own namespace, eg, properties['gpx-ish']['coordTimes'] instead of properties['coordTimes'], and documentation of the protocol to be followed (zipping the coordTimes and coordinates lists together).

@TheMarex
Copy link

If we are going to to standardize this, we should go with timestamps instead of coordTimes.

@planemad
Copy link
Contributor

Since we're expecting users to use this along with togeojson, the change will have to be implemented there first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants