Latest Contributions by AlanRex1

I just wanted to add a quick amendment to the comment above, relevant to more than just this specific issue: even if an issue is reported on https://status.arcgis.com feel free to create a support case or post to GeoNet.  If it’s on the Status page that means we’re aware of the issue and working on it, but it’s always helpful to hear from you if there is an issue impacting your work. ... View more

Hi Matt, Sorry to hear that!  Do you have a support ticket open?  I think that would probably be the easiest way to troubleshoot this issue.  In all of our other tech support cases, users were reporting the same error ("Error performing submit job operation for Export Tiles on Export Cache") and several of them have since confirmed the issue is resolved for them.  Frank was actually the only report I've seen of the "timeout" error.   I've just checked on my own device and I can download, so I think we might need to get an analyst involved to help isolate what's different from our environments. ... View more

Thanks again Frank! I can confirm that the operations team has resolved the current issue and have recently updated the Health Dashboard.  They are still investigating the initial cause of the problem but customers should no longer experience any latency.   ... View more

Thank you Frank (and the previous reporters). We have reproduced this issue and it has been reported on the ArcGIS Online Health Dashboard (ArcGIS Online Health Dashboard).  Our operations team is working on resolving the issue.   ... View more

Hi Doug, If you have maintenance I would suggest logging a Tech Support case for this issue.  If you're not on any maintenance right now feel free to PM with your contact info and I can try to get a case going for you. -Alan ... View more

Hi Casey, I was not able to reproduce this issue.  My guess is that this might be related to browser or network specific issues?  Do you see any request failures in your browser's Dev Tools Network tab?  If you're still having problems I'd suggest logging a Tech Support case.  If you don't maintenance with us, you can PM me your contact information and I'll see if I can get a case set up for you. Regards, Alan ... View more

Hi Andy, I was able to reproduce the issue.  I contacted our basemaps team and the issue is now resolved (at least from my testing).  Please let us know if you see any further issues, and thank you for bringing this to our attention! ... View more

Hi Christine, Let's get a tech support case started.  I'll PM you. ... View more

Hi Rosemary, If you are still able to reproduce the issue feel free to place a call in to Tech Support to get a case logged.  From your email it looks like you're associated with a university and most universities should have access to support.  If not, feel free to PM me your contact info and I'll see if I can get a case set up for you.   Thanks! ... View more

Hi Brittany, No problem, I just sent you a message.  Please reply to that or let me know if you had any trouble getting it. ... View more

Hi Jessica, If you are still encountering this issue I would suggest logging a Tech Support case with us so we can investigate in more detail.  If you don't currently have maintenance with Esri, feel free to PM and I'll try to get a case set up for you. Regards, Alan ... View more

Hi Brittany, I'm sorry to hear about the troubles you're encountering!  Regarding the problem of your tabs losing all of their points, I think it would be best if you could create a Tech Support case on this issue.  If you don't have maintenance with us at the moment, please feel free to PM your contact info and I'll see if I can get a case set up for you.   Regards, Alan ... View more

Hi Priscilla, If you are still encountering this issue I would suggest logging a Tech Support case.  If there's a bug here we'd want to get that logged.  If you don't have a maintenance contract with us please feel free to PM your contact info and I'll try to get a case set up for you. Regards, Alan ... View more

Hi M S,   I just spoke with the US support analyst who was working with the Canadian support analyst you were working with.  You should be getting this information via your case but I wanted to respond here for other users who may view this thread.   The bug that you were attached to is not actually relevant to your particular use case.  That bug is specific to geocoding ONLY the postal codes in Canada (not a full street address), and then only when zoomed in beyond a specific extent.      First a quick note about Canadian Addresses.  Like US addresses, they are technically split into two sections.  In the US we call the two parts Zip+4 (12345+6789).  In Canada they're called Forward Sortation Area (first three digits, A1A) + Local Delivery Unit (second three digits, 1A1).  In the Esri datasets, we have two fields; one called Postal (which for the US is the 5 digit zip code and for Canada is the FSA) and one called PostalExt (which for the US is the zip+4 and for Canada is FSA+LDU).   Regarding BUG-000086454, when a user is zoomed into certain extent in the Map Viewer the request that's sent to the World Geocoding Service includes location and distance parameters, so if there are two similar addresses returned by your request the Map Viewer will zoom to the one that's closer to where you're currently looking in your map.  If you geocoded M3C 3R8, you might be closer to the centroid of M3C than you are to the centroid of M3C 3R8, and therefore the Map Viewer will return M3C instead of the "full" postal code.  That's the very basic underlying issue behind BUG-000086454 but that's not what you're running into.   You're geocoding an entire street address ("1000 Bay St, Toronto, Ontario, CAN").  When you're geocoding to the street or house level you'll be getting responses from our point address or street address locators (not the postal or postal+ext locators like the workflow from BUG-000086454).  By default, these locators will return only the Postal field I mentioned above, not the PostalExt field.    Since the Postal field only includes the first 3 characters of the full Canadian postal code, this means what you're seeing is expected behavior.  However, from a practical standpoint it's definitely more common to use the full 6 character Canadian postal code than the 9 digit US zip code, so I can definitely see room for improvement here.  Therefore, I've asked the analysts you've been working with to log an enhancement request to deal with this specific Canadian use case.  They should be providing you with the ENH code when it's been fully written up.   I hope this helps clarify the behavior you're seeing.  Thank you for calling attention to this issue! ... View more