Exhibit Submission

[qwo]

With a possible use of localwiki being adopted as an API, I suggest 'taking new pictures of each POI' being added as a task.

Norfolk has said they did not wanted to maintain the art feed anymore so the feed has only become a good starting point.

[jalbertbowden]

flickr creative commons search. i've already found a few.

[qwo]

good deal, i dont know what an organized way to do this but everythings in the json file now. as long as appropriate pictures are swapped out dont't see a problem.

So we want to update the pictures for the existing data or provide a means to include new ones, and for existing data or new exhibits?

[jonahadkins]

We can put the points in OSM, and then scrape anything with the art attribute. Pics and descriptions can be linked.. ( I think )

We currently link them, so pretty sure we can do exactly that.

Speaking of new pictures, I saw on the cheat sheet that they have DOOM-themed icons. This makes me happy.

[jonahadkins]

Cool Let's Brainstorm Sometime Soon 💡 💡

For brainstorming:

http://iartnorfolk.com/#/exhibit/19
http://norfolkart.herokuapp.com/exhibits/19

Looking over LocalWiki, I don't see many means of reading or writing GeoJSON using their API. Looking at OpenStreetMap, we would have to use the OSM REST API for exhibit submission, but for loading data from existing exhibits, we would have to use their XAPI (optimised for reads), which public Overpass servers provide means of access to. However, since these servers return XML and we need JSON, we would likely still have to rely at least on a daemon that could use the query-overpass npm package to handle GeoJSON from the REST API.

OSM API
XAPI
Overpass (X)API

We still have to define the tags and specific information we could use from OpenStreetMap proper, but we absolutely could do this.

My only issue lies with convincing regular Norfolkers to curate OpenStreetMap data directly instead of via a more user-friendly site like LocalWiki, but I think if the mobile application and site have friendly enough interfaces, we could have this as the means to update this sort of information.

[jonahadkins]

Relates To This Issue Here -- If We Can Crack Vector Tiles - Updates To The Points Would Update With The Map.

Curating The OSM Is The Easy Part; i.e Here's How To In OSM..

[bschoenfeld]

LocaWiki API definitely allows for reading and writing of GeoJSON. I'd be glad to assist. You can look at the walking tour app in my Github account for an example.

The idea behind using LocalWiki was that it offers a simple interface for non technical curators to add content. Users could see that content on LocalWiki or in this art app.

We already have a curator from Portsmouth who is adding outdoor art to LocalWiki, though he's in the early stages.

I'm not familiar with OSM. So I hope someone can tell me if it would be better suited for this. How's the learning curve for someone who wants to add content with images and descriptions?

On Oct 1, 2014, at 9:04 PM, Ryan Y. notifications@github.com wrote:

Looking over LocalWiki, I don't see many means of reading or writing GeoJSON using their API. Looking at OpenStreetMap, we would have to use the OSM REST API for exhibit submission, but for loading data from existing exhibits, we would have to use their XAPI (optimised for reads), which public Overpass servers provide means of access to. However, since these servers return XML and we need JSON, we would likely still have to rely at least on a daemon that could use the query-overpass npm package to handle GeoJSON from the REST API.

OSM API
XAPI
Overpass (X)API

We still have to define the tags and specific information we could use from OpenStreetMap proper, but we absolutely could do this.

My only issue lies with convincing regular Norfolkers to curate OpenStreetMap data directly instead of via a more user-friendly site like LocalWiki, but I think if the mobile application and site have friendly enough interfaces, we could have this as the means to update this sort of information.

—
Reply to this email directly or view it on GitHub.