Import Features to VAHydro

[jdkleiner]

dh features must be created prior to attaching discharge timeseries data.

• Features to be imported:
  1. Facilities
     • Import all for now, understanding some facilities will already exist in VAHydro - duplicates can be resolved at a later date
  2. Release Points
  3. Outfalls
  4. Conveyances

The above imports will be performed using feeds by Connor+Morgan on d.bet first (with Joey's assistance)

• Views creation:
  • Views queries need to be developed to ensure successful import of the above features
  • This will also serve to build a foundation of knowledge for Connor+Morgan on creating views queries, which we'll ultimately need to implement for generating SWUDS-compatible data exports

• We need to make sure Morgan has a GitHub account
• Joey needs to create user account for Morgan on d.bet

[jdkleiner]

dH Feature Mapping:

• Facilities

bundle	name	ftype	hydrocode	fstatus	wkt_geom
facility	MIRANT POTOMAC RIVER L.L.C.	wwtp	echo_DC0022004	active	POINT (38.81953 -77.04167)

• Release Points

bundle	name	ftype	hydrocode	fstatus	wkt_geom	dh_link_facility_mps
transfer	TO DC0022004001	release	vahydro_DC0022004001	active	POINT (38.81953 -77.04167)	echo_DC0022004

• Outfalls (ftypes: outfall, outfall_ms4, outfall_internal, outfall_stormwater)

bundle	name	ftype	hydrocode	fstatus	wkt_geom	dh_link_facility_mps
transfer	FROM DC0022004	outfall	echo_DC0022004001	active	POINT (38.81953 -77.04167)	echo_DC0022004

• Conveyances

bundle	name	ftype	hydrocode	fstatus	field_dh_from_entity	field_dh_to_entity
conveyance	DC0022004 TO DC0022004001	water_transfer	vahydro_DC0022004_DC0022004001	active	vahydro_DC0022004001	echo_DC0022004001

• Conveyance geom field populated in vahydro automatically from release and outfall geoms

[jdkleiner]

See below for the Facility ftype naming conventions we use in VAHydro.

ftype
agriculture
commercial
fossilpower
hydropower
industrial
irrigation
manufacturing
mining
municipal
nuclearpower
public water supply
unknown
wwtp

Let me know if you come across any facilities that don't match one of these categories, and we can add them

[connorb5]

Do release points get the same geometry as the facility or as the outfall?

[rburghol]

Yup — unless we know otherwise we assume that the release is at the facility so if we know facility coords we choose that, if not we choose outfall.

On Wed, Feb 28, 2018 at 1:54 PM connorb5 ***@***.***> wrote: Do release points get the same geometry as the facility or as the outfall? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEXAIhd0qNCoK0bRAT-JmzPmOYiui6Tjks5tZaDEgaJpZM4R81vx> .

-- -- Robert W. Burgholzer 'Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity.' - Charles Mingus Athletics: http://athleticalgorithm.wordpress.com/ Science: http://robertwb.wordpress.com/ Wine: http://reesvineyard.wordpress.com/

[connorb5]

Last question: What happens if I don't have coordinates for a particular facility? Should I leave it blank or as NA? Right now, about 20/900 active facilities don't have associated geometries and are set by default to output geometry as POINT (NA NA). ECHO is reworking their spatial data it seems as this has only recently appeared in the database. I'm doing the same for outfalls that don't have geometries. I can set them to the lat/long of the facility if that's preferable.

[rburghol]

Hmmm. Do they have outfall geometries? If so, I’d use those, otherwise the wkt field must be null, abd then we need to flag those for review.

On Thu, Mar 1, 2018 at 1:21 PM connorb5 ***@***.***> wrote: Last question: What happens if I don't have coordinates for a particular facility? Should I leave it blank or as NA? Right now, about 20/900 active facilities don't have associated geometries and are set by default to output geometry as POINT (NA NA). ECHO is reworking their spatial data it seems as this has only recently appeared in the database — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEXAInTm0bBjSoIQzdDWDWZvq0oUdev5ks5taDwegaJpZM4R81vx> .

-- -- Robert W. Burgholzer 'Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity.' - Charles Mingus Athletics: http://athleticalgorithm.wordpress.com/ Science: http://robertwb.wordpress.com/ Wine: http://reesvineyard.wordpress.com/

[connorb5]

The majority of facilities without geometry have outfall geometries, but 3 do not. I will list these as null so we can review them at a later date. Its possible ECHO will update again in the future and restore lat/long data so this may only be a short term issue

[rburghol]

Cool - good deal.

…

On Thu, Mar 1, 2018 at 2:03 PM, connorb5 ***@***.***> wrote: The majority of facilities without geometry have outfall geometries, but 3 do not. I will list these as null so we can review them at a later date. Its possible ECHO will update again in the future and restore lat/long data so this may only be a short term issue — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEXAIlcp4ip4-V36ik6YfJZCi0k5NmVhks5taEYXgaJpZM4R81vx> .

-- -- Robert W. Burgholzer 'Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity.' - Charles Mingus Athletics: http://athleticalgorithm.wordpress.com/ Science: http://robertwb.wordpress.com/ Wine: http://reesvineyard.wordpress.com/

[connorb5]

New sample imports are up under documentation -> imports. These should match the requested formatting, but let me know if there are any withstanding issues with them.

[jdkleiner]

Connor - everything looks spot on except for the releasepoint hydrocodes. These should use the full outfall code, so vahydro_VA0000248 should be vahydro_VA0000248004 and so on. This fix will also need to go into the conveyance file in the from_node column.

We should try to meet soon with you and Morgan so I can start walking you guys through the import process.