Latest Contributions by RobertJensen

Hi Kyle, We don’t have out-of-the-box data preparation functionality at this time for adding cross street data into locators, but we can add this to our backlog for a future release. In Pro 3.3, the ability to search for streets between other streets was added. Intersections can be built into a street address role with the name of the intersection in the address field, for example “Main St & Center Ave”, but the determination of the intersection at each end of a road segment requires pre-processing today. Please consider these options. ... View more

Hello Mike, The standard SMP product does not allow you to edit the network dataset. If you are interested in this particular workflow of adding your own privately managed roads to the network, you are correct that the StreetMap Premium Custom Roads product was created for this exact purpose. There is a different licence for Custom Roads. Please contact your account manager for more information.   However, if you just want Esri, or our data provider, to add in a newer road, you can send us the location and we can check to see if it has been added to the latest StreetMapPremium dataset release (that is soon on its way to you) or if we need to tell the data provider to add it for a future release. ... View more

Hi Brian, Choosing "Address Location" as the Preferred Location Type is just that, a preference. In those cases where a rooftop location does not exist, the World Geocoding service will fall back to the next best available match level. At the same time, the preference does not act as a filter to exclude all matches that are not rooftop. One option for you is to move into the Category parameter and expand the Address checkbox and then click "Point Address" as the sole selection. This will limit the type of responses you will get for your requests. Another option is setting up a locator view for your Org in ArcGIS Online. In the view, you would select the geocoding constraints that work best for you. Your observation that NYC should have better building and parcel locations is spot on, and is a continuous conversation that Esri has with its data providers. ... View more

Hi Michael, There is a mention of this in the "What's New" blog. What’s new in ArcGIS Online (October 2019)  ... View more

Hi Michael, Yes, this information will included in the "What's New" in the October update of AGOL. ... View more

Hi Michael, BF-USA is collecting rooftop locations themselves in order to feed into the World Geocoding service. Currently the default location used by the World Geocoding service is "street" because of requirements for directions and navigation. This necessitates a geocoding user to specify "locationType=rooftop" in their requests today. The Geocoding recognizes that users have an expectation of getting the rooftop location by default, so in the near future, the Online system will make the switch, but this will require additional changes that permits users with directions and navigation needs to continue to be successful. ... View more

The first release of the World Geocoding Service that includes content from BFUSA will come later this year. At this time, the data will only be used in the World Geocoding Service. ... View more

Hello Michael, Matching to a rooftop location does require the underlying data for an address to be positioned at the rooftop. When Esri looks for the best available data, the inclusion of rooftop specific locations is a must have, but not all addresses in a dataset will have a rooftop location. Some have curbside, driveway, front door, or parcel centroid locations instead... and that balance produces a mixture of potential results for geocoding. To your point, when a rooftop location isn't available the system will fall back to the next best available location for that address. To improve the system overall, Esri has partnered with companies like BuildingFootprintUSA to obtain more addresses with a rooftop location. The capability for rooftop locations has always existed whenever and wherever the data supported it. Thanks, Robert ... View more

Hi Jose, Since you've posted this question in the SDE section, I presume that you're working with versioned data. If not, please reply to that effect as the resolution to your question will be different. So, the simplest, well... only, way to deploy a representation in a feature class across a versioned environment is to create the representation class in a version. Once the representation class has been added, it will automatically persist to all other versions. Although a representation class can be added to any version, it is a best practice to add them to the default version. Rob esri-redlands ... View more

Hi Ted, At this time, sql server 2008 r2 is in 'community tech preview' as you're probably aware. As such, the 9.4 release is not certified with this version. Once the 9.4 release is certified against the R2 version, this issue will be revisited. ... View more