|
POST
|
Patrick, as has been mentioned before, if you did not save your data as a feature service, all your data has been embedded in the web map. That being said, it is still possible to export it, it will just take a few extra steps. First open the web map that was from the map tour builder in the ArcGIS Online map editor. Find the Map Tour layer in the table of content, open the context menu for that layer and select the Save as layer option at the bottom. Open that new layer's item page and click the "Publish" button. This will publish your data as a new feature layer. Open the feature layer item's page. This page should will allow you to export the data in a variety of formats (CSV, file geodatabase, geojson, etc.)
... View more
02-22-2017
08:22 AM
|
1
|
0
|
4188
|
|
POST
|
The story map crowdsource app displays larger photos when a viewer clicks on a point. These photos are generally 600px - 800px wide depending the viewers screen resolutions. Uploading low resolution photos will lead to viewers seeing blurry or grainy photos which is not a good experience. For this reason we have added a minimum resolution requirement so contributors cannot add grainy photos to the app. If you must allow low resolution photos, you can do so by editing the app configuration through the AGO Assistant. General instructions for editing the app JSON can be found in this blog post: https://developerscorner.storymaps.arcgis.com/story-map-crowdsource-advanced-configuration-60ecd32f0182#.kjs3516wa. The last section has instructions about editing the photo upload configuration. Instead of adding the third photo section, edit the minimumSize attribute to be the smallest size of photo you want to allow. Remember, the app check the smallest side of the photo. So if your mimimumSize is set to "200" and a user tries to upload a photo the is 150px x 300px, they will still get an error that their photo is too small.
... View more
02-21-2017
05:07 AM
|
0
|
0
|
1121
|
|
POST
|
Yes, you can add your old feature service to a new crowdsource app but will require editing the underlying JSON configuration through the AGO Assistant tool. Here are the steps: Open the webmap that we created in the in your new app in the ArcGIS Online map editor. Remove the current crowdsource layer. It will say "Do not remove" but you can ignore this since you'll be replacing it. Add the feature layer from the old app into this webmap. Open the AGO Assistant and choose "View item JSON" in the navbar dropdown. Then click on this same webmap item. Copy the layer id of the feature layer you just added to the webmap under the data section. Should be the only layer under "operational layers." (Fig. 1) Now choose the app item, scroll down in the data section till you find the map and crowdsource layer reference. Replace this layer id with the id you just copied (Fig. 2). Fig. 1 Fig. 2
... View more
02-20-2017
09:54 AM
|
0
|
0
|
1599
|
|
POST
|
Crystal, because your images are very large, we would highly recommend uploading the images in the app and letting the app store a copy of your photo. This automatically optimizes the images for the web and will create the second thumbnail size for you. If you just reference the full resolution images, you will find that your story is very slow to load, especially on slower internet connection. We recommend that all photos used in story maps be less than 500kb to make sure they load quickly. If you need to keep the image referenced on your server, you should create two new images (one thumbnail, and one web optimized photo) for each photo. For each of our apps that allow you to reference images by a URL, we have guidelines in our FAQ to help provide the best experience to your viewer: Frequently Asked Questions | Story Maps. Besides just optimizing them for the web, managing them in the app will make sure they are always available when the app is available. They follow the same sharing permissions as the app and you will not have to worry about breaking links if you move your photos to a different folder on your server.
... View more
02-15-2017
08:06 AM
|
1
|
1
|
1364
|
|
POST
|
This indeed looks like it has to do with the https issue I mentioned previously. Because the cascade app is accessible over both http and https, maybe you we're viewing http version of the story. This is a security restriction put in place by the browser to prevent secure information being leaked by an insecure embedded app. Unfortunately, there is nothing we can do to override this security restriction. The good news, wetlandswatch.org does have a https version of their site. Just make sure you embed this URL instead: https://wetlandswatch.org/. Sagecoast does not have a https certificate so you will not work if the cascade URL has https. I would recommend contacting Sagecoast and request that they add SSL certificate to their website. This is best practice for websites as if is better for SEO, provides better security for their users. They can even receive a free certificate (Let's Encrypt - Free SSL/TLS Certificates). If sagecoast is unable to add a ssl certificate to their website, you have two options: Instead of embedding the webpage, provide a link. You could even take a screenshot or use an image of their logo as the link. (Not Recommended) - Embed the http://sagecoast.org URL then make sure you always share the cascade story using http at the beginning of the URL instead of https. However, if a user finds another link through arcgis online or has a browser extension that auto redirects to https, the embedded webpage will still break. Also, we plan to disallow all http connections and embedded content in about a years time to prevent some of the issues stated above as well as provide better security and best practices to our users.
... View more
02-14-2017
07:46 AM
|
0
|
0
|
1250
|
|
POST
|
Check the URL of the cascade app to see if it starts with https. Does the URL of the website you are trying to embed also start with https? The browser will not allow you to embed an http URL into an https website. This is a security restriction the browser sets in place. You must have an SSL certificate installed on the website you embed and you must use the https URL to that website. If you are using an https URL for the website and are still having issues, can you provide the URL of the website so we can investigate?
... View more
02-14-2017
06:08 AM
|
0
|
3
|
1250
|
|
POST
|
That is correct, because the browser requires a secure connection, the app must ensure it has a secure connection before showing the button. If the app did not have a secure connection, a user could click on the button but they would always receive an error because the browser would reject our request for location. We believe this a poor user experience and have chosen to disable the button unless we can verify if the browser has a secure connection. The browser does not just require the app to have a secure connection but all parent frames the app is embedded in. Unfortunately, there is not a reliable way to determine if all parent frames have a secure connection from within embedded app so we always disable if the app is embedded. If you know that you have secure connection all the way to the embedded app and you are willing to host a customized version of the code, I can point out what needs to be changed.
... View more
02-13-2017
10:56 AM
|
0
|
1
|
1442
|
|
POST
|
Unfortunately, there is no work around to show the locate button when the app uses a http (insecure) URL. This is a security restriction the browser puts in place to prevent a user's location being leaked to a hacker or unauthorized user. The standard imagery with labels basemap only has general POI labels and not all road labels. If you want road labels, you can add this transportation layer on top of an imagery basemap: http://www.arcgis.com/home/item.html?id=94f838a535334cf1aa061846514b77c7.
... View more
02-13-2017
10:25 AM
|
1
|
0
|
1442
|
|
POST
|
Hmm, I just opened the your app in Safari and the participate button worked for me. If this comes up again, can you get the users's browser and version they're using? For users that are uploading photo's I need a little more information to debug? Do they get any errors?, what type of internet connection do they have (a slow connection may timeout and cause the upload to fail), and browser information. I also looked at you image rotation issue. It looks like the photo you uploaded contains its orientation in the metadata so the browser is still flipping it automatically for you: online metadata and exif viewer. Maybe try editing the photo with a different photo editor or strip out the metadata. You can test an image using this tool: online metadata and exif viewer
... View more
02-07-2017
11:56 AM
|
2
|
0
|
1145
|
|
POST
|
The Story Map Crowdsource supports Internet Explorer 11+, Chrome, Firefox, Safari as well as Most versions of iOS and Android browsers. We have not heard too many users complain about upload issues; can you provide more information if you have the opportunity: Can you share a public link to your story? What browser/OS are your participants using? Did you make any changes outside the Crowdsource Story builder?
... View more
02-07-2017
10:55 AM
|
2
|
0
|
1145
|
|
POST
|
As the error states, the smallest size of your photo must be at least 700 pixels. The app is rejecting if because the smallest side is 679 pixels. This is to make sure viewers do not see grainy when the view the photos.
... View more
02-03-2017
09:27 AM
|
1
|
0
|
1092
|
|
POST
|
Hi Pete, we do not have a time frame when the form editor will come out but it will be the second half of this year at the earliest. If you have an immediate need for custom fields, you can download and customize the app: https://developerscorner.storymaps.arcgis.com/custom-forms-in-the-story-map-crowdsource-beta-79af2014c8da#.q5ad3hiso. If you do not have a developer, I would recommend looking at our Crowdsource Reporter app: Crowdsource Reporter | ArcGIS for Local Government.
... View more
01-31-2017
06:27 AM
|
0
|
1
|
1501
|
|
POST
|
Hi Laura, the "build" folder is just a folder that hold temporary files used in development and does not contain the source code. In order to build your app, you can run "grunt test" which will build your app then run a simple test server so you can test your app before uploading it to your server. If everything appears normal, upload the contents of the "dist" (distributable) folder to your web server.
... View more
01-30-2017
05:58 AM
|
0
|
0
|
762
|
|
POST
|
Hi Jennifer, we have not not seen this issue before. Can you tell us a little more about your situation? Do you ever see the a beta message and have a place to enter your story title? Or do you only see a grey background with a blue loading indicator (no text under the loading indicator)? How did you start building the crowdsource story? Did you try to share a webmap to the template? Did you create a new app from arcgis online? Or did you start from the story maps website? Are you in an organization in ArcGIS Online? What permission level are you? What operation system and browser are you using? Also, if you're willing can you send your browser console log (just upload it as an attachment). Below are instructions for Chrome: Save Console Log Open this URL: https://arcgis.com/apps/StoryMapCrowdsource/index.html?fromScratch&debug Wait until the app stops responding (If nothing happens within a couple mins but the loader still shows, the app has stopped responding). Open the JavaScript Console: View => Developer => JavaScript Console Find an empty space in the console window, right click and the click "Save As." Then upload this file as an attachment to your response.
... View more
01-27-2017
05:39 AM
|
0
|
0
|
831
|
|
POST
|
Can you share the URL to the photo you used? And a public URL to your story?
... View more
01-25-2017
09:06 AM
|
0
|
1
|
615
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 01-10-2018 05:56 AM | |
| 1 | 02-03-2016 11:13 AM | |
| 1 | 03-17-2017 07:22 AM | |
| 1 | 08-25-2017 06:35 AM | |
| 1 | 10-25-2016 05:09 AM |
| Online Status |
Offline
|
| Date Last Visited |
04-08-2026
08:01 AM
|