Renaming of some properties

[alexrobin]

What about renaming the new place property to shape or something equivalent so it can be used for non-geographic features?

Also what was the rational for spelling out coordRefSys? Could the common crs acronym be used as the property name instead? It seems to me that everybody who would use something else than CRS84 would probably understand what CRS means.

Thanks

[rob-metalinkage]

the term "locus" may be more appropriate - and would open up the possibility of having spatio-temporal geometries such as trajectories as an extension type. (not in the core - but another extension obviously)

[lvdbrink]

shape could work for me, but locus is too uncommon and difficult a word in my opinion. Let's stick to easy to understand words if we can...

[lvdbrink]

Some of the rationale around the name coordRefSys is here: #3

Basically an old GeoJSON draft already had a crs property we wanted to avoid confusion with.

[alexrobin]

@lvdbrink Ok, makes sense. Thanks for pointing me to earlier discussions about crs. Is it still a potential issue or has that GeoJSON draft been completely abandoned?

[lvdbrink]

The draft is abandoned (crs did not end up in the standardized version of GeoJSON) but to my understanding there are still tools that support this.

[cportele]

OGC Moving Features Encoding Extension - JSON also specifies a GeoJSON extension that adds a "time" member - with a different schema (an array) than in JSON-FG.