Modify

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#15863 closed defect (fixed)

ImageryCompare geojson output issues

Reported by: simon@… Owned by: team
Priority: normal Milestone:
Component: External imagery source Version:
Keywords: Cc:

Description

The geojson output of ImageryCompare is slightly less copy pasteable into ELI that it could be

  • The name of the "attribution" object is mispelled and the schema does not contain a field "terms-of-use-url" in the "attribution" object
  • The geojson Feature object name needs to be "Feature"
  • There is no field "valid_georeference" in the schema

Attachments (0)

Change History (9)

comment:1 by anonymous, 6 years ago

Summary: ImageryCompare geojson output issues!ImageryCompare geojson output issues

in reply to:  description comment:2 by Klumbumbus, 6 years ago

Replying to simon@…:

  • There is no field "valid_georeference" in the schema

Hm. I think it doesn't really make sense as long as it is not part of the ELI schema.

comment:3 by stoecker, 6 years ago

Resolution: fixed
Status: newclosed

Fixed the typos.

The additional fields are there because this is an export of JOSM database in another format. It tries to be as compatible to ELI format as possible, but it still covers our dataset.

comment:4 by anonymous, 6 years ago

I'm not opposed to having the extra fields, the just should be at least documented a bit, so that people know in advance what they need to remove and don't have to start hunting down validation errors one by one.

comment:5 by stoecker, 6 years ago

See ImageryCompare, the part "JOSM-only properties according to JOSM-schema".

comment:6 by anonymous, 6 years ago

It needs a sentence that it will actually preserve and output them in the converted output, that is what isn't clear, not that the two systems have somewhat differing schemas.

in reply to:  6 comment:7 by stoecker, 6 years ago

Replying to anonym:

It needs a sentence that it will actually preserve and output them in the converted output, that is what isn't clear, not that the two systems have somewhat differing schemas.

Feel free to change it. It's a wiki.

Anyway it would be much easier if ELI would simply support the missing JOSM features.

comment:8 by stoecker, 6 years ago

Component: unspecifiedExternal imagery source

comment:9 by Klumbumbus, 6 years ago

I added a hint.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.