Including images in GeoJSON

up vote
2
down vote

favorite

Is there a correct way of including links to images within geoJSON?

This is the FeatureCollection I have for an object on my site:


 "type": "FeatureCollection",
 "features": [
 
 "id": 1234,
 "type": "Feature",
 "geometry": 
 "type": "Point",
 "coordinates": [
 -0.322825,
 51.065361
 ]
 ,
 "properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park"
 
 
 ]

I also want to include the links to multiple images. Is it OK to add another property? For example:

"properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park",
 "media": [
 "https://example.com/image1.jpg",
 "https://example.com/image2.jpg"
 ]

Or is there a better / more standard way of doing it?

asked 1 hour ago

Terence Eden

1113

New contributor

add a commentÂ |Â

up vote
2
down vote

favorite

Is there a correct way of including links to images within geoJSON?

This is the FeatureCollection I have for an object on my site:


 "type": "FeatureCollection",
 "features": [
 
 "id": 1234,
 "type": "Feature",
 "geometry": 
 "type": "Point",
 "coordinates": [
 -0.322825,
 51.065361
 ]
 ,
 "properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park"
 
 
 ]

I also want to include the links to multiple images. Is it OK to add another property? For example:

"properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park",
 "media": [
 "https://example.com/image1.jpg",
 "https://example.com/image2.jpg"
 ]

Or is there a better / more standard way of doing it?

asked 1 hour ago

Terence Eden

1113

New contributor

add a commentÂ |Â

up vote
2
down vote

favorite

Is there a correct way of including links to images within geoJSON?

This is the FeatureCollection I have for an object on my site:


 "type": "FeatureCollection",
 "features": [
 
 "id": 1234,
 "type": "Feature",
 "geometry": 
 "type": "Point",
 "coordinates": [
 -0.322825,
 51.065361
 ]
 ,
 "properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park"
 
 
 ]

I also want to include the links to multiple images. Is it OK to add another property? For example:

"properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park",
 "media": [
 "https://example.com/image1.jpg",
 "https://example.com/image2.jpg"
 ]

Or is there a better / more standard way of doing it?

asked 1 hour ago

Terence Eden

1113

New contributor

Is there a correct way of including links to images within geoJSON?

This is the FeatureCollection I have for an object on my site:


 "type": "FeatureCollection",
 "features": [
 
 "id": 1234,
 "type": "Feature",
 "geometry": 
 "type": "Point",
 "coordinates": [
 -0.322825,
 51.065361
 ]
 ,
 "properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park"
 
 
 ]

I also want to include the links to multiple images. Is it OK to add another property? For example:

"properties": 
 "popupContent": "In loving memory ofrnGordon Wisemanrn15.4.30 ~ 11.8.06rnWho spent many happy hoursrnin this park",
 "media": [
 "https://example.com/image1.jpg",
 "https://example.com/image2.jpg"
 ]

Or is there a better / more standard way of doing it?

geojson

asked 1 hour ago

Terence Eden

1113

New contributor

asked 1 hour ago

Terence Eden

1113

New contributor

asked 1 hour ago

Terence Eden

1113

New contributor

asked 1 hour ago

Terence Eden

1113

asked 1 hour ago

Terence Eden

1113

New contributor

Terence Eden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a commentÂ |Â

1 Answer
1

active

oldest

votes

up vote
2
down vote

AFAIK GeoJSON is standardized by the Internet Engineering Task Force (IETF), and the standard mainly defines the implementation of geographic objects.

The properties are based on and extended from the key: value structure of JSON itself; you can populate it with anything that fits this concept.

The exact contents should be tailored to the parsing capabilities of your target software; it's likely some frameworks/systems can automatically parse image URLs from a dedicated property.

For interchangeability, I would probably stick to the standard properties: key: value, just like you did.

In many applications, properties are treated as attributes/field/columns...you can add as many as the target system allows. However, I would avoid furrther nesting of property objects.

answered 52 mins ago

ThingumaBob

4,5381222

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "79"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

Terence Eden is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f298808%2fincluding-images-in-geojson%23new-answer', 'question_page');

);

Post as a guest

Name

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

AFAIK GeoJSON is standardized by the Internet Engineering Task Force (IETF), and the standard mainly defines the implementation of geographic objects.

The properties are based on and extended from the key: value structure of JSON itself; you can populate it with anything that fits this concept.

The exact contents should be tailored to the parsing capabilities of your target software; it's likely some frameworks/systems can automatically parse image URLs from a dedicated property.

For interchangeability, I would probably stick to the standard properties: key: value, just like you did.

In many applications, properties are treated as attributes/field/columns...you can add as many as the target system allows. However, I would avoid furrther nesting of property objects.

answered 52 mins ago

ThingumaBob

4,5381222

add a commentÂ |Â

up vote
2
down vote

AFAIK GeoJSON is standardized by the Internet Engineering Task Force (IETF), and the standard mainly defines the implementation of geographic objects.

The properties are based on and extended from the key: value structure of JSON itself; you can populate it with anything that fits this concept.

The exact contents should be tailored to the parsing capabilities of your target software; it's likely some frameworks/systems can automatically parse image URLs from a dedicated property.

For interchangeability, I would probably stick to the standard properties: key: value, just like you did.

In many applications, properties are treated as attributes/field/columns...you can add as many as the target system allows. However, I would avoid furrther nesting of property objects.

answered 52 mins ago

ThingumaBob

4,5381222

add a commentÂ |Â

up vote
2
down vote

AFAIK GeoJSON is standardized by the Internet Engineering Task Force (IETF), and the standard mainly defines the implementation of geographic objects.

The properties are based on and extended from the key: value structure of JSON itself; you can populate it with anything that fits this concept.

The exact contents should be tailored to the parsing capabilities of your target software; it's likely some frameworks/systems can automatically parse image URLs from a dedicated property.

For interchangeability, I would probably stick to the standard properties: key: value, just like you did.

In many applications, properties are treated as attributes/field/columns...you can add as many as the target system allows. However, I would avoid furrther nesting of property objects.

answered 52 mins ago

ThingumaBob

4,5381222

AFAIK GeoJSON is standardized by the Internet Engineering Task Force (IETF), and the standard mainly defines the implementation of geographic objects.

The properties are based on and extended from the key: value structure of JSON itself; you can populate it with anything that fits this concept.

The exact contents should be tailored to the parsing capabilities of your target software; it's likely some frameworks/systems can automatically parse image URLs from a dedicated property.

For interchangeability, I would probably stick to the standard properties: key: value, just like you did.

In many applications, properties are treated as attributes/field/columns...you can add as many as the target system allows. However, I would avoid furrther nesting of property objects.

answered 52 mins ago

ThingumaBob

4,5381222

answered 52 mins ago

ThingumaBob

4,5381222

answered 52 mins ago

ThingumaBob

4,5381222

answered 52 mins ago

ThingumaBob

4,5381222

add a commentÂ |Â

Terence Eden is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Terence Eden is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Post as a guest

Name

Search This Blog

Iyfjky