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.

[ghost]

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 )

[ghost]

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 💡 💡

[ghost]

For brainstorming:

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

[ghost]

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. [email protected] 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.

[jonahadkins]

Pics and descriptions arent an OSM thing - maybe just need to make sure local wiki points get added into OSM

[ghost]

@bschoenfeld: I couldn't run your walking tour example (this one?), and I saw no POST or PUT references to LocalWiki in that repo, only Google Maps. I know I probably missed something, since my JavaScript knowledge needs work.

I could probably provide a unified interface to LocalWiki if it could accept the extra data fields in the GeoJSON I would need to display in iArtNorfolk (branding pending, at @wbprice's request), but managing all of that with as little knowledge of LocalWiki as I have just seems daunting. Hauntingly daunting, in fact!

I would absolutely love to get together with you sometime to learn more about how to use LocalWiki for the sorts of transactions necessary to integrate the two.

@jonahadkins: I would love to use OSM directly with support from LocalWiki to achieve this. A major hurdle for me regarding this project involves providing a simple interface from a mobile website: I would love to provide an opportunity to integrate with the device's camera to take a picture, provide a form afterwards to include a title, description and artist(s), but outside of HTML media capture, I don't know how to achieve this.

If this attribute has decent enough support, I would love to use it for user-submitted art pieces and submitting their locations directly to OSM.

[bschoenfeld]

Yeah, you've got the right app. That app is read only, so no POST or PUT to be found. I used LocalWiki to enter all my data, but it wasn't ideal. I'd be happy to work on some code that puts data into LocalWiki. That should be pretty simple. I'm sure I can build a simple JS API that takes pictures, location, and description and builds a page.

[ghost]

We currently have a POST route, but we may need to modify it to allow users to actually submit exhibits, or we may need to either provide a mobile application which could do this or another route on the mobile website to do this part. I'd prefer to have a mobile application do this, so that would take some time, but if we can find a way to properly integrate this into the iArtNorfolk site, we can do this relatively soon.

OAuth would prove necessary either way, so I see that as a prerequisite to completing this part.

[ghost]

Blocker: Code4HR/local-art-api#26.

[civicissuebot]

Hello! This issue looks like it still needs help!
It's been clicked on 1 times through the Civic Issue Finder on http://www.codeforamerica.org/.
Can this issue be closed or does it still need some assistance?

If you wrote this issue, you can always update the labels for specifying tasks, add more info in the description to make it easier to contribute, or re-write the title to make more contributors interested in helping out.
If you are an open source contributor, ask and see how you can help by commenting or check out more open issues in this repo at https://github.com/Code4HR/localart/issues.

Just doing a little 🌱 open source gardening 🌱 of Brigade projects!
For more info/tools for creating civic issues, check out Got Issues Thank you!