Research / Test - Spatial Views for Parking Zones

[atdservicebot]

With the new schema for the parking zones where the parking restrictions will be located on a table, we need to figure out how the different parking zones will be displayed for the web map.

Migrated from atd-geospatial #321

[atdservicebot]

From jaime-mckeown on 2019-10-08:

5/10/2019

• I did some research for how to symbolize a layer based on related tables. The only way to use any fields in the table is that a join must be created, and because many relationships exist the join must be exported in order to see all of the records.
• If we went this route, the only way to symbolize all zone types would be to use cartographic representations since the exported records from the join would be coincident. This will cause a problem with symbology in AGOL as cartographic representations don't really work. I read about a work-around, but it was cumbersome.
• So, I feel like I'm back to square one here. If all the data needs to continue to be symbolized the same way, I can move all the parking_restriction table fields into the parking_zone layer. The overall new schema removes the problem with duplicate fields across multiple layers. We can keep the relationships between parking_zones and parking_spaces / parking_paystation_meters for connectivity and ease of editing.
• Another positive with this approach is that less editing will be required to move the data into the new schema as the parking_zones would stay separate.
• If parking_zones move back to multiple lines, we can leave one set of parking spaces, then add a many-to-many relationship between parking_zones and parking spaces so each space would relate to both parking zones.
• Parking meter and paystation points would only be related to the parking zone related to paid parking.
• If a many-to-many relationship exists between parking_zones and parking_spaces / parking_paystation_meters, the PARKING_ZONE_ID field would not need to be on the parking_space and parking_paystation_meters layers as the relationships are created through selections.

[atdservicebot]

From jaime-mckeown on 2019-10-08:

Comment from John on 5/14/2019

• thanks @jaime-mckeown. i wonder to what extent joins (or more specifically, spatial views) might suit our symbology needs. the main symbology challenge is displaying the zones with attributes from the parking_restrictions table, right? in which case perhaps we could layer multiple spatial views of the restrictions + zones with different symbologies ( e.g. one view/layer for each restriction type).
• what other symbology challenges (besides zones + restrictions) do you see here?

Comment back to John

• It's more then just a join to symbolize. You have to export the join to the same GDB in order to see all of the data since there is a one-to-many join. Additionally, we will have multiple zones on top of each other so that's another problem with symbology.

Comment from John

• OK. Looking forward to more discussion when we meet on Friday. In the meantime, take a quick look (if you haven't already) on the spatial views docs, because I'm under the impression that if you do this on SDE you don't need to export.

http://desktop.arcgis.com/en/arcmap/10.3/manage-data/using-sql-with-gdbs/example-creating-a-spatial-view-in-oracle-with-sql.htm

[atdservicebot]

From jaime-mckeown on 2019-10-08:

5/15/2019 Spent some time today trying to figure out how to create a spatial view for the parking_restrictions table info related to the parking_zones. Successfully created a spatial view, then moved on to being able to publish the view to a feature service in AGOL to be used in a Web Map. Finally making progress, will be ready to discuss with John on Friday.

[atdservicebot]

From jaime-mckeown on 2019-10-08:

5/22/2019 Finally got back to the parking project today and created more sample data. Re-published the 2 spatial views for parking zones to AGOL. Started working on publishing paystations_meters to AGOL, but finding that the symbology won't draw without the related data.

[atdservicebot]

From jaime-mckeown on 2019-10-08:

5/23/2019

• Been working on trying to get the parking data into AGOL with the relationship classes.