You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In instances where there a few incidents that are spread throughout the county, it seems like the ArcGIS API will sometimes only return some of them with the current geospatial coordinates supplied.
Example:
Incident Number 2312004685
Priority 1
Incident Municipality SALISBURY TOWNSHIP
Origination 12/5/2023 2:34 AM
Primary Agency WHITE HORSE EMS
Current Units AMB491
Public Location BUCHLAND RD / PEQUEA CREEK
Public Type MEDICAL EMERGENC
Incident Number 2312004689
Priority 3
Incident Municipality LANCASTER CITY
Origination 12/5/2023 2:37 AM
Primary Agency LANCASTER EMS (LEMSA)
Current Units AMB067
Public Location E LEMON ST / N DUKE ST
Public Type MEDICAL EMERGENCY
With these 2 being the only incidents, only the first one appears to be fetched. Playing with the live map seems to show the same issue, so I don't think messing with the geospatial coordinates itself will alleviate the issue. Perhaps splitting up the county into quadrants would be effective.
The text was updated successfully, but these errors were encountered:
In instances where there a few incidents that are spread throughout the county, it seems like the ArcGIS API will sometimes only return some of them with the current geospatial coordinates supplied.
Example:
With these 2 being the only incidents, only the first one appears to be fetched. Playing with the live map seems to show the same issue, so I don't think messing with the geospatial coordinates itself will alleviate the issue. Perhaps splitting up the county into quadrants would be effective.
The text was updated successfully, but these errors were encountered: