Skip to main content
Geographic Information Systems

Return to Answer

replaced https://tools.ietf.org/html/draft with https://datatracker.ietf.org/doc/html/draft
Source Link
Community Bot
Community Bot
  • 1

The child FeatureCollection would be considered a Foreign Member as per the specificationspecification

So it is a legal object, but applications will not necessarily treat it as a GeoJson object.

Another approach is to use a JSON array of FeatureCollections. Note that the array is just JSON. Only the items in the array are GeoJson objects, since according to the specspec,

A GeoJSON text is a JSON text and consists of a single GeoJSON object.

The child FeatureCollection would be considered a Foreign Member as per the specification

So it is a legal object, but applications will not necessarily treat it as a GeoJson object.

Another approach is to use a JSON array of FeatureCollections. Note that the array is just JSON. Only the items in the array are GeoJson objects, since according to the spec,

A GeoJSON text is a JSON text and consists of a single GeoJSON object.

The child FeatureCollection would be considered a Foreign Member as per the specification

So it is a legal object, but applications will not necessarily treat it as a GeoJson object.

Another approach is to use a JSON array of FeatureCollections. Note that the array is just JSON. Only the items in the array are GeoJson objects, since according to the spec,

A GeoJSON text is a JSON text and consists of a single GeoJSON object.

Source Link
intotecho
intotecho
  • 922
  • 2
  • 10
  • 24

The child FeatureCollection would be considered a Foreign Member as per the specification

So it is a legal object, but applications will not necessarily treat it as a GeoJson object.

Another approach is to use a JSON array of FeatureCollections. Note that the array is just JSON. Only the items in the array are GeoJson objects, since according to the spec,

A GeoJSON text is a JSON text and consists of a single GeoJSON object.