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

Implement JOSM attributes #815

Merged
merged 5 commits into from
Mar 13, 2020
Merged

Implement JOSM attributes #815

merged 5 commits into from
Mar 13, 2020

Conversation

grischard
Copy link
Collaborator

@simonpoole
Copy link
Contributor

While I believe having equivalent attributes in ELI and JOSM is a good idea, could we confirm that these are all actually in use in the JOSM side and not things that were introduced for a specific case and then never reused?

@Marc-marc-marc
Copy link
Collaborator

could we confirm that these are all actually in use in the JOSM side

it is the trend to request "confirmation of use" before a reconciliation :(
what was the defect? the size of the filetransfert for Vespucci? the size on the smartphone? or is it just to keep a schema with no unused elements?

ping @stoecker @Klumbumbus for the ack

@stoecker
Copy link

"transparent" and "format" are relatively new and currently no wms_endpoint entries use them. But they are needed for proper support of wms_endpoint.

"custom-http-headers" usually will probably be used extremely seldom for "official" services, that's more a feature to get some strange services to work. It is needed from time to time, but at least I'm always happy if it works without.

"last-check" is used, but not as active as it should be - I'm not sure, maybe that idea is a failure and obsoleted by the wiki preview and the automatic checks we do nowadays.

Everything else is actively used.

@simonpoole
Copy link
Contributor

simonpoole commented Mar 13, 2020

could we confirm that these are all actually in use in the JOSM side

it is the trend to request "confirmation of use" before a reconciliation :(

Just to avoid us adding something, potentially adding support for it in code and JOSM saying "this hasn't really worked" ... definitely asking for a quick "OK" is sensible.

@stoecker
Copy link

Regarding last-check: https://josm.openstreetmap.de/ticket/18926

@stoecker
Copy link

stoecker commented Mar 13, 2020

last-check is gone now. We have better (i.e. working :-) mechanisms now to server the intended purpose to check the validity of the dataset.

@grischard
Copy link
Collaborator Author

Oh great, now you've broken my PR :-)

@grischard grischard marked this pull request as ready for review March 13, 2020 22:24
@grischard grischard merged commit 0e94ca1 into gh-pages Mar 13, 2020
@grischard grischard deleted the josm-attributes branch March 13, 2020 22:24
@grischard
Copy link
Collaborator Author

Merging this as it is. I'll admit the limits of my intellect when it comes to having the mirror tag in the json schema, and happily take any PRs.

@simonpoole
Copy link
Contributor

As I understand it that is simply an alternative site for the same data, so shoud be modeled as a json object mirror containing some of the fields with different values. What needs to be checked if one of these objects is enough or if we need an array of them.

@don-vip
Copy link
Collaborator

don-vip commented Mar 14, 2020

As I understand it that is simply an alternative site for the same data

Yep.

@grischard
Copy link
Collaborator Author

What needs to be checked if one of these objects is enough or if we need an array of them.

Some like https://josm.openstreetmap.de/wiki/Maps/Czech%20Republic#PrahaIPRlow-vegetationorthophoto have two mirrors.

grischard added a commit that referenced this pull request Mar 15, 2020
@Klumbumbus
Copy link
Contributor

You forgot logo-url in this PR?

@grischard
Copy link
Collaborator Author

I did.

},
"valid-georeference": {
"description": "Set to `true` if imagery source is properly aligned and does not need imagery offset adjustments. This is used for OSM based sources too.",
"type": "string"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not boolean?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uh huh. Why not!

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

Successfully merging this pull request may close these issues.

6 participants