Support Address or XY table to Feature Service/Feature Class workflow
Open
backlog
enhancement
- Dominant language
- C#
- Stars
- 25
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
UI Considerations:
- Selecting geocoding service/settings (if address table)
- Selecting input coordinate system (if XY Table)
How do we handle the following?:
- Unsuccessful geocodes (bad address information)
- Unsuccessful XY placement (bad XY data)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.