Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
Mike,


 


I passed your questions/comments
on to Accela Engineering and received an initial response.


 


Our Standard XAPO for Accela GIS
will not be able to handle cases where an address point doesn’t intersect the
associated parcel geometry. For the additional logic needed to be able to
evaluate data and find/select parcels or address points that do not overlay
each other, a custom XAPO adapter would need to be developed.


 


If we end up going down that
road, additional analysis would be required and GIS data examples would need to
be provided so that an estimate could be done for the custom XAPO adapter.


 


If using our standard XAPO
adapter for AGIS, the end user would be presented with a list of address points
and or parcels and owners that intersect the selected object and the user would
have to select what other components of APO they want to pass back to Accela
Automation.


 


What Accela Automation stores
for GIS objects is normally the Parcel’s GIS unique ID and then the information
for Parcels, Addresses and Owners is stored as transactional data to the new
record. However, any GIS feature ID can be associated to an Accela Record, it
just is normally the Parcel ID.


 


Paul H. Rose


Senior Consultant

Paul McCullough
Code Block
Mike, 
I have requested a meeting with Hema...
Can we use a multipoint geometry?
Mike
Code Block
Yes, we can use
multipoint.  I would have thought either multipoint or multipolygon were
definitely the way to go.  Realistically, Planning’s needs for addressing
are much simpler than DBI’s so either would work for us in Planning.  The
planners work almost exclusively with parcel numbers rather than
addresses.  Everything else being equal I would always prefer multipolygon
but I know Alton prefers multipoint.  I think we should go with whichever
works best for DBI.


 


Thanks, mike