nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Not zoomig to geocoded address first time

ADITYAKUMAR1

HI,

I am using geocode services to geocode and zoom to the address. When I use world geocoding it works fine but when I use my custom geocoding it geocodes well but doesnt zoom to the first time. from second geocode it works as expected. I get the below error fist time.

I am not sure if its a problem with custom geocode or any other issue is there. Has anyone faced similar issue?

Thanks
Aditya Kumar

Find more posts tagged with

Accepted answers

ADITYAKUMAR1

@JoelBennett I managed to resolve it from the server side. Earlier i was using the data from the sql server but now i created a geodatabase. Imported the layer inside it. Created a locator and assigned Auto into the performance tab under properties section. Published it and its working as expected.

Thanks

All comments

JoelBennett

This error indicates the client-side projection engine is being used before it's fully loaded. Unlike other modules which you can immediately use after bringing them in via require, define, or declare, the projection engine must be explicitly loaded as well. Loading this module is asynchronous, so is not immediately available upon calling load. You must wait until the promise returned by the load function resolves before it can be used.

At a minimum, you would need something like this:

require(["esri/geometry/projection"], function(projectionEngine) {
	projectionEngine.load().then(function() {
		//do geocoding logic
	});
});

However, it would probably be better to move the importing and loading of this module into your application startup code.

ADITYAKUMAR1

@JoelBennett Thnaks for the response. But I am confused why this happens only with custom geocoding services and not with World geocoding services. And the projection Engine has problem just at the first search.

JoelBennett

Without knowing the details of the workflow, it's impossible for me to say. What is plainly evident, though, is that your custom workflow is using the client-side projection engine, whether explicitly or behind the scenes. Perhaps it is because the service is returning results in a different coordinate system than the map, thus making projection necessary.

Whatever the case, it has a problem with the first search because it hasn't loaded yet. It seems to be that by the time the second search is attempted, the projection module has fully loaded, and therefore works after that. The solution is for you to load it yourself prior to any searching taking place. Perhaps the best way to do that would be to load it before instantiating your Map control, when your application is starting up:

require(["esri/map", "esri/geometry/projection", "other/modules"], function(Map, projectionEngine, otherModules) {
	projectionEngine.load().then(function() {
		var map = new Map({
			//etc
		});
	});
});

ADITYAKUMAR1

Thanks

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.