Quick answer
Resolving a supported site input into candidate latitude/longitude coordinates, with property, source, convention and datum verification before downstream solar-model use.
Answer: Latitude/longitude auto-detection resolves a site input into geographic coordinates, often through address geocoding, a map selection or a supported location source. The returned point is a candidate location, not a survey or an accuracy guarantee. Solar teams should verify the intended building or parcel, coordinate convention and source before using the location for weather selection, sun-position calculations or geometry alignment.
Different inputs produce different location evidence
An address lookup matches an address database. A map pin records the selected map position. A device location depends on the device and its conditions. A parcel lookup requires a supported parcel dataset; an ordinary address geocoder does not automatically resolve every parcel identifier.
Google’s Geocoding API documentation distinguishes location types including rooftop, range-interpolated, geometric-center and approximate results. Its rooftop category refers to address-level location information, not measured roof dimensions or a guarantee that the point is on the required roof face. Ambiguous requests can produce multiple results; review the matched address and location type.
These are examples of one vendor’s documented response semantics, not proof that SurgePV uses that service or exposes those fields. Confirm the actual application’s supported inputs and provider before promising automation.
Verify the point before accepting it
Compare the returned address/point with the customer’s intended property and current available imagery. Identify the correct building on a multi-building site and distinguish an entrance, parcel center and proposed array location. New construction or outdated imagery may require another permitted source or site confirmation.
A hypothetical review finds a pin at the address entrance while the intended array is on a rear outbuilding. Record the selected building/location and its source, then review which downstream inputs depend on that change. Moving the pin does not itself measure roof tilt or update an obstruction model correctly.
For rural or off-grid sites, use supported coordinates or survey/GIS evidence where an address match is inadequate. A visual map pin is not proof of a legal boundary, setback or construction staking position.
Preserve coordinate meaning, not just digits
| Record | Why it matters |
|---|---|
| Latitude/longitude fields and units | Avoid swapped axes or mixing degrees with projected distance units |
| Hemisphere/sign convention | Preserve north/south and east/west meaning |
| Coordinate reference system/datum | Identify the spatial reference and any transformation |
| Source and timestamp | Track geocoder, map selection, device or survey evidence |
| Matched property/building | Confirm the intended site rather than only a postal match |
| Verification/uncertainty | State what has actually been checked and what remains provisional |
For hypothetical sign-convention examples, 10° south is latitude −10° and 20° west is longitude −20° in the common signed-degree convention. These numbers illustrate notation only; they do not identify a verified project or define every API’s axis order.
More decimal places improve numerical resolution, not necessarily positional accuracy. Do not relabel six-decimal output as sub-meter survey evidence. USGS’s datum glossary distinguishes horizontal position references from vertical elevation references. When importing another dataset, document both as applicable instead of assuming coordinates with similar numbers are already aligned.
Use the location with appropriate downstream checks
GIS site analysis and weather selection need the actual source, spatial coverage, resolution and method. Latitude alone does not determine climate or annual irradiance. Sun-position work also needs time/date and the supported time-zone convention; longitude alone does not establish clock-time solar noon.
Confirm the selected weather dataset and its suitability instead of automatically taking the nearest station. A coordinate does not independently prove utility service territory, tariff eligibility or a site’s electrical supply arrangement. Likewise, geolocation and LiDAR data integration are separate steps: a point does not provide roof geometry.
Handover and permitted use
Designers should keep a location record with their accepted model inputs. Site teams should report building, obstruction or imagery discrepancies. Sales teams should show a verified property view with its limitations, not claim a fixed percentage improvement in forecast accuracy.
Use geocoding, imagery and parcel/survey sources under their applicable permissions and terms, including restrictions on storage or redistribution. Verify the actual product workflow before asserting native address-to-weather, parcel lookup or LiDAR automation.
Frequently asked questions
Does a rooftop geocode measure the roof?
No. It is location evidence under the provider’s semantics; roof geometry requires separate data and validation.
Are six decimal places a guarantee of accuracy?
No. Numerical resolution cannot remove source, matching or georeferencing error.
Can a map pin establish a property boundary?
No. Use the appropriate authoritative boundary/survey evidence and qualified review for the required purpose.
Does the detected point select the correct tariff automatically?
Not necessarily. Verify service territory, customer eligibility and the actual tariff separately.
Related Glossary Terms
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
