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

Possible best initial placement could also use metadata from map template / category #75

Open
timwaters opened this issue Feb 4, 2016 · 2 comments

Comments

@timwaters
Copy link

"best placement" uses YQL to find a potential best place for the map based on the title only.

We can get more metadata from the API and pass that to the query.

If maps are part of a category and the category is set to a default location, then it should go to that location first.

In addition we could use Wikidata for getting places if supplied in metadata?

@timwaters timwaters changed the title Possible best intial placement could also use metadata from map template / category Possible best initial placement could also use metadata from map template / category Feb 4, 2016
@susannaanas
Copy link

Map template has two fields for location: textual (location, free text) and Wikidata location (Qid, accepts currently only one value). Additionally data can be stored in the name or the description. Categories rarely have location unless we start to use it for that. Category name or text on the category page may hold clues to the location.

@Abbe98
Copy link
Member

Abbe98 commented Feb 18, 2016

I have used Pelias(Mapzen Search) for reverse-geocoding in the past, the public API returns great results most of the time.

Actually this functionality could be client side.

http://abbe98.github.io/blog/2016/02/04/digging-deeper-with-heritage-data-and-a-geocoder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants