Latest Contributions by WalidAlmasri1

Thanks!  This definitely helps, but I am trying to add the date range of the data in the title of the dashboard.  Is that even possible? ... View more

Yes, I did have specific categories selected, mainly removing StreetName as that is problematic.  Including StreetMidBlock as a category would definitely be my recommendation.  You also lose the ability to search by 'StreetMidBlock' when you disable categories in the coordinates too. I hope to see this added in the very near future. Thanks! ... View more

@ShanaBritt That is correct, but I just figured out why.  Under Locator Properties > Geocoding Options, once alter the Categories to support from "All categories supported by the Locator" to "Only categories selected here", the ability to search with any of the block formats above is unsupported. ... View more

@ShanaBritt is there a particular way the data needs to be in order to return the "Addr_type" output field to equal "StreetMidBlock"? I've actually removed our "Block of" information from the address and now only do the full hundred block address and am having good results, but in areas where ranges are limited, mapping to StreetMidBlock would be helpful as some get missed, but I'm not sure how to return that result from the geocoder.  Everything I return is LatLon, StreetAddress or StreetAddressExt no matter how I type using the examples ESRI provides. 100 block of New York St, Redlands, CA 1600 blk E Cliff Dr, El Paso 200-500 block Taylor St, San Francisco 1700-1900 blk of Locust St, Philadelphia, Pennsylvania Thanks!! ... View more

Hi @ShelbyZelonisRoberson, exactly correct.  Build a geocoder using only centerlines with Street Address Role.  You need to have address ranges in the centerline though in order for this to work. On the backend, the data is converted into a new table.  So addresses like 1264 N Main St, are converted to 1300 Block of N Main St and if the address is 1231 N Main St, we convert it to 1200 Block of N Main St. You don't need to have 'block of' text in your address, but the geocoder will understand it if it's there.  Then run those new addresses through the geocoder to get the new location.  I'm not certain how having block information in the centerline would affect geocoding accuracy since we don't have that, but let's assume the street had an address range of 1000-3000, addresses that get converted to 1000 Block are placed on the beginning point of the line, addresses that are 2000 block would be placed on the center of the line, and addresses on the 3000 block will be placed on the other end of the line. The only downside I'm seeing here is if you have multiple addresses on one street that get converted with the same block information, they will stack.  One way around that would be to geocode the actual address but only display the 'block of' address, but then that could potentially place the address close to where you are trying to mask.  Or limit the data by date range. I hope this helps, let me know if you have any questions. ... View more

Still hoping someone has an answer for this? ... View more

I'd like to add here that experience builder has this correct. ... View more

@ShanaBritt THANK YOU, this is exactly the information I was looking for.  Why I was unable to find this answer is beyond me.  I guess it makes sense now because that's how you have to type it in the Locate box in Pro... It is now matching my coordinates 🙂   ... View more

@ShanaBritt Correct, I do have the addresses as "700 Block E Olive Ave" for example.  Those will geocode to the centerline, but if there is no address (null) the locator does not resort to plotting the lat/lon of the data: See below: I can create an event layer just fine with this test layer. Also, my geocoding settings:   ... View more

Hello @ShanaBritt  Making an event layer works out fine, but that's not what I am trying to do.  We have many records that map an exact location and I am trying to geocode masked addresses (to hundred block - EX: 2352 = 2300) back to the street centerline.  Most of the locations do geocode back to the centerline, but many that do not have an address, but have Lat/Lon, to do not get processed by the geocoder even with coordinate category selected.  I have investigated other methods like reverse geocoding the layer, which yields better results (sort of), but also causes issues when the reverse geocode goes to the wrong street since it was closer than where the address specifies. I'm really trying to find how precise data is anonymized and I'm not having very good luck it seems. ... View more

@TonghuiMing here is some information regarding the data.  The data originates in UTC in separate tables.  The data is then converted to PST on the back end to another table that allows me to bring it into ArcGIS Pro for mapping.  I then enable time on the layer, publish with the time settings below to Enterprise 10.9.1 This layer is published to a dashboard and several other Web Appbuilder applications. When I query the data in SQL, I return 48 records (FieldName between '2022-10-31 00:00:00' and '2022-11-02 23:59:59') When I use the Date Range Selector in our Dashboard, where the between date is between 11/1/2022 and 11/1/2022, I return  48 records. When I open our Web App built within Enterprise 10.9.1 and use the filter widget it selects only data between 11/1 and 11/1 beginning at what appears to be 8:00am, so everything from 12:00am to 8:00am is missing.  It then proceeds to select data from 11/2 up to 6:32am (next record is at 7:38am and is not included.  Returns 51 records. WAB 2.26 I create an empty web app using just the Web Map (for dashboard) for the Application and this time it also returns 51 records, but this time the dates are from 10/31 beginning at 11:09pm (next previous record is 11:14pm and is not included) to 11/1 up to 10:00pm with the next record not included at 11:40pm. But, just to recap.  SSMS gives me the correct number of records, the dashboard gives me the correct number of records, WAB 2.26 and our Portal give a different result.   ... View more

@AlixVezina no problem.  If you find out where I can manually edit it too that would help in the mean time while the fix gets implemented (If it is possible). Thanks! ... View more

@AlixVezina it appears the change that was made flipped the data being selected.  Before when I searched for something that occurred between the dates of 11/1/2022 and 11/1/2022 it would pick several some from 11/2/2022, now with WAB 2.26 it selects the same number of records but includes records from 10/31/2022. instead of 11/2/2022. ... View more